Bitwig Studio 1.2 BETA 4

[gesslr]

Hi.

I'm getting some weird behavior with Beta 4.

I have a lot of hardware synth units. I'm trying to set up a template for them. So right now I have one instrument track sending midi to a HW unit via a HW Instrument Device and a separate audio track set up to record the resulting audio. (I'm choosing not to use the audio in in the HW Instrument Device.)

Everything is great until I get to three of the synths. For each, I can only hear the synth if I select the exact same audio input for each one...but they are all patched into different inputs on my audio interface. In this case I have to select "MicroQ" (the audio input for my MicroQ) for the MicroQ (of course), but also for 2 other synths. If I select their labelled inputs, I hear nothing. But if I select "MicroQ" for all three, I hear three distinct synths playing on three different inputs. It is very bizarre.

Before you go there, my inputs are labeled correctly, and my current set up works in Cubase, Studio One, and DP without incident.

I'm not sure, that I'm explaining it correctly, so I made a video. It's 5 minutes long and I ramble a bit (my first one), but at 2:25 I get to the crux of the problem. Before that I provide context and show it working with other synths. I should also say that this is an early effort to start working on a template in 1.2 as I just got started.



I "hope" it's a bug and not FOUE (friggin obvious user error), but I'm stumped.

MacPro 5,1
OSX 10.10.5
28 gb ram
Motu 828 Mk2 & Mk3 audio interfaces
Motu Midi Express 128s

Thoughts appreciated.

Thanks.

[Jolaff]

Can we make custom tags? It looks like we can but it doesn't works....

[owensands]

Hi.

I'm getting some weird behavior with Beta 4.

I have a lot of hardware synth units. I'm trying to set up a template for them. So right now I have one instrument track sending midi to a HW unit via a HW Instrument Device and a separate audio track set up to record the resulting audio. (I'm choosing not to use the audio in in the HW Instrument Device.)

Everything is great until I get to three of the synths. For each, I can only hear the synth if I select the exact same audio input for each one...but they are all patched into different inputs on my audio interface. In this case I have to select "MicroQ" (the audio input for my MicroQ) for the MicroQ (of course), but also for 2 other synths. If I select their labelled inputs, I hear nothing. But if I select "MicroQ" for all three, I hear three distinct synths playing on three different inputs. It is very bizarre.

Before you go there, my inputs are labeled correctly, and my current set up works in Cubase, Studio One, and DP without incident.

I'm not sure, that I'm explaining it correctly, so I made a video. It's 5 minutes long and I ramble a bit (my first one), but at 2:25 I get to the crux of the problem. Before that I provide context and show it working with other synths. I should also say that this is an early effort to start working on a template in 1.2 as I just got started.



I "hope" it's a bug and not FOUE (friggin obvious user error), but I'm stumped.

MacPro 5,1
OSX 10.10.5
28 gb ram
Motu 828 Mk2 & Mk3 audio interfaces
Motu Midi Express 128s

Thoughts appreciated.

Thanks.

You sure you don't have your routings for you interface sending the all those ins to the same asio inputs? I know on my RME I can do that np. You say that in other DAWs its setup right so im guessing maybe not. Might be an issue with the new audio rewrite they did. I know I was having issues at first with my 24 outs but I only use 4 ins so maybe someone with as many inputs as you is finding an issue when you have loads of inputs.

[goatgirl]

Can we make custom tags? It looks like we can but it doesn't works....

Custom tags work, just make sure there is a space after each tag name you create.

Edit: This behaviour has been reported as its a silly requirement for the last tag.

[Jolaff]

Can we make custom tags? It looks like we can but it doesn't works....

Custom tags work, just make sure there is a space after each tag name you create.

Edit: This behaviour has been reported as its a silly requirement for the last tag.

Oh ...I was testing it with only one tag so I never noticed that once we use the spacebar the tag is created...

thanx

Edit: yeah this is not that much annoying having to hit the spacebar but this is quite silly...

[Hez]

Anyone managed to get group tracks to retain their routing when moving between projects? Audio receivers seem to maintain it fine, but when I drag a group with a.) a multi-out VST and b.) 8 audio tracks, with track input set to the VST outs as well as audio receivers receiving the VST outs (so that I can monitor live), the track input seems to erase to "No Input" every time I drag the master group between projects.

