Page 2 of 12 < 1 2 3 4 ... 11 12 >
You need to be logged in to post
Options
Index
#540139 - 06/09/19 04:21 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/07/13
Posts: 5382
Loc: South Carolina
Charlie Fogle Offline
Veteran

Registered: 04/07/13
Posts: 5382
Loc: South Carolina
You may be correct there's no issue with the XML file. As I said, I have no experience with applying them in BIAB/RB or knowledge of using them in any manner. Also, XML files ability to be imported into PGMusic software is a fairly new feature so I was giving my best guess. Your issue with the two instances of INTERLUDE also led me in this direction. At the same time, I'm fairly confident from the various results obtained, there's no defect with RealBand regarding generations of 240 or 255 bars.


It sounds odd when I say it but I believe the issue is no more than something from somewhere has put a command around bar 240-241 since you consistently have the issue there.


You can easily select a few bars prior to bar 240 carrying the selection beyond 241 perhaps to bar 245 and manually make changes to the chords, replace instruments and only regenerate those few bars to see if completing a smaller size task makes a difference. You can do this to one instrument or to all of them at that section only.


To select a section of all the instruments -

Select the radio Snap To Grid Button in the upper left tool bar area.

Select a track, multiple tracks or all the tracks (to select multiple tracks use the control on any desired additional track or shift key between the first and last track you want to choose.)

Place your curser at bar 238 and Press F7

Place your curser at bar 245 and Press F8

The selected section (all tracks)should be highlighted in blue.

Right Click on the blue selected area or Select the large Generate Button

From the drop down menu - Generate\Regenerate All (selected region) (selected tracks) - The selection reads different in the large radio generate button than from the Right click method but the result should be the same.

Only the selected area should regenerate and apply the changes you made to the chord chart.
_________________________
BiaB Ultra Pak+ 2020:RB 2020 Build 1. Dell Inspiron AIO Desktop; Windows-10-64 bit, 7th Generation AMD A9-9425 Processor Five Core 3100 Mhz and 16GB DDR4 Memory.

Top
#540163 - 06/09/19 10:33 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: Charlie Fogle]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
Originally Posted By: Charlie Fogle
You may be correct there's no issue with the XML file. As I said, I have no experience with applying them in BIAB/RB or knowledge of using them in any manner. Also, XML files ability to be imported into PGMusic software is a fairly new feature so I was giving my best guess. Your issue with the two instances of INTERLUDE also led me in this direction. At the same time, I'm fairly confident from the various results obtained, there's no defect with RealBand regarding generations of 240 or 255 bars.


It sounds odd when I say it but I believe the issue is no more than something from somewhere has put a command around bar 240-241 since you consistently have the issue there.


You can easily select a few bars prior to bar 240 carrying the selection beyond 241 perhaps to bar 245 and manually make changes to the chords, replace instruments and only regenerate those few bars to see if completing a smaller size task makes a difference. You can do this to one instrument or to all of them at that section only.


Thanks, Charlie, for elaborating on your perspective on XML files. And thanks for your suggestion for me to experiment with the 240/241 bar boundary by making various changes to a small section of bars before and after this boundary and then regenerating those tracks. Unfortunately, I had tried this during one of my previous tests and repeatedly ran into the exact same problem. To substantiate my claim that there is indeed an issue with the 240/241 boundary during RB track generation process, I created a video that documents this entire scenario using a test song that I had created by manually entering the chords into RB's Chord Window. IOW, this test song was not created from opening a .XML file. You can watch this video on my Youtube channel at this link:

https://youtu.be/khIKS_RAGHg
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540183 - 06/09/19 02:43 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 05/30/00
Posts: 19522
Loc: Marysville, Mi. USA
rharv Offline
Veteran

Registered: 05/30/00
Posts: 19522
Loc: Marysville, Mi. USA
muzikluver,
Maybe try sending this to support via email, or Chat with them tomorrow.
Since you can post the video file, PGMusic may be able to replicate or explain.
https://www.pgmusic.com/support.htm


Edited by rharv (06/09/19 02:43 PM)
_________________________
Make your sound your own!

Top
#540186 - 06/09/19 03:10 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: rharv]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
Originally Posted By: rharv
muzikluver,
Maybe try sending this to support via email, or Chat with them tomorrow.
Since you can post the video file, PGMusic may be able to replicate or explain.
https://www.pgmusic.com/support.htm

