One Synth Challenge #173: Bucket Pops and Bucket One by Full Bucket Music (exponent1 wins!)

[doctorbob]

Pro tip: Bucket Pops has multiple outputs you can use for the drums~!

Indeed. Strange beast to find ... like the old rhythm systems in those old 80's keyboards ... even my dual manual + bass pedals Kawai organ (KX 430) had this (better samples/sound though!!).
db

[MadMcMan]

Bucketpops has some sort of weird bug where when you feed it midi and then maybe some modulation it crashes when then trying to load the gui.

This can result in loss of data as i found out when using it to create multi layered percussion sounds.

Save your presets and don't rely on the DAW to save settings as when you reload you might find everything back at init

[Full Bucket]

I have updated Bucket Pops to version 1.1.4:
https://www.fullbucket.de/music/bucketpops.html
This should fix the UI crashes with the VST3 and potentially CLAP version.

BTW: If you have the chance to choose the CLAP version, pick the CLAP version.

Note that I am not monitoring this forum. If you have issues it is much safer to send me mail (as folks just did) with all the good information:

• What is you platform (Win/Mac) and OS version?
• What version of the plugin are you using (number as well as "N" or "non-N")?
• What plugin format are you using (AU, CLAP, VST2, VST3)?

Again I want to thank BJ and Richard for choosing one... no two! of my babies for the KVROSC. And of course I wish everybody good luck! I am super-excited to hear your results!

Cheers, Björn

[MadMcMan]

legend and i'll swap to the clap version. i think i used the VSTManager plugin to install things.

I have updated Bucket Pops to version 1.1.4:
https://www.fullbucket.de/music/bucketpops.html
This should fix the UI crashes with the VST3 and potentially CLAP version.

BTW: If you have the chance to choose the CLAP version, pick the CLAP version.

Note that I am not monitoring this forum. If you have issues it is much safer to send me mail (as folks just did) with all the good information:

• What is you platform (Win/Mac) and OS version?
• What version of the plugin are you using (number as well as "N" or "non-N")?
• What plugin format are you using (AU, CLAP, VST2, VST3)?

Again I want to thank BJ and Richard for choosing one... no two! of my babies for the KVROSC. And of course I wish everybody good luck! I am super-excited to hear your results!

Cheers, Björn

[empphryio]

Reaper Windows 11 wasn't seeing CLAP 7/1/23 version. But that's OK. Not going to email. VST3 works fine for both pops and one. Very nice. Thanks.

[doctorbob]

Same issue too with my Reaper ... dropped it in the same place as the Apricot.clap file - Reap just not seeing it.

dB

[ZonderP]

Anyone using the VST 2 version of Bucket ONE dares to give my brand new VeeSTeeEx wrapper a try?
It gives you enhanced preset experience - at least I'd hope so.
It's an entry in the KVR Developer Challenge 2023, which just went live today.
You can download the wrapper from here:
https://www.kvraudio.com/product/veeste ... roductions

And as a goody, I shared my first VeeSTeeExPresets file - dedicated to Bucket ONE -, for download here:
https://www.kvraudio.com/product/veeste ... /downloads

