Bitwig 4 - what's gonna be in it?

Official support for: bitwig.com
Locked New Topic
RELATED
PRODUCTS

Post

machinesworking wrote: Wed May 05, 2021 1:33 am Apple often depreciate and break 'custom' code, and any company might with such a drastic change in architecture. Then again the Bitwig guys are super smart IMO, the basics are very solid, so any tweaks are probably not that drastic.
What are some things that Apple has broken and deprecated?

Also, from what I've seen the transition to Apple Silicon has been pretty smooth. I wouldn't be surprised if it hasn't been an issue.

Post

coroknight wrote: Wed May 05, 2021 1:44 am What are some things that Apple has broken and deprecated?
One such thing has been the ability in macOS to audition a ".mid" file in Finder by pressing space to activate Quicklook. Maybe Apple is mindful of the forthcoming MIDI 2.0 and is reserving any related improvements.
Bitwig 5.1.6 + Akai MIDIMix + Launchpad X + MuLab 9.3.18
Roli Lumi Keyboard x 2 + Universal Audio Apollo Twin X
Mac Mini M1 16GB/4TB + macOS 14.4 Sonoma

Post

Well, no v4 today either.

2 new videos just dropped. Feels like they're "buying time" with those videos recently :wink:

https://www.youtube.com/watch?v=Y80apKuClH4

https://www.youtube.com/watch?v=pqDwl7fpzyQ
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

+ a new press release / tutorial on Polymer:

https://www.bitwig.com/learnings/musict ... lymer-139/
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

Can you see waveforms on Maschine's screen when using it with Bitwig?

Post

stamp wrote: Wed May 05, 2021 2:36 pm Can you see waveforms on Maschine's screen when using it with Bitwig?
What happened to the announcement?

Post

stamp wrote: Wed May 05, 2021 2:36 pmCan you see waveforms on Maschine's screen when using it with Bitwig?
I really, REALLY doubt it. Most we could count on are text, maybe some faders like in Moss' Push2 script. Perhaps it's even the same - or slightly modified - extension that Moss made?

https://youtu.be/Y1OhZq6EKmY
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

antic604 wrote: Wed May 05, 2021 1:26 pm + a new press release / tutorial on Polymer:

https://www.bitwig.com/learnings/musict ... lymer-139/
That article was published weeks ago, a late press release! Definitely stalling!
X32 Desk, i9 PC, S49MK2, Studio One, BWS, Live 12. PUSH 3 SA, Osmose, Summit, Pro 3, Prophet8, Syntakt, Digitone, Drumlogue, OP1-F, Eurorack, TD27 Drums, Nord Drum3P, Guitars, Basses, Amps and of course lots of pedals!

Post

SLiC wrote: Wed May 05, 2021 2:48 pm
antic604 wrote: Wed May 05, 2021 1:26 pm + a new press release / tutorial on Polymer:

https://www.bitwig.com/learnings/musict ... lymer-139/
That article was published weeks ago, a late press release! Definitely stalling!
Yeah, just noticed that too :)
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

antic604 wrote: Wed May 05, 2021 2:47 pm I really, REALLY doubt it. Most we could count on are text, maybe some faders like in Moss' Push2 script. Perhaps it's even the same - or slightly modified - extension that Moss made?
If that's the case the video is pretty misleading since the thumbnail shows Maschine with waveforms.

Post

Merger of Izotope + NI + Bitwig = trinity of love or triad of destruction? Maybe that’s why...
Han

Post

coroknight wrote: Wed May 05, 2021 1:44 am
machinesworking wrote: Wed May 05, 2021 1:33 am Apple often depreciate and break 'custom' code, and any company might with such a drastic change in architecture. Then again the Bitwig guys are super smart IMO, the basics are very solid, so any tweaks are probably not that drastic.
What are some things that Apple has broken and deprecated?

Also, from what I've seen the transition to Apple Silicon has been pretty smooth. I wouldn't be surprised if it hasn't been an issue.
So do you have a couple hours? :hihi:

Every transition has had it's victims. This time we have NI, who will take forever to port, because they've used the same GUI toolkit (from the horses mouth) etc. since 15 years ago. So I'm certain Apple have long since depreciated the code, which along with not working on Apple Silicon, doesn't do interface resizing or VST3. So one way to have issues porting to AS is to use super old code. My other DAW Digital Performer has beginnings in 1985, so there's no doubt they have some work cut out for themselves.

The other way is to use tricks not recommended by Apple or toolkits that 'port' code between Windows and Mac OS. Apple actively depreciates or cripples this sort of thing, but shortcuts are going to happen for a lot of developers and then they will drastically fail in an OS update. Hopefully Bitwigs own Java and toolkit they built for their GUI doesn't fall into this category, otherwise Bitwig will take a long while to get to native AS.

The third thing is worth mentioning, Apple are not perfect, they're guilty of both the above things themselves, and they often depreciate code that no one can figure out why they did it other than control. Melda plug ins and their main developer have ranted about this for years, and to his credit, even though it comes across as pure hate for the company, even putting a "How to switch to Windows" page on his website in reaction to changes in Catalina that cost massive amounts of developer time, Melda did all the work, and ported to native AS quickly because getting things ready for Catalina and Big Sur, made them ready for porting to AS.

Anyway we could go even further down this hole, but suffice to say Apple does not care one iota about backwards compatibility. The good part of this is in all the years of using their products I can count on one hand the amount of crippling bugs I've seen, whereas Microsoft is the exact opposite, supremely backwards compatible, but I spent last weekend fixing my roommates laptop, and absolutely nothing worked. The disk was reading 100% acticvity in Task Manager, with nothing running, and it slowed it to a total crawl, like 3 minutes for Chrome to open up.The bug was well documented online, but the solutions were nonsense. Nothing worked and a full reinstall of Windows 10 was the only solution after trying dozens of things like fixing the file structure, registry checking, virus scans, defragging, Smart disk check, removing running processes etc.etc. etc. Slightly faster but still 1/10 the speed it should be. Deep disk checking wasn't possible because the disk is reading 100% activity, so we put in a new SSD, upon removing the old HD it check out fine doing a deep scan on another computer...

Anyway probably more than you wanted, but the issue of Apple making it hard on developers to keep up with their moving target is well known, and we will see as far as porting to native Apple Silicon, because it's been 6 months and so far only Logic is native.

Post

machinesworking wrote: Wed May 05, 2021 8:58 pmAnyway probably more than you wanted, but the issue of Apple making it hard on developers to keep up with their moving target is well known, and we will see as far as porting to native Apple Silicon, because it's been 6 months and so far only Logic is native.
Reaper is as well...

Post

Maybe Bitwig wanted to bring native Apple Silicon support in the next version but have hit some snags?
MacPro 6,1 // Live 11 // Bitwig 4 // Reason 12 // Logic X // Soundtoys // U-he // FabFilter // Arturia // Vintage Hardware

Post

Apple are keeping lazy devs on their toes ;)

Locked

Return to “Bitwig”