I swear it was working before I added the audio receivers in - seems like there's some condition whereby you can't maintain both audio receiver & track input routing when dragging between projects - one or the other has to go.

[gesslr]

Hi.

I'm getting some weird behavior with Beta 4.

You sure you don't have your routings for you interface sending the all those ins to the same asio inputs? I know on my RME I can do that np. You say that in other DAWs its setup right so im guessing maybe not. Might be an issue with the new audio rewrite they did. I know I was having issues at first with my 24 outs but I only use 4 ins so maybe someone with as many inputs as you is finding an issue when you have loads of inputs.

Hi Owen. Yes I am sure I am not doing that. The synths fire and the sound comes in the various inputs, and they are routed and meter in CueMix (Motu's audio interface software) correctly. It's as if the right things are happening behind the scenes; the fail seems to be at the drop down selection. Really weird. Thanks.

[TeotiGraphix]

Can we make custom tags? It looks like we can but it doesn't works....

Custom tags work, just make sure there is a space after each tag name you create.

Edit: This behaviour has been reported as its a silly requirement for the last tag.

Oh ...I was testing it with only one tag so I never noticed that once we use the spacebar the tag is created...

thanx

Edit: yeah this is not that much annoying having to hit the spacebar but this is quite silly...

Am I missing something here? You can just hit the Enter/Return key as well which will create the tag and leave it ready to enter a new one.

What am I missing?

Mike

[TeotiGraphix]

USAGE NOTE:

I wasn't aware of this one but SHIFT + double click on a group will dive into it.

Mike

[ThomasHelzle]

Thoughts appreciated.

Thanks.

I would also guess it's the new audio core. I had problems in the previous version with my Scarlett 18i20 and it's driver showing an assertion error each time I started the audio engine, opened audio preferences etc. and each time BWS would add several audio inputs to the audio prefs, so sometimes I ended up having over a hundred...
So this part is really new and still in it's shaking-down phase, so yeah, I could imagine that over a certain number of inputs, the internal logic is getting scrambled somehow.

Cheers,

Tom

[Jolaff]

Can we make custom tags? It looks like we can but it doesn't works....

Custom tags work, just make sure there is a space after each tag name you create.

Edit: This behaviour has been reported as its a silly requirement for the last tag.

Oh ...I was testing it with only one tag so I never noticed that once we use the spacebar the tag is created...

thanx

Edit: yeah this is not that much annoying having to hit the spacebar but this is quite silly...

Am I missing something here? You can just hit the Enter/Return key as well which will create the tag and leave it ready to enter a new one.

What am I missing?

Mike

You are right.

I was typing "test" as a tag and then clicking on "ok" to create the preset ....but I should have type "test" then "enter or spacebar" then click ok...

[gesslr]

Thoughts appreciated.

Thanks.

I would also guess it's the new audio core. I had problems in the previous version with my Scarlett 18i20 and it's driver showing an assertion error each time I started the audio engine, opened audio preferences etc. and each time BWS would add several audio inputs to the audio prefs, so sometimes I ended up having over a hundred...
So this part is really new and still in it's shaking-down phase, so yeah, I could imagine that over a certain number of inputs, the internal logic is getting scrambled somehow.

Cheers,

Tom

Thanks Tom. Well it seems to behave otherwise...I shall continue to press on!

[Beerhunter]

@ goatgirl,

thanks for the hint... but the Buffersize is equal and i don't get x-runs using Jack. So it seems like an interface problem, not a setup problem or even bitwigs.

[Beerhunter]

hi,

i just stumbled over a strange behaviour of the Commander.

Just launch it and try to scroll down via touchpad . Every time i try it, it just closes instantly.
It´s working if i use up/down keys, but in general i use the touchpad. So maybe Mousepointer bug ???

can anyone confirm this behaviour ? Thanks

[Hez]

Getting a lot of crashes when clicking on certain tracks in the arranger view. Haven't managed to narrow it down any further than that so far (I thought it was tracks containing TAL-Sampler, but some of them seem fine, and now I've started getting it on ones just with plain audio). Other than that it has been relatively stable for me so far, including some major group track abuse between projects etc.