For each instance of Nebula is initialized the all have to go through the same load process.
ie, checks if ROM memory is ok, SSE2 is supported etc..
Do these checks really need to be done for each instance upon initialization? I mean I can understand if the first instance of it needs to do some kind of initialization but why can't any instances from that point forth use the information ascertained in the first initialization?
not only the cpu load of nebula, but also the loading time must be improved!! it's almost the sound, that counts, thats why we all go with nebula. but workflow counts a bit as well!
i had another idea, how workflow could be improved: the program conversion. almost every programs are sampled @96khz and a lot of people (like me) work @ 44.1khz. now, every time you load a certain program it needs a few seconds to convert the program. this is something, which could be reduced to once! no? what about temporary converted-vectorfolder, or even bether a dialogue in nat: create(convertet) library @44.1 or whatever sr you want??
a further workflowimprovement would be a mode like this: you load a whole unit which is defined by the developper (eg. an eq made of 3-10 programs(low,mid,hi etc.)) now your ram and cpu usage is high, but you can adjust everything at once. after the adjustment, you press kind of freeze-button, and everything you didn't use of this unit would be unloaded from memory at this time.
what do you (especialy giancarlo) think of these ideas?
imo you should be able at adjustmenttime to switch fast between programs for comparison, otherwise nebula brings you an incredible sound, but you can't get the full benefit because you aren't able judge your adjustments right. you can only say that a certain program does improve the signal or not. but to find out which program would improve the signal the best, is very hard at the current situation. do i miss here something?
about rate conversion, there should be an utility in nat, but it was never debugged cause my lacking of time. And again, most requested features of ever, freeze and (not mentioned here but winner among requests) keyboard numeric input are NOT possible in current architecture without introducing (problably) a couple of hundreds of bugs