Bass Station II Patch Editor


This Max patch helps the Bass Station II user get an overview of their patch. It can be used as a software editor, making it easier to access some of the on key functions.  There is also the option of sending LFOs to modulate the Bass Station’s parameters.

Download

How did this project use Max?

Max was used to interpret the MIDI sysex patch data to form a GUI. The same GUI can be used to send cc's back to the synth.


March 25, 2014 | 8:58 am

This is just what I was looking for.

I’d love to make it a Max for live device so I can load the right sound and automation for projects I save.

A few things that are really missing (unless I’m not doing something correctly) is updating the GUI when I twist knobs on the Bass Station. I’d like to type values into dials.

Also I don’t know if it’s possible, but sending a dump automatically from the synth to the GUI when I switch a preset would be great!

I’ll see if I can hack it together when I get a chance to open the patch.


April 8, 2014 | 8:28 am

Cool, I have now added a, pull patch from hardware button.


July 29, 2014 | 9:36 am

I started a Max for Live version of this. I’m not great at Max, but it’s pretty easy to just add M4L UI elements and plug them in where the existing ones are and then modify the presentation mode to only display those.

Wish this had CC in for two way UI updates. If I have free time I’ll take a crack at that but like I said, I’m not very good at Max and this is quite a sophisticated patch for me.

M4L doesn’t support syses but you can use a standalone patch running as an APP to plug in two way sysex using Max’s cross patch protocols. For example. the Juno 106 editor does this.

http://www.maxforlive.com/library/device.php?id=220

SysEx-Linker is here, http://www.neilbufkin.com/NB/News/Entries/2012/6/30_Juno106Control_-_Big_Update_by_Fabrizio_Poce.html


July 30, 2014 | 9:11 am

Ok, so I ended up spending an entire day on this.

I made a M4L patch with modular UI patches. It requires THERITEOFBASS’s original patch to be embedded. I had to make some minor adjustments to the original patch. I added [send] and [receive] objects to all the original UI patch points so I could forward the calls to and from the M4L UI elements in the parent patch.

I will post it up in a couple of days. I have to finish the filter and ARP sections and make some UI tweaks to maximize the small space. I also have to get the SYSEX companion patch fixed up. I have sysex to the BSII, haven’t finished wiring up the receiving patch dump.

I would very much like to add UI updates of changes made on the hardware. This might have to wait for a second version. I want to minimize the amount of hacking done inside THERITEOFBASS’s patch so that improvements and features to the original patch stay consistent with the M4L version. If/when I do add incoming UI updates I’ll try to do it in a way where it updates both UIs.

Actually, as is, if you open up the Max for Live patch and open up the sub patcher with THERITEOFBASS’s patch, UI changes from the M4L elements update the full page UI. If I can figure out how to use the Window element I may also add a button then to display THERITEOFBASS’s patch as an alternative UI. Though I think integration with Live’s modulation and mapping features would only work with the M4L UI elements as they have special bindings for Live’s API scripting such as being able to Macro Map.

Look for it in a couple of days. THERITEOFBASS, I’d like permission to cross post the patch on maxforlive.com with your credits attached if that’s ok as well.


Viewing 4 posts - 1 through 4 (of 4 total)