Controlling Track 16 mixer make sense !
1 Like
I load 50gb samples when booting takes a minute.
No not the spinny thing, the whole device and project and sounds all loaded.
It’s your card not tonverk
1 Like
Interesting. My card is the card that came with it, so I would have guessed it would be more efficient.
More efficient? The general consensus is the provided cards aren’t the best, and you should update ASAP.
I believe one user noticed a 50% decrease in boot time when they tried another card (similarly loaded, I believe).
This:
1 Like
I am using the default card as well. I’m perfectly happy with the 1 minute wait time. I sit and sip a coffee and do a stretch or two then it’s good to go. Can’t really complain to be honest.
If you are having 10 minute+ load times something is probably wrong with a sample or elmulti or eldrum or something that you are loading or maybe an issue with the card. You could try a different card or maybe try formatting your samples and loading a small bunch at a time and see when the issue starts.
I am also loading sample form mars samples many that I converted to elmulti files.
But I guess I’m referring to my project being ready not all samples loaded into RAM so maybe you are right? But I only care about my project sounds loading up. It will take me several more minutes to select track, think about what I’m editing, decide to add something and by the time I start browsing 5-6 minutes have passed and everything is loaded to ram anyways. I guess maybe on a new project you have to wait 5 minutes but it isn’t like you can’t start browsing kits and working on stuff while more loads. Personally I just flick it on and go make a coffee come back and it’s ready, problem solved: D
My point to him was that his load times seem abnormally long, but yes you can get a faster card
Last weekend I tried seeing if the size and number of added WAV files made a difference to boot time. I generated the files with a Python script, which I can provide if anyone’s interested.
This is purely about boot time, with an empty new project loaded & ready, so I didn’t see the “spinny thing” at all.
- Before the extra files => 25 sec
- Extra 10GB (100 x 100MB) => 25 sec
- Extra 10GB (100,000 x 1MB) => 25 sec
So just putting files on the card does nothing to change the basic boot process. Seeing the samples pop up in the list was different, of course, It took much longer (several minutes) to finish loading the list of 100,000 x 1MB samples than it took for 100 x 100MB samples (~ 5 seconds). I didn’t try scrolling to the bottom of the 100,000 sample list, but there were no errors.
So, I conclude that the spinny thing is what you see when Tonverk is loading samples in to RAM for the active Project. You don’t get it at all just from storing samples on the card, even hundreds of thousands or tens of GB of samples. I know this might be “obvious” but I think it’s important to clarify, since I have seen posts saying things like “I put 30GB of samples on the card and now it takes forever”.
Also: when loading samples in to RAM for a project, the GB and card speed matter. When reading a list of sample names (presets, etc.) from the card, the numbers of samples is what matters, not the GB, since it’s not actually loading the sample in the process.
3 Likes
I just want to clarify to everyone that I’m not the one who has 10 minute load times. That was another user. I just raised the initial question about load times as compared to the M8 when loading the same amount of data. Appreciate the discussion, though!
I don’t think m8 preloads samples tho. it reads samples off the sd card in real time, no loading into ram afaik, so I guess the only loading it needs to do is midi data & config type stuff for the current song.
1 Like
Repeat : Not a Tonverk issue ! - - It was a bad SD card
This is updated/corrected above - it was down to a rogue/inferior card - when the user switched back to the stock card the loading issue was completely gone !!
It’s a non issue … unless you expect dodgy cards to deliver good performance
3 Likes
Check out this video. The compressor is on these electron units. Make a hissing crackling sound at the end of songs or if you let it ring out and don’t hit the stop button anybody else getting this and how do you stop this if it’s even possible am I the only one?
https://youtube.com/shorts/e3e12ZMbAJc?si=dl_2Dh01clfJ_mRX
Without knowing what all the settings are it’s hard to say where that is coming from. Chances are the compressor settings are revealing something from the depths of the mix, most likely a combination of some of the fx. Go through all the fx, turning them on and off one at a time with the compressor on, see what effect it has on the sound.
2 Likes
Yeah, the noise generator in warble or dirtshaper will do that, though it can be audible regardless of compression settings
Loads of stuff in the Tonverk adds noise, the compressor will bring it out!
It’s a feature, not a bug!
1 Like
Not a bug compressors do this depending on sounds sources…
Depends on the compressor threshold, too: it only acts on audio above the threshold. So raising the threshold might help the problem.
1 Like
What kind of card do you use on your Tonverk?
I’m too young to be a Boomer, but I am Generation X, and so my context for questions about MIDI, Latency and so on includes articles like this one in Sound On Sound from 2002.
The author does some measurements with hardware synths, and comes up with figures like 3.2ms for the Korg M1, between the start of MIDI Note On data in the cable to audio coming out the synth. The latency does not include delays in keyscanning or computing the MIDI command, which was impossible to measure but would be at least a ms. Performance over USB (as it was in 2002) and using soft synths on PC (MME, ASIO) was worse.
It’s an interesting read. 10ms, while not yuge, can definitely be improved upon, in my opinion. But having experienced PC DAW latency in the past, dealing with MME vs. ASIO drivers for example, it’s a little triggering to me to see some people complaining about “latency” in general terms without quantifying what they mean and how they experience it. There was never an expectation of zero latency in anything that has a computer involved, from the Yamaha DX7 to the Tonverk, Macs or PCs, Fairlights or Synclaviers. 
4 Likes
When people say latency in a general sense they’re using it as a shorthand for noticeable latency. You could almost say it’s a bit of totum pro parte at work (latin for “whole for the part,” a metonymy that is a common figure of speech in colloquial English).
e.g. When somebody says the police came by you know they aren’t really referring to all of them… likely just Sting.
4 Likes
Okay, so I got a pair of wireless headphones that claimed (and measured by some even) a 20ms latency. When I used that on TV, it’s still in a tiny way, perceptible between hitting the slim keys and the sounds coming forth. Nevertheless, it’s very suitable for regular jamming and curating up your tracks. Recording on time could pose a different challenge.
TLDR; 20ms is not good enough for hardware and a wired connection.