Yes it’s the only solution for me. I tried to restart the device, unplug re-plug, turn off elektron engine and restart it but no. I always have to restart my computer.
I noticed there’is a loop in the Elektron Engine soft, status indicate : “measuring, initializing, then fault” and it’s looping.
I’ve just installed the latest Beta
No sound from main and no fx only individual outs Rytm mk1
Windows 10
I7 32 gb
Ableton 10 suite
Heat working fine
All was working fine 2.017
In overbridge mode the tempo of my DT has a locked symbol on it.
I intend to send the clock to my DAW
im wondering if this helps the multitrack fx. reverb and delay.
multi tracking always comes out dry.
Im using Cubase 10 artist. I cant really use this feature if the tracks keep recording dry with no fx.
Send the clock from your DAW to the DT, not the other way around.
Anyone using OB with Ableton, do not monitor the track you’re recording, use another track for monitoring. You will then have zero latency via OB.
Are “stuck notes” on Digitone fixed with this one or not? It’s not present in either fixed issues or known issues, even though it’s 100% known by Elektron as they explicitly said in my support ticket.
Thanks for the reply
I’d like the digitakt to control the tempo.
Mojave 10.14.6 rytm mk 2 os beta 1 , still not working already ONE YEAR !!, super disappointed with all this s@23@%
I am new to Elektron. Got my Analog Rytm MKII couple days ago. Installed overbridge. I am on Mac (2018 i9 32GB 2TB SSD macbook pro / AMD Vega 64 eGPU/ Antelope Audio Zen Tour via Thunderbolt / Mojave 10.14.6 / Studio One 4.5)
In Studio One If the sequence play by Rytm it 100% fine but if I use Studio One to sequence the Rytm. Playback is all glitchy and crackle and missing beats. I tried to use maximum buffer size, safe buffer and maximum dropout protection in S1) Still the same.
And while the OB vst is running, Studio One became very very slow, even quite Studio One takes 1 min and usually just instant.
And my laptop and interface been recording 96khz 64 samples without any problem with Overbridge 48kHz 1024 samples still crackle like hell…
That’s not the correct way to do this though, you need to have the DAW in control of the tempo. There is no benefit in having the DT control the tempo.
Hello! I think I found a potential bug in Overbridge when recording from my Digitone to Logic.
When recording instrument channels (3+4, 5+6, 7+8, or 9+10) with delay set on the DN the delay is not fed into Logic, but the rest of the audio is, so you get the non-delayed version when recording specific channels. However if you record the master channels (1+2) the delay is fed into Logic and is recorded OK. Of course recording master includes all of the instruments together.
When using the Digitone with its companion Overbridge app open, the sound comes out of my computer OK with the delay in-tact.
My setup:
Thanks for any help you can offer!
No.
Not an error. The effects are sends meaning there is one delay fed by the other tracks. The return feed is routed to the main outs, hence why you hear it when monitoring the main (½) outs.
Ok I figure out the reason of stuttering.
If I open the “edit/sequence/pattern” view in the studio one, the cracking/stuttering/distortion/missing beat will present.
But if I close the that view can only look at arrangement/console view, overbridge run perfectly fine without any crackling at all…Any one have solution for this?
This is working better for me than the previous version. I was getting glitches before. Now everything sounds smooth so far, but periodically my Digitone becomes completely unresponsive and has to be turned off and on again. (Mac OS Mojave)
I’m wanting to use my digitakt live and having a tempo control on my digitakt would be very handy.
Thanks again for your reply. I’m fairly new to the digitakt so I’m just trying to find my way.
turn off clock/transport on the OB plug in and “receive clock” on the DT. Turn on “send clock” on the DT and “Ext” on ableton (dunno about other DAW).
I have DT as the master clock and it seems to work fine tbh, not sure exactly why this “the wrong way” to do this (interested to find out though!)
If you have DAW as master clock, it’s a lot trickier to change tempo from pattern to pattern for example…