CHOPGRID Happy Accident Sample slicer

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
RELATED
PRODUCTS

Post

ok, I will answer the Sequoia concern first .. just spent the last 2 and bit hours digging through, upgrading my mac to 15.7 to see if i could replicate the issue.. there was a issue with the packaging of the DMG, which seemed to be kind of specific to certain machines, just not my my intel 13.x machine, my m4 15.1 and then 15.7.7 and my m5 macbook pro running 26.4.x .. anyway, it was a small issue which has been patched.

Please do contact me if you have these issues as testing every platform and every permutation of hardware is hard..

As for midi.
Chopgrid runs as a audio effect as you are unable to route audio through a instrument. to run it as a midi instrument, set up a midi channel and you can direct the midi to the chopgrid channel. Same way you would with Stutter Edit for example.
It was a choice i had to make, otherwise it would have been two seperate plugins like Serum does, one for synth/chopping and another just for effects routing.

i hope that makes sense.

if you have a look on the instagram, there is a 1.0.24 video i made walking through it.

Post

new version online - v1.0.27 - app now runs on MacOS!
amazingly fast support, much appreciated!

Post

enjoy

Post

Version 1.0.27 VST3 still has folder creation/write issues on Tahoe. Registered version doesn't recall anything on Ableton Live 12.4.3 session load. Not the chops, nor the plugin settings..

Post

Can you define what you mean by folder/write issues in Tahoe a bit more and i will have a look today after work
This is so weird people are having issues with Tahoe so much, its my main test machine i use.. i know different versions have different quirks, but still.

the plugin recall thing is something on the production list, its a carry forward from when this was just a standalone app not a plugin.. its a bit trickier than just saving as each DAW handles it state recall differently..

Post

planet_b wrote: Wed Jul 22, 2026 7:46 pm Version 1.0.27 VST3 still has folder creation/write issues on Tahoe. Registered version doesn't recall anything on Ableton Live 12.4.3 session load. Not the chops, nor the plugin settings..
I'm on Tahoe and I can confirm this same behavior in Reason 14 :(

Post

BROEKN LABS wrote: Wed Jul 22, 2026 3:27 pm
anyway, i know its not exactly a great look, announcing a plugin to the then follow up with a patch.. but there were some really helpful suggestions both here and on email, which i rolled in to the update also.
I don't see a problem with it. Especially a one-man show. I'd be more concerned if there were no patches.

Post

The workaround is to save the Chopgrid session and then load it again when you open the song/session.

Post

Thank you for the reassurance Parma. Its been almost a year in development for the stand alone and the VST3/Plugin side has been the last 6 weeks or so.. and there are fundamental decisions made for the standalone version which dont necessarily neatly translate to a plugin version so there has been a lot of thread pulling ..

Even things like plugin state saving, the standalone (and the vst for that matter) have the save state, but just standard plugin state saving based on session is a much larger job.. and I have also been hyper aware of rolling out endless updates/patches.. obviously if something is broken, its patched.. but features i am trying to bundle them so i get a bit more time to beta test them.

its just time in the end.. my day job is eating into my chopgrid development time ..

I do want to say how much i appreciate all the feedback tho..

and yep, its definitely a one man show.. and doing all the video, graphics, social media, promo etc.. i barely have any time to make any music. i spend most days in the studio, but its working on something to do with chopgrid ..

Post

BROEKN LABS wrote: Thu Jul 23, 2026 12:12 am Thank you for the reassurance Parma. Its been almost a year in development for the stand alone and the VST3/Plugin side has been the last 6 weeks or so.. and there are fundamental decisions made for the standalone version which dont necessarily neatly translate to a plugin version so there has been a lot of thread pulling ..

Even things like plugin state saving, the standalone (and the vst for that matter) have the save state, but just standard plugin state saving based on session is a much larger job.. and I have also been hyper aware of rolling out endless updates/patches.. obviously if something is broken, its patched.. but features i am trying to bundle them so i get a bit more time to beta test them.

its just time in the end.. my day job is eating into my chopgrid development time ..

I do want to say how much i appreciate all the feedback tho..

and yep, its definitely a one man show.. and doing all the video, graphics, social media, promo etc.. i barely have any time to make any music. i spend most days in the studio, but its working on something to do with chopgrid ..
No problems. You're doing fine!

Post

Yeah, don't sweat the bugs and stuff. Shit happens.

What's more important is how you're dealing with it and so far it's been exemplary.

The updated build feels way more solid. Tempo shifts are much more better.

I've been throwing longer loops into it and the results are fantastic.

Despite its complexity it's very quick to get results.

Post

Thanks.. yeah there is a definitely a lot to unpack in it.. I wanted to make it super easy to get things happening but also not be just a toy 1 trick pony plugin but with a lot of depth for people who are keen.

its hardwork tho.. i essentially created 18 plugins in 1.. and then add getting that to be a vst3 to run cross platform and across every daw permutation and release.. im sure there are obscure DAWS i havent even heard of. and then add how different operating systems handle it .. its a definitely a thing

Someone on reddit was like "fine but where is the linux build" .. i almost had an aneurysm

Post

For anyone following along. Currently building a Session persistence linked to the DAW session, so when youi save your daw session with instances of chopgrid, it will keep its settings/slices etc.. so when you reopen its all there still like you left it.

and if you want to make a default session to open across different sessions, you use the save session feature already there.

to be transparent, this was a standalone app which then was ported to a VST, which is why some of the features you would assume from a VST are not as forthcoming as you would expect.. so a lot of the plumbing for multiple instances of chopgrid just isnt really there for saving etc..

but yep, currently am working on state persistence and a few other small bug fixes like Setting persistence (midi play, gate etc) .. will roll them all out as 1.0.28.. hopefully over the weekend.

thank you for all your constructive feedback tho. hope its living up to your expectations

Post Reply

Return to “Instruments”