Hi, I wonder if anyone uses this Rhino synth, I didn´t read a lot of it here. But I was impressed when I saw it but not yet very familiar with it.

Some opinions would be nice, what do you think ? Does anyone use that synth ? I think it went a bit under because of the other major companies who were posting at KVR

Is it worth the money ?

btw: The demo boost up my CPU, 1 Absynth and 2 Junox use the same CPU in my system as one Rhino......is that normal ?

cheers
Ingo

Is it worth the money!!!!

YES!!!!

Rhino is gorgeous, and ranks as one of my 'Best Buys' as far as I'm concerned. (up with Pentagon, Sonic Synth and Reaktor)

It's a deep synth to get to know and I have only scratched the surface so far. In fact the first track I have ever published on this site has two instances of Rhino in it...

CPU usage can be high(ish) if a patch uses a lot of oscilators and effects but then all you need to do is render to .wav and carry on.

I'd recommend anyone to buy it but at the end of the day you get out of it what you put in. Play with the demo some more, read the manual that is now available - but most important of all - do you like the way it sounds... or does it make the sounds you want?

Support is great, 'Tick is always around the forum and puts up fixes ASAP.

Anyway... you can tell I'm a fan

Thanx Wookie. Which operating system and Cubase Version are you using ?

Yes, you are right: manual is up now. cool.

I hate rendering because there is everytime something that has to be changed, I need still full control till the end...


So Tick is around here ?? Cool, that is important....

Actually I use FL Studio under Win XP.

I understand about rendering down, not my favourite cup of tea either. If you drop down to the Big Tick support forum and have a look in there, I'm sure you'll get an idea of what sort of support we get from him.

Quote:

I hate rendering because there is everytime something that has to be changed, I need still full control till the end...

Then switch to Tracktion! You can freeze any track, which is only a temporary wav-render, hit un-freeze to continue editing!

Actually FL Studio has something similar as well now... not that I've tried it yet, but it looks like there will be quite a take up by other sequencers over the next few releases ..

Wookie wrote:

Actually FL Studio has something similar as well now... not that I've tried it yet, but it looks like there will be quite a take up by other sequencers over the next few releases ..

Are you sure? I have been playing for FL Studio for a week, but haven't come across anything like that. Please let me know.

Back to Rhino, it's a flexible synth at a very reasonable price for it's feature set. It may seem initially different to program but is actually simple once you spend a bit of time with it.

What impresses me the most about Rhino is it's range of timbres and ability to get very complex. There are some CPU intensive patches and Rhino is not SSE optimized yet, I believe.

Big Tick has been one of the better companies when it comes to customer support.

Yeah. I'm spending too much time here
'Tick

I've got it and I like the sounds (which is why I bought it) but I have not had a chance to really dig in and make use of it. The one big problem I find is the heavy CPU strain on a P4. Hopefully 'Tick will sell enough of them to buy a P4 and do some optimization. At this point I see myself recording solo tracks to HD, or creating sounds in Rhino and using those sounds in a sampler. Normally I would not bother but there are some sounds in this VSTi that are worth the trouble. I guess bottom line is the sound.

Robert

I must say the sounds are very nice, even if there is only 64 presets. I'm actually impressed, and if you've followed any of my earlier threads, that's saying a lot.

*BUT* there are some problems, like the CPU pegging on one of the presets as the audio fades, acting like a denormal issue, but it ONLY does that on one preset that I've noticed (It's a sequenced preset, starts with an "O" I think, and is about 25 on the list.) I also noticed a few others as they fade out bounce around on CPU usage as they fade out, going up like 10%-30% of CPU on my 1.7ghz Intel machine. That's not acceptable to me.

Not a bad synth, that's for sure, but it does need to be optimized still. I had very similiar issues with Albino with version 1.00, but 1.01 fixed the problem of high CPU utilization on certain presets.

Devon

Devon,

I've just released the 1.03 upgrade. It should fix this cpu spike issue
Have fun,
'Tick

Also, is there a particular reason the majority of the presets overload the outputs? Don't understand why I have to manually turn down every one myself. Least there's only 64 presets.

I'll give it a shot to see if that clears up the problem.

Devon

I guess it all comes from your default host level. You're lucky, since there's a very easy workaround: download this file and run it to divide the default Rhino output by 4.

You may have to rename the file to rhinogain.reg after downloading. For some reason it downloads as rhinogain.mp3 for me.

'Tick

this synth sounds gorgeous to me. I was having a go with the demo last night and was really in awe - but the cpu spikes scared me away (amd 1.4 win 98se). I'll try the 1.3 demo and see how it goes. but if you've got a machine that can handle it, most definately, this thing is worth the money.

Well, that fixed the problem with the few errant presets that were spiking. I just wish this thing wasn't such a CPU hog though. Oh well. I'll keep looking for updates.

Devon

Devon,

many of the preset patches are CPU intensive but you can get massive sounds with reasonable CPU use. I did the demo song on a Athlon XP 1700+ with less than 50% load and five or six instances - can't remember now.

To me that's reasonable.

Bruce

Ya, but when you like D50'ish, and it's eating 50-75% of your CPU for that one instance, and then I switch to FM7 for sounds that sound similiar, and it's eaching maybe 10% max with twice as many notes, I find it hard to justify trying to get this to work for me. Don't get me wrong, it sounds great, it just needs more work in optimization. Until it gets there, I can't afford that much of my CPU gone. I used to bounce down EVERYTHING, now I'm getting more in the habit of bouncing down NOTHING. More control = more speed for writing and editing in the end.

Devon