why would vst~ interupt the scheduler?
Hi, well, I have done a quite extensive test regarding graphical abnormalities and scheduler interuption regarding the vst~ object in max when updating parameters via the vst’s supplied interface or by merely just loading the plugin. The test was done by sending random midievents into the object while playing around with the interface. I found that about half of the plugins I tried actually stopped the scheduler entirely when twiddling knobs, which makes you know, using the vst~ object with a max interface in a realtime situation useless unless you know which plugins don’t apply.
I am wondering what the vst’s that are causing problems could be doing to cause this issue. I know that they must rely on like quicktime or directdraw or whatever to update the interface, and that’s probably the case. The thing is, plugins that cause scheduler interuptions in max will load in a program like Cubase without much of the same problem. I do notice the same thing happening though, certain plugins cause the vertical time locator to stop moving while others do not…
anyways, It’s probably not necessary, but I made a list [for myself] of plugins that caused me grief during tests. And by that I mean each of these would cause a metro to completely stop functioning when updating parameters [some caused max to stutter and crash]… on max 4_5_7 and XP… anything starting with an underscore denotes an author versus an individual .dll file/plugin…
/Max Load/Gui/Scheduler Errors//
_Dr Ambient (Drumatic)
_Karma_Fx //modular piece of crap [get nord!]
_Prosoniq //Other Than Northpole
_Rcg Pentagon 1, Triangle 1+2
Aneotic Room Sim
Ballsequencer (100% Cpu In Max)
Mjharmonicpingonly //Excessive Parameters
More Feedback Machine
Synapse Plucked 4.X
Synapse Scorption 4.X (3.2 Might Work)
Voyager (Cpu Error)
Xchorus //Doesn’t Respond To Cc Messages
inserting a new plug-in interrupts the audio
signal because it means disonnecting an
connecting signals .. is that what you mean?
No that is not what I mean. Obviously that would be the case with things when inserting a new plug. Maybe I’ll repost in a week when I have time to build an example patch plus link to working versus nonworking plugins.
I remember somebody said that on Xp when you interact with a certain
part of the Gui, probably opening and moving some windows, the audio
All the best
> No that is not what I mean. Obviously that would be the case with things when inserting a new plug. Maybe I’ll repost in a week when I have time to build an example patch plus link to working versus nonworking plugins.