Thanks for the suggestion. I'll try emailing it to them first along with a link to this discussion.
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540228 - 06/09/19 07:06 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/07/13
Posts: 5382
Loc: South Carolina
Charlie Fogle Offline
Veteran

Registered: 04/07/13
Posts: 5382
Loc: South Carolina
Thanks for posting the video. You're correct, there's nothing in the chords to cause the chord change and it's clearly there. Rharv's correct that it will likely be best to let support examine the file. I asked someone knowledgeable about XML files and they told me a chord change would be obviously visible and they did not think the XML file had any thing to do with your issue. This test you did seems to confirm that.
_________________________
BiaB Ultra Pak+ 2020:RB 2020 Build 1. Dell Inspiron AIO Desktop; Windows-10-64 bit, 7th Generation AMD A9-9425 Processor Five Core 3100 Mhz and 16GB DDR4 Memory.

Top
#540244 - 06/09/19 07:45 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: Charlie Fogle]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
I sent them an email several hours ago with links to both discussions about this issue (here and in the BiaB forum) as well as a link to my video. I'll let all of you know when they get back to me and what they say about all of this. Thanks for all the help!
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540249 - 06/09/19 09:03 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/07/13
Posts: 5382
Loc: South Carolina
Charlie Fogle Offline
Veteran

Registered: 04/07/13
Posts: 5382
Loc: South Carolina
<<< I'll let all of you know when they get back to me and what they say about all of this. >>>

Please do. It's an intriguing problem.

Charlie
_________________________
BiaB Ultra Pak+ 2020:RB 2020 Build 1. Dell Inspiron AIO Desktop; Windows-10-64 bit, 7th Generation AMD A9-9425 Processor Five Core 3100 Mhz and 16GB DDR4 Memory.

Top
#540403 - 06/10/19 07:26 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: Charlie Fogle]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
Well, this afternoon I received a reply from Joe at PG Music to the email I sent to technical support yesterday. Before I share what Joe wrote to me, I'll share with I wrote in my email:

"Dear Technical Support,

I started using RealBand for the first time a few days ago to find out if it resolves the 255 bar limit in Band in a Box per the suggestion of another user in the Band in a Box forum. In the process, I discovered a problem that occurs repeatedly when RB reaches bar 241 during its track generation process using the BiaB engine. Rather than explain the problem in this email, I'll provide you with a link to the discussion I started in the RB forum on your website as well as a link to a video I created that documents this problem. I'll also provide you with a link to the original discussion I started in the BiaB form that resulted in my decision to try RB in order to create arrangements for two of my songs that exceed the 255 bar limit. Perhaps you could explain why this is happening and if there's anything I can do to work around it. Better yet, perhaps you could fix this problem without much effort. Thanks for your help!

(links included)

Tom"

And here is the reply I received:

"Thank you for contacting us. Although the limit for the song length in Band-in-a-Box is 255, generally speaking the closer you get to that point the more work the Band-in-a-Box engine taxes your computer and thus can create some pretty unwanted results.

As a general rule, the shorter the song the better it is. Even if you need to export smaller portions as a .wav then import them into another DAW to increase the length of it that would be a good work around.

Let us know if you require further assistance.

Cheers,
Joe
PG Music Inc.
Important Reminder: Please include all previous correspondence when replying to this message."

In my opinion, this is a strange reply. I contacted support about a bug in RB's execution of BiaB's engine to overcome the 255 bar limit, and support responded with a discussion on BiaB and a recommendation to use songs that don't get close to the 255 bar limit. Huh?
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540420 - 06/11/19 03:38 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/07/13
Posts: 5382
Loc: South Carolina
Charlie Fogle Offline
Veteran

Registered: 04/07/13
Posts: 5382
Loc: South Carolina
Thanks for posting the update.

Interesting reply from Joe. It seem that although the RealBand program doesn't have a limit of 255 bars, the BIAB algorithm within the RealBand program becomes unstable when generations near the BIAB physical limit of 255 bars.

An analogy would be a rope designed to be safe under a specific load at 20' will not break when used at that load at the 20' length. The same rope braided to a length of 100' will still be designed to work at that load for 20' and may break when used at the 100' length.


It's a limitation of BIAB although it presents within RealBand.
_________________________
BiaB Ultra Pak+ 2020:RB 2020 Build 1. Dell Inspiron AIO Desktop; Windows-10-64 bit, 7th Generation AMD A9-9425 Processor Five Core 3100 Mhz and 16GB DDR4 Memory.

