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

edited Mar 28 '16 at 02:37

12
4

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

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 (251)

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 (251)

edited Jun 02 '17 at 17:50

It will be great!

link

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

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 at 01:37 by chrisfostertv (21)

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

  — (Apr 27 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 at 15:28 by hockinsk (21)

Sysex is supported in control scripts.

link

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

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

link

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

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 at 22:31 by hockinsk (21)

This is an User forum. If you have requests about a feature development you should write to support@bitwig.com.

And I suggest to stop comparing to this or that: no other DAWs can do natively what Bitwig does and will do with The Grid.

If what you need is another DAW, then use another DAW.

It is like asking Tesla to produce the Ferrari's roar..

My 2c.

Fabrizio

link

answered Apr 27 at 01:16 by fsciarra62 (774)

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,111 times

Last updated: Apr 27 at 15:28