I was referring to model cycles, syntakt, digitakt 2 & digitone 2, which all felt very stable at release. I have no doubt they will fix it, just want to manage expectations for other users.
The setup is very simple:
DT2 DIN-Midi-OUT ā TV DIN-Midi-IN
Both audio signals go analog into a Bluebox. From there into an OT, then AHfx ā USB ā Audacity.
I have the feeling that the latency fluctuates slightly, but I canāt see that in the audio file.
I did a second test setup to rule out a possible error in the Bluebox:
DT2 as master left out ā AHfx IN
TV slave right out ā AHfx IN
Same latency of approx. 20 ms
This isnāt relevant, donāt worry about this: itās just the machine adjusting to tiny subdivisions, and in fact resynchronizing. I have witnessed this in the past and it was rock solid.
This is more serious.
There are two possible issues: transport (start/stop) and synchronization/BPM matching.
Letās rule out transport first.
A way to adjust the timing yourself is to press left or right arrow keys to momentarily slow down or speed up the tempo and resynchronize. Another way is to stop and hit play at the right time, of course: once youāve managed to resynchronize, do you observe a desynchronization later?
One idea btw: have you waited for the whole project to get loaded before pressing play on the source?
- Might not be relevant, I agree, but other Elektron machines show no fluctuations.
- Oh, Iāve just triedāitās actually completely impossible to nudge on the Tonverk itself. It just ājumpsā randomly. The Octatrackās behavior is different, so Iāve managed to sync it to the Tonverk. 8 minutes inātheyāre still in sync. To be clearāno MIDI involved here.
- The Tonverk has been on since Friday and Iām only working on one project, so I believe itās completely loaded.
I certain cases, like sync to Ableton, I have seen this. In my case, it was the source that wasnāt 100% correct, but in Cirklonās case, I would dare even imagine this ^^
I donāt understand.
Open tempo menu while the unit is playing. Press Left arrow briefly: have you seen tempo changing? If you stay pressed, it should even go slower, and for a longer time.
You mean, you havenāt switched it off once since Friday?
I would actually have to look at the MIDI stream data, but thatās not really my area of expertise ;-).
Perhaps the error occurs when playing back the audio data and not at the MIDI level.
No intern audio routing.
My Digitone show tempo fluctuations when synced to the Syntakt.
md does too synced to erm multiclock
its not uncommon for the tempo numbers to oscillate when MIDI clock slaved, many devices do this. As long as thereās no audible tempo fluctuation or jitter, the numbers moving around is not critical.
Easiest way to tell if there are actual fluctuations is to multitrack record audio into a sample accurate digital recorder from both the clock master and slave, and then inspecting the waveforms graphically side by side from different points of the recording.
It was my badānudging the slave device, but the Octatrack handles this situation (by not responding to nudge).
The way to reproduce: Any device (clock + transport) ā Tonverk. Play. Nudge the Tonverk. It starts jumping.
Switched it off once to move it to its permanent place from the table, but yes.
Iām positive itās not the clock source, yes. I have a lot of MIDI-clocked devices around the studio and the Tonverk is the only one that shows any kind of sync issues.
I have issues with the autosampler. I tried to autosample my Yamaha CP reface via audio cables and midi. Some of the samples being recorded have a start latency. When I press a key the sample does no play immediately instead there are some milliseconds delays. Most of the samples start immediately. Itās only a minority of samples.
Have you tried running it again Iāve had issues in a first pass and then they were corrected by re-sampling again not convenient but worth a shot.
This issue was also reported in Loopopās review video IIRC. Seems like slight bugs in the autosampler still, perhaps?
There might be some background tasks going on which cause unintended lag, messing with the autosampler process⦠or a million other things the devs surely know more about than meā¦
Unit has gone back today returned. Wont be getting another, its second brand new Elektron unit I have received that has been defective.
I can wait for a patch if that would fix the problem. If itās a broken unit I have to send it back. A clear answer from elektron would be helpful.
I recommend you send them a message through their website. No telling how much they read what goes on around hereā¦
I am observing something strange. When previewing the lofi kalimba multi instrument, it sounds fine. When I play it after loading, it is slightly distorted (no effects, overdrive, routing or similar applied). I can get it back to undistorted by dialing back trig velocity to 46. Very noticable on note A5 when going back and forth between velocity 46 and 47.
Could this this be some kind of normalization in the sound preview?
There is no way to get the kalimba to sound as loud as other instruments without it distorting I suppose? Level and amp vol are maxed on the track, velocity above 46 distorts the sound.
previous releases were on iterations of a platform that has now been in mass production for 8 years. this is a new platform and dramatically increased complexity, and they also changed the underlying development framework to embedded rust (and one has to assume thereās RTOS and/or some version of embedded linux in the mix somewhere to make development on this platform easier going forward, vs previous bespoke operating systems). thereās gonna be bugs.
edit to point out that one of the big advantages of these changes in platform and development approach is that they will very likely be able to reduce dev and testing time on new FW modules and get features in place faster than they could before once a lot of the underlying system infrastructure has been cleared of its youth bugs.
Rust, really? Nice to see its adoption! For us it drastically speeded up the development process as well as increased the overall product stability. Hope Elektron will experience the same ![]()
This is too weird. Arenāt you the only user with this problem - and occurs twice with different units?