Using the AU plugin with the latest version of Digital Performer in OS 10.12.6, style =CBG_FID, the song is programmed to go to the 'b' drum pattern at bar 26 and stay there through bar 42. It doesn't. It goes to the 'b' pattern at bar 26 but switches back to the 'a' pattern at bar 32. It did this even after I cleared the plugin from the project, reinstated a new instance, and put in the chords again. I can fix it by copying and pasting, but why is this happening?

Part deux - working on this same song, I had to cut 13 measures after doing an edit on the track. (I'm adding BIB tracks to a guitar/vocal recorded to a click track.) I googled 'how to delete measures'. It says:

"Highlight the measure, then "Edit>Delete Measure". In the Dialogue Box, insert the number of measures you want to delete."

Using the AU plugin, there is no "delete measure" option in the DP EDIT menu, and I can't find an EDIT menu in the plugin. There is a 'delete measure' option with a right-click on the measure, but no dialogue box to enter the number of measures to be deleted. I had to delete them one by one. (I suspect I should have highlighted all 13 measures before the delete command. I'll try that next time.) When I was done, I re-rendered the song and the tracks came out blank, but with a snippet of audio on the very ending, and the tracks were about 1/3 shorter than the song.

At least I can copy and paste an edited BIB chart into a new instance of the plugin and start over with no issues, but it would be nice if I didn't have to.

Is there a PDF manual somewhere for the AU plugin? That might help.

New bug: After building a song in linear fashion - 112 bars - I found a wrong chord in the middle of the song. When I typed in the new chord, a chord 8 bars earlier also changed. I hit 'undo' and tried it again. Same result. That's when it dawned on my why my chords weren't always lining up correctly - change a chord, and a different chord somewhere else also changes. Gotta keep your eyes open!

Bar 32 bug is consistent. I program the 'b' drumbeat at bar 27 and switch back to the 'a' drum beat at bar 52. BIB switches back to the 'a' drumbeat at bar 32. I suspect it's because when I open a new instance of the plugin, the blue box for the 'a' drumbeat is already there at bar 32. The first thing I do with a new instance of the plugin is set the length and uncheck the blue box at bar 32 but the plugin isn't getting the message.

ETA: Just noticed another one. I programmed two one-measure stops at the intro: D... and A... . The next measure, the drums start, but the kick is absent on the downbeat - just a little blip like half of a hi-hat. I can C&P to fix it, but really?

If anyone else is having these bugs in DP10, and if they went away in the 2021 version of BIB, let me know. In the mean time, it would be nice if BIB sent a fix for these bugs without us having to pay to upgrade. (I'm on build 426 of BIB 2020)

To clarify, I love what this software can do, but it feels like it's been put together with duct tape and bailing wire.

the app is windows centric. way too many dialog boxes. seems to be out of the early 2000s. the mixer UI is amateur. clunky. I'm sure it would not be too to ask to have it look like a real console. and act like one. like a lot of these apps, BB has a lot of legacy features so someone who has been using it for a while won't get lost. and you a right about the plugin. it has cost me two expensive upgrades and the thing still doesn't perform well. where's an Apple coder when you need him. j.

Thank you for the feedback uncledunc! Here is a link to some resource videos for the plugin which I suggest you watch to get a better understanding of how it works: https://www.pgmusic.com/support.bbplugin.htm

I have tested the issues that you reported here and unfortunately I cannot seem to replicate any of them. Perhaps another user could confirm whether they are having the same sort of issues. The latest version of the plugin is v3.7.23, if you are using an older version, please upgrade to the latest release version. It would also be helpful if you could post a short video outlining the issues you're describing. You can post a video to this forum or email it to me at aguy@pgmusic.com.

Working on a new track, it's the same thing. I have programmed the b drum pattern to start at bar 26 and run though bar 49. The b drum pattern starts at bar 26 but goes back to the a pattern at bar 32. I have build 426 of the 2020 version. It does this on every single song I use it on. when I open the plugin, the blue 'a' box is already there at bar 32. Perhaps they need to get rid of that, since it seems to stay no matter how the song is programmed.

See my post in the Mac forum on real tracks N/A. I may have found a work around that should be on your FAQ page.

Adar I found several RDs last year the did the same thing. it seemed that they would revert back to the "A" style early or even randomly at times. For the life of me I can't remember the solution but it seemed that some RDs have some small unusual style issues at times.

This time, I tried adding a 'b' green box at bar 32 and then snipped out the drum fill during editing.

Hi uncledunc, could you please email your song to me at aguy@pgmusic.com so I may take a closer look?

Did it again on a new song, switches back to the 'a' pattern at bar 32. Also, after going back to the 'a' pattern at bar 39, (the way the song is programmed) it gives me a random fill at bar 40. It did a similar thing later in the song - a random fill where none is programmed.

I also had to do the drum track workaround to get rid of the drums N/A message - right click on the drum track in the plugin window - go to choose a new drum track - choose the track it can't find - now it can find it.

I'll email the song. Video at the link.
https://youtu.be/ityZyzfIToM