Bitwig Studio 1.3.6

[TrueAndFalse]

Nice to see how fast Bitwig Studio grows. It is still the best DAW for me.

[Serobliss]

I have to report that after installing the 1.3.6 version i'm still getting this nasty bug with audio events deleted when i add a new one to a clip : see video right there :




So unfortunately, it's really hard to use bitwig for the moment, at least for me, so bad because i bought the license only 5 days ago and i'm unable to use the software (that has some other really cool features that i like by the way ) and it's really REALLY frustrating...

I could reproduce it and fixed it for the next update. Thanks for reporting!

Oh really thanks a LOT for taking this into account !

[golddustwoman]

Full screen in OSX causes loss of control over random knobs and sliders when using mouse.

I can't reproduce this. Which OSX version and which computer hardware are you using, and could you explain what means loss of control?

2.7 GHz Intel Core i5 OSX 10.11.2 With instrument open the knobs are not aways rotating when moved, and values do not change when trying to change loop length of a clip using mouse to raise /lower length settings.Thank you.

[volker@bitwig]

Full screen in OSX causes loss of control over random knobs and sliders when using mouse.

I can't reproduce this. Which OSX version and which computer hardware are you using, and could you explain what means loss of control?

2.7 GHz Intel Core i5 OSX 10.11.2 With instrument open the knobs are not aways rotating when moved, and values do not change when trying to change loop length of a clip using mouse to raise /lower length settings.Thank you.

Strange ... does it always happen for you when going full screen? Does the GUI also appear distorted then, or could it be that the mouse positions are offset, so that you have to click somewhere outside the controls in order to hit them?

[golddustwoman]

Full screen in OSX causes loss of control over random knobs and sliders when using mouse.

I can't reproduce this. Which OSX version and which computer hardware are you using, and could you explain what means loss of control?

2.7 GHz Intel Core i5 OSX 10.11.2 With instrument open the knobs are not aways rotating when moved, and values do not change when trying to change loop length of a clip using mouse to raise /lower length settings.Thank you.

Strange ... does it always happen for you when going full screen? Does the GUI also appear distorted then, or could it be that the mouse positions are offset, so that you have to click somewhere outside the controls in order to hit them?

Just tried with track pad, same thing happens. I opened a Polysynth track, then tried to adjust knob controls, they wont always rotate, then opened a new clip for the Polysynth and tried to adjust length in left column, the values stick. Not a major prob, but thanks for looking into it.

On further investigation finding many mouse/trackpad 'action' delays in fullscreen mode only, moving sliders/knobs and making basic selections all seem to lag. Happens in centre of screen too, so not an issue with monitor edge. Using Macbook Pro 2.7 GHz Intel Core i5 8 GB 1867 MHz DDR3 - OSX 10.11.3

[Beamboom]

After getting a chance to work with it a bit today, all is not well in Bitwig land for Tomsa. I am getting random crashes of the audio engine after recording individual mono tracks. This is in really basic projects, i.e. one track of me recording/playing back my trumpet practice session today. Bummer. I have sent a bug report.

I too experience a lot of crashes on my 64bit Ubuntu machine in regards to editing recorded mono tracks. I use a guitar in a current project and the engine seems to randomly crash when cutting/moving inside the recorded segment, although I've not yet manage to make a bulletproof steps to reproduce. Luckily it's just the engine, nothing is lost in the project.
Still, quite annoying!

It's been like this also in the RC versions, but I can't recall it being so in 1.3.5. Although this may be coincidence, I don't very often record audio into the projects.

[mrfrenkie]

Still here.


OSX 10.11.2
Quad Capture 55
Bitwig 1.3.6

[u-u-u]

Hey devs, could you reproduce this? Just asking because you didn't commented on it. If really necessary I can make a video.

FIXED - Free running automation is not shown correctly in content preview section of launcher clips.

Yes, the time range of free running automation is displayed correctly now. But the automation play marker in those launcher clips isn't displayed correctly:
- if the free automation isn't looped, its playhead in the launcher is looped with the clip content
- if the free automation is looped but with a different loop length than the clip content, the playhead isn't looped correctly (different (both incorrect) behaviour when automation loop is shorter/longer than the clip content loop!)

[ThomasHelzle]