Top
#540424 - 06/11/19 05:02 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: Charlie Fogle]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
That's one way to look at it, Charlie, but I think there's more to it than that. On the one hand, RB doesn't even allow the BiaB engine to reach the 255 bar limit. This is why it only generates tracks up to 240 bars and then starts over with an additional 240 bars (or, in the case of my 320-bar song, an additional 80 bars). Although Jim Fogle's post on 6/8/19 above identified two gaps that occurred in his test song (one in all tracks at bar 240 and one in the base track at bar 272), my complaint isn't about the FIRST 240 bars. My complaint is about the SECOND 240 bars. More specifically, my complaint is about the BEGINNING of the second 240 bars, that is, the VERY FIRST bar if it doesn't have a chord assigned to it along with any subsequent bars that don't have a chord assigned to them as well.

In my test song and in a test song that Pipeline did (see his post on 6/9/19 in my BiaB forum topic "An idea to fix the dreaded '255 bar limit'"), RB inserted a C chord in the first unassigned bar, which from these two test cases appears to be a default operation within RB. Thus, on the other hand, RB's implementation of the BiaB engine for any unassigned bars in the BEGINNING of the second 240 bars is faulty because it doesn't account for the last assigned chord at the end of the first 240 bars. Or, as Pipeline put it in his post, "I would say that's a bug they need to look into as it's not stitching it correctly." This is why a glitch will sometimes occur at the 240/241 bar boundary as well as an erroneous chord change.

Regarding Jim Fogle's test, those gaps appeared only after he had changed all the rests, shots, holds in his song to whole chords. The gaps at bar 240 may have been due to a beat calculation error, which may correspond indirectly to the gap that appeared from bar 184 to bar 240 in one of my test songs with a 4/4 time signature when I used a 3/4 style. However, the gap in the base track at bar 272 could have been random and may have disappeared if he had regenerated that entire track or just a small section of that track surrounding bar 272. I say this because I had encountered a similar gap in BiaB on a finger picking acoustic guitar track in one of my songs that did not exceed or even come close to the 255 bar limit. When I regenerated the song, that gap went away.

CORRECTION: Jim Fogle's first gap appeared at bar 248, not bar 240. See my post below.


Edited by muzikluver (06/11/19 05:18 AM)
Edit Reason: Added a correction at the end
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540427 - 06/11/19 05:15 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
I just realized after checking Jim Fogle's post again that the gap in all the tracks of his test song was actually at bar 248, not bar 240. So, my theory about a beat calculation error for the first 240 bars is incorrect. So, perhaps this gap reinforces what I said above about RB's implementation of the BiaB engine at the BEGINNING of the second 240 bars.

I also did not point out that Jim Fogle's base track had a gap at bar 244 as well, but he didn't mention this in his post.


Edited by muzikluver (06/11/19 05:23 AM)
Edit Reason: Added additional statement at the end
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540431 - 06/11/19 05:48 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 05/13/03
Posts: 7940
Loc: Rio Grande Valley, Texas
silvertones Offline
Veteran

Registered: 05/13/03
Posts: 7940
Loc: Rio Grande Valley, Texas
Yes
_________________________
John
ESI Gigaport HD+
Lenovo Turion II /4 Gig Ram/ Win7x64 be
15.6" Monitor
"The only Band is a Real Band"
www.wintertexaninfo.com/BANDS/JohnnyD.php

Top
#540432 - 06/11/19 06:00 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 12/08/02
Posts: 6316
Loc: Chicago
MusicStudent Offline
Veteran

Registered: 12/08/02
Posts: 6316
Loc: Chicago
muzikluver, I suspect you now can more appreciate what the term "baggage" means. crazy
_________________________
Dan
BIAB2019
BIAB User Map
SoundCloud


Top
#540437 - 06/11/19 06:28 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: MusicStudent]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
Originally Posted By: MusicStudent
muzikluver, I suspect you now can more appreciate what the term "baggage" means. crazy

I sure can! Obviously, as Bob (jazzmammal) pointed out, "RB isn't perfect," and I never expected it to be perfect. I just didn't know what types of issues I would be running into. This forum contains plenty of posts about such issues. Of course, BiaB has its own issues as well. But it's still a great program, and RB has the appearance of being a great program for its primary intended use as a DAW. I just haven't used it enough yet as a DAW to know that for sure from my own experience and may never know that because of my limited DAW needs.
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540439 - 06/11/19 06:36 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 12/10/15
Posts: 860
Loc: Cornwall UK
Mike Head Online   content
Expert

