Problem in Reaper

jiltloop

Hi guys, I have a problem in reaper, basically I am running reaper and rewiring reason through it. I mainly have a beat playing from reason and the problem is that when I am playing a loop the kick at the start of the loop tends to double trigger everytime the loop restarts. I have the loop starting a bar in from the 00 at the start of the sequencer because I know that can cause this problem, but it doesn't make any difference. No matter where I have the loop set up in reaper or reason I get the double trigger problem. Any help welcome thanks!

dav nagle

jiltloop wrote: »

Hi guys, I have a problem in reaper, basically I am running reaper and rewiring reason through it. I mainly have a beat playing from reason and the problem is that when I am playing a loop the kick at the start of the loop tends to double trigger everytime the loop restarts. I have the loop starting a bar in from the 00 at the start of the sequencer because I know that can cause this problem, but it doesn't make any difference. No matter where I have the loop set up in reaper or reason I get the double trigger problem. Any help welcome thanks!

Firstly,
Are you using Re drum or Dr rex?

jiltloop

Hi dav, I'm using re drum but al my notes are drawn in on the sequencer page and I have none of the trigger buttons activated on the re drum module

dav nagle

jiltloop wrote: »

Hi dav, I'm using re drum but al my notes are drawn in on the sequencer page and I have none of the trigger buttons activated on the re drum module

Geez man there is nothing worse than an unknown double trigger. I was hoping it was your pattern sequencer. Is it only the very fist kick that double triggers?

jiltloop

Yeah it's only the start of the loop thats double triggering and it's hard to tell but it sounds like its always the kick. It's very frustrating because it happens on every single track I start.

dav nagle

jiltloop wrote: »

Yeah it's only the start of the loop thats double triggering and it's hard to tell but it sounds like its always the kick. It's very frustrating because it happens on every single track I start.

I know I sound like a mammy but have you considered double checking the midi notes for the drum track, maybe there is one note at the start that is doubled?

jiltloop

Yeah that's definately not the problem. I only started using reaper recently and I've noticed this problem every time i'm rewiring it with reason. I know that once I've sequenced and arranged the song out that it won't be a problem because it's only when I'm listening to the beat in a loop. Also it doesn't double trigger when I first start the loop either, only when it loops back to the start.

fitz

Sounds like an extra kick note at the very end of the loop...

jiltloop

fitz wrote: »

Sounds like an extra kick note at the very end of the loop...

Hi fitz, I don't think that's the problem because it isn't an isolated occurrance, it happens with every beat that I rewire with reaper from reason. Even with old beats that I made in reason before I got reaper.

frobisher

Try quantizing the first kick drum hit so that it definitely occurs within the start of the loop rather than at the end of the last one. Might do nothing but worth a try!

jiltloop

I'll give that a go and see if it does anything, I'll try anything at this stage.

i57dwun4yb1pt8

also try the reaper forum - they are always good for a fix ;-)

jiltloop

Yeah I might try the reaper forum actually, never thought of that before. Cos this problem ain't going away no matter what I try.

frobisher

Doesn't sound like a reaper issue. Unless you're triggering the sounds by midi from reaper through rewire?

jiltloop

No I have the beat sequenced in reason so baiscally the only control reaper has over reason is through the tempo and the play and loop functions. But this problem never arises when I'm using reason on its own.

ICN

The problem is definitely with reaper, not reason by the sounds of it.

I'm not familiar with the program, but it would be worth trying different Ch.delay / buffering / processing / latency settings. I had exact same problem with ableton. Sounded like the first beat was repeated.. Then caught up / reset itself.

I had to record some audio into ableton. Then look at the file where the audio began. The difference between 0 and where the recording began was the amount of delay that needed 2 be adjusted.

It helped rewire when I fixed it. Maybe there is something similar in reaper?

Record reason into it & look at the file. Forget about looking towards reason, as its slaved to reaper.

Hope that helps!

jiltloop

Yeah I think maybe I should try the trial and error aproach in preferences and see if that sorts it. Thanks for the advice.

jiltloop

ICN wrote: »

The problem is definitely with reaper, not reason by the sounds of it.

I'm not familiar with the program, but it would be worth trying different Ch.delay / buffering / processing / latency settings. I had exact same problem with ableton. Sounded like the first beat was repeated.. Then caught up / reset itself.

I had to record some audio into ableton. Then look at the file where the audio began. The difference between 0 and where the recording began was the amount of delay that needed 2 be adjusted.

It helped rewire when I fixed it. Maybe there is something similar in reaper?

Record reason into it & look at the file. Forget about looking towards reason, as its slaved to reaper.

Hope that helps!

Cheers for the advice, problem solved now. I went in to preferences to try the things you mentioned above, and first thing I did was change the buffering from the default 1200ms to 1000ms. Problem solved straight away! I didn't think buffering could cause problems like that.

ICN

Excellent! I love it when a plan comes together!


That was close.. You nearly had to buy a new computer!! :pac::pac:

jiltloop

To be honest I think I do need a new computer, mine's a heap of junk!

ICN wrote: »

Excellent! I love it when a plan comes together!


That was close.. You nearly had to buy a new computer!! :pac::pac: