asked Nov 01 '15 at 18:44 by wygonjinn (281)

edited Mar 28 '16 at 02:37

15
5

When will Sysex be supported by BitWig, in any capacity? Even In babysteps. BitWig dosn't need to go all out -- where you can create your own Sysex messages byte by byte, but for the love of Hardware atleast allow VSTS to pass on Sysex messages thru the Hardware Instrument device!

Sysex is crucial for setups where one has lots of (old-ish) hardware that needs to be controlled in very specific ways, and would surely be a a cherry on the cake for BitWig that is that last nudge for users of other DAW's

12next page »

Is this ever going to be on the road map?

If not, then BitWig is risking becoming just a toy compared to Cubase, and other DAWs which do support Sysex! Please re-think this!

link

answered Mar 26 '16 at 00:59 by wygonjinn (281)

edited Mar 27 '16 at 17:19

That's no good.

I code VST Editors which control Hardware Synthesizers based on the Synth's Sysex Implementation.

BitWig needs to support passing Sysex Messages from VST's -> To the Audio Interface. It does not, and support has said it's not on the roadmap to be added to BitWig 1 or 2, so I permanently made the switch to REAPER and haven't looked back since :)

link

answered Jun 02 '17 at 17:47 by wygonjinn (281)

edited Jun 02 '17 at 17:50

As for the Sysex support, I do I have some good news: I was able to prototype a controller script, catch CC events from one external device, map it to Sysex commands, and send it to another external device. So Bitwig does support Sysex at the controller level, and we can route between the devices. So if some Bitwig users have the need, there is a way.

More specifically, I was trying to come up with some external control for the Waldorf Blofeld's multi-mode (which I think is really awkward to use with the Blofeld UI). But this failed, not because of Bitwig, but because the Blofeld's Sysex support seems to be broken / incomplete. While I can dump / recall complete setups, it does all kind of weird things when I request to switch to multi-mode. And parameters for multi-mode slots are mostly missing. I am giving up on this specific idea.

But if you have an ancient synth or external FX device which needs Sysex control, this can be done in a controller script (if you have some coding skills), basically taking any midi event (CC or even notes) and map them to a Sysex command.

But I do see that this will not cater many users, and it is not what people would expect when it comes to "Sysex support" (as in editing and automating in the UI).

link

answered Dec 16 '19 at 03:09 by mindanao (72)

For interested folks: Bitwig's Javascript runtime comes as part of the Oracle JRE 8 runtime (which runs Bitwig Studio), and it is called "Nashorn Engine".

It is ECMAScript 5.1 compliant (so it is pretty outdated and will not support most of the new ECMA 6 language features and fancy code structures we see coming up lately).

However, it is pretty easy to draft simple scripts, and the runtime will reload them upon change, so it is a smooth "try and test" experience.

Bitwig's documentation is kind of "meh", some guess work and experimentation will be required to glue things together.

  — (Dec 16 '19 at 03:40) mindanao

As an update to my previous comment, the latest Bitwig 3.1 release is now shipping with the Java 12 JRE. The updated Nashorn engine is still based on ECMAScript 5.1, but it now comes with ES6 variable block scope, let and const keywords, so this helps. Classes and modules are still not supported, unfortunately. The entire Nashorn script engine is now deprecated and scheduled for removal, though.

  — (Jan 21 at 10:08) mindanao

It will be great!

link

answered Oct 27 '16 at 23:47 by kresbeatz (141)

A module for sending or receiving a Sysex Dump will be a great feature for all users which have midi synths !

link

answered Nov 19 '17 at 05:29 by Ghislain2b (41)

When it comes to the management of external midi hubs, routers or networks... Bitwig treats each port as a 'controller' and with that, comes a world of pain.....ditto for big Audio port counts. Bitwig is fantastic for what it accomplishes in the box, unfortunately it's awareness of the hardware environment that exists outside this domain is retarded (with the exception of eurorack, which is tiny in comparison to hardware desktop/ keyboard hardware market)

One does not need to compare Bitwig to other Daws to know it's retarded in the area of external hardware and in this case the sysex protocol.

This situation is holding back a very big user base in Cubase and Logic from transitioning to Bitwig.

Your suggestion of 'Stop' has been rejected, thank you.

link

answered Apr 27 '19 at 01:37 by chrisfostertv (19)

sigh. I think I will not be able to sleep well tonight... sigh...

  — (Apr 27 '19 at 02:22) fsciarra62

I think for a lot of perhaps older users, the attractiveness (at least for me) was I could use my older gear and Bitwigs modular approach to taking that older gear up a level. Much of the time, all I need is simply to be able to pass on sysex. I don't see what the big dea lis. Why can't it just send and receive the sysex on the midi channel if it can already send midi note and CC? It seems only half of midi standard is being used at the moment on the sequencer side at least?

link

answered Apr 27 '19 at 15:28 by hockinsk (21)

Sysex is supported in control scripts.

link

answered Jun 02 '17 at 17:40 by Ottworks (444)

Definitely need at least Sysex pass-through to support the excellent Modulation Processor 3244

link

answered Jul 10 '17 at 04:12 by chrisfostertv (19)

Bump. Please add at least basic sysex support, just to get data to older gear and of course lots of VSTi need to send and receive it too! Don't force us back to Cubase lol!

link

answered Apr 26 '19 at 22:31 by hockinsk (21)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×3

Asked: Nov 01 '15 at 18:44

Seen: 2,524 times

Last updated: Jan 21 at 10:08