Registered: 12/10/15
Posts: 860
Loc: Cornwall UK
HI

Just a thought to stop the first chord in a new song coming up as C just set the key sig of the song to the chord you want.
However if you want to start on a note in a key that is not the tonic that is a problem.
But you can always change the first chord yourself anyway.

Starting a new version of song for part 2 to stitch on as a wav, I guess you would need to end part one on a key signature bar before it reaches its critical bar number for you.
At a point that makes musical sense of the arrangement currently generated.
Then create part 2 set to that key sig. the problem then being you may have to regenerate multiple times to come up with same arrangement that the software came up with in part one.
You may well struggle here a bit as what was say bar 220 of a song in part one
In your part two song will be back at bar one and may well get treated as an opening phrase, and therefore not sit well, with where the arrangement would have gone in a continuous generation of more bars.
You will also have to negate the count in at some point .

Seems a rather messy workaround to me and a bit hit and miss

Just my take
Mike
_________________________
BIAB2019,UltraPlus, Asus N55S,W10/64,Akai EIEpro,
Yamaha Clavinova CVP405,CoolsoftVirt,MidiSynth
Novatation Impulse61 Ctr kbd,Cakewalk blab,Kontakt

http://mikesmusic.byethost16.com/

Top
#540466 - 06/11/19 09:09 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: Mike Head]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
Originally Posted By: Mike Head
HI

Just a thought to stop the first chord in a new song coming up as C just set the key sig of the song to the chord you want. . . .

Thanks for your suggestions and for joining the discussion, Mike. I think you misunderstood what I said. RB doesn't change the first chord in a song to C. It inserts a C chord into bar 241 if bar 241 doesn't already have a chord assigned to it. This chord won't be visible in the Chord window, but you'll definitely hear it in the arrangement. The quickest workaround for this is to simply insert a chord (the most recent chord that occurred prior to bar 241) into bar 241 before asking RB to generate all the BiaB tracks. However, even after doing this, a glitch will sometimes occur at the 240/241 bar boundary because of RB's attempt to switch to another chord first---probably the C chord.
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540498 - 06/11/19 12:28 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
I just sent Joe at PG Music support the following reply to his email:

"Hi Joe,

Thanks for your reply to my email and for the comments you made about the behavioral characteristics of the 255 bar limit in Band in a Box. While I do appreciate this information, I have to tell you that the email I sent you was not about problems I was having with this limit in Band in a Box. Instead, my email was about the problems I was having in RealBand because of how it had implemented the Band in a Box algorithm/engine to generate BB tracks for several songs that contained more than 255 bars. This is why I was using RealBand in the first place---as a workaround to the 255 bar limit. But rather than take the time to go into those problems in this email, I strongly encourage you to read through the discussions I started on the "255 bar limit" in your Band in a Box and RealBand Windows product forums. I also shared a video in the discussion on the RealBand forum that shows the main issue I had contacted you about. The links to this video and to both discussions are at the end of my original email below, but I'll provide them again here:

(links included)

Thanks for revisiting this issue.

Tom"
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540504 - 06/11/19 12:43 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 12/08/02
Posts: 6316
Loc: Chicago
MusicStudent Offline
Veteran

Registered: 12/08/02
Posts: 6316
Loc: Chicago
You are persistent, I will give you that, but what about buggy do you not understand? <said with a big smile grin >

Top
#540507 - 06/11/19 01:03 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: MusicStudent]
Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 232
Loc: Albuquerque, NM
Originally Posted By: MusicStudent
You are persistent, I will give you that, but what about buggy do you not understand? <said with a big smile grin >

I sure am! And I hope that's a good thing---especially in this case.

Are you asking me about "buggy" or "baggage"? I suspect that you're using both terms interchangeably. As I mentioned above, my primary intended use of RB is to generate arrangements for my songs that exceed the 255 bar limit and to save those arrangements as instrumental demos that I can share with other people. But after Pipeline suggested in a reply to my discussion of this issue on the BiaB forum that I check out the VST plugin for using two instances of BiaB within Tracktion, I'm thinking of pursuing that option instead of RB when I have the time to set it up and try it out, which I haven't done yet. Nevertheless, I'm not done pursuing a resolution of this issue in RB yet and won't until I'm sure that I've "beaten this horse" completely to death. grin
_________________________
BiaB 2020 Win UltraPAK Build 709, RB 2020, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650 3 GHz, 8 GB RAM, 500 GB SSD (boot) & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V

