In the Help/About section of the Bitwig dashboard.
Bitwig 5 is up
so we might fallback to 4.4.10 -
- KVRAF
- 4066 posts since 3 Jul, 2022
Damn !
-
- KVRAF
- 9567 posts since 6 Jan, 2017 from Outer Space
Yeah, we get a new version before…
-
- KVRer
- 26 posts since 17 Dec, 2009
Bitwig Studio 5, Beta 7 [released 24 April 2023]
New Features
Bottom right area of the Pop-up Browser now has:
An X button for closing without inserting selected content
A Confirm button for inserting selected content and closing the browser
A pair of ▴ and ▾ buttons, for selecting the previous and next result in the list
Delay compensation (PDC) now includes group- and project-modulators
Improvements
Opening the Devices filter automatically unfolds the Devices item
Show Confirm button in Pop-up Browser, even if nothing is selected
Mute/Solo/Arm shortcut commands now operate on all selected tracks [32244]
Fixes
Duplicate instances of project remotes were being displayed [32308]
Pitch expression editing in Detail Editor Panel was more sensitive than in version 4 [32518]
Fixed an incorrect automation follow behavior adjusting the end of an Arranger clip [32387]
Recording the Launcher with Record on scene launch records clips for unarmed tracks (a regression) [32365]
Improved behavior when remote controls should follow any selection
Default sequencer latency is set to 50 ms now
Option to Convert Track (to Instrument/Audio/Hybrid) now works in the Mix view [15422]
Note FX Layer and Note FX Selector devices: Inactive note FX layers never go to sleep now [32438]
HW Instrument device: Was sometimes sending first note on wrong channel [32532]
Audio Sidechain modulator: Wasn't working well when used on plug-ins [32380]
Some old projects didn't reopen in Bitwig 5 [32433]
Crash in some cases of double-clicking on clip loop bar when there is automation in the track [30786]
Curve (MSEG) device/Pop-out Editor fixes:
Histogram window wouldn't open with curve points selected
Typing to edit curve points would close the Pop-out Editor
Curves: Pre-highlighted points could 'jump' after clicking [32459]
Moving points in the Pop-out Editor with [CTRL] pressed was opening the preset browser on release [32290]
Crash when replacing Curves Grid module with Segments Grid module [31888]
Some touch interaction were not working in curve Pop-out Editor [31861]
Various browser fixes/improvements:
Favorites-only filter (the special star in the Browser) was not being saved with the Use current selections functions [32510]
Suggested autocomplete actions are now more clever than before
SEARCH-FIELD IS NOW FOCUSED< EVEN IF CAPS LOCK IS ON
Allow multi-selection of Device Type (Instrument/Note FX/Audio FX) using the SHIFT modifier
Fixed rare out-of-memory crashes with huge libraries (more than half a million files) [32334]
Regression b5 to b6: Device/Preset browsing using cursor keys was broken [32486]
Some invalid browser index files could crash the application [32366]
Various project modulator/remote control fixes:
Fill button had no effect on Occurrence Operators when controlled by project modulators [32528]
Modulating the global crossfader is now stored [32362]
Crash when using undo after moving global modulators to Crossfade Mode [32475]
Assigning remote controls for time signature shouldn't be (and now isn't) possible [32439]
CLAP plug-ins: Fixed note expression gain scaling
VST3: Fixed crash with iZotope BreakTweaker [32482]
Spanish localization was making Inspector width break on no selection [32513]
Removed incorrect deprecated message in extensions API [27649]
New Features
Bottom right area of the Pop-up Browser now has:
An X button for closing without inserting selected content
A Confirm button for inserting selected content and closing the browser
A pair of ▴ and ▾ buttons, for selecting the previous and next result in the list
Delay compensation (PDC) now includes group- and project-modulators
Improvements
Opening the Devices filter automatically unfolds the Devices item
Show Confirm button in Pop-up Browser, even if nothing is selected
Mute/Solo/Arm shortcut commands now operate on all selected tracks [32244]
Fixes
Duplicate instances of project remotes were being displayed [32308]
Pitch expression editing in Detail Editor Panel was more sensitive than in version 4 [32518]
Fixed an incorrect automation follow behavior adjusting the end of an Arranger clip [32387]
Recording the Launcher with Record on scene launch records clips for unarmed tracks (a regression) [32365]
Improved behavior when remote controls should follow any selection
Default sequencer latency is set to 50 ms now
Option to Convert Track (to Instrument/Audio/Hybrid) now works in the Mix view [15422]
Note FX Layer and Note FX Selector devices: Inactive note FX layers never go to sleep now [32438]
HW Instrument device: Was sometimes sending first note on wrong channel [32532]
Audio Sidechain modulator: Wasn't working well when used on plug-ins [32380]
Some old projects didn't reopen in Bitwig 5 [32433]
Crash in some cases of double-clicking on clip loop bar when there is automation in the track [30786]
Curve (MSEG) device/Pop-out Editor fixes:
Histogram window wouldn't open with curve points selected
Typing to edit curve points would close the Pop-out Editor
Curves: Pre-highlighted points could 'jump' after clicking [32459]
Moving points in the Pop-out Editor with [CTRL] pressed was opening the preset browser on release [32290]
Crash when replacing Curves Grid module with Segments Grid module [31888]
Some touch interaction were not working in curve Pop-out Editor [31861]
Various browser fixes/improvements:
Favorites-only filter (the special star in the Browser) was not being saved with the Use current selections functions [32510]
Suggested autocomplete actions are now more clever than before
SEARCH-FIELD IS NOW FOCUSED< EVEN IF CAPS LOCK IS ON
Allow multi-selection of Device Type (Instrument/Note FX/Audio FX) using the SHIFT modifier
Fixed rare out-of-memory crashes with huge libraries (more than half a million files) [32334]
Regression b5 to b6: Device/Preset browsing using cursor keys was broken [32486]
Some invalid browser index files could crash the application [32366]
Various project modulator/remote control fixes:
Fill button had no effect on Occurrence Operators when controlled by project modulators [32528]
Modulating the global crossfader is now stored [32362]
Crash when using undo after moving global modulators to Crossfade Mode [32475]
Assigning remote controls for time signature shouldn't be (and now isn't) possible [32439]
CLAP plug-ins: Fixed note expression gain scaling
VST3: Fixed crash with iZotope BreakTweaker [32482]
Spanish localization was making Inspector width break on no selection [32513]
Removed incorrect deprecated message in extensions API [27649]
-
- KVRAF
- Topic Starter
- 12098 posts since 2 Dec, 2004 from North Wales
I am glad they said everyone who had a licence when the beta started could get this or I would have just missed it!
Maybe a ew more weeks yet...
Maybe a ew more weeks yet...
X32 and 24C mixers, S88MK3, Live + PUSH 3, Osmose, RedShift 6, Pro3, S4, Tempera, Syntakt, Digitone, OP1-F, OPXY, TR-1000, Eurorack, TD27 Drums, Guitars, Basses, Amps and of course lots of pedals!
-
- KVRAF
- 5068 posts since 27 Jul, 2004
It´s not listed in the fixes but the browser preview that transient were cutoff when having set audio device to a higher latency (1024 samples or more) was fixed too...
Now browser preview works in this situation again like it did in V4
Now browser preview works in this situation again like it did in V4
-
- KVRAF
- 19846 posts since 16 Sep, 2001 from Las Vegas,USA
The browser is still a mess in Beta 7. I sent in yet another bug report.
It got me to thinking....my BUP which I received with my original purchase is good until July 3rd but if I had paid for a year of BUP I would basically have paid them to beta test and bug hunt their software. That just rubs me the wrong way. As it is I'm watching Bitwig get worse (for me) over time. One usually equates "Update" with progress not regress .......
I don't need modulation toys like MSEGs etc. I just need a solid DAW for composition with a plugin manager that makes it easy to organize, find, and call up the plugins I need. I didn't think that was too much to ask. Apparently I was wrong.
Guess I'm stuck cussing at FL Studio every day for the stupid way it handles Mod Wheel, Pitch Bend, and Aftertouch data.....
It got me to thinking....my BUP which I received with my original purchase is good until July 3rd but if I had paid for a year of BUP I would basically have paid them to beta test and bug hunt their software. That just rubs me the wrong way. As it is I'm watching Bitwig get worse (for me) over time. One usually equates "Update" with progress not regress .......
I don't need modulation toys like MSEGs etc. I just need a solid DAW for composition with a plugin manager that makes it easy to organize, find, and call up the plugins I need. I didn't think that was too much to ask. Apparently I was wrong.
Guess I'm stuck cussing at FL Studio every day for the stupid way it handles Mod Wheel, Pitch Bend, and Aftertouch data.....
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- KVRAF
- 1905 posts since 2 Apr, 2015
Just think of that, testing software, who would have thought it!
My plan had run out a few months before beta 5 so I paid for another year when it came out and one of the main reasons is because of the browser changes and how much I hated the last one.
I guess you don't need to renew in July though, it is your choice. From my perspective you get V5 for no cost, but for me there is cost, c'est la vie.
My plan had run out a few months before beta 5 so I paid for another year when it came out and one of the main reasons is because of the browser changes and how much I hated the last one.
I guess you don't need to renew in July though, it is your choice. From my perspective you get V5 for no cost, but for me there is cost, c'est la vie.
-
- KVRAF
- 26966 posts since 3 Feb, 2005 from in the wilds
If you don't want to test betas, then don't. Nobody is forcing you to do it.Teksonik wrote: Wed May 24, 2023 5:40 pm The browser is still a mess in Beta 7. I sent in yet another bug report.
It got me to thinking....my BUP which I received with my original purchase is good until July 3rd but if I had paid for a year of BUP I would basically have paid them to beta test and bug hunt their software. That just rubs me the wrong way.
-
- KVRAF
- 4066 posts since 3 Jul, 2022
Fully agreed... And saying you don't care about modulations as a bitwig user is like saying you don't like meat in a barbecue party... blasphemy....pdxindy wrote: Wed May 24, 2023 5:55 pmIf you don't want to test betas, then don't. Nobody is forcing you to do it.Teksonik wrote: Wed May 24, 2023 5:40 pm The browser is still a mess in Beta 7. I sent in yet another bug report.
It got me to thinking....my BUP which I received with my original purchase is good until July 3rd but if I had paid for a year of BUP I would basically have paid them to beta test and bug hunt their software. That just rubs me the wrong way.
-
- KVRAF
- 4066 posts since 3 Jul, 2022
Well, I understand your logic and you are somehow right in principle.Teksonik wrote: Wed May 24, 2023 5:40 pm . . I would basically have paid them to beta test and bug hunt their software.
But.
It is factually unrealistic to hope that a software as complex as Bitwig (or any DAW) will work straight out of the box with your computer, your midi setup, your VSTs, your audio card without beta.... There is just way too many cases to test. It is not achievable in a reasonably financially realistic way.
For your information, for softwares that are developped in a controlled environment, you often have 50k to 100k automated tests. But those are tests done "in a lab", you need to confront them to the reality of the wild life... That's why everybody does beta.
And that's why you should take it as an opportunity to make sure the system works for you. Not as a service you are providing them.