Haven’t encountered many problems so far, but what I really would like a solution for is the differences in volume when you tweak multiple patterns separately. I guess that kits are the answer, but are there workarounds I could use now?
2 Likes
I’m sure this has been addressed, hopefully someone can point me in the right direction- how can I offset the small but noticeable delay when trying to record Tonverk directly over usb into Logic? It’s not on the grid. I have transport set to in from Logic.
Is there an easy way to know what samples fail to load when copying over and opening a (3rd party) project?
I’m also curious if when you’re going from one synth patch to the next to auto-sample, does cancelling the process usually decrease the file size?
Is it a cache thing when the device over-states the file size when you don’t?
Has anyone really been far even as decided to use even go want to do look more like?
This is called latency compensation , not tonverk exclusive sadly google it
I haven’t been able to get USB MIDI out to work on various other gear. I’m just trying to send MIDI clock to one of the bastl kastle2 units. Doesn’t detect no matter what I do.
Also concerning midi over usb, had lots of issues trying to get the torso t1 to work properly sending midi into the tv over usb.
Is midi over usb one of the areas where the tv is known to be in need of bug fixes?
2 Likes
yeah, i think tonverk is fine with receiving clock but difficulties arise when it attempts to sync to other gear
When TV users bring up latency, what are they talking about? Is it real-time playing latency (as in how it feels to input notes with an external keyboard or the TV’s keys) or sync problem with other devices?
Imagine you have another drum machine and Tonverk. Both are receiving midi from the same clock source.
The timing that the Tonverk’s trig “hits” is behind the others. Imagine this was a kick, for example.
Additionally, imagine that it’s inconsistent: sometimes it sounds like they both trigger the same kick around the same time, and other times the Tonverk lags noticably behind.
There’s another type of latency with midi I’ve noticed, which is that when I play a melody into the Tonverk, it plays it back at a later step than, say, it I played the same melody into an external sequencer that triggers the same sound.
2 Likes
I think the problem you’re running into is that the other gear has to be a USB host for this to work. The TV is a USB device, not host. So it’s not really a bug. (But would be a cool feature if they added host functionality! And I know others have requested this in the feature request thread.)
little of column A, little of column B.
There’s a lot of processing stages in TV and it will have audible latency to send audio through it with multiple effects and bussing etc. vs just bypassing it. it apparently also has USB audio latency issues unrelated to that but I can’t speak on that since I don’t really record it that way. It had pretty bad MIDI sync issues early on receiving a MIDI clock but it’s pretty good now in my experience, though I don’t really use USB MIDI with it and that may still be less tight than DIN MIDI is. I can layer TV hits with Syntakt’s with no audible issues, but to do so I usually find it easier to have the sequences played on each device because that gives me a more dynamic drum sound than just sequencing both of them externally with the same pattern would.
Thank you for clarifying this! Aha, but I think that applies maybe to the T1, not to the Bastl Wave Bard? The Wave Bard doesn’t get a single thing from TV, which TV should be able to send midi over USB, right? Or is this where TV needs to be a host?
With the T1, what was weird was that I got some notes, but with unusual behavior, when playing into the TV machines from T1 over USB. Host functionality playing a role here too maybe?
Will move over to feature requests if needed too, but still curious about what’s what here in case anyone knows.
I’m finding the sample editor a good substitute for the lack of slice mode.
The method i’m using is to resample a break (or whatever you want to chop up) into the machine and use the editor to set the start and end points, and basically save as many individual slices as you need. What’s nice about the editor is you can zoom in on the start and end points, using function to snap to zero, and once you save a sample the previous start and end points remain, so all you need to do is move the start point to the end point, then move the end point to the next slice point. I set loop to on in the editor when auditioning and save all the samples to the same track. It’s a quick process if you skip naming them (you can always add them to a specific directory after). Within a couple of minutes you’ll have a handful of “slices”.
Once you have all the samples, go to the track you saved them to, set the track to mono and add as many triggers as you created and sample lock each one.
You can then use placement = randomize for essentially the same thing as Octatracks random slice grid.
Then plock each samples pitch, play mode, envelope, filter etc…
7 Likes
I’m no expert but my understanding is when you make a usb connection for midi or audio, one always needs to be a host.
Edit: I forgot to mention, you don’t have to use your computer for this if you don’t want to. There are devices that can be a midi host for you. I think the CME H2MIDI Pro will do it.
1 Like
An iPad works as a USB host, for example.
True but that won’t necessarily help @noisebox connect to their other devices, like a dedicated host/hub will. (Although you could probably plug a regular usb hub into an ipad and be able to route midi between the devices, assuming you had the right app…)
Yes, sorry - didn’t mean to derail. I should try with my Retrokits RK006.
I’ve done something like this with a cheap USB-C multiport adaptor attached to my iPad. Connect my Tonverk by USB-C, and my 61-key MIDI controller by USB-A, then use AUM on the iPad to route the MIDI. But I still hope for USB Host functionality at some point, for MIDI at least if not for audio too.
Quick question regarding this… do you experience timing jitter as well as timing latency with the Tonverk?
Latency is something I’d expect TBH, the processing inside the TV will (I think) unavoidably cause some latency when clocked from a device with much lower processor overhead (like a Syntakt).
System latency is manageable if there is the option in the device to adjust for it somehow (not sure if this is the case with the Tonverk as I don’t own one yet).
But jitter is a much bigger problem. I’ve searched Elektronauts for Tonverk+jitter but can’t see a conclusive answer (unless I’m missing something) to the following question: does Tonverk experience timing jitter as well as latency or is the issue latency only?
It was a thing on release FW but they fixed it
1 Like