The best Tip when dealing with the Ren is....

Save often, very, very often

Don't create some shit that's a masterpiece and go call your girl to brag on it or any other meaningless activity until you hit save

The Ren can't be trusted at all bruh

After spittin game at my girl I came back to the ren and the ren was -32 bruh, it was froze like a mofo bruh. I hope it was an anomaly

On a side note, anyone daring enough to use it live on stage is a brave mother ****

Yeah, I constantly do save as, as well in case my current file gets corrupted. Though so far the Ren has been mostly stable for me, just random weird s### every once in awhile.

you can't trust the Ren any more then you can a female bro

InspectahEX wrote:you can't trust the Ren any more then you can a female bro

lmfaoo gotdamn...

More tips for the Ren:

Stop the sequencer before you load any new plugins. This alone will minimize your crashing.

Create keygroups of plugin synth parts when possible. Multisampling is your friend, not just for technical reasons but for creative purposes too.

The demo version of Samplit http://www.cdxtract.com/samplit.php lets you autosample 12 keys at a time, save them as almost any format and quickly make a keygroup of your synth sound then unload the synth. This will keep your CPU usage really low which will help with the crashing as well.

I was told by Garth from chicken systems that they are going to be including the Renaissance sampler format in their translator software as well as an autosampler. Once this happens keygroups will be so easy to make... just click, walk away, come back in a few minutes and you have a nice mapped keygroup for your Ren... can't wait. Should be in version 6.1 I was told (at 6.0 right now)
http://www.chickensys.com/products/tran ... n_akai.php

I would certainly use Chicken System products if they can translate into MPC Ren Keygroup format!

Avoid the undo button when possible.

forwerd wrote:Avoid the undo button when possible.

I stay away from the undo big time. I hit it and it erased some shit from last week

Airyck wrote:I was told by Garth from chicken systems that they are going to be including the Renaissance sampler format in their translator software as well as an autosampler. Once this happens keygroups will be so easy to make... just click, walk away, come back in a few minutes and you have a nice mapped keygroup for your Ren... can't wait. Should be in version 6.1 I was told (at 6.0 right now)
http://www.chickensys.com/products/tran ... n_akai.php

Garth is a good guy. He helped me to get some old Yamaha Motif .W2A & .W3A files converted to EXS24. Not at all as simple as it seemed. I don't completely understand keygroups as far as what they do or are used for but if he's developing a Ren format, I'm down.

The crazy thing is the " latency " almost gives it a mpc 60 vibe

I''m still on the shelf with the Ren

I like it one minute and I want to shoot it the next

Better Mouse Trap wrote:" latency "

Last time i checked it was 1.7 milsec..does not affect my work..

Doesn't it depend on buffer setting?

What sort of latency is that, playback latency?

Someone should test actual latency, from pad hit to sound coming out, at various buffer settings, and compare to hardware MPCs.

Not sure how you would test for that, maybe a connection directly to the pads somehow, or close-mic the finger hitting the pad?

Oh!
I thougnt you were gonna say...










































































get a real MPC.

SimonInAustralia wrote:Doesn't it depend on buffer setting?

What sort of latency is that, playback latency?

Someone should test actual latency, from pad hit to sound coming out, at various buffer settings, and compare to hardware MPCs.

Not sure how you would test for that, maybe a connection directly to the pads somehow, or close-mic the finger hitting the pad?

It clearly only lists input latency, processing and output are not factored in that reported number. You'd need a properly reported number on an interface that costs as much the Ren itself to get a number that low.

The Ren is not alone in not listing the true RTL number. Over 75% of interfaces and software I've ever encountered do the same skewed reporting on the GUI.

Still the true RTL number is likely between ~4/5 - 8ms, certainly a very usable number for live input if your session can stay at at a low buffer for awhile or even the whole way.

Not really RTL, round-trip latency, in the case of an MPC.

That is more a measurement applicable to monitoring a live audio input, through the software, which you are not really doing (at the moment) in MPC Software.

What is important in an MPC, in terms of pad-playback response, is just the audio playback/output latency, and any latency in the pad sensing and MIDI input to the sound engine.