|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
Mic Stand Bob
on Dec 22, 2009, 6:01pm:
Hi, I have found a problem with graphic updating on all the voxengo 64bit vst plugins in Cubase 64bit 5.1 and 5.1.1. I typically have mix sessions that push over 5gb of ram use, and i have troubleshooted this problem to find it only happens when windows task manager is showing cubase using around 3900 mb of ram or more.
the problem:
plugins do not update their GUI as settings and knobs are changed with my mouse. the audio does change immediately as the knob is twisted. if I hide the plugin by clicking the "e" in cubase and then reopen the plugin, the changes i made are shown. if i make more changes, I must close the plugin and reopen each time to get visual feedback of the changes. this applies to many settings in all the 64bit voxengo vsts. just to point out one common parameter between plugins. I get this behavior with the oversampling button. if the button is on "1x" and i switch to "auto", it keeps displaying 1x until i close and reopen the plugin window. then it will display "auto" as i had selected
Exception: while i am working in Cubase and already have voxengo 64bit plugins open in the session, if I run cubase over about 3900 mb of ram used, any new voxengo plugins i add to the session will exhibit the problem, however the plugins that existed in the open cubase session, before the usage went over 3900-4000mb, will graphically update as expected. If I close the session entirely and reopen, all voxengo plugins will exhibit the problem.
If I remove Other "ram hungry plugins" in a session that has crossed the 3900mb of ram to bring the Ram usage below 3900mb, I can then save and close the cubase session. upon reopening the session, the voxengo plugins will work normally.
My System:
Asus P6T deluxe v2
Intel i7 920
6gigs of ram
Windows 7 x64 RC Ultimate
Cubase 5.1.1
Nvidia Geforce 9800 GT graphics card
RME Fireface 800
has anyone experienced this or had success with large 64bit sessions?
thanks,
Darrell
the problem:
plugins do not update their GUI as settings and knobs are changed with my mouse. the audio does change immediately as the knob is twisted. if I hide the plugin by clicking the "e" in cubase and then reopen the plugin, the changes i made are shown. if i make more changes, I must close the plugin and reopen each time to get visual feedback of the changes. this applies to many settings in all the 64bit voxengo vsts. just to point out one common parameter between plugins. I get this behavior with the oversampling button. if the button is on "1x" and i switch to "auto", it keeps displaying 1x until i close and reopen the plugin window. then it will display "auto" as i had selected
Exception: while i am working in Cubase and already have voxengo 64bit plugins open in the session, if I run cubase over about 3900 mb of ram used, any new voxengo plugins i add to the session will exhibit the problem, however the plugins that existed in the open cubase session, before the usage went over 3900-4000mb, will graphically update as expected. If I close the session entirely and reopen, all voxengo plugins will exhibit the problem.
If I remove Other "ram hungry plugins" in a session that has crossed the 3900mb of ram to bring the Ram usage below 3900mb, I can then save and close the cubase session. upon reopening the session, the voxengo plugins will work normally.
My System:
Asus P6T deluxe v2
Intel i7 920
6gigs of ram
Windows 7 x64 RC Ultimate
Cubase 5.1.1
Nvidia Geforce 9800 GT graphics card
RME Fireface 800
has anyone experienced this or had success with large 64bit sessions?
thanks,
Darrell
Aleksey Vaneev
on Dec 22, 2009, 7:13pm:
Thanks for the details, and I'm sorry about this problem. Have you tried using the latest GlissEQ? Does it behave in a similar way? If so, please contact me via info@voxengo.com - I'll send a development version for you to try when you have time.
LuxDelux
on Jan 28, 2010, 10:19pm:
Hi, I just want confirm this bug. I also use Cubase 5.1.1 64bit and Windows 7 64bit.
However I only have this problem with VariSaturator, haven't noticed it with Voxformer.
For example I have in my chain only Voxformer and Varisaturator after it, Voxformer works fine, Saturator has updating problems.
Cheers
However I only have this problem with VariSaturator, haven't noticed it with Voxformer.
For example I have in my chain only Voxformer and Varisaturator after it, Voxformer works fine, Saturator has updating problems.
Cheers
Mic Stand Bob
on Jan 28, 2010, 11:23pm:
Aleksey has worked with me to resolve this bug. all 64 bit plugins updated after Dec 25, 2009 should have this issue resolved. unfortunately, we have to wait for the updates for each plugin. I use jbridge to get around the problem in Cubase 64 by running the 32bit vsts until the plugins are updated. voxformer is one of them that has been updated.
Darrell
Darrell
LuxDelux
on Jan 29, 2010, 7:06pm:
Thanks for the info. Good to know it is resolved. I shall wait for the update then :)
Aleksey Vaneev
on Feb 1, 2010, 3:01pm:
I plan to release update to VariSaturator in couple of weeks.
|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
Copyright © 2002-2012 Aleksey Vaneev - Terms of Use - Privacy Policy - About Voxengo - Questions & Answers