Hi,
On reflection, it feels like this is the first time I have had to find and delete Isadora Preferences in over a decade. And on that older machine (running Isadora since 2011) there were quite a few versions of Isadora preference files (all now deleted) going back to pre Isadora 1.3 - I think. Anyway it is a testimony to how stable Isadora is as a program considering the amount of I/O and file passing work it does. Unfortunately, I have to reset my (hypothetical) crash counter between terminal crash incidents.
@mark said:
Isadora imports sound files into RAM.
That is very good to know, I assume that fact is outlined in the Isadora manual, but I suspect like most, I don’t always get to the manual before making moves when patching. Anyway experimentation is an effective way of learning - finding out the hard way what does not work, to really know what does.
Are you suggesting an implementation where the size of the audio file is detected by Isadora and its potential impact in the system is reported in a warning before it is allowed to be added to the media bin?
Cheers
Bonemap