I think it makes dealing with Bucket ONE presets very comfortable - not only to select one of the 99 built-in ones from the 'Preset Picker' (you can do this similarly from within Bucket ONE's GUI) -, but also you do not need to switch away from the edit section. And when you edit a preset to your liking and want to save it in the VeeSTeeEx's preset database, just use 'Preset -> Import internal preset...' and give it a name. You will not be asked to commit your changes, when you choose another preset with the Preset Picker.

Just a short guidance on how to wrap 'Bucket ONE':
Assuming you didn't change bucketone.dll resp. bucketone64.dll to something else...

In the downloaded zip file, you'll find two 'dll' files - one for 32 bit, the other for 64 bit.
Copy the 32 bit one to the folder where 'bucketone.dll' is in and rename it to 'BucketONEEx.dll'.
When you want to wrap the 64 bit version, copy the 64 bit VeeSTeeEx dll to the folder where 'bucketone64.dll' is in and rename it to 'BucketONE64Ex.dll'. (You could also go for all lower case - if you prefer to do so...)
Then load the either 'BucketONEEx.dll' or ''BucketONE64Ex.dll' into you host.
Next step would be to use 'Menu -> Reveal in file explorer -> Presets file'.
This will show you the just newly created, empty VeeSTeeEx presets file.
Temporarily remove the loaded VeeSTeeEx wrapper from you project, or close the project completely - just so that you will be able to replace the presets file (it would be locked otherwise) with the one that you downloaded.
Important: For the 64 bit version you need to also rename the preset file to 'BucketONE64Ex.VeeSTeeExPresets'!
In case the top bar didn't show in the same light black as the Bucket ONE GUI, take a chance and delete the file called
'BucketONEEx-GUI.xml' in that same directory. It will be recreated when you open your project again and open the GUI of 'BucketONEEx' resp. 'BucketONE64Ex' and usually then the color detection mechanism works...

That's it for the start.
I hope it works for you and I'm curious about your feedback!

Thanks for trying it out,
Patrik

Edit:
Just discovered a small bug when saving an internal preset, then the name of the preset doesn't get updated to the new name at the top area (Pilot) and it also doesn't get auto-activated as active preset... - This kind of things happen with adding new features the last minute - Will be fixed in a next version. Good thing is, the new preset is in the database.

And:
Totally forgot that I added the BucketOneEx.VeeSTeeExPresets file to the 1.0.1 version zip file I uploaded late last night. So no need to go the extra mile and downloading that file separately...

[doctorbob]

Anyone have issues with BucketPOPS plugin type issues? e.g.

1. Created project using vst2 version of BucketPOPS.
2. Removed vst2 version from Reaper path so it doesn't see it ...
3. Install the CLAP version - Reaper sees it and can load it on a new track OK.
4. Open project (from 1) and the CLAP version does not replace the vst2 version of BucketPOPS.
5. The same happens if you install the vst3 version (removed clap).

No real problem, except if you need to change implementation versions as you will lose any settings.

I just wanted to move over to CLAP, and found my project just won't load the CLAP version in place of a VST (2 or 3) version. And ... yes I have tried it with a single track with just a BucketPOPS on it ... I have told Bjorn.

Mind you, it still could be a user error by an old f*rt!

dB

[ELEX]

...
Mind you, it still could be a user error by an old f*rt!

Don't know about the old f*rt bit, but I do know that the different plugin formats have unique entries in reaper's plugins ini file, so one will never load automatically instead of another.

[doctorbob]

Yup, this is true, but the devs can arrange for the ID's of the different formats to be the same, and therefore make them interchangeable .. I think ...

As I said, it's not really a problem or issue as I will keep using the same format as I started with making the track. I just wanted to check out the other formats with my existing track in case there was any extra functionality or performance gains - but no go.

dB

[Full Bucket]

Hmmm, being an economical person I did reuse the IDs...

[ELEX]

Hmmm, being an economical person I did reuse the IDs...

That makes no difference in this case, as Reaper will add it's own identifier for the plugin list. Those will always be different for different formats. Even the format of the entries in the relevant .ini files differs. Here's how they look:

bucketone64.dll=52E10651E6ADD901,1717710129,Bucket ONE (Full Bucket Music)!!!VSTi

bucketone.vst3=4B3F8F2680AED901,936489014{F2AEE70D00DE4F4E4675427566622D31,Bucket ONE (Full Bucket Music)!!!VSTi

[bucketone64.clap]
_=4753A1EAA6AAD901008ADE2250A8D901
de.fullbucket.BucketOne=1|Bucket ONE (Full Bucket Music)

Does allow for plugins with the same internal ID to coexist, which is handy. But fully excludes the kind of interchangeability @doctorbob thought possible.

[Full Bucket]

Thanks for the heads up, ELEX!

[doctorbob]

Thanks for the heads up, ELEX!

<sigh>Thanks Bjorn/ELEX. So Bjorn tried to do the right thng, and Reaper (and maybe other DAW's) had other ideas!

Not a usual use-case, probably only me in the whole world would fall foul of it ...
dB

[1234Hi5!]

Bucketone might be the quickest I’ve ever bailed on a synth interface and gone direct to changing the parameters via the daw - guess I’ll have to read the manual