It was the same here…After a couple of tries, it worked. Connect Tonverk First, then the iPad. As i said, took me a couple of times… (direct Connection, no dongle, usb c both sides)
Unfortunately I can’t get it to work after many many retries, even after rebooting the iPad and the Tonverk. Tried with 2 different iPads, fairly new models. (One is an M1 and the other I don’t know) Cable used: the one in the box, port used: left most port. Also tested with a 3rd party cable. Right most port of the Tonverk is connected to the charger. Occasionally I hear the beep sound on the iPad like it would be connected to a power source. Apart from that nothing happens, no audio, no midi.
If I connect to Mac I do get audio from the Mac on the Tonverk which suggest that the hardware isn’t broken but I don’t seem to be getting any midi.
So this is very confusing, maybe something is broken on my unit after all.
I’ve read a few sketchy anecdotal comments offered up here or elsewhere, perhaps ‘suggesting’ 20ms or so of ‘latency’ … not sure of the context, but anyway, not quite sure about that …
… Here’s a bit of community science to put some data down
I loaded an impulse of 5ms duration into both devices, the DTii was clocking the TV MIDI and its inputs were fed into the TV … the output was streamed via usb into Audacity for convenience
On one step the sample is panned, the DT was set Left and it was right on TV
On another step the impulse was centred on both, you see the ‘delay’ more clearly here although it is inaudible when monitoring, the impulses stack into one slightly stretched one
The latency through this configuration sees the DT Impulse arrive just under 0.8ms behind the TV ‘reference’ point
I’ve no idea how this stacks up compared to other Elektrons, but it’s musically inaudible in this test although there could be phase cancellation at certain fixed frequencies, but that applies to any latency which there always will be
Seems like there’s not much of an ‘issue’ to dwell on in this particular use case, but ymmv …
Here’s a slightly dense collation of that info in a diagram fwiw
Just saved a diagnostics file on the SD card and can confirm it’s running linux:
Feb 27 17:26:04 machbike0 kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Feb 27 17:26:04 machbike0 kernel: Linux version 6.12.34 (oe-user@oe-host) (aarch64-esp5-linux-gcc (GCC) 13.2.0, GNU ld (GNU Binutils) 2.42.0.20240216) #1 SMP PREEMPT_RT Mon Jun 30 15:39:32 UTC 2025
Update: We can now also confirm the platform is running on ARM64 (aarch64).
Well, if you are running a different OS than other people, its inconclusive at best. Something somewhere in the code might have changed, which could have “fixed” the issue compared to the OS version other people are using, even if it didnt specifically even try to address the issue in question.
Main thing is, your findings sound encouraging! Hopefully when that OS update comes, every TV out there will suddenly have such a decent RTL
Hey does anyone knows why you can’t automate Subtracks Bus/Sends routing via Plocks ?
Is it because the track have 8 built in seq tracks, meaning that it’s not possible to have a “main” sequence to automate main parameters of the track ?
Not sure if we will get an answer, but I would guess the answer is minuscule/no difference. I was mainly asking in the context of reads for project and multisample loading. If someone wants to pull the specs off the factory SD card that will at least give users a minimum baseline of what not to go under when shopping for higher capacities - because it’s not listed anywhere.
Hmm unless I missed a hidden shortkey or setting, Tonverk does not have a PER PATTERN MODE, only a PER TRACK MODE. At least it’s default on PER TRACK MODE and I don’t see any way to switch it (as seen on the DT(2)/DN(2)/ST).