Originally Posted by musocity
All the bbw's are the same and have same Al Gore functions Plugin and RealBand can call on all of these if made to do so.
It doesn't generate up tracks using a different Al Gore Rhythm it's the same function that's called on.
That's why the bbw4 version is now 1124 as it used the flac and was just changed for that fix of not using flac.
They can be made to cal on every Biab function but we certainly don't want that, it's just the basic generate Al Gore Rhythm code that needs to be moved over to the C++ JUCE Plugin, they had to do this with Mac in the first place also to get the Mac version but spending 6 months to move the new version features/functions code over to Mac each year is crazy. The Mac version of the Plugin is ready now because of the crossplatform JUCE code used but it has to wait 6 months for the backend bbw4.app to get the new code added. Isn't that a good reason to move the generate code to JUCE ?
Once it has the code in the Plugin and a Track Edit you will have instant generate in any DAW with non destructive editing, you won't have to wait for wav files to be rendered to drop in. The current 2024 bbw4.app would probably work with the new 2025 Mac JUCE Plugin except for the flac on Mac right now but Mac users will still need to wait for 6 months.

That's why I asked, generate up and upload some sample Brent solos for MV either mp3 or frozen SGU so he will see what you say the flagship Al Gore can do.

<< It doesn't generate up tracks using a different Al Gore Rhythm it's the same function that's called on. >>

That's incorrect. Open RealBand and generate a track. Highlight a section of track and attempt to replace that section with RT-1152 and see if the section is replaced with silence. It isn't replaced when I attempt it here. RB and the Plug-in don't recognized MultiStyles, RT-silence and many other features and tools of the main program. I'm sure that's intentional when you think about it. It's giving users raw track audio data they can manipulate themselves in a DAW. Remember, DAWs are post audio generation editors. BIAB generates audio.

BBWs may all be the same but the bottom line is you, MusicVillian nor anyone else can produce the same complexity arrangements reading RealTrack folder wma files or reading them direct into Reaper with scripts Reading a wma file direct bypasses 100% of BIAB's internal processing and manipulation of those wma files whether it's done by bbw or not. There's something in BIAB no other program has and ripping audio from the program doesn't capture it. BIAB can combine Part Markers, Bar Settings, the RealTrack Medley Maker, Song Form, and MultiStyles and activate all of them across a single measure. Those actions used together are producing audio that is literally impossible to generate in any other existing software with audio that functions exactly like a RealTrack. It can only be done manually editing and comping multiple tracks which takes far longer than hitting the play button.

What MV thinks is a performance track is no different from a audio snippet playing a G to F progression other than the length of the audio clip. Look at the pictures above. It's 1:13 minutes of audio clip from a RealTrack wma file. PG Music generated the same as they generate all demos by setting up the BIAB Chord Sheet to play a backing band along with the solo clip.

<< That's why I asked, generate up and upload some sample Brent solos for MV either mp3 or frozen SGU so he will see what you say the flagship Al Gore can do.>>
That's what demos do. Learn how to use BIAB and it's advanced tools, features, and processes and you can make tracks and songs that sound just like theirs.

Last edited by Charlie Fogle; 01/12/25 01:26 PM.
BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.