avantronica

well, specifically Tiger folks running Max5

however, interested to here if this is an issue beyond OSX 10.4.11

any time i load a vst~ object i get general intermittent audio drop-outs, maybe once or twice a minute at most

this is only happening when i instantiate the vst~ object with a valid plugin name and only with regards to Max5

all is well otherwise and all is well in Max4.6

it makes no difference when i swap machines

it makes no difference when i turn off all wifi and routers

it makes no difference when i select a pro soundcard

it makes no difference what vst is loaded or whether it is opened or sounding

this is doing my nut in, because I can't (along with c74 support) get to the bottom of it

it just needs one other person to observe this audio drop out to stop me going crazy here

if you run the patch attached it'll be a bit dull and may take a few minutes to conclude - but it'd be mighty appreciated, i can fwd results to support

of note: it glitches on the audio output side, but if a quickrecord is also recording the tone it is *not* affecting the audio recorded, but which had sounded glitchy

we are talking about 50-100ms drops, very easy to hear

and *only* when vst~ is activated in Max5

ps max file (not text) attached as i'm mailing from different m/c

CORRECTION: text to paste in below, file missing extension

hey folks
well, specifically Tiger folks running Max5
however, interested to here if this is an issue beyond OSX 10.4.11

right
any time i load a vst~ object i get general intermittent audio drop-outs, maybe once or twice a minute at most

all is well otherwise and all is well in Max4.6
it makes no difference when i swap machines
it makes no difference when i turn off all wifi and routers
it makes no difference when i select a pro soundcard
it makes no difference what vst is loaded or whether it is opened or sounding

we are talking about 50-100ms drops, very easy to hear
and *only* when vst~ is activated in Max5

vst-fun-and-games

My first suggestion would be to check your signal vector size, but there's also the memory from long ago that there was a problem with airports around that time that played havoc with things. Try turning your airport off, if you have one.

Also, the use of mute~ is generally deprecated. It's better to put things in a poly~ and turn 'em on and off from there these days.

i'd already turned off airport and even downed the whole network to be safe

the signal vector size is 64, but i'll experiment above

mute~ is there for the purposes of that test patch only !

it just allows an A/B comparison between normal and malfunctioning without any user patching - [ not sure it'd make sense in a poly in this instance but it's a good tip for other cases ]

this still doesn't explain why there is only one circumstance reliably causing fault even if all else is constant

there are glitches for me using vst~ in max5 on tiger

no other triggers for this fault except that !!

mute~ is there for the purposes of that test patch only !
it just allows an A/B comparison between normal and malfunctioning without any user patching - [ not sure it'd make sense in a poly in this instance but it's a good tip for other cases ]

there are glitches for me using vst~ in max5 on tiger
no other triggers for this fault except that !!

it happens on both of my intel macs
i've emptied the vst folder etc etc

I have had another Tiger user confirm the same behaviour - so that's three machines - it'd be very helpful if someone (anyone please) could give the patch a try ! FWIW increasing the sample vector size reduces the frequency of the glitches but does not resolve the issue.

fyi, if you are experiencing this issue, please either wait for 5.0.8, or use the updated vst~ posted on a previous thread:

https://cycling74.com/forums/index.php?t=rview&th=39568&rid=5088

VST fun and games