This is not a Ver. 2014 thing. It happened with song created in 2013 and now when played in Build 378 of 2014 too.
Customer support offered: (1) run BiaB from C drive, (2) restore to factory settings.
Nope.
Style: _CMPFMH2
The strummed guitar drops out for two bars and then comes back in.
I need to send a file to someone and this is very frustrating.
Any ideas? Thanks.
Hhhmmm ... interesting.
I added an "A" part marker and now it works and plays through.
Does BiaB not like to play four measures in a row of the same chord?
AAAGGGHHH! Crap. I changed the key and it's back doing it again!!!
Well, if you want, PM me with and email addy and you can attach the file to the reply and I'll see if I can figure it out.
--Mac
Is there any chance it is one of the more exotic chords? For example, a couple of years ago I discovered a bossa style that did not know what to do in the piano part when I wrote XmMaj, so it just laid out. PG Music fixed it with the next patch.
If that's the situation, Mac will be able to reproduce it.
I'm still working on the file sent off and on, and just now experienced the total dropout of two measures on the Fingerpicking guitar part when regenerating.
Investigating...
If I can get that to happen again, I'm gonna Freeze the file immediately, I'd like your permission to pass it on to pgmusic development team that way.
--Mac
Yes, absolutely can pass on.
Glad you experienced it too.
Thanks.
Has not happened again here.
Its on the list to Open at random, generate a few times and remember to Freeze when spotted again.
If you can get the chord dropouts to happen, freeze and sent to pg yourself, reference this thread as a url.
--Mac
And also for the record, those seem to be the exact same two bars where it did the same thing to me when I was experimenting with the file.
Were you able to FREEZE that and if so, did you email the songfile to pgmusic?
I would recommend that.
--Mac
Yes, froze and sent to PGM.
Have not heard back yet.
(Only sent it last night.)
Turns out it is a Bug.
Was it supposed to be fixed in Patch # 380?
'Cause it is still happening.
Thanks.