Bitwig 5 is up

[SLiC]

Yup- the fact that they said anyone who had a plan at the time it was 'announced' will get it takes all the pressure away from people screaming for it to be released before their plan ends (as mine did yesterday!)

Yeah, that was an excellent decision!

Especially when the betas always seem to take about 3 months!

When has it been 3 months?

I remember generally being about 5-6 weeks

This one came out early April…it’s June tomorrow….just feels like a long time maybe!

[SLiC]

Just a heads up if you use soundtoys …the recent 5.4 update caused CPU spiking specifically in Bitwig, they have just released 5.4.1 to fix it

[catzilla]

Anyone else getting this thing where the stop button on the transport bar randomly stops working? I can't reproduce it but I had to force quit a couple of times already. Not sure how to report this.

Restarting the audio engine helps me in this case. I mean full restart through terminating it first.

[neverbeeninariot]

Bitwig Studio 5.0 Beta 9 (Pre-Release) is up.

Changelog

[SLiC]

Bitwig Studio 5.0 Beta 9 (Pre-Release) is up.

Changelog

I’m not seeing it again, maybe as my plan expired … an someone cut and paste it please?

[neverbeeninariot]

My bad - malformed URL in last post, should be working now. But for the hard of clicking...

New Features
* Button & Buttons (Interface) modulators, and Button (Logic) Grid module: All have a Bipolar option now, for toggling between +100 % (+1) and -100 % (-1)

Improvements
* Manual mappings that launch clips now also trigger their release action when the button is released [32470]
* Pop-up Browser: Information area for the selected result now becomes scrollable when more space is required (instead of changing the height of the Pop-up Browser)
* Copy and paste have been reworked to work much better for incoming modulations, manual mappings, Grid signal connections, I/O buss routings, Sends etc.
* Segments (Envelope) and Curves (LFO) modulators and modules: Smoothing algorithm is smarter now, jumping to the current value on voice start/wake and then smoothing afterwards
* MIDI (Note-driven) modulator: Now has an Inspector parameter for whether to apply Smoothing or not [32452]
* Organ device: Drawbar names now start with the drawbar number

Fixes
* CPU performance of Bitwig Studio should be improved (a regression from v4.4)
* Arpeggiator (Note FX) device: Was often hanging notes when not shown on screen [32642]
* Time Shift (Utility) device: Was stuttering, creating a hanging buffer sound when going to sleep [32614] [32615]
* Select Out (Mix) Grid module: Was not reloading correctly [32508]
* All devices using BWCURVE files [Curves (LFO), Segments (Envelope), Scrawl (Oscillator module), Transfer (Shaper module), Slopes (Data module), and Keytrack+ (Note-driven modulator)]: With points selected in the Pop-out Editor, values can now be typed or edited with the Histogram interface (by clicking the right-facing triangle button) [32509]
* Deleting a collection now remove it from the Quick Sources areas [21586]
* Remote Controls weren't following the device preview for browsing sessions [32453]
* Plug-ins: Synth plug-ins were landing in the Audio FX category
* Track/Project modulator fixes:
* * Project level modulator timing was wrong [32617]
* * Fixed a crash when dragging a time range in project modulator automation lane [32138]
* * Track modulators were not shown in the automation chooser [32595]
* * Now respecting the Exclusive Solo preference when using keyboard shortcuts to toggle solo (a regression) [32677]
* Deleting an automation time selection now applies to the left-most value to the selection instead of the right-most value (a regression) [32678]
* Removing the audio output interface and reactivating the audio engine was leading to a place where playback never stops (a regression) [32574]
* Track Remotes modulator mappings were not saved correctly when saving a clip to the library [32571]
* Remote Controls were uninitialized for certain controllers, leading to wrong mappings [32675]
* Fixed a crash when closing the remote controls editor [29967]
* Devices were sometimes showing the "Default" preset name instead of the device name
* ALS (Ableton) Import - Wasn't displaying the names of the cells from Drum Racks [27834]
* ALS (Ableton) Import - Some volume levels were importing incorrectly [32661]
* Plug-ins: Waves Studio Rack was crashing on load (a regression) [32390]

[tlkmx]

Imo i think a few things should be possible to upgrade the browser. Let me know if its a stupid idea and if there are workaround.

