KVR Audio is the Internet's number one news and information resource for open standard audio plug-ins. We report new releases, product announcements and product updates (major and minor) for all VST Plug-ins, DirectX Plug-ins and Audio Units Plug-ins (and RTAS too). We manage a fully searchable audio plug-in database (updated daily), and offer many free member services including user reviews, product update notifications and a very active discussion forum. We also host official support forums for many plug-in developers plus the official Receptor support forum.
Plug-in Database: Virtual
Instruments, Effects & Hosts
Plug-in
Ranks
Banks & Patches
Download & Upload
Plug-in Ratings
by KVR Members
Wiki: Tutorials,
Audio Lexicon, ...
Listen to Music
by KVR Members
Search
KVR

Google Powered Search:

in new window

KVR Powered Plug-in Search:

AuthorTopic: ATTN: Oddity and Cubase SX Users!
no_barcode
Posted: 26th July 2003 19:16
Would someone who uses Cubase SX and GMedia's Oddity please try this for me:

-Open Cubase's VST CPU Meter and The Oddity at the same time.

-Tweak one of The Oddity's sliders with your mouse while playing something, you may have to tweak the slider quickly.

-Now: Tell me if you get a CPU spike of 10-20% at seemingly random intervals.

I cannot figure out why this happens to me. Every other VST/VSTi works fine and The Oddity works great in every other Host. It's really driving up a wall.
[absurd]
Posted: 26th July 2003 20:06
I just tried this, and it happens to me too. I have a 1ghz pent. 3, and when I move the sliders CPU usage shoots all the way up to 100% Confused
no_barcode
Posted: 26th July 2003 20:54
How about if you bind that same slider to your MIDI controller, hide The Oddity's GUI, and then tweak the slider using your controller? Does it still happen?

For me, it seems to be related to the GUI.
no_barcode
Posted: 27th July 2003 04:54
Well, at least one other person is experiencing this. So I know I'm not imagining it.

Thanks [silent]
[absurd]
Posted: 27th July 2003 13:37
no_barcode wrote:
How about if you bind that same slider to your MIDI controller, hide The Oddity's GUI, and then tweak the slider using your controller? Does it still happen?

For me, it seems to be related to the GUI.


I tried this, and the CPU doesn't jump if I am rapidly turning knobs even with the GUI open, so it appears to just happen when the mouse is used to move the sliders.
suthnear
Posted: 27th July 2003 22:18
Have you tried switching off Enhanced Mouse Mode in Setup? I was noticing some odd behaviour with oddity (and my other ohm plugs as well) and I switched this off. It seems to have helped Smile
no_barcode
Posted: 28th July 2003 17:21
Thanks for your replies.

I got an email from Dave at GMedia Music. He said they have been able to replicate this problem a few times, and they'll probably start working on tweaking the mouse control routines as soon as their programmers get done with their current projects.

Until then, he suggested doing what suthnear had suggested and/or just not have the GUI open when you're playing live using a controller. He also mentioned turning "Autoload" off - but I'm not quite sure what or where that is.
Fire Sledge - Ohm Force
Posted: 29th July 2003 08:56
I don't know what the Cubase CPU-meter is actually measuring, and how accurate it is. Does the sound drops when CPU spike occurs ? If not, it is not related to sound and isn't very important IMHO.

-- Laurent
no_barcode
Posted: 29th July 2003 09:42
Fire Sledge - Ohm Force wrote:
I don't know what the Cubase CPU-meter is actually measuring, and how accurate it is. Does the sound drops when CPU spike occurs ? If not, it is not related to sound and isn't very important IMHO.

-- Laurent

Yes, the sound drops - for me.
smart
Posted: 29th July 2003 09:46
I can check this out in FL later.
no_barcode
Posted: 29th July 2003 09:51
smart wrote:
I can check this out in FL later.

CPU seems fine in FL Studio, Orion Platinum, and Tracktion. It's one of those "Cubase things." Cubase is notorious for them...
Forum topics in the archive are read only. New posts should be made in the main KVR Forums.
Disclaimer:
All communications made available as part of this forum and any opinions, advice, statements, views or other information expressed in this forum are solely provided by, and the responsibility of, the person posting such communication and not of kvraudio.com (unless kvraudio.com is specifically identified as the author of the communication).