How is the Autosampler now that jitter has been “fixed”? Are you still seeing random notes being noticeably off? That was my biggest gripe and I wonder if it’s fixed for either USB or MIDI
I’ve only done around 12 or so auto sampling instruments since the update and all have been good
5 Likes
I spent a few hours autosampling from Ableton, and have had zero issues. Very, very pleased with the process. Only annoyance, to me, is that I can’t easily figure out the range you sample from. It shows on a keyboard, but doesn’t list the notes (ie. C2).
Also sampled a few hardware synths via MIDI, which, also, worked flawlessly.
1 Like
Yes, it’s a bit annoying. They’re using their MIDI note numbers, with 60 being C5 I believe.
Autosample sounds great - in theory. Over the past few days I’ve tried to autosample various synths with a 40-50% success rate. Audio comes in, latency is calculated, I always go for 0-127, only one velocity layer. Even though the sampling process finishes without error message, about half the created multisamples don’t load, there is an error message. Is it me? Are others having similar issues? I really didn’t pay north of 1k€ to have to debug the files created by Tonverk.
1 Like
I got my Tonverk last wednesday. Yesterday and today, I multisampled 30 sounds with Autosample. All of them work.
There were a couple of suboptimal results at first but that was because of operator error. Now that I have understood all settings, it works the way I want, every time.
The most common user error might be to forget pressing the Test button before starting the sampling. I now press it a couple of times and watch what latency I get. Then I press again until I get a value in the middle of the range. I don’t know if this improves things but I consistently get excellent results. Also, I sample a sensible note range. Usually 48-84.
Loading the presets I made with these samples has so far never failed.
3 Likes
Yes it’s completely sorted
yeah, i’d say autosample works as it should maybe 40% of the time that i’ve used it
tonverk has sadly been delegated to a $1500 dirtshaper / degrader / warble fx box for my dn2 until the bugs are fixed (or it’s sold)
I’ve multisampled about 40 things and all of them appear to work perfectly, as far as I’ve used them, that is.
I’d also like to know , have you run your samples through the arp ?
Because when I had a TV the timing through the arp would be wrong because of the different start times of the samples, so you wouldn’t get straight 16ths for example.
I only ask because they would sound ok with chords and lead lines , but the arp exposed they were wrong.
Same, I do the average latency thing and similar note range (mostly to save time.).
If I consistently got failures and errors I’d be contacting support and/or my dealer for a replacement
That’s not normal, I multisampled my Protein last night, about 25-30 times. Every single patch was good.
I’d be looking at my setup if this was happening and eliminating other physical errors, trial an error with new cables etc.
Tonverk is pretty solid multisampler, I haven’t had a single error across about 80 patches now.
You can run into settings problems when you cancel a sampling process once it’s underway, but that’s to do with settings going back to default values without you realising, rather than it going wrong.
2 Likes