Top
#540511 - 06/11/19 02:10 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 12/08/02
Posts: 6316
Loc: Chicago
MusicStudent Offline
Veteran

Registered: 12/08/02
Posts: 6316
Loc: Chicago
Quote:
But after Pipeline suggested in a reply to my discussion of this issue on the BiaB forum that I check out the VST plugin for using two instances of BiaB within Tracktion, I'm thinking of pursuing that option instead of RB when I have the time to set it up and try it out


If you had fun exploring RB, you are going to have a blast with the BIAB VST. I can't wait for all the drama to come. grin



Quote:
...until I'm sure that I've "beaten this horse" completely to death


Not the first time I have heard this expression here in the forum. crazy
_________________________
Dan
BIAB2019
BIAB User Map
SoundCloud


Top
Page 2 of 12 < 1 2 3 4 ... 11 12 >


PG Music News
We're at The NAMM Show!

Heading to The NAMM Show? Make sure you stop by Booth 1015 (Hall E) - we'll be doing product demonstrations every hour, with some RealTracks Artists popping in for performances with Band-in-a-Box too!

Click here for more information about The NAMM Show, held in Anaheim California at the Anaheim Convention Center.

It's Almost Over - Order by January 15th to SAVE on Xtra Styles PAKs & Loops-with-Style PAK 1!

NEW products for Band-in-a-Box® 2019 for Mac: Xtra Styles PAK 8 and Loops-with-Style PAK 1!

--SPECIAL PRICING ONLY AVAILABLE UNTIL JANUARY 15TH!--

We've added 164 fantastic new RealStyles in Xtra Styles PAK 8! These are imaginative new combinations of our existing RealTracks library that fall into four categories: Rock/Pop 8, Jazz 8, Country 8, and Celtic 1. To celebrate the release of Xtra Styles PAK 8, ALL of our Xtra Styles PAKs 1-8 are on sale for just $29 each! Learn more & listen to demos here.

Also brand-new is our Loops-with-Style PAK 1 for Band-in-a-Box®, which gives you the chance to expand your loops collection with 100 new loops! We've taken the RealDrums and RealTracks source audio and remixed, remastered, and combined it to create these original loops. All of your favorite genres are covered like jazz, funk, rock, pop, electronic, hip-hop, and more! To show them in action, we've created 50 new RealStyles that each include two of the loops. Plus, if you use the loops in Band-in-a-Box, we've included intelligent versions of the loops that automatically switch at A and B part markers. Each loop has a matching sister loop that works perfectly for another substyle! Get started with Loops-with-Style PAK 1 for the introductory price of just $19 until January 15th (reg: $29). Learn more & watch a great video demonstration here.

Note: Xtra Styles PAK 8 and Loops-with-Style PAK 1 require the Band-in-a-Box® 2019 or higher UltraPAK, UltraPAK+, or Audiophile Edition.

Windows User? Choose from these links: Xtra Styles PAKs | Loops-with-Style PAK 1

Built-in Audio Chord Wizard Enhancements in Band-in-a-Box® 2020!

Our Band-in-a-Box® 2020 for Windows version includes some great enhancements to the Built-in Audio Chord Wizard!

-The built-in Audio Chord Wizard is now accessible from the [Audio Chord Wizard] button.
-The Audio Edit window now displays chords and tempos for each bar. They are shown when the Audio Chord Wizard mode is active so that you can see the tempo for each bar as you set the bar lines.
-When you start entering bar lines, the program automatically sets the tempo to the tempo of the first bar.
-Once the tempo of the first bar is set, the program automatically moves the location of the first bar of audio over so that the visual space of the count-in bars is visible.
-After you’ve added the bar lines, IF you adjust the first or second bar and the tempo of the first bar changes accordingly, the program automatically changes the tempo of the song to match.
-Multi-window display. This gives the Audio Chord Wizard a multi-window view so that you can see and edit both the Audio Edit window and the Chords Sheet at the same time. This display is best viewed with a small toolbar mode. This allows you to see the chords as they are being interpreted by the wizard.
-The Audio Chord Wizard can send the transcribed MIDI notes to the Soloist track for further analysis by the user (via Piano Roll or Notation window). Note that this is a "snapshot" view every 8th note of the pitches present, not an attempt at polyphonic transcription. To use this feature, enable the "MIDI to Soloist" check box.

