yes the RC interface seems a bit quirky to me also was just about to give up - there is a new Beta 3 being tested one of the features is Source code clean-up, building with C++14 - yes PG could learn, you can drop any midi into the chord track and it will auto fit to the scale/chord. Yes RT love em. It was mentioned in another page about linking the midi of real charts to the real audio so you could enter a midi solo and it would try to fit the corresponding audio of the real charts notation to your midi and like multiriffs give you different ones to choose from that would be closer to your midi notation you need rather than just using any bit of solo the real track artist was playing to fit to your song - RapidComposer has a similar regenerate function (below). BB could well use a multiriff like rb and in the bb audio editor window be able to access the other audio tracks not just the user audio so it could have the same audio edit window as rb that lets you select any track and add some non destructive pan and volume adjustment wav overlays for starters then maybe later a separate automation node lane underneath.
I was thinking maybe we could start a pledge donation 64 c++/vsti upgrade, somewhere in here $30,000 was mentioned - I don't know how many users are hobbyist and how many use it for music production. Maybe we could start a pledge page and see how it goes ? - I would be willing to pledge $1,000 as a starter.
"I find it really strange that a program that has been around for this long has got so many problems. Nevertheless, -I like the concept of BIAB and there are simply nothing like it on the market but the issues I have experienced should have been taken care of before release. A program like this should inspire and not make the user frustrated and loose inspiration. PG should offer a Demo version ! "
I think that nailed it, my sentiments exactly. They have started now on the 2017 version, so that gives them 6 months to reprogram a solid C++ version, if there is not a profound change for 2017 that is it for me, Hasta la vista, baby. If so I will get into scripting in Reaper and create a script users can use and share instrument/drum tracks they have recorded/created and Reaper reads the BWF chord markers & Acid tempo within the wav file (created in Reaper's render dialog from the track makers) and then fits them to your Reaper's chord/marker track. Having very large forum with so many users there would be a large community input of tracks and further script development.
"I find it really strange that a program that has been around for this long has got so many problems. Nevertheless, -I like the concept of BIAB and there are simply nothing like it on the market but the issues I have experienced should have been taken care of before release. A program like this should inspire and not make the user frustrated and loose inspiration. PG should offer a Demo version ! "
I think that nailed it, my sentiments exactly. They have started now on the 2017 version, so that gives them 6 months to reprogram a solid C++ version, if there is not a profound change for 2017 that is it for me, Hasta la vista, baby. If so I will get into scripting in Reaper and create a script users can use and share instrument/drum tracks they have recorded/created and Reaper reads the BWF chord markers & Acid tempo within the wav file (created in Reaper's render dialog from the track makers) and then fits them to your Reaper's chord/marker track. Having very large forum with so many users there would be a large community input of tracks and further script development.
This thread is painful read. Why do you keep making these silly posts when you clearly have no idea what you are talking about? You obviously have no idea what the difference is between Object Pascal and C++ yet you posting this nonsense. Object Pascal and C++ are basically interchangeable, simply changing from one language to another will accomplish nothing other than wasting thousands of manhours.
They have started now on the 2017 version, so that gives them 6 months to reprogram a solid C++ version...
This statement clearly indicates to me that very little is known about the time it might take to translate a computer language for a program of this size.
Moreover, C++, Object Pascal, C# etc are all high-level languages. The compiler converts the high-level source code to machine code instructions that the processor can handle. Essentially, the end result machine code for "Hello World" is the same regardless of what high-level code it started as. The source code is not what is executed when you launch the program.
We all (myself included) want reliable and robust products, and improvements to the interface.
However, yes, please close this thread, it's littered with nonsensical statements.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
Win10Pro,i9,64GB,2TBSSD+20TBHDDs,1080TI,BIAB'24,Scarlett18i8,Montage7,Fusion 8HD,QS8,Integra7,XV5080,QSR,SC-8850,SPLAT,FL21&others,Komp.14,IK suite&others, just a guitar player-AXE FX III &FM9T, FishmanTP, MIDIGuitar2, GK2/3'sw/GI20
However, yes, please close this thread, it's littered with nonsensical statements.
If this is the new standard then LOTS of threads here would have to be closed!
I am actually surprised you would take this stance; weren't you the one who created animated screenshot demos showing PG how to redesign the GUI? To me it seems Pipeline is making specific suggestions in that same spirit! He might be underestimating the time required (or not if the right team were in place) but his main point that this software needs more than an annual fresh coat of paint is one the majority of users would probably agree on.
And a complete rewrite is sometimes necessary to move forward. However, my suggestion, as always, would be a complete rewrite but NOT of BIAB or RealBand! Instead, package that sweet RealTrack engine and functionality into a VSTi and market it to the whole world of digital producers instead of the small niche that uses BIAB. Leave out lots of the features that are applicable to a stand-alone program and create a streamlined killer VSTi that lets me use RealTracks in my DAW. Not in RealBand...My DAW!
And keep BIAB and RB just as they are with annual bug fixes for anyone who loves those interfaces!
However, yes, please close this thread, it's littered with nonsensical statements.
If this is the new standard then LOTS of threads here would have to be closed!
I am actually surprised you would take this stance; weren't you the one who created animated screenshot demos showing PG how to redesign the GUI?
Hold your horses JJJ. Please don't misquote me.
The O/P stated: "Best to just close this silly thread. [CLOSED]" I simply agreed that it should be closed, because a rewrite in a different language (that's the subject matter of the thread, isn't it?) is just begging for trouble. And with absolute respect to the O/P's intentions, comments about doing this is 6 months are simply bizarre.
Please note that I also stated:
Originally Posted By: VideoTrack
We all (myself included) want reliable and robust products, and improvements to the interface.
I didn't suggest not to produce a better, more robust version with a better interface. I suggested that starting again from scratch and writing it in a new language was not the way to deliver this. I've been writing high-level and low-level code in multiple languages for most of my working career. Believe me, I know how not to approach this.
And if the truth be known, I actually truly admire Pipeline's stance. There is clearly a genuine intention from Pipeline to improve the product. I support that 100%. And there is always room for improvement. The way it gets delivered is the only part that I have concerns about.
Bring on a better product? Certainly!
I hope this clarifies. Trevor
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
I have also been a programmer for many years! But I don't think any of us has the information to know what shape this software is in and what it would take to convert it to a new language. If large chunks are coded in compiled libraries and only required a GUI replacement it will be a different project than if everything is spaghetti-ed in one big codebase. And it also comes down to your team and their experience. Six months is probably too aggressive but I suspect Pipeline was not stating that as an absolute amount of time anyway.
I can see how the PG staff might not relish users telling them what to do and how to do it but who knows? Maybe they appreciated your screen demos and Pipeline's language suggestion!
One last thing...when he suggested closing the thread and called it silly I think that was sarcasm because someone had called him out in a rude way!
If you are a programmer you can easily take a look at the RB project (exe) and go from there.
I think I was even able to get it into Visual Studio .. you see the basic structure, which gives you an idea how much work it would be. One user here (SolidRock)used to make patches and recompile it. Even posted links on these forums with no complaint from PGMusic. I'm sure that's pushing it a bit for the use agreement.
Just checked; Realband & BiaB exe files open in VS 2010 Ultimate version here .. FWIW I altered how RB looks here, with encouragement from certain PGMusic staff. Granted it's not a major overhaul, but I like it better. Easier to see certain things for me. While tinkering with this I made various 'skins' (Stone look for Rock, Straw for Country, etc) but decided the one that made me most efficient was best for me. I can easily see selected tracks this way, and when used in combination with User Categories (these change the icon on the left end of Tracks) it is also obvious to other users as well. Since Barry does Vox (mainly) and John was the drummer, it is pretty obvious what the track would contain .. plus the Category assigns FX to the Track with their individual settings. Makes quick easy work when mixing a project with multiple SEQ files. Since I recorded the drums with the same mic set up on each song, using a preset Category gives me a good starting point between songs. There are a ton of cool features once you learn them.
For the record, this was a blank project I opened and assigned Categories to show these features. My actual production files contain many more Categories (with various images) so I know that, for example, a given track was John's hi-hat mic or the mic on the kick pedal [snap] .. or the speaker mic in front of the hole on the bass drum [boom]. How far you take it is up to you.
It's all good
Last edited by rharv; 06/03/1602:22 PM.
I do not work here, but the benefits are still awesome Make your sound your own!
Making BIAB a 64-bit app is not an easy task to accomplish. BIAB is written in Apple's Carbon framework which allowed a transition from OS 9 to OS X. So actually most of the BIAB is based on a last century code. Carbon doesn't support 64-bit mode. So in order to make it 64-bit, PG-Music developers would have to transition to Cocoa framework on which all modern Mac and iOS apps are based on which means rewriting BIAB completely from the ground up. Whether or not PG-Music developers are ready to do so we don't know. Rewriting BIAB for modern Cocoa framework will likely break compatibility with older macOSes which means many customers with older OSes will not be pleased about.
But the bottom line here is eventually PG-Music will have to do this transition. Otherwise many customers will have to stick forever on their current Macs with High Sierra or run Windows in Virtual Machines and use Windows version of BIAB.
With Mac going to 64bit only, it seems inevitable that Biab will have to go Cross-platform 64bit re-write now. This will give you the same version/features/release date on both Win and Mac. I can't see any other way, can anyone else see another solution ? Maybe it's already in the pipeline.
You won't like this (and I doubt PG will do it) but:
PG COULD SIMPLY DROP MAC SUPPORT!
As someone else was just today threatening to never buy BIAB again if there wasn't a RB for Mac next time, I could argue PG is already halfway there, to dropping it.
Again, I just don't see the "musical end of the world" need to go there, but that's just me.
Larry
Win10Pro,i9,64GB,2TBSSD+20TBHDDs,1080TI,BIAB'24,Scarlett18i8,Montage7,Fusion 8HD,QS8,Integra7,XV5080,QSR,SC-8850,SPLAT,FL21&others,Komp.14,IK suite&others, just a guitar player-AXE FX III &FM9T, FishmanTP, MIDIGuitar2, GK2/3'sw/GI20
I assume you are correct but since I don't really care if APPLE lives or dies, it means I don't care if BIAB works on Macs or not.
In case there was confusion as to my post when I said:
"...I just don't see the 'musical end of the world' need to go there..."
I was referring to 64-bit, as in "lack of a 64-bit BIAB is not music ending," not RB/BIAB for Mac's.
Larry
Win10Pro,i9,64GB,2TBSSD+20TBHDDs,1080TI,BIAB'24,Scarlett18i8,Montage7,Fusion 8HD,QS8,Integra7,XV5080,QSR,SC-8850,SPLAT,FL21&others,Komp.14,IK suite&others, just a guitar player-AXE FX III &FM9T, FishmanTP, MIDIGuitar2, GK2/3'sw/GI20
Band-in-a-Box® 2025 pour Windows est disponible en Français.
Le téléchargement se fait à partir du site PG Music
Pour ceux qui auraient déjà acheté la version 2025 de Band-in-a-Box (et qui donc ont une version anglaise), il est possible de "franciser" cette version avec les patchs suivants:
Band-in-a-Box 2025 für Windows Deutsch ist verfügbar!
Die deutsche Version Band-in-a-Box® 2025 für Windows ist ab sofort verfügbar!
Alle die bereits die englische Version von Band-in-a-Box und RealBand 2024 installiert haben, finden hier die Installationsdateien für das Sprachenupdate:
Update Your Band-in-a-Box® 2025 to Build 1128 for Windows Today!
Already using Band-in-a-Box 2025 for Windows®? Download Build 1128 now from our Support Page to enjoy the latest enhancements and improvements from our team.
Already using RealBand® 2025 for Windows®? Download Build 5 now from our Support Page to ensure you have the latest enhancements and improvements from our team.
PowerTracks Pro Audio 2025 is here! This new version introduces many features, including VST3 support, the ability to load or import a .FLAC file, a reset option for track height in the Tracks window, a taller Timeline on the Notation window toolbar, new freeze buttons in the Tracks window, three toolbar modes (two rows, single row, and none), the improved Select Patch dialog with text-based search and numeric patch display, a new button in the DirectX/VST window to copy an effects group, and more!
First-time packages start at only $49. Already a PowerTracks Pro Audio user? Upgrade for as little as $29!
Video: Summary of the New Band-in-a-Box® App for iOS®
Join Tobin as he takes you on a tour of the new Band-in-a-Box® app for iOS®! Designed for musicians, singer-songwriters, and educators, this powerful tool lets you create, play, and transfer songs effortlessly on your iPhone® or iPad®—anytime, anywhere.
One of our representatives will be happy to help you over the phone. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday, and 8:00AM to 4:00PM PST Saturday. We are closed Sunday. You can also send us your questions via email.
One of our representatives will be happy to help you on our Live Chat or by email. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday; 8:00AM to 4:00PM PST (GMT -8) Saturday; Closed Sunday.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean