PG Music Home Forums PG Music Product Forums Band-in-a-Box for Windows 2022 Version - Observation/Issues

I am hoping this a good spot to share some issues I have discovered while kicking the tires on the latest release. To the extent it is meaningful, I have the latest build (908) and have been digging around the new software only to find some strange behavior along the way.

Before I get started, I am a big fan and advocate of the software; I simply am hoping that by highlighting the issues it will get to a place where it will shine:

1) Multiriffs. In concept, this without question is a bonus feature especially if you want control at a granular level of instrument performances. However, what I have learned is the only way in which to control severe unexpected results is to ONLY access the Multiriffs feature by highlighting your targeted number of bars and rightclicking that passage to enter the Multiriffs window. If you otherwise rightclick on the track to do so, the software goes into confusion mode and, in my case, makes all of your tracks the same and effectively erases all of the other tracks. Unless you have the presence of mind to undo the action under the File menu, you will be generating a performance with that instrument on ALL of your tracks. If you do access the Multiriffs feature via the highlighting method I described, you will be able to generate performances on your designated track. The first two to three passages go without a hitch but in my case it gets hairy when you highlight additional passages: no further generations happen and in some instances select bars go silent. (The good news in this regard is AudioEdit reveals that a sound wave was created so when you export you hear what was generated, just not within the software itself.) All of this was not a "one off" event: I have tried exploring this feature on separate music files with consistent undesirable results.

2) AudioEdit. My understanding is this is the 'replacement" function to the Bar Settings window. This makes sense given that Bar Settings will not show all of the tracks you are using after a certain number so you will have to be well versed in AudioEdit to control each tracks automation instructions if you start building Utility tracks. However, the Bar Settings window, while simple, had global usefulness. If you changed one instrument with automation instructions, it would not alter others. For example, if you add or delete bars in your song form, Bar Settings would follow in sympathy. That's over, unfortunately. If you change your song form, you now have to revisit each track in AudioEdit and reinvent the wheel as now your automation for those other tracks have remained static and in effect ignores what should otherwise be a global instruction.

Last observation: PG Music is sympathetic to users who like the old functions but there is no question that the replacement functions create conflicts with legacy ones. It feels like the user has to be careful not to use both as that will only yield more unexpected results.

I hope this is helpful and if others have found workarounds I am all ears. Otherwise, I also hope this helps PG Music with useful guidance on streamlining an otherwise useful music tool.

E.

E.,

I will reply to your #2 AudioEdit.
"My understanding is this is the 'replacement" function to the Bar Settings window."

While I find AudioEdit / node volume automation a very useful tool, I sincerely hope it will not replace functions in "Bar settings" window. And bar settings menu will be further developed to include all tracks. This (Bar setting menu) is a rapid way to get where you need to get. While AudioEdit is more precise it will take 10 times (or more) longer to get full scale project rolling, than using settings at the bar, especially if you are changing things around(!!) All I am saying, one should not replace the other.

And also your last observation. "PG Music is sympathetic to users who like the old functions..."
It is a difficult question, but here is my view. I came to understanding that BIAB got to where it is because of loyal followers. I agree 100% without a doubt that some things have to be changed to move forward, but there has to be open dialog, not to ignore folks who dedicated many many hours in making BIAB better. Again, you raised a very important topic(s) and I think the best way to approach it is to have focused discussion on particular feature(s), so Peter and team can see fuller pictures of what users want.

P.S. I consider this year update one of the best in short time I was here. I hope this trend will continue.

I think having more than one way to "skin a cat" (disclaimer: no cats were actually skinned in this thread) is the best way. One thing that is ongoing right now is that many of the menus and screens are being slowly developed to meet the new features such as the new all track equal. the tracks setting and dialog window is an example of that process.

Multiriffs is a game changer but will take a little while longer to pound out the issues and bugs.
for me it is working really well, but it did glitch a bit today and I lost my favorite riff. It may have been pilot error, as i hit accept during playback without stopping.

I urge patience the product may be out of Beta now but prelease testing is still ongoing. that is where the little glitches get worked out.

"While I find AudioEdit / node volume automation a very useful tool, I sincerely hope it will not replace functions in "Bar settings" window."

Thanks for the input. I don't think PG Music will abandon their loyal following - I am simply saying that in appealing to all there are some hurdles not resolved in the latest release.

Again, I wanted to highlight what I view as bugs in an effort to help others and let PG know as well

Although I am a new user of BIAB, I really like BIAB, and it is precisely because I like it from the bottom of my heart that I always give opinions.

Because my English is not good, I have been unable to express. This discussion has written all I want to express. So, I will not repeat it, I will just talk about my solution.

1：I don’t use this feature for the time being, I’m generating riffs in BIAB VST

2：I will never edit the audio volume in BIAB, I always do it in STUDIO ONE.

Finally, about BAR SETTINGS and CHORD SETTING are very important functions of BIAB, but they are not perfect so far. The main reason is that you can't see the channels after the style changes, and you can't see all the channels of the Utility. This is a well-known problem.

Keep the channel inside consistent with the mixer, and keep the name and style of the mixer consistent.

Make the channel in the bar settings easier, such as adding solo, mute

I am currently forced to have no way, sometimes all AUDIOs are generated, and then I go to other software to adjust it myself.

Your work is similar to what I do. I prefer editing in Studio One.

...Deb

As do I.

Update: PG Music delivered Build 912 into my inbox this morning. I have yet to install but remain optimistic.