The All In One Source Bitwig Information & Speculation Thread

[Ingonator]

But you may not need to since you can simply put your midi generators ON THE SAME TRACK IN FRONT OF YOUR INSTRUMENT
BMS allows for way more freedom in this regard, but yes, I feel the need for midi routing too.

Honestly to me it is a kind of mystery that things like proper support for MIDI controller (at least a MIDI to USB adapter like my E-Mu XMIDI 1x1 which appears properly in other softwrae...), multiple audio putputs and MID routing is not supported from beginning on.


Just checked with my Yamaha Motiif ES 7 USB connection and my Korg NanoKONTROL.

While the NanoKONTROL seems to be recognize properly the Motif ES 7 is only recognized as a generic controller. Strange thing is that the name of the input right besides "Generic MIDI keyboard" (in the drop-down menu) uses the proper name (e.g. "Yamaha MOTIF ES-1" or "E-Mu XMidi1x1").

The problem i got now is that i have two controllers called "MIDI keyboard" which is confusing when i want to select a specific one at e.g. the mixer page.
It would be nice if it would be at least possible to rename this yourself but i have not found that option.

As already mentioned i did not really observe this problem with other hosts, Standalone synths (e.g. Reaktor 5 standalone) and some Sysex programs including an old one like SendSX. in those i usually get the names which above i mentioned in brackets.


Ingo

[ThomasHelzle]

But you may not need to since you can simply put your midi generators ON THE SAME TRACK IN FRONT OF YOUR INSTRUMENT
BMS allows for way more freedom in this regard, but yes, I feel the need for midi routing too.

Honestly to me it is a kind of mystery that things like proper support for MIDI controller (at least a MIDI to USB adapter like my E-Mu XMIDI 1x1 which appears properly in other softwrae...), multiple audio putputs and MID routing is not supported from beginning on.


Just checked with my Yamaha Motiif ES 7 USB connection and my Korg NanoKONTROL.

While the NanoKONTROL seems to be recognize properly the Motif ES 7 is only recognized as a generic controller. Strange thing is that the name of the input right besides "Generic MIDI keyboard" (in the drop-down menu) uses the proper name (e.g. "Yamaha MOTIF ES-1" or "E-Mu XMidi1x1").

The problem i got now is that i have two controllers called "MIDI keyboard" which is confusing when i want to select a specific one at e.g. the mixer page.
It would be nice if it would be at least possible to rename this yourself but i have not found that option.

As already mentioned i did not really observe this problem with other hosts, Standalone synths (e.g. Reaktor 5 standalone) and some Sysex programs including an old one like SendSX. in those i usually get the names which above i mentioned in brackets.


Ingo

You are right. But check out Live 1.0 for a slight reminder how far we have come
Give it some time...

Cheers,

Tom

[xamido]

For now it's a no for me. Still buggy and too expensive, especially with 3rd party plugin. I've just deleted the demo. Perhaps if they fix the problem and have sales next time, i will try the demo again.

[KoolFartWind]

I hope they sell well, too and provide a generic Linux version later on.

[Ingonator]

But you may not need to since you can simply put your midi generators ON THE SAME TRACK IN FRONT OF YOUR INSTRUMENT
BMS allows for way more freedom in this regard, but yes, I feel the need for midi routing too.

Honestly to me it is a kind of mystery that things like proper support for MIDI controller (at least a MIDI to USB adapter like my E-Mu XMIDI 1x1 which appears properly in other softwrae...), multiple audio putputs and MID routing is not supported from beginning on.


Just checked with my Yamaha Motiif ES 7 USB connection and my Korg NanoKONTROL.

While the NanoKONTROL seems to be recognize properly the Motif ES 7 is only recognized as a generic controller. Strange thing is that the name of the input right besides "Generic MIDI keyboard" (in the drop-down menu) uses the proper name (e.g. "Yamaha MOTIF ES-1" or "E-Mu XMidi1x1").

The problem i got now is that i have two controllers called "MIDI keyboard" which is confusing when i want to select a specific one at e.g. the mixer page.
It would be nice if it would be at least possible to rename this yourself but i have not found that option.

As already mentioned i did not really observe this problem with other hosts, Standalone synths (e.g. Reaktor 5 standalone) and some Sysex programs including an old one like SendSX. in those i usually get the names which above i mentioned in brackets.


Ingo

You are right. But check out Live 1.0 for a slight reminder how far we have come
Give it some time...

Cheers,

Tom

I though Bitwig was supposed to be superior to Live in any way or not?

Those are also very basic features which should work properly before doing more complex stuff.


BTW here is a screenshot about how my controllers look in Bitwig:



