first of all thanks for your interest... below is the scheme of the patch.
nan as said is coming out from the vst~ object (plugged to Kontakt), i see it through number~ and it is printed as well on the max window.
thank you for all your replies...
@ Rodrigo: the number is for displaying reasons only. in this way I can see the "nan" and use some ways to trigger action accordingly.
"So the nan you're getting (I didn't see any in my system, but I didn't load a vst) is happening in the max world (and no the msp world)"
well, to me it looks like it is happening in the MSP (vst) world, the max objet i use as said is for displaying reasons only. I could have used snapshot as well, as you suggest...
"well, yes, you know already that it is coming from the plug-in, so you know there is nothing you can do.
as long as your IO device driver doesnt chrash from them, nans aren´t dangerous. :)"
you are right, but the DSP stops working at all! so i unless i manually send a 0 and a 1 DSP just stops working... no sounds...
@Andrzej thanks, i tried with that, but the problem is I want to eradicate the problem at the origin. Once i get nans they will never stop unless as said i close and reopen the dsp. By using bitsafe~ I only transform nans to 0s, to i lose the only thing i have to detect them and in case do some trick accordingly... ;-)
BTW, nan is such a new thing to me, and looks like i have to figure out why the hell they are coming from my VST.
Here are some thoughs...
A) I did not upgrade or modify anything in Kontakt. So it should not be a bug or something I guess. It has been working flawlessy for years
B) I have changed something in my max/msp world, so I guess this is responsible for that, in a way or another. This points to point...
...D) is it possible that some MIDI informations sent from Max to the VST are directly responsible for a nan output from the vst as well?
This i guess is the point I may need to look at... unless...
..E) by changing some instrument variable inside Kontakt itself (like gain, filters etc...) that sampler is completely responsible for the nan output. Even though i doubt that because I even tried to send super-distorted signals for hours from it, without getting any crash or nan in the VST...
So... a long story short, does anybody of you guys have any idea? ;-)
Thanks A LOT!
I have run into this issue with Omnisphere and also just found out about bitsafe~
My question is, how expensive an operation is bitsafe~?
I'm tempted to use it not only after VST~ objects, but also following adc~ objects and (for absolute safety) just before dac~ objects. I had a very unpleasant experience (extremely LOUD bang in a very powerful PA system) due to NANs a few weeks ago.
Actually they are very dangerous to your hearing ---- when Omnisphere produced (what I later discovered was) NAN values, the very powerful PA system to which my rig was connected produced an incredibly loud transient bang. Trust me, you don't want that happening more than once, ever!
nans aren´t dangerous. :)
Raja --- thanks for the info --- I have bitsafe~ objects all over the place now in my Max 5 system and I have seen no detrimental effects. This is totally defensive as I have never actually run into a problem with NAN on my Max 5 system but you never know.