intelligence within it to do all the functions it needs
But, as I mentioned earlier, forum users were unable to agree on what functions the plugin needs. I suspect many current Band-in-a-Box users have not given much thought to what functions they would expect the plugin to perform.
I can generate up RealDrums directly in Reaper so that can be done in the Plugin easy enough
That is an apples to oranges comparison between your Reaper script and plugin code. There is no way a non-coder like myself can judge how easy it is to modify the plugin code so the plugin can generate up RealDrums. I don't understand how that statement is relevant to the conversation.
The whole idea of the Plugin was to be able to add extra instrument tracks to a recorded DAW session.
Agree but let's change the statement just a little bit; how's this:
The whole idea of the Plugin should be to be able to add extra instrument tracks to a recorded DAW session.
Why did I change your statement from "was" to "should be"? Because presently a user can not save a Band-in-a-Box (BiaB) SGU or MGU file and know for sure the file will work properly in the plugin. Back to the first part of this discussion, certain main BiaB program functions that are saved in a SGU or MGU file do not work in the plugin.
My highest priority is for the plugin to utilize ALL the main program functions that can be stored in a SGU or MGU file.
For example the main BiaB program SGU or MGU file can store MultiStyles, can the plugin reconstruct them? The main BiaB program SGU or MGU file can store F5 Bar Settings, can the plugin implement those settings?
It was to attract NEW DAW only users not old Biab users that just want to get the Biab track into a DAW, they can just drag n drop.
I agree but what producer is going to work on a SGU or MGU file in the main BiaB program only to find the work does not correctly transfer?
Let Biab be for the old and current users but let the BBPlugin be for Professional/DAW/Studio users not old Biab users
No! It's not an either or situation and it never should be. The main BiaB program is where an audio producer should start the song creation and then use the plugin to review alternate instrumentation and riffs.
All this that I have been posting with Sforzando can be put into a separate BBPlugin Standalone that can be used for a Live Arranger.
While that is a nice idea there is no sign PG Music is interested in competing with arranger keyboards. Sometimes when you are a small, family owned business you choose not to compete with giants of the industry.
You are totally limiting the BBPlugin potential by making it for old users that just want the Biab tracks in their DAW that they now have in Biab main app, making a mirror image of the main app in a plugin is pointless.
Why is wanting the plugin to accurately recreate the tracks in a main BiaB program SGU or MGU file pointless? How does that limit the plugin potential? Don't you believe the plugin should accurately playback a SGU or MGU file?
The BBPlugin working how I showed could open a frozen SGU directly in the BBPlugin with identical layout and sections and read the frozen section data in an SGU/MGU and instantly play that, or it can get bbw4 to open the frozen SGU/MGU track data and render that direct to the SavedTracks folder as text and midi data (NO WAVs).
But the frozen tracks were created in the main BiaB program. You just proved my point that an audio producer likely will use both the main BiaB program and the plugin. Earlier you said leave the main BiaB program for the old folks and let the DAW users have the plugin. I just can't envision up and coming audio producers getting SGU or MGU files from us old folks.
Just a little joke here.
Great conversation. It's nice to exchange thoughts and look at different points of view.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean