Bitwig Studio 1.3.6

[ThomasHelzle]

Just to keep those that may experience the same issue, Dom suggested I try turning off the auto suspend on Omnisphere to see if that helps. Will try it and report back soon.

Yes, Dom had suggested I do the same quite some time back, but it didn't help in my case. BWS still shuts off the VEP5 engine and to get it started again, I had to go through what you described above.

For what ever reason, BWS shuts down the VEP5. No other DAW I use has this issue, but again, they don't have VEP5 to test what's wrong.

Most unfortunate

But it may work if you're on just one machine. Keep us posted.

Cheers!

Same here, turning off auto suspend does not do anything in the cases I have seen (and never has). Either it's broken or it address a different problem from what we encounter here.

Cheers,

Tom

[IAmRickyRiot]

Just to keep those that may experience the same issue, Dom suggested I try turning off the auto suspend on Omnisphere to see if that helps. Will try it and report back soon.

Yes, Dom had suggested I do the same quite some time back, but it didn't help in my case. BWS still shuts off the VEP5 engine and to get it started again, I had to go through what you described above.

For what ever reason, BWS shuts down the VEP5. No other DAW I use has this issue, but again, they don't have VEP5 to test what's wrong.

Most unfortunate

But it may work if you're on just one machine. Keep us posted.

Cheers!

Same here, turning off auto suspend does not do anything in the cases I have seen (and never has). Either it's broken or it address a different problem from what we encounter here.

Cheers,

Tom

So far turning Auto Suspend off on Omnisphere seems to have worked. I've been messing around for a short time and haven't had any drop outs yet. Will definitely report back when I spend more time with it. I have used VEP in years so I can't add anything to that side of things unfortunately.

[codec17]

Hi!
Just a stupid question,
When you send in a crash report, do you send some info on the crash?
Like, can they see whats going wrong?
Got the same problem over and over and over again,
and can reproduce it in 3 different ways and send it in on 3/4 different ways ,so thats why the question.
As you can read, im just a "musician" that wants to make music not a coder or programmer ..

[c-wave]

Hi!
Just a stupid question,
When you send in a crash report, do you send some info on the crash?
Like, can they see whats going wrong?
Got the same problem over and over and over again,
and can reproduce it in 3 different ways and send it in on 3/4 different ways ,so thats why the question.
As you can read, im just a "musician" that wants to make music not a coder or programmer ..

Definitely helpful to add some description. They just want you to send it anyway even if you don't feel like adding a description.

[codec17]

Ah ok.. Thnx c-wave!
Yes descriptions also included....
Cant wait for 1.3.7....

[ThomasHelzle]

Hi!
Just a stupid question,
When you send in a crash report, do you send some info on the crash?
Like, can they see whats going wrong?
Got the same problem over and over and over again,
and can reproduce it in 3 different ways and send it in on 3/4 different ways ,so thats why the question.
As you can read, im just a "musician" that wants to make music not a coder or programmer ..

Yes, they can see in what module etc. the crash occurred if you send a crash report. I don't know all the details, but that is basically the point of it. But what they can't see is what you did last before the crash and in what circumstances it happened or your project, so it may still make sense to send an accompanying project file with some explanations to support where you say "If I do this and that in this project, xyz happens". And of course on what kind of system, audio interface and drivers, OS etc.

In the crash reporter description I always try to be as clear as possible, especially if I can repeat it, I start adding information each time it happens and the more I learn about the specific circumstances.

The main point is enabling them to reproduce it, which in some cases is the main problem.
If it does not happen on the devs machine, it may be impossible to fix.

Cheers,

Tom

[reflekshun]

NEW Added Post Recording Actions to clip launcher which are activated after a specified duration has been recorded. This can be used to record clips of a predetermined fixed length as well as to record multiple takes automatically to multiple clips.

Is there anyone who can explain how this works? I would love to have any form of a multiple takes system in Bitwig! Any help is much appreciated

[takaii]

Bitwig team have been awefully quite latly xD can only mean one thing suprice suprice i hope

[ThomasHelzle]

NEW Added Post Recording Actions to clip launcher which are activated after a specified duration has been recorded. This can be used to record clips of a predetermined fixed length as well as to record multiple takes automatically to multiple clips.

Is there anyone who can explain how this works? I would love to have any form of a multiple takes system in Bitwig! Any help is much appreciated

In the Transport bar there is first the record button an then the automation write button which has a little dropdown menu. Open it and you will find the post recording actions. One of them is "Record into next free Slot". This together with a setting for after how much time it should happen is indeed a kind of take-option.

Cheers,

Tom

[reflekshun]

NEW Added Post Recording Actions to clip launcher which are activated after a specified duration has been recorded. This can be used to record clips of a predetermined fixed length as well as to record multiple takes automatically to multiple clips.

Is there anyone who can explain how this works? I would love to have any form of a multiple takes system in Bitwig! Any help is much appreciated

In the Transport bar there is first the record button an then the automation write button which has a little dropdown menu. Open it and you will find the post recording actions. One of them is "Record into next free Slot". This together with a setting for after how much time it should happen is indeed a kind of take-option.

Cheers,

Tom

Wow, this is a really cool feature, thank you so much for explaining it so clearly and well Will try this tomorrow!!

[sonson5]

Bitwig team have been awefully quite latly xD can only mean one thing suprice suprice i hope

I have the same feeling / hope.. fingers crossed.

[sonson5]

Does anyone have any clue or at at least any speculation based on whatever logical reason out there when will 1.3.7 or at least it's RC version be out and what fixes/new add-ons will it include?

I have always used bitwig for exploration and sound design and I have started using it full time now and I swear I am waiting for the new 1.3.7 as if I am waiting for my new baby to come to life.

[Ogopogo]

Does anyone have any clue or at at least any speculation based on whatever logical reason out there when will 1.3.7 or at least it's RC version be out and what fixes/new add-ons will it include?

I have always used bitwig for exploration and sound design and I have started using it full time now and I swear I am waiting for the new 1.3.7 as if I am waiting for my new baby to come to life.

http://www.kvraudio.com/forum/viewtopic ... 9&t=457581

[nickallen]

nickallen, BUG! on midi tracks, PUNCH-OUT stop recording before loopmarkers end and leave a bit space. Check gif and you understand.

punch out.gif

This should be fixed in the new 1.3.8 RC 1 release.