There’s more confusion/discussion here
Just a guess on my part on your issue!
hmmm… I would still argue that it’s rather a midi issue, cuz with TV as master, sending clock and transport downstream results in the other devices being delayed. I might be completely wrong tho.
Anyway, I’m wondering what’s the culprit and if this can be fixed with the current architecture. From what I know, TV’s OS is built on Linux, so this might be some system overhead. The only other time I noticed similar latency was with Waldorf Iridium, which is built in a similar way.
Check my results, it completely depends on audio routing, audio latency involved.
TV is 3 ms ahead master and 9 ms late slaved.
So TV master, seems like transport START is sent 12 ms after TV audio (really not sure about that, I would like to mesure it). But if slaved device is plugged in TV inputs, you get 15 ms latency…(4 ms if TV is slaved)…
There is audio latency, would be technically possible to reduce it with buffers size but it probably won’t happen for performance stability ; for me the main problem is the lack of audio latency compensation settings…
1 Like
Anyone know what’s going on with tonverks firmware getting buggier? Sd card was not removed like it says, and on restart I got this lovely message, a second reboot “solved” it but worrying to say the least.
1 Like
I wonder if this change:
Tonverk now attempts to automatically repair errors in the SD card file system.
is causing all of these weird boot/project/sd card issues
I’m still on 1.3.1. Feels like it’s better to wait to upgrade as the bugs I currently have are not causing any real issues for me
1 Like
Just reporting back that since 1.3.2 I have not seen any phantom encoder movements. Not a single one. 
Hopefully it stays that way.
Edit: I have been using it for several hours every day since 1.3.2, so I’ve spent a fair amount of time with it since the update.
Maybe someone else who has this issue can report back about it as well?
3 Likes
I have been getting “windows detected an error” on two different (brand new) SD cards when entering USB DISK MODE since 1.0.
i don’t really understand. are you saying there’s a straightforward way for have TV as midi slave and also have the audio in sync? or does TV have to be midi master?
knobs are still going on mine on 1.3.2
what’s the deal with the twitchy encoders? is this def a hardware issue that has be repaired physically? I haven’t raised it with support yet.
1 Like
Ughhhh, sorry to hear it.
Have you tried a new project? Just curious. I started fresh with 1.3.2 . Maybe there’s some weird software bug remnant on older projects after an upgrade. Dunno, just spitballing.
Yep I have those ghost movements even on 1.32 . Hope this will fix on next update 
yup i made a fresh one on 1.3.2 and still. its weird that its supposedly a hw bug but it kinda comes and goes, could never quite pinpoint the cause/trigger
Since 1.3.2 I’m pretty sure it’s gone on encoder E for me. Need to check encoder D, but that was much more sporadic with the ghosts than E anyway,
1 Like
No. I am saying latency also depends on audio routing. Did you check the link ?
Best way to connect/synchronize Tonverk and Digitone 2? - #15 by sezare56
Hi, I have only track 7 no play recorded trigs from sequencer…
I hear the sound when I play notes, but nothing from sequencer…
Typically mutes. (Happened to me today after swapping global / pattern mutes)
1 Like
Yeah thx a lot !! No purple mute but green muted !
Regards
1 Like
oh I get you, yeah thanks that’s helpful
1 Like
Since the most recent update I’ve had an issue on boot 2 times now.
When I start up TV it hangs on the loading screen, no matter how long you wait. Need to switch it off, which brings up the power down yes/no screen. Hitting yes it will half shutdown, like screen goes blank but there are still some back lights on the buttons. I need to plug pull. When I re power and turn on its fine.
Concerns me as I’m worried It’ll corrupt my project or worse damge the TV itself