Bitwig

dom@bitwig · Post by **dom@bitwig** » Thu Oct 23, 2014 12:09 pm

Online now!

We currently get a lot of feedback without any technical information, like operating system, used hardware, used audio interface and drivers etc.
Please be sure to mention your setup when sending feedback to beta@bitwig.com

Thanks!
Dom

Changes in Bitwig Studio 1.1 BETA 6
Released on 23.10.2014.

FIXED Controller API: accent observer reports wrong value range.
FIXED Controller API: crash when updating value of number settings programmatically.
FIXED It was possible to create connection which was not considered considered as a feedback connection in the processing graph, but which broke the inter-track dependencies and caused the engine to hang.
FIXED Audio editor does not repaint correctly after onset creation.
FIXED "Exclusive mode" checkbox overlays with recording offset field when using WASAPI.
FIXED Changing presets while recording should not create new automation lanes for parameters that are changed by the preset for Bitwig devices.
FIXED Couldn't create "LOCALAPPDATA\Bitwig Studio" directory on windows using JRE 1.8.0_20 during initial launch.
FIXED Crash when changing routing output of a track which is deactivated.
FIXED Crash when dragging tracks with side-chain routings from sub-channels to another document.
FIXED When track is getting sidechain input from another track's PRE or POST output it gets soloed together with the track which is chosen in sidechain routing.
FIXED Note Editor in FOLD mode: note gets misplaced when moving it out of bounds using arrow key.
FIXED When cutting raw audio and resizing the start of the left part, the start of right part gets resized too.
FIXED Setting the play start position using the detail editors ruler area doesn't work with the time-selection tool selected.
FIXED URL in version update notifications needs to be URL encoded when opening it in the browser.
FIXED Crossfader section in mixer looks weird with scrollbar and/or sub-channels.
FIXED Crash when removing unused controller in Studio I/O panel.
FIXED Crash when incrementing a discrete parameter's modulation amount using a controller.
FIXED Crash when quantizing audio after split to onsets operation in clip launcher audio editor.
FIXED Modulation of a VST parameter changes the value but doesn't change the knob's pie.
FIXED Rare crash when selecting clip launcher slot on hardware controller while the document is closing.
FIXED After dragging device from one track to another, its nested devices are no longer selectable.
FIXED Moving onset by dragging position field does not update position until unselecting onset.
IMPROVED Double clicking a device in the mixer panel in a sub channel (eg drum or layer) would show the track's device chain and not the sub channel's.
IMPROVED Audition velocity changes with time threshold instead of playing a new note on each mouse move.
IMPROVED Automatically show macros when dragging a preset from the browser which had macros assigned.
IMPROVED ALT+Space showed the System Menu on Windows but shouldn't.
IMPROVED Automatically reload controller script when any file inside the parent directory of the main script changes.

Ogopogo · Post by **Ogopogo** » Thu Oct 23, 2014 12:29 pm

Bottom of mixer tracks looks weird now.

dom@bitwig · Post by **dom@bitwig** » Thu Oct 23, 2014 12:40 pm

Why is that? What do you mean?

xbitz · Post by **xbitz** » Thu Oct 23, 2014 12:41 pm

win 8.1, seems the project/remove unused samples takes account n-1 row, both b5, b6

bbbug.jpg

ok ... it's not a blocking point

TeotiGraphix · Post by **TeotiGraphix** » Thu Oct 23, 2014 12:49 pm

Ogopogo wrote:Bottom of mixer tracks looks weird now.

Are you talking about the little 10 pixel strip at the bottom of them where the master channel's strip is lighter?

Mike

dom@bitwig · Post by **dom@bitwig** » Thu Oct 23, 2014 12:55 pm

I guess this is what he means.

It is the new natural habitat where the scroll bar lives

"FIXED Crossfader section in mixer looks weird with scrollbar and/or sub-channels."

The lighter section below the master is excluded, because the scroll bar can't go there.

Ogopogo · Post by **Ogopogo** » Thu Oct 23, 2014 1:03 pm

Yeah, that's what I meant. I guess it just adds a bit extra complication to that area of the theme seeing as how it's its own little chunk of trackjust sitting there, and also a different color than the rest of the track there. I liked how the scrollbar just popped up at the bottom before but I guess that would get in the way of the A/B selector now? Oh well I'm probably being way too nitpicky, sorry.

TeotiGraphix · Post by **TeotiGraphix** » Thu Oct 23, 2014 1:05 pm

dom@bitwig wrote:I guess this is what he means.

It is the new natural habitat where the scroll bar lives

"FIXED Crossfader section in mixer looks weird with scrollbar and/or sub-channels."

The lighter section below the master is excluded, because the scroll bar can't go there.

Ah yeah, selecting cross faders and pulling the browser over to show the scroll bar for the tracks definitely makes those scroll track backgrounds.

Mike

dom@bitwig · Post by **dom@bitwig** » Thu Oct 23, 2014 1:22 pm

Ogopogo wrote:I liked how the scrollbar just popped up at the bottom before but I guess that would get in the way of the A/B selector now?

Exactly, and that looked really broken... just as Teoti also mentioned.

xanthos · Post by **xanthos** » Thu Oct 23, 2014 1:22 pm

nice update!

any nasty known bugs left?

kurasu · Post by **kurasu** » Thu Oct 23, 2014 1:24 pm

xanthos wrote:nice update!

any nasty known bugs left?

go find them!

xbitz · Post by **xbitz** » Thu Oct 23, 2014 1:40 pm

both new receivers stop working if u group them (ctrl+g)

win 8.1, b5, b6

goatgirl · Post by **goatgirl** » Thu Oct 23, 2014 1:52 pm

dom@bitwig wrote: FIXED URL in version update notifications needs to be URL encoded when opening it in the browser.

I guess that explains the 'Error openning location' error i got when I opened beta 5 and clicked to download the update.

Though I must point out that they have a spelling error in their error message... its 'opening' ... tut tut !

volker@bitwig · Post by **volker@bitwig** » Thu Oct 23, 2014 2:01 pm

goatgirl wrote:
dom@bitwig wrote: FIXED URL in version update notifications needs to be URL encoded when opening it in the browser.
I guess that explains the 'Error openning location' error i got when I opened beta 5 and clicked to download the update.

Though I must point out that they have a spelling error in their error message... its 'opening' ... tut tut !

Yes, the link in the update notifications should work for the next update with this fix. Thanks for the hint about the spelling error, just fixed it.

goatgirl · Post by **goatgirl** » Thu Oct 23, 2014 2:18 pm

volker@bitwig wrote: Yes, the link in the update notifications should work for the next update with this fix. Thanks for the hint about the spelling error, just fixed it.

Wow, I'm impressed by the speed you are fixing all these bugs.

Bitwig

KVR Audio

Bitwig Studio 1.1beta6