Full screen in OSX causes loss of control over random knobs and sliders when using mouse.

I can't reproduce this. Which OSX version and which computer hardware are you using, and could you explain what means loss of control?

2.7 GHz Intel Core i5 OSX 10.11.2 With instrument open the knobs are not aways rotating when moved, and values do not change when trying to change loop length of a clip using mouse to raise /lower length settings.Thank you.

Strange ... does it always happen for you when going full screen? Does the GUI also appear distorted then, or could it be that the mouse positions are offset, so that you have to click somewhere outside the controls in order to hit them?

I read several reports recently about problems with fullscreen on OSX. Could it be weak graphics cards in combination with the fullscreen mode somehow triggering something odd?

Cheers,

Tom

[volker@bitwig]

Hey devs, could you reproduce this? Just asking because you didn't commented on it. If really necessary I can make a video.

FIXED - Free running automation is not shown correctly in content preview section of launcher clips.

Yes, the time range of free running automation is displayed correctly now. But the automation play marker in those launcher clips isn't displayed correctly:
- if the free automation isn't looped, its playhead in the launcher is looped with the clip content
- if the free automation is looped but with a different loop length than the clip content, the playhead isn't looped correctly (different (both incorrect) behaviour when automation loop is shorter/longer than the clip content loop!)

Yes, I could reproduce it. I get the error right after creating a new clip with automation and switching it to free running. If i stop playback and start it again it seems fine, following any changes to the loop settings correctly. Thanks for reporting!

[askewd]

2.7 GHz Intel Core i5 OSX 10.11.2 With instrument open the knobs are not aways rotating when moved, and values do not change when trying to change loop length of a clip using mouse to raise /lower length settings.Thank you.

yes same specs as mine. Fullscreen is unusable due to horrendous lags. Switch out of fullscreen and everything perfect. Devs are aware of problem.

[volker@bitwig]

Full screen in OSX causes loss of control over random knobs and sliders when using mouse.

I can't reproduce this. Which OSX version and which computer hardware are you using, and could you explain what means loss of control?

2.7 GHz Intel Core i5 OSX 10.11.2 With instrument open the knobs are not aways rotating when moved, and values do not change when trying to change loop length of a clip using mouse to raise /lower length settings.Thank you.

Strange ... does it always happen for you when going full screen? Does the GUI also appear distorted then, or could it be that the mouse positions are offset, so that you have to click somewhere outside the controls in order to hit them?

I read several reports recently about problems with fullscreen on OSX. Could it be weak graphics cards in combination with the fullscreen mode somehow triggering something odd?

Cheers,

Tom

I've also read those reports and initially thought it might happen only on computers without a dedicated graphics chip, but did not have any luck reproducing it so far, even on computers very similar to the reported hardware. I did not notice any difference when going full screen.

[WXLF]

The small orange line indicating what buffer is selected, is on the 512 spot, yet it says 256 samples below. You can see it says 512 after switching back to that spot.

I should've looked at the DSP performance graph to see what that said the buffer was set to before i closed bitwig.

I haven't tried to reproduce it but I am betting it is because I opened Bitwig without the previous hardware connected. komplete audio 6 was output.. shut down bitwig/computer.. reopened with output as built in output.

[WXLF]

FIXED - Sometimes engine crashes on OSX when connecting to document.

I'm not sure what type of document this "FIXED" was addressing but it seems there is still some funny business going on.

maschine doesn't seem to like bitwig sometimes.

The fix was related to certain audio hardware which seemed to cause trouble.
You mean machine doesn't like bitwig when using it as a plugin, or as a MIDI controller?
How did you configure your plugin hosting preferences - bit bridge oder 32/64?
Which audio hardware did you configure as inputs/outputs in your audio preferences?
Does it happen randomly or always in certain projects?

the engine is connecting for that project now. honestly i don't know what's going on, i think i'm just going to not use maschine anymore. drum machine should be more cpu efficient anyways

but to answer your questions..
-As a plugin. -I have it set to 32/64. -input/output = komplete audio 6.

[SpellBound]

There is a couple bugs exists:
First. Drug and drop of any audio file on free place from the side browser does not create a new audio track.
Second. When you try to make audio container longer by triggering up right side of the clip it works like looping (triggering down right side of the clip)




OSX 10.11.2, imac 5K