Overbridgeis more stable and works much better using a dedicated audio interface (my tiny audient ID4 does the job). I guess it is related to USB Bandwidth or something. Setting usb only in digitakt also helps. Regarding the settings of the audio interface, 48kHz with a 256 or 512 buffer does the job.
I have been trying to incorporate my Digitakt / Digitone into Reaper ever since I have them.
I find your advice to be very useful. At first I hoped the tricks in your first post would solve my sycing problems.
It works way better than with OB sync. At times its really very good.
But just yesterday I had a very frustrating session where I tried to compose and just have playback from the Digitakt.
It went slightly out of sync whenever I stopped the playback.
This is the main issue in my eyes.
As for your further tips:
I always have midi set to no input on the actual track that holds the DT OB plugin.
I am sending notes to the DT via a send from a track called OB pattern change which works quite nicely. (Is this what you mean by your Nr. 2. tip?)
I am using looped midi items in the length of the actual pattern which makes it easy to extend a part by just dragging it.
I want to use DT for all my drums while composing. This means a lot of stop and restart and sync is the main issue.
It is so sad. In that very session I have such a cool groove going (with locks, probabilities and all that stuff).
But yes I do have a quite good sync with OB otherwise. If the sync is a bit loose, I adjust the clock offset (of reaper to digitakt). You should not forget to arm the tracks that contains the overbridge plugin (it changes everthing). Another important stuff is to avoid to send SPP.
Another fun stuff you can try is no clock, but only transport send/receive. If digitakt tempo and reaper are the same tempo, it works
I really thought you had perfect sync in Reaper with midi clock instead of OB sync.
If I get your right, this is not the case.
I really, really want to compose and jump across my piece of music and want the Digitakt to stay in sync.
The thing is, at times it does. But it can loose sync randomly and this is so disgusting.
Its the USAMO from exptert sleepers.
I will want to produce just midi clock with this an see if it makes things better.
It works with audio priority (so much higher in timing accuracy).
I will report if it works. Might be of use for others too.
What I mean by this is that triggering pattern 1 on DT will automatically playback region 1 in reaper, when triggering pattern 2, it will playback region 2 etc, a bit like an ableton sesssion. Also, you can change the seeking behaviour in reaper > preferences > audio > seeking to decide if the playback of the region has to be finished before it seeks to new region, or if reaper has to wait for a few bars . IMO, one bar is perfect for this, try it.
This trick can also be used when live triggering reaper sections (which can act as ableton live scenes, see REAPER Resources) to trigger a given digitakt pattern. To do this, let blank space beetween section, and fill the sections with a clip containing pattern change (note or pc ), and apply the delayed playback.
Dear Dissofiddle (wich is a really funny name ),
First I have to say sorry. I did not reply because I did not get a notification of the newer posts.
I am still interested in this thread.
I was into my account settings and did not find a way to get informed per mail when new post arise.
So, sorry once again for not answering.
I can answer all of your questions with a big YES.
All works kind of. But I when moving in an arrangement I lose sync in a way that sets the digitakt just an annoying 16th/32nd off.
It would be better not to play then.
For the Usamo (which could be interesting for anyone else reading this thread).
I did everything right as it was described in the manual.
I had proper clock and start/stop/continue messages.
The Digitakt refused to follow the Usamo.
Send it back because it ist not useful, sorry expert sleepers.
1 - Have you deactivated the midi in/out in the digitakt (use only usb ) ? It seems to change a lot concerning the bandwidth.
2 - What audio interface settings are you using ?
3 - what are setting are you using in the overbridge pannel ?
4 - gave you tried with another daw on the same computer ? like ableton lite which is often included when buying midi keyboard or else
1 - No, I never new this could be a problem. A thing here could be that it may take away the
possibillity to put in notes via a connected keyboard. I am pretty sure that the sequencer does
not accept notes that are put in via usb (maybe wrong - will try).
3 - you see me baffled. I didnt even knew that there was something like this panel.
I do not use the Digitakt as audio interface, though.
Would you recommend to match the latency settings with the ones in my audio interface?
Note: I do not use Digitakt as an audio interface.
You mentioned that strange behavior where the Digitakt was in sync, when you play a song from the start, but not when you jump in somewhere in the middle of a song.
This is what I am facing constantly. Digitakt is in sync when I start from the beginning.
As you might understand, this is not a good way for producing, tedious and time consuming.
Very, very much thanks.
I am still trying to get all this information to work.
You see me corrected. My Digitakt gets the note information via USB for the sequencer on autochannel.
Its good to be wrong (good news ).
I am still trying to find the right settings in Overbridge settings.
Lowering it under the audio interface range seems to make things better.
I have to investigate on this tomorrow when I habe a bit of spare time.
I will once again give your recommendation another try, to not sync via Overbridge.
EDIT: Once again, firing too fast.
I learned that Reaper (and I would myself consider rather advanced) has surprises for me.
I never knew there was a way to put a track to input monitoring only while having it in record armed mode.
Means, there are two options for accomplishing this goal. Record mode on for lower latency and NO actual recording happening.
About Routing : Happy to learn that routing works, it does work for me.
Another trick about this : you can change the routing on a global basis or on a per-pattern basis. This is very cool as it allows you to dynamically decide for every pattern what should go to the master and what should not. To do this, you have to go in the pattern export menu.
When I use MIDI as the timecode source I am not able to change it to anything below 0, so is there a way to have no delay after pausing on reaper? I am using the latest version of vista and a new issue i see is that the timecode does not start at 0 seconds at the start, it starts from 4 seconds and 18 miliseconds.
As for timecode starting later, confirm that timecode offset and playback lag compensation are both set to 0 (as shown in my screenshot above). If the issue still persists then it must be something with how you have reaper set up or your timecode file in reaper.
Is there anything you recommend i do because im trying to use reaper as like a timestamp thing so when i click pause i know where to put a cue and then do that again and again but i cant do that if theres a 1 second delay bc of freewheel
Usually I will first put markers in Reaper to find the exact locations that I want to place my cues. Then I open a TC window in Reaper to take those TC values and put then directly into my Vista cues. I have also had some fun with setting up the Reaper timing scale to Measures and Beats to allow the cursor to lock to the beats. This makes it very easy since that never is the same as the TC value.
We first experienced the Alpha King when up on the NW surface randomly whilst collecting drops and the odd bit of obsidian and element ore. Unfortunately we used that barb in a "test" battle against the Alpha Rockwell - which with only 2 of us we surprisingly won!
Now the rest of the tribe need to also do it we spent hours up on the NW surface killing hundreds of them with no luck spawning an Alpha. Also tried standing on a rock where alpha nameless was spawned all night on a 10/90 day/night and still no luck.
Something to note, I have seen 2 alpha reapers in just a few short trips to the surface. Both of those have been high in elevation oh the jagged rocks. The first one I wasn't ready to fight, so I ditched it. The 2nd I killed solo. It did a lot of damage, but died really quickly.
Have not yet seen any, and that's through many trips to the surface (have a fair number of ascendant blueprints and saddles and such to show from it). Usually we get two, sometimes up to 6 or so reaper kings per beacon drop, occasionally it's just the seekers. But alphas have been nonexistant.
The problem with Aberration is theres only 1 active alpha per map. Theres only 1 alpha karkinos or alpha basilisk or alpha reaper king spawned at given time until dead or despawned. Thats what ive seen as server admin of a private server.
I can confirm this is not the case. On my official server I have fought and killed an alpha basilisk while my tribe mate killed an alpha karkinos at the same time. Alphas simply have a low spawn chance.
3a8082e126