Left you see "Generic MIDI keyboard" while on the right you see the proper names.
In other hosts like e.g. live 9 i get the correct names like on the right of the screenshot.
As mentioned both controllers in the mixer appear as "MIDI keyboard".

As you could see those Generic MIDI keyboards only have an input but no output which is another problem.


Ingo

[lfm]

One thing was strange - that they host the download stuff from same server as their site, you cannot even get a glimpse of final release notes etc due to heavy downloads - site down when I tried.

Otherwise, newly released software is expected to need a handful of patches the coming months - that should be covered by an introduction reduced price as compensation. Not even Microsoft is safe in this regard with new Windows releases, and they have massive betatesting for years.

The impression I got from developers is that they will quickly respond to anything. I wish them great success.

[vandrewal]

They could have beta tested Bitwig until 2020, their first release would still be buggy. Once you release a program out to the world, especially for something as big as Bitwig, bugs will occur. The real test is to see how quickly they are addressed and fixed. I have not had the chance to try the demo yet as I am still at work, but hopefully they have a decent report system to report any crash and unexpected behaviour?

[tooneba]

neither ctrl +t nor ctrl+shift+t works in linear track view

[EnGee]

Very nice beginning Congratulations to them.

I didn't buy it and not sure if I will, but it gives me a very good first impression. The workflow needs some time to be learned.
My mpk mini was recognised and clicking the question mark gave me a nice control map for it.

I don't know what they programmed in Java? is it all? or just the web service? or ? Anyway, it has a very nice interface and it is very easy on the eyes. I can't say better than others, but different feel.

Nice thing to play with before going to sleep, my dreams will be orange!

ZzzzZZzzZzzzz

[ThomasHelzle]

I though Bitwig was supposed to be superior to Live in any way or not?

Those are also very basic features which should work properly before doing more complex stuff.


BTW here is a screenshot about how my controllers look in Bitwig:



Left you see "Generic MIDI keyboard" while on the right you see the proper names.
In other hosts like e.g. live 9 i get the correct names like on the right of the screenshot.
As mentioned both controllers in the mixer appear as "MIDI keyboard".

As you could see those Generic MIDI keyboards only have an input but no output which is another problem.


Ingo

Well, Bitwig has it's fanboys already like every other software.
I personally am not interested in the better/worse discussion or what the developers did wrong.

I know exactly what you mean. I had the same problem. Since I'm interested enough in Bitwig to go the extra mile, I created specific controller scripts for my devices and everything works as expected now. I personally also think that shouldn't be necessary, but that's how it is on Launchday of this 1.0.

It is very easy to change the scripts, so if you are seriously interested I can help you with creating scripts for your keyboards. But only if you have more than a passing interest, otherwise I rather try to help people who are seriously interested in Bitwig for whatever reasons.

I think you know the situation from your own threads

Cheers,

Tom

[Ingonator]

They could have beta tested Bitwig until 2020, their first release would still be buggy. Once you release a program out to the world, especially for something as big as Bitwig, bugs will occur. The real test is to see how quickly they are addressed and fixed. I have not had the chance to try the demo yet as I am still at work, but hopefully they have a decent report system to report any crash and unexpected behaviour?

Problems with controller support (or at least adding manual naming, see my post above), missing multi channel support for VSTs and missing MIDI routing are not small bugs IMO and also something that should be done in v1.0 and not later...


Ingo

[whyterabbyt]

Problems with controller support (or at least adding manual naming, see my post above), missing multi channel support for VSTs and missing MIDI routing are not small bugs IMO

No, they're not, they're design decisions, informed by priorities, available resources, and deadlines. Like with any other software development project.

[ThomasHelzle]

They could have beta tested Bitwig until 2020, their first release would still be buggy. Once you release a program out to the world, especially for something as big as Bitwig, bugs will occur. The real test is to see how quickly they are addressed and fixed. I have not had the chance to try the demo yet as I am still at work, but hopefully they have a decent report system to report any crash and unexpected behaviour?

Problems with controller support (or at least adding manual naming, see my post above), missing multi channel support for VSTs and missing MIDI routing are not small bugs IMO and also something that should be done in v1.0 and not later...


Ingo

I take that as a no to my question if you want help and leave you to your rumblings.

Cheers,

Tom

[tooneba]

Problems with controller support (or at least adding manual naming, see my post above), missing multi channel support for VSTs and missing MIDI routing are not small bugs IMO

No, they're not, they're design decisions, informed by priorities, available resources, and deadlines. Like with any other software development project.

Poor decision. Isn't that what he was implying? idk.

[Numanoid]

Is Bitwig hot? Almost 10 pages of comments in just 24 hours

Just want to dial in with the verdict published in Computer Music 202 just out.

They give it 9 out of 10, and give it "Editors Choice", "Innovation" and "Performance" Award