Read more about these enhancements here, or jump to the New Feature - Audio Chord Wizard (ACW) Enhancements section of our New Features video here.

The Band-in-a-Box® 2020 for Windows® Special ENDS January 15th!!!

IT'S YOUR LAST WEEKEND TO SAVE UP TO 50% ON YOUR BAND-IN-A-BOX® UPGRADE!

Our SALE on Band-in-a-Box® 2020 Upgrade purchases ends January 15, 2020, so there is still some time to save up to 50% when you purchase your Band-in-a-Box® 2020 for Windows Upgrade!

Customers LOVE Band-in-a-Box® 2020 for Windows with over 50 new features, plus the 202 New RealTracks, new RealStyles, 15 new MIDI SuperTracks, 170 new Instrumental Studies, 30 new MIDI Styles, 280 RealDrums Transcriptions, the 2020 Free Bonus PAK, 2020 49-PAK, and new Xtra Styles PAK 8!

We've packed our Free Bonus PAK & 49-PAK with some amazing Add-ons! The Free Bonus PAK is automatically included with most Band-in-a-Box® for Windows 2020 packages, but for more even more Add-ons (including 40 Unreleased RealTracks) upgrade it to the 2020 49-PAK for only $49. You can see the full lists of items in each package, and listen to demos here.

Check out our Band-in-a-Box® packages page for all the purchase options available.

Learn more about all the new features in Band-in-a-Box® 2020 for Windows at: www.pgmusic.com/bbwin.new.htm

If you need any help deciding which package is the best option for you, just let us know. We are here to help!

Band-in-a-Box® 2019 for Windows Patch Update Available! (Build 642)

Still using Band-in-a-Box® 2019 for Windows? Build 642 is a free update full of updates for version 2019, and includes a VST DAW Plugin update to 1.16.29.

Learn more and download here. | Direct download

Note: this patch is not intended to update your version to the recently released Band-in-a-Box® 2020, which is available for purchase here.

Summary of Changes for Version 2019 Build 642 (Jan 08 2020):
Changed: Default the 'include similar styles in the stylepicker' to false each bootup.
Improved: BootupLog.txt will include more elaborate information when troubleshooting bootup problems. This only applies if WriteBootUpLog.txt is present in the Data folder.
Updated: PDF and help (routine cleanup/updaes).
Fixed: "There is no audio file currently recorded" error message when using Audio > Plugin.
Fixed: [Video] > Render Video(s)... menu item should launch the Make Chordsheet Video dialog if Video RealTracks export is not available.
Fixed: Access violation in Song Titles browser if no song is selected when clicking [Close].
Fixed: Applying audio effects using Audio > Plugins would fail with error "Plugin cancelled. Original file is preserved".
Fixed: Audio > Edit Audio > Timeshift Audio would crash the program if the Audio Edit window was not open.
Fixed: Audio will not import to a custom position if there is already audio on the Audio track.
Fixed: Band-in-a-Box might crash during bootup if an ASIO driver was previously selected, and the device is no longer connected to the computer.
Fixed: Band-in-a-Box might crash during bootup if there is a problem with font installation (usually after upgrading Windows 7 to Windows 10).
Fixed: Band-in-a-Box might crash when opening a song that contains note-based lyrics.
Fixed: Bar Lyrics and Section Text layers do not line up with bars in Notation window if there are repeats in song, and fake sheet mode is enabled.
Fixed: Clicking OK in the MIDI/Audio Driver Setup dialog should not close the floating Mixer window.
Fixed: Close button in Select chorus start/end dialog should behave like Cancel, ie user clicking on bar afterwards shouldn't do anything.
Fixed: Crash with error "external exception C06D007F" while launching if using Windows XP.
Fixed: Dragging a single track to export MIDI causes that track to be permanently soloed.
Fixed: If an ASIO driver cannot connect during bootup, the default WAS driver should be used instead.
Fixed: If using the 64 bit version of Band-in-a-Box, the BB2Go window would display an erroneous QuickTime version, and converting files to .m4a would fail. QuickTime is only available for the 32 bit version, but is only required if using Windows Vista or earlier.
Fixed: Lyrics would not display in the Big Lyrics if "Show chord symbols above the lyrics" was enabled.
Fixed: melodists were getting quantized incorrectly.
Fixed: Possible crash if editing a text layer while using the floating Notation Window.
Fixed: Possible freeze when importing compressed audio files.
Fixed: Practice window | Master Solos | Blues Piano, displays N/A.
Fixed: RealTracks #2975 (Vocal Oohs-Aahs) sometimes played incorrect chords for m7b5 and C7.
Fixed: Rebuilding styles list was causing errors sometimes.
Fixed: Several Piano and Organ MIDI SuperTracks have been edited to remove spurious MIDI events (e.g. mod wheel sometimes caused 'warbling' effect).
Fixed: Sforzando might not automatically be added to the VST list, causing Hi-Q patch selection to fail.
Fixed: Some bars for the B section of RT 2529 were dropping out.
Fixed: Some Bass and Nylon Guitar RealTracks (including 2718, 2724, 2722, 2725, 2719) have RealCharts added.
Fixed: StylePicker: User Category list wasn't refreshing after choosing a new user category.
Fixed: The About dialog said 'for Macintosh' instead of 'for Windows'.
Fixed: The Drop Station would not update if dropping a file onto Presonus Studio One.
Fixed: When choosing a compressed format for rendering files, and "One file per track" is enabled, the resulting files are .wav format instead of the compressed format.
Fixed: Wrong notes on Oohs and Aahs RealTracks.

