having problem with rhino in project5

Official support for: bigtickaudio.com
RELATED
PRODUCTS

Post

Some very CPU light synths do work OK with P5 and Sonar, but anytime you use a synth as powerful and analog smooth as Rhino, you will run into these problems, forget about even considering running CPU monsters from Arturia(I know, I "owned" all of their synths), you computer will have a heart attack !

Post

all of that might be true except for the fact that i've used P5 and rhino (older/original versions) on my old PIII 450 without problems and my newer P4 2.4 gHz also without problems

Post

AzureCrystal wrote:
blakflag wrote:Wonder if the new Rhino also has some hefty initilization to do? If so I classify this as P5's boo boo, not Rhinos. I complained to Cakewalk but theres been no word back.
I stopped using Sonar and any Cakewalk products for the same reason, they do not work well with VST technology, they pretty much "wrap" ASIO and the overhead causes a lot of trouble, like this one, I would say this is a classic and well known Cakewalk problem, nothing with Rhino....
I used FL Studio before and it worked fine but I like Project5 too much to switch back.
my music: http://www.alexcooperusa.com
"It's hard to be humble, when you're as great as I am." Muhammad Ali

Post

AzureCrystal wrote:Some very CPU light synths do work OK with P5 and Sonar, but anytime you use a synth as powerful and analog smooth as Rhino, you will run into these problems, forget about even considering running CPU monsters from Arturia(I know, I "owned" all of their synths), you computer will have a heart attack !
Must respectfully disagree as far as Sonar 5 goes. I use it with Rhino and all the Arturia stuff and have NEVER had a problem like what is being described here. Can run multiple tracks of "monsters" at decent latency with no issues.

Post

AzureCrystal wrote:Some very CPU light synths do work OK with P5 and Sonar, but anytime you use a synth as powerful and analog smooth as Rhino, you will run into these problems, forget about even considering running CPU monsters from Arturia(I know, I "owned" all of their synths), you computer will have a heart attack !
Then what am I...Magic? :roll:

Post

I disagree as well. All of my synths work great in Sonar 5 Produecer edition. I have plenty of supposedly cpu hungry instruments - like Rhino - and they work just fine with multiple instances and zero problems.

On the other hand, I had a brief problem with latency, clicking and cpu spikes and discovered it was my ANTIVIRUS software and NOT Sonar or my instruments (vsti's). I switched to a more well-known and reliable antivirus (avast) and no more audio problems.

Mike

Post

ATS, Are you inserting a patch change at time 0:00? That would definitely explain the stutter. Rhino does need some time to change patches, and I think it could cause something like you experience.

OT: To the P5/Sonar supporters, I didnt claim that in general CPU hungry plugs dont work. (cant speak for AzureCrystal just myself). I just have a specific beef with cakewalks VST wrapper. That is, theres some kind of re-initialization that goes on when looping measures that shouldnt be happening, and makes some plugs that have a lot of initialization to do stutter during playback when they hit the loop marker. The plugs I've seen this with are Dr Fusion, and Arp2600VA. Not necessarily Rhino because I stopped using the VST wrapper.
You are not a beautiful snowflake.

Post

hey ATS
i recently switched to a different set of 'protection' software and i stared getting pretty much the same symptoms you report. I think I've tyraced this down to a constant real-time memory monitoring anti-viral software. I turned this very protective feature off and the crackles went away.

Post

How about you lettin' us in on which anti-viral software that there be, wrench? Just so's I don't buy it in the future.

Use NOD32 here myself, no issues at all.

Considering all the problems ATS has been having with P5, that the rest of us don't have and can't replicate, maybe this is a big part of his issues. P5 is certainly not a buggy piece of software in general (anymore). CPU hog, yes. Buggy, no.

Post

The one that caused me grief was EZ Armor by CA Associates - what a piece of crap software. Avast has worked very well since.

Mike

Post

Rhino 2 has lived happily, often times in many instances, in both Sonar 4 and 5 PE. I just received the S6 upgrade, and I imagine that will be about the same.

Cheers,
Envoy
Image
the dreamer that remains . . .

Post

it's the step up from EZ Armor, but still from Computer Associates

specifically
e Trust Pest Patrol Active Protection
'Detect Pests in Memory'

Comcast has recently taken over Time/Warner RoadRunner in this part of the Midwest, so maybe they'll be changing their free and upgrade anti-virus, anti-spyware, anti-spam, anti- etc. package

Post

fwiw, i use "AVG Free(or Personal?)" from grisoft (click here) - daily updates, lightweight, integrates with mail clients, etc... the only downside is you have to scan all fixed drives

hth
p

Post

AzureCrystal wrote:
blakflag wrote:Wonder if the new Rhino also has some hefty initilization to do? If so I classify this as P5's boo boo, not Rhinos. I complained to Cakewalk but theres been no word back.
I stopped using Sonar and any Cakewalk products for the same reason, they do not work well with VST technology, they pretty much "wrap" ASIO and the overhead causes a lot of trouble, like this one, I would say this is a classic and well known Cakewalk problem, nothing with Rhino....
:roll: And this is a classic and well-known misconception about the way Cakewalk works with VST.

I would say, can you reproduce this Rhino issue in a project that contains nothing but Rhino? You mentioned StylusRMX, which may be a contributing factor. Also, you have downloaded the latest version of the (poorly named) VST adapter? I know that it fixes some issues with Project 5, and with looping.
Now Somewhat Retired

Post

[quote="AzureCrystalI stopped using Sonar and any Cakewalk products for the same reason, they do not work well with VST technology, they pretty much "wrap" ASIO and the overhead causes a lot of trouble, like this one, I would say this is a classic and well known Cakewalk problem, nothing with Rhino....[/quote]

Just get directxizer and you should stop having having any problem siwth any vst plugins, if you're having problems with the stock vst adapter that comes with cakewalk...

Post Reply

Return to “Big Tick”