giancarlo wrote:it's simple: you convert only programs smaller than x. X is your bar. You could raise the bar and convert ALL programs. It's possible an old computer will take ages for converting a program so you disable conversion lowering the bar.
But if you DO adopt a lower value, you run the risk (particularly with an older/slower computer) with some programs (long reverbs, delays and suchlike) that you'll end up with the conversion disabled (the flashing symbol next to the sample rate readout) and it won't sound as it should.
Surely taking RATE CNV up to maximum and adding a progress bar of some sort during loading/conversion would make more sense, so:
a) you can see when conversion is still happening rather than thinking Nebula has crashed
But is up to you. I prefer to have a big value, convert everything and wait, I'm young guy a have a lot of time. This parameter has nothing to do with Nebula performance or Nebula sound but obviously emulation presets that are not converted will sound rare or quirky.
Enrique Silveti. Acustica Audio customer and technical support.
OK. Question answered. Strange parameter. I would just get rid of it (i.e., set it to maximum and remove it from the GUI) or implement something like what Martin suggested.
The user either wants to load a patch and know that when it's loaded, it's loaded properly, or they don't. If they are in such a hurry that they think a patch took too long to load, then they won't try to load that patch again.
But making it possible to load a patch, but incorrectly, with no warning but a gently flashing arrow, simply doesn't make any sense. It may be degrading the quality of patches for an unknown number of users who are unaware of the problem.
So for now: Best to leave RATE CNV at maximum (9000). To make things faster, I've raised loading thread priority (LOADER PR) to maximum (4); loading is speedy and I have no problems from CPU spikes. If you get problems from spikes then reduce LOADER PR to 3.
Last edited by biomuse on Wed Jun 08, 2011 7:54 pm, edited 1 time in total.
Exactly. A big value will always ensure good-sounding results, whereas having a much smaller default for RATE CNV could well mean that new users on a slower computer (unaware of the significance of the flashing symbol) may simply assume that Nebula sounds cr*p. See the problem enrique?
Surely the better default will be one that lasts the course and always sounds good, with the option for slow computer users of reducing the load time at the expense of audio quality
enriquesilveti wrote:Thank you for the inputs we will find a way to satisfy every customer with slow and fast computers.
Actually, I'll add one more suggestion to the pile:
I think everything would be more or less okay as it is if the warning (that you had not converted successfully) was more obtrusive. As it is, if you don't look at the PROG page, you're counting on your ears to make the determination. I'll grant that, in many cases, you're going to notice immediately because things sound wonky. But in the case where you don't (maybe where you instantiate a plugin and it converts successfully but on a subsequent reload it fails to convert properly and you are going straight into an offline render, as one possible example) that could leave you scratching your head wondering what went wrong with your render.
If Nebula was simply more insistent (I hesitate to suggest a popup, but something that would be pretty hard to miss) and didn't require my diligence to check up on the SRC for true peace of mind the default RATE_CNV setting might matter a bit less. There are lots of less obtrusive (than a popup) ways to handle it that would still make it easier to catch your attention.
I still tend to agree with Martin et. al that the disadvantages outweigh the advantages of the current default; but truly the real problem isn't the loading and unloading of programs, it's the possibility that you could process with incorrectly sampled programs.