Summary of changes for Band-in-a-Box DAW Plugin 1.16.29:
Added: copy selected cell if nothing highlighted
Added: shift-arrows to select in chord sheet
Added: SHIFT-ENTER to go backwards in chord sheet
Added: SHIFT-TAB to go backwards in chord sheet, TAB to go forward
Added: support for all Biab file types
Fixed: Added message if attempting to drag tracks before generating
Fixed: Alert window buttons "punch hole" when pressed
Fixed: Audio stutters when resizing plugin in some DAWs
Fixed: auto gen after open feature not working in Studio One 4
Fixed: bounds when highlighting in chord sheet
Fixed: C#7b5b9b13 to chord sheet
Fixed: distortion when stopping playback in pro tools
Fixed: losing focus in chord sheet
Fixed: make selected cell at the end after pasting
Fixed: Open dialog in infinite loop
Fixed: plugin stops playing non-synced tracks when closing and then opening plugin
Fixed: Send space bar keystrokes to DAW
Fixed: some styles not dragging all tracks from blue button
Fixed: track text not resizing correctly
Fixed: Transpose not working
Fixed: Verify folders before each call to Biab

New Left-Handed & Student View Guitar Window in Band-in-a-Box® 2020 for Windows!

With Band-in-a-Box® 2020 for Windows, the Guitar window has been remade and now supports the left-handed (in addition to right-handed) guitar and student view!

The student view is the view a student (or YouTube video watcher) would have of the (right-handed) guitar facing him with the head at the right and low notes at the top. There's also a left-handed student view, so all 4 possible views are supported.

To change the view, press the [Guitar] toolbar button to open the Guitar window and then the [Settings] button.

See this new feature in action when you jump to the "Left-Handed & Student View Guitar Fretboard" topic in our 2020 New Features video: Click here...

Loops with Style PAK 1 - Just $19 Until January 15th!

The recently released Loops-with-Style PAK 1 is your chance to expand your loops collection with 100 new loops!

To show them in action, we've created 50 new RealStyles that each include two of the loops. Plus, if you use the loops in Band-in-a-Box, we've included intelligent versions of the loops that automatically switch at A and B part markers. Each loop has a matching sister loop that works perfectly for another substyle!

We're offering Loops-with-Style PAK 1 at the introductory price of $19, but only until January 15, 2020 (reg. price $29). Purchase here.

Note: Loops-with-Style PAK 1 requires the Band-in-a-Box® 2019 or higher UltraPAK, UltraPAK+, or Audiophile Edition.

Watch the demonstration video...

Windows user? Click here for product information, or to to purchase Loops-with-Style PAK 1.

Forum Stats
30943 Members
63 Forums
61947 Topics
523190 Posts

Max Online: 2519 @ 01/16/20 06:39 AM
Newest Members
EdWiliams, ransmusic, GinaS, RPC71, BJL

30943 Registered Users
Top Posters (30 Days)
Noel96 259
Matt Finley 187
MarioD 180
Pipeline 169
VideoTrack 158
Jim Fogle 132
Jim 131
Rustyspoon# 130
Rob Helms 105
Janice & Bud 105
Today's Birthdays
No Birthdays