Speedrum updated to 2.4.0

[Thomaz]

I can't say for sure, but if the crash happens on GUI reopening, it's possible that the problem is related to Direct2D or the graphics card driver. Especially if it started happening recently. If you can, try to update them first, or downgrade if you know that there was a recent driver upgrade, to see if it has an impact.

Thanks for the feedback. I’ve checked the drivers and everything else, but it all seems to be the same as usual — no updates or anything like that. Who knows what Microsoft is messing up behind the scenes with their updates again. Over the next few weeks I’ll have the chance to try everything on a different machine, so we’ll see how it runs there.

I will be doing a bugfix update soon, probably in the first week of the new year, it will also contain some deeper fixes to the API I use, so you can try that

Sounds great - thanks for your efforts.

[apisonic]

bugfix update v2.3.3
download as usual at https://www.apisonic-audio.com/
changelog at https://www.doc.apisonic-audio.com/spee ... gelog.html

All the best in 2026 to everyone!

[mabian]

bugfix update v2.3.3
download as usual at https://www.apisonic-audio.com/
changelog at https://www.doc.apisonic-audio.com/spee ... gelog.html

All the best in 2026 to everyone!

Thanks! The Linux archive contains a VST2 file with name libSpeedrum2.so instead of Speedrum2.so.
VST3 seems correct...

Is that ok?

Thanks,
Mario

[apisonic]

bugfix update v2.3.3
download as usual at https://www.apisonic-audio.com/
changelog at https://www.doc.apisonic-audio.com/spee ... gelog.html

All the best in 2026 to everyone!

Thanks! The Linux archive contains a VST2 file with name libSpeedrum2.so instead of Speedrum2.so.
VST3 seems correct...

Is that ok?

Thanks,
Mario

Thanks for reporting it, I've reuploaded it with the correct name.

[sinkmusic]

Thank you, Apisonic!
Speedrum rocks!

[Thomaz]

Many thanks for the update — much appreciated!
Unfortunately, the plugin is still crashing on my system. It’s also behaving quite strangely now and sometimes seems to delay Reaper’s actions.

For example, when I make changes to a saved kit and then save it in Speedrum using the save icon, the saving process appears to take a long time. During that time, Reaper becomes very sluggish and unresponsive.

The original issue is also still present: if I open and close the Speedrum window several times, Reaper eventually crashes completely.

Could this be related to the Speedrum kit folder? Mine is quite large — I’ve already stored several gigabytes of kits there.

[apisonic]

Many thanks for the update — much appreciated!
Unfortunately, the plugin is still crashing on my system. It’s also behaving quite strangely now and sometimes seems to delay Reaper’s actions.

For example, when I make changes to a saved kit and then save it in Speedrum using the save icon, the saving process appears to take a long time. During that time, Reaper becomes very sluggish and unresponsive.

The original issue is also still present: if I open and close the Speedrum window several times, Reaper eventually crashes completely.

Could this be related to the Speedrum kit folder? Mine is quite large — I’ve already stored several gigabytes of kits there.

Please contact me via the support contact form on the web so we can continue there where we can exchange files, so I can try to see what's really happening because I assume it's something very specific.

[Sascha Franck]

Hi there!

I'm currently evaluating Speedrum.
I like it quite a bit already, but I've got some questions:

- When you preview samples in autoload mode, they are always loaded onto the selected pad permanently. Is there a way to get back to the previously loaded sample others than reloading the entire patch? Ideally, this "preview in context" mode should only load samples temporarily, waiting for a final confirmation (that's how Battery 3 did it and also how TAL-Drums is doing it, very convenient).

- Does the slicer create a corresponding MIDI file that can be dragged into your host? This is what I'm familiar with from other slicers (reaching back to good old ReCycle), but I couldn't find any such an option on the UI and it's not mentioned in the manual, either.

- Are there any modulation options going beyond 1:1 MIDI CC control? I assume there aren't (nothing in the manual, either), but I might miss something. And in case there aren't, are there any plans to add such?

Cheers!

[apisonic]

- When you preview samples in autoload mode, they are always loaded onto the selected pad permanently. Is there a way to get back to the previously loaded sample others than reloading the entire patch? Ideally, this "preview in context" mode should only load samples temporarily, waiting for a final confirmation (that's how Battery 3 did it and also how TAL-Drums is doing it, very convenient).

Yeah, it's an autoload, not a preview. But I definitely plan to implement the preview mode in the upcoming updates.

- Does the slicer create a corresponding MIDI file that can be dragged into your host? This is what I'm familiar with from other slicers (reaching back to good old ReCycle), but I couldn't find any such an option on the UI and it's not mentioned in the manual, either.

Not at the moment, but it is one of the things that will be implemented in the next feature update 2.4, which will contain primarily Slicer improvements.

- Are there any modulation options going beyond 1:1 MIDI CC control? I assume there aren't (nothing in the manual, either), but I might miss something. And in case there aren't, are there any plans to add such?

Not in the classic sense (dedicated mod envelopes and LFOs), although there is modulation of certain things via the sequencer... a complete modulation system is planned into which some current things will be assimilated.

[Sascha Franck]

Many thanks for the answers, appreciated!
Unfortunately, for the time being I will then likely go with TAL-Drums as previewing, while ok in Speedrum, is more elegant and because I really like being able to drag MIDI patterns from sliced loops into Logic.
I promise to reevaluate Speedrum, though, once these things are in, as I really like the easy to use interface and some other things (the humanize options are really welldone IMO).

[Sascha Franck]

Ok, before I make a decision (fwiw, I'm not in a hurry), do you have a rough roadmap about when the 2.4 update may come?

[apisonic]

Ok, before I make a decision (fwiw, I'm not in a hurry), do you have a rough roadmap about when the 2.4 update may come?

I don't like to give estimates, but roughly, let's say the beginning of spring

[Sascha Franck]

Thanks. I may even wait for so long, not sure.
As said, I'm not under pressure, just want to get rid of Battery one day.

[apisonic]

It could easily be sooner, which I hope, this was really rough.

[KTlin]

I noticed a peculiarity with the velocity curve in Speedrum (the global curve as well as the per pad curve). It behaves completely different than the velocity curves in all the other samplers that I've ever used, but because it's quite complicated to explain the issue here in writing I recorded a video. I'll send it to you in a PM.