I would like to be able to attribute miniature the same way its done for the pack for any of the things in my quick source.
Like right now i have too many folder looking the same and its impractical..



Why the packs can have one when way more importantly my specific folders cannot ?

__________

I think it would be great if it was possible to select for every specific quick source a default state.
Like i want that my quick source is always opened with the filter location on so i see all the folders..



__________

I think it would be really nice to also have the possibility to sort order by file size.
Also i would enjoy a most used sorting order but maybe its too complicated ?

Also having a clearer limit between native plugins. vst's clap and preset with maybe a line just showing separation ?

Does any of theses have workaround ? is it stupid or do you think it make sense ? I will write to them depending haha i dont want to propose more dumb functions no one care

[Bobby L'Avenir]

Midi capture/retrospective record is essential, i'd happily skip all the latest stuff in favour of this, waaaaaay to many ideas get lost because this isn't available

https://www.monkeyc.audio/

Problem Solved!

Tried the demo, too messy, better if it's in the daw like cubase, ableton, studio one and so many others

[pdxindy]

Tried the demo, too messy, better if it's in the daw like cubase, ableton, studio one and so many others

Try Bird's Midi Cap. Not messy. Simple to use.

https://www.birdsthings.com/midi-cap

[muzicxs]

Try Bird's Midi Cap. Not messy. Simple to use.

https://www.birdsthings.com/midi-cap

Looks great! And for only 14 dollar!

[mxbf]

stupid criticisms / drunk / maybe a kerne of truth

I wish the arrangement view had more features like from Cubase and Logic's arrangement, where you can easily just drag around sections and use the arrangement more flexibly as a sketch pad that will lead to a finished production.

Cubase has an "arranger track" and I think dragging entire sections around in Logic is really easy (havent booted logic in almost a year so i might be wrong, but i seem to remember it being easy), this is the kind of feature I would want. If you're not familiar with the "arranger track" this shows it:

Cubase is so clunky and convoluted though, I don't really enjoy using it where Bitwig is immediate and flexible so it is more conducive to creative expression. Cubase is more sophisticated in many ways though, I will say.

Personally I find the session view in Bitwig basically completely useless besides just as a place to store a bunch of audio files that I need to cut down before placing into the tracks. I don't boot up Bitwig when I am wanting an Ableton "session view" workflow. I would just use Ableton for those times. I also just don't like the session view at all. the Arrangement View is where most of the attention should go, and the session view is not that important. any features you can add to the arrangement side are more important for the actual process where people are fleshing out and completing their best possible productions.

anyway, thanks for such amazing software that has made producing so fun.

[shyko76]

the Arrangement View is where most of the attention should go, and the session view is not that important.

Well, for me it's quite the opposite. Session view is THE reason to use something like Bitwig or Live (in addition to a classic sequencer).

[LarsDaniel]

the Arrangement View is where most of the attention should go, and the session view is not that important.

Well, for me it's quite the opposite. Session view is THE reason to use something like Bitwig or Live (in addition to a classic sequencer).

Exactly. I think @mxbf is making some wild assumptions about what “people” do with Bitwig.
I use Session view 99% of the time, as Bitwig is the core of my “live” setup. For me, Bitwig Session is like an instrument. For “classic” daw work, I still go to Cubase (mostly), as I am having too much trouble adjusting to the way transport (and some other things) work in Bitwig Arrange.
So yes, there are things I wish was possible in Arrange, but even if I could feel at home in Arrange (like I do in Cubase), it would not be the reason for using Bitwig. Session view is.

[Hanz Meyzer]

I agree that the arrangement clips lack of grid lines, the fill need some transparency (why not optional)? Also contrast slider for gridlines. Would be nice if Bitwig team actually was improving this core feature stuff. The clips also waste a lot of space, the whole clip in height could be used to draw the note content. Seeing note content side-by-side is quite important in my opinion, to keep an overview of the interaction of instruments... Bitwig makes it really hard to do "classic" note/rhythm arrangement. Not everybody wants to do generative stuff.

[pdxindy]

I would like to be able to attribute miniature the same way its done for the pack for any of the things in my quick source.
Like right now i have too many folder looking the same and its impractical..

I would like to be able to create our own packages with their own graphic... and being able to add a graphic for Collections and Folders would be welcome.