Drsbaitso

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...

_Karma_Fx //modular piece of crap [get nord!]

Mjharmonicpingonly //Excessive Parameters

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...

//directdraw crap?//
/Max Load/Gui/Scheduler Errors//

_Algomusic
_Anarchy
_Antares
_Anwinda Soft
_Arcdev
_Audio Damage
_Bigtick
_Bioroid
_Bluetubes
_Bram@Smartelectronix
_Bserrano
_Buzzroom
_Dashsynthesis
_Sonalksis
_Daves
_David Ross
_Devine Machine
_Dexters Plugins
_Dfx
_Digitalfishphones
_Djmarko
_Dmi@Smartelectronix
_Dr Ambient (Drumatic)
_E-Phonic
_Efm
_Elogoxa
_Evm
_Focusrite
_Fretted Audio
_G200K
_Gmedia
_Hg Fortune
_Insert Piz
_Ioplong@Smartelectronix
_Novuzeit
_Jasonsynth
_Karma_Fx //modular piece of crap [get nord!]
_Krakli
_Linplug
_Mnb
_Muon
_Mutagene
_Ndc
_Novakill
_Nubi3.Com
_Nugen
_Nullpointer
_Odo
_Oli_Larken
_Otiumfx
_Plogue
_Prosoniq //Other Than Northpole
_Psp
_Psychic_Modulation (Ph0Ne)
_Rcg Pentagon 1, Triangle 1+2
_Redshift Audio
_Refx
_Scuzzphut
_Silverspike
_Sknote
_Slimslowslider
_Soundhack
_Subtek
_Tiny God
_Tkplugins
_Tweakbench
_Maxx_klaster //toxic3
_U-He
_Ugo
_Ukm //Chorus
_Urs
_Virtual Creations
_Waldorf
_Wurr Audio
_Wwaym (Nwbass)
_Xavier
_Xsynth
_Z-Plugs

A0 Creamplifier
Abakos
Additive Synth
Admiral Scamp
Aneotic Room Sim
Arcdev Cyclotron
Av Chromium
Azr3
Ballsequencer (100% Cpu In Max)
Basslane
Baxxpander
Bitcrusher
Byd_Equinox
Cableguys Curve
Camelphat Free
Chip32
Chodspace
Chopitch
Convolver
Crystal
Dblue Glitch
Discodsp Discovery
Dq7
Fb1
Filterizer
Filtertuete
Fortune Cookie
Ftmstring
Ganymed
Greenwah
Grenade
Gtg K1
Hematohm
Impulse
Juno106
Jup-6
Karlette
Kp-6
Kt Granulator
Lost Technology
Lpgeq2
Mdsp Flanger
Mgtriggergate
Microgram
Mixbox
Mjharmonicpingonly //Excessive Parameters
Mono
More Feedback Machine
Morphite
Mr Green
Nlsynth
Nyquisteq5
Osiris6
P-600
Paax
Pan-Oh-Rama
Pariseq
Pg-23
Pulsewidthmodifier
Q_Del0Izer
Qwarpfilter
Quikquak Rayspace
Reverbomatic
Ringmod_Vst_Pc
Rogue
Rotopuker
Rubytube
Saturator
Scanned Synth
Soha Sonata
Solo
Dq1_Stereo
Spec Monkey
Synapse Plucked 4.X
Synapse Scorption 4.X (3.2 Might Work)
Synth1
Trasher
Tube Booster
Vectic
Vivaldi
Voctopus
Vopm
Voyager (Cpu Error)
Vstjuno6 //Sourceforge
Vstsynthfont
Warever
Wnmiasma
Xchorus //Doesn't Respond To Cc Messages
Xcita
Xtal
Xverb
Ymvst
Zodiac6

why-would-vst-interupt-the-scheduler

inserting a new plug-in interrupts the audio

connecting signals .. is that what you mean?

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. 

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

> 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
is interrupted...

2006/8/1, binez0r :
>
> 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.
>
>
>


why would vst~ interupt the scheduler?