Device Details

Device Overview

Name/Version: Bass Station II Editor 2.0
Author: JoeM  
Description: A Max For Live patch to control and observe parameters on the Novation Bass Station 2

Known issues:
Native SYSEX is Mac only

**
1.0 versions were based on the work of Justin Foster (TheRiteOfBass)
http://cycling74.com/project/bass-station-ii-patch-editor/

V 1.1
- Live UI updates from hardware changes
- Random Feature
- Bug fixes

V 1.2
- Added drag and drop sysex file patch support

V 1.3
- Support newer SYSEX format

V 2.0
- Complete rewrite of MIDI messaging (no longer depends on embedded patch from Foster)
- SYSEX message passing via native object (Mac).
- Support CC messages via router
- Ability to select different MIDI routings
- Custom UI Elements when using Max 7 in Live
 

Device Details

Tags hardware
Live Version Used: 9.1.8
Max Version Used: 7.0.1
Date Added: Aug 02 2014 18:13:21
Date Last Updated: May 14 2015 04:09:37
Device Type: midi_device
Download URL (report link) https://www.dropbox.com/s/mjf4phk5z260lmr/Bass%20Station%20Editor%202.0.zip?dl=0
License (more info): AttributionNonCommercialNoDerivatives


Comments

GREAT Device - UI update is not working for me. I'm on a MAC. Can you explain how the Bass station router works? I've tested the OSX version. What settings in live Midi panel are required?

Nice work fella

Hi,

Thanks, glad you like it.

I'm not sure what you mean by UI update? If you mean, "turn a knob on the bass station, see it on the device", that feature isn't in there yet.

The patch can decode incoming SYSEX patch dumps but it doesn't recognize all the Continuos Control messages. If you want the UI to reflect what the device's current settings are you need to use the router and request a patch dump using the button on the lower right of the "Bass Station" logo text.

To use the router:
1) Plug in Bass Station 2 via USB
2) Open the router. It should auto-select the Bass Station MIDI in and outs. If not, select them from the drop downs.
3) Open the M4L patch. It will auto connect.

Actually, technically the order of 2 & 3 don't even matter. They'll find each other as long as they're running. They connect using a local network, not any of Live's midi routing since it blocks SYSEX data. No extra settings are required on the Live side.

Also, I plan on adding incoming CC control.
It's not difficult it's just a lot of stuff to wire up.

I should be able to easily add drag and drop .sysex patch files and maybe even a patch browser. As soon as I find the time.

Hey,
thank you for this !
But what I really miss is a way to automate the "speed in beats" for the LFO !
I can't map this to an Modulator in Ableton :-(
Is it possible to implement ?

some other ideas are:
- random possibility
- preset slots with morph

Thanks, best reg

frank

Hey Frank,

Thanks for the feedback.

The new version 1.1 should fix the problem with "Speed in Beats" for both LFOs.

I also added a random feature. It's random for MOST parameters but not all. Things that would really make the patches unusable are locked to their current setting. Some examples,

- OSC tuning course and fine
- LFO to pitch
- Mod env to pitch
- OSC 1 mix amount (sub and 2 change)
- Noise, Ext, Ring mix amount
- LFO keysync
- Distortion
- OSC filter mod
- LFO slew
- others?.

I think this makes the random feature more usable. I get good sounded patches almost any time.


As far as your idea for presets and morph.

You can save a snap shot of the patch into Live. Every parameter is a M4L native object to Ableton should save the current state. There are some M4L patches already available that can take snapshots of device states and morph between them.

It's unlikely that feature will be added inside this patch as it would be a lot of overhead to store the patch state separately.

I'm looking into the ability to load up and store SYSEX presets though so you can mange your patches as syses files, with possibly an browser in the patch. I'm waiting for feedback from the Max forum to fix a big I've had when I tried building this.

I managed to figure out what was wrong with my sysex importer, so I just did another quick update to 1.2 with that feature added.

Hi there

This looks great. Is it compatible with 64bit Live?

Hi Joe,

I used your patch to make a simplified version that works for my setup, i.e. one direction controller.

http://www.maxforlive.com/library/device/2818/bass-station-2-controller

Thanks for all the work you have done. Saved me a tonne of time :)

Updated the patch to work with the new SYSEX format.

NEW VERSION COMING SOON

I have a new test version that works with SYSEX without needing to use a patch router. It will be Mac only at first since it requires a new external I wrote in C.

I'm currently testing and working on updating the UI to move the settings for this new feature and handeling of patches to a popup instead of cluttering up the panel.

Also will have a new custom UI elements for users who are using Max 7.

Hey,
great work, again ;-))

It makes a lot of fun to use .

(vers. 1.3)

But, please mapp the controls to make more sense when used it with Push
like with http://www.maxforlive.com/library/device/2818/bass-station-2-controller

And, I don't know why, but in my case, I loose sometimes the connection to the Hardware. I used some mfl midi-LFO's to control some parameter...
But maybe next time I will take the integrated LFO's in the full screen version (nice idea)

Ah, one thing,
there are some "live.menu,live.button and live.tab" in the selection of automation / envelopes !
would be great to have the right names.

Thanks
,-)

2.0 version posted. I think all the previous issues with parameter naming are fixed.

2.0 has experimental, (but stable for me) support for a new native Max object to transport SYSEX/CC messages bidirectionally to the hardware without needing a router patch or, in the case of CCs, having to have the track armed for live UI updates.

Native routing is OS X only. In fact, i haven't even tried opening thison a Windows machine so I do hope it doesn't crash. External Max patch router is still support for Windows and Mac as previous versions.

The only planned features I have left are group random lock/unlock like I have in my Hawk-800 editor that I posted yesterday. As in previous version, random is pre-programmed to only effect the paramaters that are considered, to me at least, most musical. Therefor it doesn't change things like OSC tune modulation, noise volume, and some other parameters that are more than likely to result in patches that are considered more SFX that musical. If this really bothers you and you can't wait for the next release, it's trivial to change the allowed parameters. Simply open up the main JS(processcc.js)file in the cc subpatch and change the false values to true for the random parameter dictionaries.

What can I do to help you make this thing work on windows? So far it loads, but none of the variables seem to initialize properly and it doesn't appear to be sending anything to or from the bass station.

It should work on Windows with the router, but I don't have a box to test on. I've been swamped all summer with day job project, I plan on getting back into my Max patches once the long, dark, New York winter comes in.

Hi! I hace a problem I hable two bass station II, when I put the editor in two tracks intro Ableton I don't know how configurate it intro Options, I can see severas ports that I haven't like slim phatty And daemon ports,. But I can't see my ESI M8u ports or bass station USB ports, If I turn the ports to bass station And Live opcion when I change a program It's catch the val?es of the bass station, but If I move any parameter ?ntimo the editor in a track, in live mode Options sends the same parameters to the other bass station 2 though it's configurate in another track...How can I resolve the problem?

Best regards

I think possibly what's happening is that your Bass Stations are set with MIDI Remote In activated in Live's preferences. That means that Live will receive the CC messages that the hardware receives. Now if that's the case, and you have a track armed with "All Devices' as the input, then the CC messages that one bass station sends when you a control get routed through Live and into my patch and out to the other Bass Station.

The way around this is to select the specify BS for the track in the input devices, or only use the Router or CoreMIDI (if on Mac) modes.

The router is pre=programmed to a specific port number, so if you have two instances you'll have to open up the device in Max and change the port number to be unique per device, otherwise you'll have the same issue where 1 BS input is being routed to both Max devices.

Login to comment on this device.

[ browse device library ]