From: Chrissy M. <chr...@ho...> - 2013-01-30 20:53:22
|
hi Mike, I have patched the very latest VST_Sync patch and this time I have installed to my /usr/bin/lmms directory (which makes testing easier, no more changing files for me),anyway i see good improvements with this patch, like ;) (* note LMMS default install on linux is /usr/local/bin/lmms *) (1) the clicks/pops are almost gone when using dblue_glitch (i think the actual sounds used have an effect here)(2) i can seem to load far more vst and vst(i) into a project with less cpu overhead(3) the export seems flawless (what you hear in the song is what you get exported) some things that need looked at in general and i believe they are NOT relevant to your patch, but i will list them here;_ (1) every vst/(i) gives this warning RemotePlugin::DebugMessage: failed getting shared memory(2) exporting a song with even the smallest buffer size i.e 64 frames always gives a silence at the start of 0.002ms or roughly 76samples (testing in audacity) : the frames size has a direct effect on this , : this could be a soundcard issue tho?(3) when opening a saved song with vst/(i) already in it, sometimes the terminal will show 2 instances being created although only 1 actually shows up, perhaps this is harmless behaviour but worth looking at?(4) Automation is messed up at the moment, eg open a new song , goto bb_Editor add an automation track and drag the volume control of the triple-osc into that track, there is no automation showing what should be 100%, it is the same for all test i have done regarding any automation (* note i can report these as separate bugs if needed* ) keep up the good work and p.s i hope the vst_sync makes the next release as i think it is almost there ;) thanks Mikobuntu ;) |