Max5 is causing syslogd to eat 120% of my processor usage(Leopard)
in my main patch(and i think in that patch only) the process syslogd is taking up to 102% of my cpu usage when i turn audio on. when i look into console i get the following messages:
14-05-09 12:55:08 macbook-pro-van-younes-riad [0x0-0x18018].com.cycling74.MaxMSP[226] [0x0-0x18018].com.cycling74.MaxMSP 226 com.apple.console Notice vst_audiomaster 7
14-05-09 12:55:08 macbook-pro-van-younes-riad [0x0-0x18018].com.cycling74.MaxMSP[226] [0x0-0x18018].com.cycling74.MaxMSP 226 com.apple.console Notice vst_audiomaster 23
these messages repeat like 200 times in console.
i’m using battery 3 and Luxonix LFX-1310 ( http://www.luxonix.com/home/en/products.html?id=lfx1310 )
in this particular patch. i’m on OSX 10.5.6
can anybody understand the console message and tell me what causes the problem?
i have exactly the same problem – with syslog creating tens of thousands of log files – a log file of over 1 gig size in around an hours use (see my recent post here http://www.cycling74.com/forums/index.php?t=msg&th=39529&start=0&rid=0&S=1279be22cd79615cb99fa83f454d8697)
i would also appreciate some help as i have had to use ableton live simply as a vst host via rewire
chris
Looks like this problem was introduced in version 5.0.7. If you want a workaround the vst~ from 5.0.6 will probably work for you. You can grab the older installer here:
Mac:
http://www.cycling74.com/download/Max5_37726.dmg
Windows:
http://www.cycling74.com/download/Max5_37726.dmg
Thanks,
Rob
Here is a version of vst~ which should fix the console messages. Let me know if it doesn’t solve the problem.
-Ben
thanks, the problem seems to be fixed. i just replaced my old vst~ object with this new one.
thanks a lot ! you save my concert of tonight !
it seems working the file system.log is calm now…
Thanx, this has been a major concern for me since it has rendered (…) my MBP as good as useless for live performance. I suppose this will be sorted out in Max 5.0.8?
Cheers,
Yes. Sorry for inconvenience, in the meantime the version posted by Ben fixed the issue.