That's it for me, these posts got deleted like so many other posts. I tried my best but I'm going now, if it's a fair thing what they have done then good things will come their way, if not let's see what happens with the future of PG. All I know is that when I leave this world to God I have done the right thing.

Originally Posted by parapente
For me the absolute best feature I used of version 7 of the plugin (and in general BiaB 2025) is THIS

LOL I wish I could get a refund on all the man hours I put into it year in year out frown

This is what I used to do, record, mix, make up tracks with BB/RB then create videos for artist that went on CMT but there were too many issues with BB/RB so I had to go full time trying to make them modern and professional since 2009.
I don't think I'll be getting back to that, in this lifetime anyway.


Originally Posted by mrgeeze
Don't think there's a roadmap. Its been a discussion point by users for at least 3-4 years.
Pgm response so far seems to be: "You don't need that."

It will happen one day, imo, a few months before AAPL decides to shut down Rosetta.

Very willing to be wrong.......again.
Originally Posted by ZUrlocker
I'm disappointed with the lack of progress or even news about a future M1 native version that does not require Rosetta. I'm a longtime customer, but I'm not buying again until there's a native M1 version.

I understand how hard it is for a small company with an aged code base to migrate to a new approach. My suspicion is it will never happen because the code base and compiler are so ancient. At some point, Apple will stop supporting Rosetta and then what?

"You don't need that."
this was the same statement when Win users kept asking for a 64bit version of Biab, "JBridge is just fine", it was argued so hard by PG for years.....until Apple banned 32bit apps, only then did PG create a 64bit Biab.
I have been trying hard to get PG to move the generate code to the C++ JUCE Biab VST plug-in to give a full crossplatform for Mac at the same time as Win. It's a shame that PG have to spend 6 months on Win then another 6 months on Mac to code the same thing. With the JUCE Plug-in it is ready now for Win and Mac as being JUCE it can be compiled to and OS standalone or Plug-in, this means there could be and iPad version. But the wait will be the backend bbw4.app that has to wait 6 months. Using JUCE will give better UI and things will be implemented easier.
I think every other company has a Win/Mac and even Linux version released at the same time !
If something unforeseen happens, do we then panic and run to transfer to a true crossplatform programing ?
I suppose why do the right thing when it can be put off, stick with 255 bar limit and time signatures that won't match your DAW and have to stay inside Biab to work also.

But why listen to the rantings of a crazy man, the voice of one crying in the wilderness.

Quote
JUCE is a cross platform framework allowing a single codebase to compile to native applications and plug-ins with the same user experience on Windows, macOS, Linux, iOS and Android, across both desktop and mobile. Native applications can be launched in the iOS and Android device simulators to simplify testing and debugging, and can be packaged up for distribution within the mobile app stores.

JUCE is the most widely used framework for audio application and plug-in development. It is an open source C++ codebase that can be used to create standalone software on Windows, macOS, Linux, iOS and Android, as well as VST, VST3, AU, AUv3, AAX and LV2 plug-ins.

JUCE allows developers to focus on the most valuable parts of their software by taking care of the differences between operating systems (both desktop and mobile) and plug-in formats. With JUCE’s library of digital audio processing (DSP) building blocks you can quickly prototype and release native applications and plug-ins with a consistent user experience across all supported platforms. Using JUCE also future-proofs your products against operating system and plug-in host updates.

JUCE makes it easy to create both standalone audio applications or plug-ins that can be loaded inside digital audio workstations (DAWs) like Logic, Live, Pro Tools, FL Studio or Cubase. A single JUCE project can be used to create VST, VST3, AU, AUv3, AAX and LV2 plug-ins from the same source code, and also provides the functionality required to host these plug-in formats in your own software.