Page 5 of 12 < 1 2 3 4 5 6 7 ... 11 12 >
You need to be logged in to post
Options
Index
#541126 - 06/15/19 10:24 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: silvertones]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: silvertones
In these days if you don't submit a perfect demo to a producer he wont even listen. Even if the song than goes 180°. I also do some local producing. If the artist doesn't care about his demo why should I.

When I gave my first song to my producer for him to evaluate at the beginning of 2017, I sent it to him as a .PDF of my lead sheet with the lyrics, melody, and chords. I also gave him a link to a video of MuseScore playing the melody of my song as it scrolled through the lead sheet, which I had uploaded to my Youtube channel. At the time, I was only interested in him producing this one song for me and didn't have any plans for him to produce an entire album because I didn't have enough songs of the same genre written yet that he could produce as an album. (I only had three other songs in the works at the time.) But after he agreed to produce this one song for me, one thing led to another with the result that he's now working on my seventh song, and I have three to four more in the queue.
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

Top
#541127 - 06/15/19 10:31 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: silvertones]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: silvertones
Send me a link to an xml file and I'll send you back a song done my way.

Sure, I'd be interested in hearing a demo of one of my songs done your way. To make this a fair and straightforward comparison of your way vs. my way, I'd like to sent you a file of the first song that I created a demo of using BiaB back in January. I can also send you a link to a video of my demo for you to listen to, but I think you should create your demo before you hear mine---unless you feel otherwise for some reason. So, how do I do that?
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

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

Registered: 05/13/03
Posts: 7789
Loc: Rio Grande Valley, Texas
Post a link here.
_________________________
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
#541133 - 06/15/19 11:15 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: silvertones]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: silvertones
Post a link here.

I sent you a PM with three links.
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

Top
#541181 - 06/15/19 03:47 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 05/13/03
Posts: 7789
Loc: Rio Grande Valley, Texas
silvertones Offline
Veteran

Registered: 05/13/03
Posts: 7789
Loc: Rio Grande Valley, Texas
Ok cool.
_________________________
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
#541190 - 06/15/19 05:49 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: Charlie Fogle
<<< 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


It's been over three days since I replied to Tech Support's response to the original email I sent them about this issue and asked them to revisit it, but I still haven't heard back from them. How much longer should I wait for them to write me back before I either write them again or give them a call?


Edited by muzikluver (06/15/19 05:52 PM)
Edit Reason: Added a quote from Charlie
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

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

Registered: 04/07/13
Posts: 5135
Loc: South Carolina
Originally Posted By: muzikluver
Originally Posted By: Charlie Fogle
<<< 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


It's been over three days since I replied to Tech Support's response to the original email I sent them about this issue and asked them to revisit it, but I still haven't heard back from them. How much longer should I wait for them to write me back before I either write them again or give them a call?


I'd send them a gentle reminder email in the morning.
_________________________
BiaB Ultra Pak+ 2019:RB 2019 Build 3. Dell Inspiron AIO Desktop; Windows-10-64 bit, 7th Generation AMD A9-9425 Processor Five Core 3100 Mhz and 16GB DDR4 Memory.

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

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: Charlie Fogle
Originally Posted By: muzikluver
Originally Posted By: Charlie Fogle
<<< 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


It's been over three days since I replied to Tech Support's response to the original email I sent them about this issue and asked them to revisit it, but I still haven't heard back from them. How much longer should I wait for them to write me back before I either write them again or give them a call?


I'd send them a gentle reminder email in the morning.

Charlie, I just sent Tech Support the following email:

"Hi Joe,

I'm writing you again to follow up on the status of your investigation into an issue that I initially contacted you about a week ago today. Though you did reply to my original email last Monday, I wrote you again on Tuesday because the information you provided in your reply did not directly address RealBand's implementation of the Band in a Box track generation algorithm. Instead, it focused on Band in a Box itself and presented a workaround to the 255 bar limit using Band in a Box. Because I already have my own Band in a Box workaround that is more suitable than yours for the types of instrumental arrangement demos I'm creating for songs that exceed the 255 bar limit and because I have the impression from another RealBand user (whose user name is jazzmammal) that RealBand is your solution to the 255 bar limit in Band in a Box, I would like you to take a closer look at the problem in RealBand that I'm presenting to you by reading through the discussion I started in the Windows RealBand product forum with the same title as this email. Only then will you understand why I contacted you in the first place about this problem and why I am following up with an additional reply to your only email reply to my original email. In addition, because it has been several days longer than the typical reply time of 0-2 days that is mentioned in your auto-reply email, I want to make sure that this issue isn't being inadvertently neglected. Though I've already provided these to you in both of my previous emails, below are links to the discussion I started in the Windows RealBand product forum along with two other related links.

(Links)

Thanks for your assistance with this issue.

Tom"
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

Top
#541259 - 06/16/19 09:52 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: silvertones]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: silvertones
Starting out with all regular tracks in RB and generating a track I noticed at the very top " generating 1/2. It generated up to bar 240 than 240 to the end. Small vertical bar at 240. Changed chord at bar 240 and it followed. It was seamless.I suspect the onger the song the more steps.

Silvertones, I'm curious about a couple of things regarding your track generation test:

1) Did you have a chord entered into bar 241 before you generated this track?

2) If so, did you listen to a small section of the track that includes a few bars immediately before and after the 240/241 bar boundary to determine if an audio glitch occurs on the 240/241 bar boundary as a result of RB's attempt to change to a different chord than the one you had entered into bar 241?

3) If you did not have a chord entered into bar 241 before you generated this track, did you listen to the same section to determine if RB erroneously inserted its own chord change into bar 241 and if you could tell if that chord was a C chord?

4) Are the "regular tracks" you started out with in RB the same as BiaB tracks (or "BB tracks," as RB refers to them)? My understanding is that "regular tracks" are different from "BB" tracks. If my understanding is correct, doesn't RB have to convert regular tracks to BB tracks before it can generate an arrangement for those tracks?
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

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

Registered: 05/13/03
Posts: 7789
Loc: Rio Grande Valley, Texas
1.yes
2.yes
3. I'd have to say no cause I had different chords 240 and 242 but it was perfect.
4. No I start with all REGULAR TRACKS NO BB TRACKS. I ALWAYS just right click on a track and choose generate/ Real Track.
The RT pick list will come up an d I choose them one at a time. Styles mean nothing when it comes to the use of RTs.
_________________________
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
#541262 - 06/16/19 10:41 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: MusicStudent]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: MusicStudent
No matter how much we may want BIAB to behave differently, it generally comes down to the fact that there is a workaround to get done what you need. It is just a shame sometimes that so much effort goes into learning this lesson for newbees. But as long as you are having fun... crazy

MusicStudent, you make made a very good point. Actually, you made two very good points. The first one is that there is a workaround to the "255 bar limit" in BiaB. In fact, there are numerous workarounds to this limit. Some of those workarounds can be implemented within BiaB itself while others involve the use of other programs like RB (as jazzmammal mentioned in response to my suggestion of an idea to fix this limit in the BiaB Windows product forum or like other DAWs (Tracktion, for example) using the BiaB VST plugin (as Pipeline mentioned in that same discussion).

The second "very good point" you made is that "it's a shame sometimes that so much effort goes into learning this lesson for newbies." Fortunately for me as a newbie, it didn't take me very long to figure out on my own a workaround to this limit that suited my needs. But other newbies may not be so fortunate. Therefore, because of the likelihood that PG Music will never fix or eliminate this limit in BiaB, I have a suggestion that would be of benefit not just to newbies who have difficulty figuring out their own workaround to this limit but also to experienced users like yourself who may get tired of seeing this "dead horse" being beaten to death over and over again in these forums. My suggestion is as follows:

Why doesn't someone (such as yourself or another experienced user like Charlie Fogle or jazzmammal) start a discussion in the BiaB forum with the topic heading of "Known workarounds to the 255 bar limit in BiaB" (or something similar) that would serve as a central repository of all these workarounds for newbies and experienced users alike to reference whenever the need arises? (To my knowledge, such a repository doesn't exist. If it does, then please point me to it.) For example, newbies who encounter this issue and inquire about a workaround could be referred to such a discussion instead of spending time rehashing the same stuff ("beating this dead horse") in a new discussion. Also, various workflow scenarios could also be discussed in connection with those workarounds with the goal of determining which workaround would be best suited for a particular workflow scenario. Because you seem to have become frustrated with this discussion and with the other discussion I started in the BiaB forum, why don't you take it upon yourself to implement my suggestion? I'll be glad to share the workaround I've been using for my particular workflow scenario (as I've already done in this forum) and contribute my thoughts on and experience with other workarounds that are mentioned.


Edited by muzikluver (06/16/19 11:13 AM)
Edit Reason: Added a second "very good point" that MusicStudent made
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

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

Registered: 05/13/03
Posts: 7789
Loc: Rio Grande Valley, Texas
Did some testing:
1. The song you sent is only 173 bars long per the PDF
2. It put down all the chords and they all appear to be right. I'll let you do that leg work.
3. I got the piano part as well BUT it was like only 1/16 of measure 1
4. I generated 3 RTs in about 5 mins.

PM me an email address and I'll send you what I got.
_________________________
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
#541270 - 06/16/19 12:11 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: silvertones]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: silvertones
Did some testing:
1. The song you sent is only 173 bars long per the PDF
2. It put down all the chords and they all appear to be right. I'll let you do that leg work.
3. I got the piano part as well BUT it was like only 1/16 of measure 1
4. I generated 3 RTs in about 5 mins.

PM me an email address and I'll send you what I got.

1. Correct, I didn't send you a song that exceeds the 255 bar limit. I didn't know you wanted one of those because I thought that you just wanted to demonstrate the difference between your procedure of using RB and generating individual RealTracks vs. my procedure of using BiaB to generate all tracks with a particular Style.
2. I'm sure the chords are correct, but I'll check them anyway.
3. There is no separate piano part. The piano part is the entire melody. The first measure doesn't have anything in it. I included two blank measures at the beginning to correspond to the two lead in measures that BiaB creates (which can be turned off). I left those two measures in place so that the melody could be synced up with the chords. Normally, I export the .XML file without those two measures for importing into BiaB and then export a separate .WAV file with those two measures in place. If RB didn't create a separate midi track for the melody, then it doesn't have this available for reference when generating each track like BiaB did for me.
4. That sounds about right.

The limit for email is 10 MB. You'll have to export a .WAV and convert to .MP3 or export a .MP3 file that is less than 10 MB (for a song this long, it will be). I'll send you my email address in a PM, but you may want to take the info above into consideration before sending me what you have. Thanks!


Edited by muzikluver (06/16/19 12:14 PM)
Edit Reason: .MP# -> .MP3
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

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

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Silvertones, you posted the following in response to my comment about the midi file not having the chords and then you made a subsequent post with your offer to create a demo for me done "your way" using RB (as described below) for me to compare to a demo done "my way" using BiaB:

Originally Posted By: silvertones
It will. It'll interpret the midi notes in the score.If you get weird chords they will be technically correct but may not be pleasing. Those you can change.
Btw also drop the use of biab. I did 10 years ago. Learn RB it does more than biab.The xml file should work the same.
Before you import turn all bb tracks in RB to regular tracks.This should give you the whole song in midi format.Right click on a track in RB and generate any Real track. Forget about styles for RT. Just add 1 track at a time with musicians you want not those dictated by the style.
Sidebar: I'm a pro player playing 4 days a week for 8 months. Then I go into new song mode. I have over300 songs done this way.
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

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

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: Charlie Fogle
Not to worry. Your work in MuseScore and .XML files is a brilliant idea and allows you to construct a song in such a manner it's much like a roadmap of your completed song. Because of the length of your song projects and also the fact there's so much post editing, an .XML file is crucial to staying on track to how the song is constructed, the arrangement of how instruments weave in and out of your arrangement and how you dynamically build your song. Don't make any changes to how you presently use .XML files to input your chords, melody, key signature and tempo.

What I suggest is that rather than think of BIAB to generate a song, think of it to generate each section of your song. Rather than record all of your song as one linear song, record each section of your song, export that section's audio and in a DAW, stitching each section together. That's a recording technique called overdubbing and it's used extensively in studio recordings. Each section of your song will be comprised of it's own BIAB .sgu file. This replicates the concept of a live musician recording a verse separate from a chorus, separate from a bridge, separate from the intro and outro. This alone eliminates the 255 bar limitation of BIAB. Generating and saving the audio of each section of your song allows you to drop that audio into it's place in an master audio file. That bypasses the long entire song renders you currently have to do. If you make edits to verse 3, you only work within the BIAB .sgu file of the saved Verse 3. The rendered audio with the updated edits then overwrites and replaces the current audio populating Verse 3 of your master audio file.

As you know, Charlie, silvertones recommends that I drop BiaB completely and use RB instead. That may be beneficial in some workflow scenarios but perhaps not others. So on the one hand, before I decide to do that, I need to do enough testing with the procedure he is suggesting that I use on my songs with RB to make sure that's the right decision for me and my needs. On the other hand, I need to have a better understanding of the procedure you're suggesting I use so that I can go through the steps involved in that procedure in order to make a proper comparison between your suggested use of BiaB and his suggested use of RB. Therefore, I have some questions for you about your suggested procedure because I'm having trouble following all the steps in your explanation.

For example, in the above excerpt of your recent post, you mention a "master audio file." I assume you are referring to an audio file in a DAW such as RB or Tracktion. If so, then would each generated section of my song exist on its own track to make it easier to update? If so, that would eliminate the free version of Tracktion as a viable DAW because it only comes with 8 tracks, and I don't think more can be added. (This wouldn't prevent me from using RB, of course.) If not, then the best way for me to update an audio section in Traction would be to overwrite the contents of the existing audio section file that I had previously imported because it already is positioned at the proper location in the song. This would not be possible, of course, if I need to add or remove a measure during my editing of that audio section or of another audio section. In that case (which occurred a few times in the song I was working on a few months ago), other sections of the song would have to be moved in order to avoid gaps or overlaps in the song.

Another question I had pertains to my importation of an .XML file. You discussed the need for numerous folders to contain all the different sections of my song in BiaB. In order for me to create those different sections, I would need to create multiple .XML files within MuseScore for each section of my song and also have a complete master .XML file as the main road map of the song. I would also need to make changes to the master file and then copy those changes to one or more of the sub-sections as I go along, and then open the .XML exports from the edited sections into BiaB to regenerate the audio for them, etc. Am I correct?
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

Top
#541276 - 06/16/19 01:52 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: muzikluver
Another question I had pertains to my importation of an .XML file. You discussed the need for numerous folders to contain all the different sections of my song in BiaB. In order for me to create those different sections, I would need to create multiple .XML files within MuseScore for each section of my song and also have a complete master .XML file as the main road map of the song. I would also need to make changes to the master file and then copy those changes to one or more of the sub-sections as I go along, and then open the .XML exports from the edited sections into BiaB to regenerate the audio for them, etc. Am I correct?

I think I figured out the answer to my own question above. Correct me if I'm wrong. Instead of creating multiple .XML files (one as the master and the others as sections of the master), it would be better to just stick with one .XML file (that would have its name changed with each iteration) to open in BiaB. Then, I would delete all the measures within BiaB for all the sections except for a particular section for which BiaB would be used to generate tracks. This could be done repeatedly for one section (for example, the verse section) that ends up being modified multiple times while all the other sections remain intact both in the MuseScore master file and in the master audio file.
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

Top
#541278 - 06/16/19 02:01 PM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: silvertones]
Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
muzikluver Offline
Apprentice

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: silvertones
Btw also drop the use of biab. I did 10 years ago. Learn RB it does more than biab.The xml file should work the same.
Before you import turn all bb tracks in RB to regular tracks.This should give you the whole song in midi format.Right click on a track in RB and generate any Real track. Forget about styles for RT. Just add 1 track at a time with musicians you want not those dictated by the style.

It may be desirable to drop BiaB and only use for songs that are ready for final production or that are close to that stage. But BiaB is very useful for working out the kinks in a song that is just being developed. For example, figuring out which chord progression sounds best for a particular section of the song or if one or more notes in a section should be modified to find out if they sound better than the current notes in that section. Because BiaB's track generation only takes seconds in comparison to the minutes that RB takes, making such changes in BiaB and listening to the quickly-generated results makes a lot more sense to me than doing this in RB.
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

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

Registered: 04/17/18
Posts: 208
Loc: Albuquerque, NM
Originally Posted By: Jim Fogle
One big difference between Band-in-a-Box and RealBand is how the two programs approach track generation.

Band-in-a-Box generates a few bars of each track then begins audio playback. Band-in-a-Box then continues to play audio while also continuing to generate tracks as a background task. Sometimes the program will stall because audio playback catches up to track generation so there is temporarily nothing to play. If that frequently happensns a user can go to preferences > RealTracks and remove the check mark for, "Speed up generation of RealTracks (disable on slow machines)". When that feature is disabled Band-in-a-Box will completely generate all tracks prior to starting audio playback.

Another way Band-in-a Box works is when the generate button is selected, ALL tracks are generated unless a track is frozen. By-the-way, Band-in-a-Box use to have only a combined play and generate button so every time you clicked play a new arrangement was created.

Finally, when a track is generated all the track is generated.

Now for RealBand. RealBand does partial or complete track generation; it depends on what is highlighted. Nothing is generated until the generate button is pressed. Audio playback does not begin until all track generation is complete.

Corresponding to the difference between how these two programs perform track generation is the time it takes each program to accomplish these tasks, which I didn't mention in my previous reply to your post, Jim, though I did mention this in a subsequent post and explained that the quickness of BiaB's approach makes BiaB more suitable than RB for working out the kinks in a song that is being developed (as an example). However, this has not deterred silvertones from abandoning BiaB completely and suggesting that I do the same. But as I've thought about the speed differences in these two programs, it occurred to me that RB would be much faster if it took advantage of Windows' multi-threading capabilities. For example, I have a 3 Ghz Quad Core PC. This makes it possible for a program like Format Factory to convert four .WAV files to four .MP3 files simultaneously because each of those files is processed independently by each of the four cores. Why doesn't RB do the same thing with songs that have four or more tracks? I know that silvertones likes to generate one track at a time after he selects a RealTrack that he wants to use for a particular track. But for someone who prefers to use a BiaB Style that has at least four instruments and wants to generate all four of those tracks at the same time, RB should be able to hand each of those track generation operations over to separate cores in the CPU to handle, thus reducing the amount of time it takes to generate those tracks by a factor of four. The same would be true of the generation of an eight track song on a PC with eight cores in the CPU, except that the time would be reduced by a factor of eight. If PG Music would make it possible for RB to multi-thread, it would be much more desirable for me and other users to use it instead of BiaB more often than not.
_________________________
BiaB 2019 Win ProPak Build 628, RB 2019 V4, Windows 10 Pro 64-bit (dual boot with Win 7 64-bit), Intel Q9650, 8 GB RAM, 256 & 120 GB HD, Tracktion 6 & 7 (freebies), MuseScore 2.1

Top
#541363 - 06/17/19 04:14 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/07/13
Posts: 5135
Loc: South Carolina
Charlie Fogle Offline
Veteran

Registered: 04/07/13
Posts: 5135
Loc: South Carolina
Originally Posted By: muzikluver


Why doesn't someone (such as yourself or another experienced user like Charlie Fogle or jazzmammal) start a discussion in the BiaB forum with the topic heading of "Known workarounds to the 255 bar limit in BiaB" (or something similar) that would serve as a central repository of all these workarounds for newbies and experienced users alike to reference whenever the need arises? (To my knowledge, such a repository doesn't exist. If it does, then please point me to it.)



such a BIAB forum discussion area exists.



Here ->-> -> -> -> -> ------------> Forum List\Post your own Tip and Tricks
_________________________
BiaB Ultra Pak+ 2019:RB 2019 Build 3. Dell Inspiron AIO Desktop; Windows-10-64 bit, 7th Generation AMD A9-9425 Processor Five Core 3100 Mhz and 16GB DDR4 Memory.

Top
#541370 - 06/17/19 05:43 AM [RealBand] Re: Glitch and erroneous chord change occurring between bar 240 and bar 241 [Re: muzikluver]
Registered: 04/07/13
Posts: 5135
Loc: South Carolina
Charlie Fogle Offline
Veteran

Registered: 04/07/13
Posts: 5135
Loc: South Carolina
Originally Posted By: muzikluver
Originally Posted By: muzikluver
Another question I had pertains to my importation of an .XML file. You discussed the need for numerous folders to contain all the different sections of my song in BiaB. In order for me to create those different sections, I would need to create multiple .XML files within MuseScore for each section of my song and also have a complete master .XML file as the main road map of the song. I would also need to make changes to the master file and then copy those changes to one or more of the sub-sections as I go along, and then open the .XML exports from the edited sections into BiaB to regenerate the audio for them, etc. Am I correct?

I think I figured out the answer to my own question above. Correct me if I'm wrong. Instead of creating multiple .XML files (one as the master and the others as sections of the master), it would be better to just stick with one .XML file (that would have its name changed with each iteration) to open in BiaB. Then, I would delete all the measures within BiaB for all the sections except for a particular section for which BiaB would be used to generate tracks. This could be done repeatedly for one section (for example, the verse section) that ends up being modified multiple times while all the other sections remain intact both in the MuseScore master file and in the master audio file.


How you do this is determined by MuseScore. If MuseScore can assign a name to a series of bars, that is all you need to do to an .XML file different than what you do now. Otherwise, you will mark sections and name these sections of your song once the file is opened in RealBand. Example: Bars 1-12 (Intro); Bars 13-21 (Verse 1) and so on until your entire song has been broken into sections and each section is named according to what it is. What's important is that your song is broken into identifiable sections. This technique will make constructing or editing your song super manageable, super easy and super fast in comparison to your current workflow. It can literally turn hours of edits and arranging into minutes.

In DAWs this technique is call arranging. All DAWs have this feature as far as I know. I've never encountered one that doesn't in the few other DAWs I've used or watched videos of. I use Presonus Studio One 4 Pro and it places a lot of emphasis on working in the Arrangement Window as does Pro Tools and Ableton. RealBand has this feature although not as complex or advanced as some other DAW's. Doesn't matter. Even RB will make constructing a song (arranging) or editing it so much easier and faster.


How does a DAW or RealBand do this? By taking advantage that every track of a song recorded in a DAW can match the song tempo to a grid. The audio/midi/loop/sample can be placed at exactly the correct point to seamlessly merge with any prior audio from that point and any subsequent audio from that point. This works with a single note, single word, single phrase, whole verse, chorus, bridge, intro or ending.


To demonstrate the technique, regardless of what format you provide a demo to your producer, assume the producer reviews your project and gets back to you with the suggestion your demo song needs a 8 bar bridge between verse 3 and the last chorus. He/she further suggests the bridge's tempo be increased from 116 to 118 to make it more dynamic and the tempo should be dropped back to 116 at the last chorus. A final suggestion is to use a different chord progression than the intro or any verse or chorus.


For demonstration, your song has an 8 bar intro. Twelve bar verses and a 16 bar chorus. Using this technique, you have sectioned and named your song project when you created it. You have created a folder tree that follows and aligns with your song section structure. Intro, verse, verse 2, verse 3, chorus and outro. Following your MuseScore .XML file, you create a BIAB .sgu file saved and named to correspond to each section and placed in the corresponding sub folder in your song folder tree.


In this example you would first create a sub folder in your folder tree that corresponds with the Bridge you will create.

Second, open up the 8 bar intro BIAB .sgu file to create the 8 bar new section from and name it Bridge. Do a Save As - Bridge.sgu into the Bridge sub folder you created.

Working in BIAB project Bridge.sgu, Increase the tempo from 116 to 118

Decide on the bridge's chord progression and modify the chord chart accordingly.

If necessary or desired, change the style of modify the instruments and also changes to any bar using the bar settings.

Once you are satisfied with the Bridge's arrangement, Render the audio and save it into the Bridge sub folder.

Open your original RealBand project for your demo

Save a new and renamed version of the RB /seq file as your new file will now contain a bridge section

From the Bridge sub folder, select the Bridge audio file

Go to the Marker for the last chorus

Paste the bridge audio snippet at the marker for the last chorus

This inserts the bridge audio between verse 3 ending and the last Chorus just as your producer suggested. It is cross faded and seamless. If for some reason it isn't seamless, RealBand uses an artificial intelligence algorithm that can regenerate the audio to be seamless in a single step. (more about this powerful and unique feature later. RB is the only DAW that can do this)


So, after reviewing these changes to your demo, your producer comes back and is happy with the changes but now wants to eliminate the intro and begin the song with a Chorus then proceed with verse 1.

you open up the latest RB version of the project, Set the cursor at the beginning of a Chorus, Using Block\Select current selection - This will highlight and select the complete chorus section.

Go to the beginning of the song and set your curser at the beginning of the intro. Repeat the Block\Select current selection command. This highlights the Intro. Paste the copied Chorus at the beginning of the Intro and the Chorus audio replaces the Intro.

I added a photo to show a Marker block section highlighted.










Attachments
RB Markers.JPG




Edited by Charlie Fogle (06/17/19 07:03 AM)
_________________________
BiaB Ultra Pak+ 2019:RB 2019 Build 3. Dell Inspiron AIO Desktop; Windows-10-64 bit, 7th Generation AMD A9-9425 Processor Five Core 3100 Mhz and 16GB DDR4 Memory.

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


PG Music News
Xtra Styles PAK 7 for Band-in-a-Box® for Windows Special Extended!

Customers LOVE the new Xtra Styles PAK 7 for Band-in-a-Box® 2019, so why would we end our special so soon?

The answer: We're not going to! We've extended our Xtra Styles PAK special to October 15th - so there's still time to add 164 new RealStyles to your collection for just $29!

In fact, we've put all of our earlier Xtra Styles PAKs (1-6) on sale for just $29 each until October 15th, and always offer specific genre for just $15 each.

For more information and to listen to demos, click here!

Band-in-a-Box® 2019 for Mac New Features Video!

Want to learn all about the new features in our just-released Band-in-a-Box® 2019 for Mac? Check out our latest video:
Band-in-a-Box® 2019 for Mac®! New! All 64 bit program, VST/AU 64 bit plugin, 202 RealTracks & more!

Jump to the feature you'd like to learn about the most by choosing from the table of contents, listed in the video description, or here.

Band-in-a-Box® 2019 for Mac - Upgrade Today and Save Up To 50%!

Just released: Band-in-a-Box® 2019 for Mac with 64+ new features (64-bit!!!!), 202 New RealTracks, 40 Unreleased RealTracks, 10 "Low Man" and Re-amped "12-Key" Metal/Thrash Electric Guitar RealTracks, "Look Ma! More MIDI!" – 30 MIDI Styles, 12 new MIDI SuperTracks, 240 new Instrumental Studies, 18 new Artist Performances, and a new Xtra Styles PAK 7!

We're having a SALE on Band-in-a-Box® 2019 Upgrade purchases until October 15, 2019 - save UP TO 50% when you purchase your Band-in-a-Box® 2019 for Mac Upgrade!

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 Mac 2019 packages, but for more even more Add-ons (including 40 Unreleased RealTracks) upgrade it to the 2019 49-PAK for only $49. You can see the full lists of items in each package, and listen to demos here.

Check out our packages page for all the purchase options available, or visit this discussion on our Band-in-a-Box® for Mac forum.

Video - 202 NEW RealTracks for Band-in-a-Box® 2019 for Mac!

With the release of Band-in-a-Box® 2019 for Mac we also released 202 NEW RealTracks (in Sets 301-328)!

Listen to all the individual demos here, or watch our Band-in-a-Box® 2019 for Mac - 202 New RealTracks Overview Video here

Get all 202 new RealTracks when you purchase any Band-in-a-Box® 2019 for Mac UltraPAK, UltraPAK+, Audiophile Edition, or the PlusPAK upgrade, on sale until October 15th!

Band-in-a-Box® 2019 for Mac - 49 Requests Fulfilled!

49 of your Problems solved? List of 49 Requests fulfilled in Band-in-a-Box® 2019 for Mac.

With Band-in-a-Box® 2019 for Mac there are a lot of new features, 202 RealTracks, and more. We get ideas for the new features and new RealTracks from our users. There are several sources, our Wishlist and general forum, support phone calls, trade shows, etc. In most cases, customers are not describing a new feature – they are describing a problem they have that they would like to have solved.

Here is a list of our features and additions in Band-in-a-Box® 2019 for Mac, presented from a unique perspective. It is from this customer list of "problems they would like solved." These are not exact quotes, they are paraphrased from our discussions with our customers. They explain what problems and requests they discussed with us, that resulted in the various new features and RealTracks. Hopefully this answers the question "Why did you add this feature/content?"

So, without further ado, here are the 49 requests/problems that we (hopefully) have solved with the release of Band-in-a-Box® 2019. We hope that many of them are relevant to you as well. And please keep suggesting new ones, we appreciate that.

Q. Almost all of my music apps are 64 bit, as is my Mac OS. But Band-in-a-Box® is 32 bit. And Apple's next OS, Catalina 10.15 is set to be released in October 2019 (the beta is available now), and that won't even run 32-bit apps! Can you make a 64 bit version?
A. Yes, we’ve done this with Band-in-a-Box® 2019 for Mac. The app is 64 bit and the executable name is still Band-in-a-Box®.app (if you have an older 32-bit version it will get automatically renamed during the install to Band-in-a-Box®-32bit.app ).

Q. I have 64 bit plugins that I want to use with Band-in-a-Box®. But they only work with 64 bit apps. Can I use them with Band-in-a-Box® 2019, without having to use any special software for this?
A. Yes, 64 bit Plugins work natively with the 64 bit version of Band-in-a-Box® 2019. This means you can use your 64 bit plugins, including ones that use huge amounts of memory (more than 2GB).

Q. Does Band-in-a-Box® 2019 work on the latest OS, Catalina 10.15, as that has many changes?
A. Yes, Band-in-a-Box® 2019 is 64-bit and runs great on Catalina (and older OS's down to and including 10.6.8 Snow Leopard)

Q. I like Snow Leopard as an OS (10.6.8), will Band-in-a-Box® 2019 still run on that with all features working?
A. Yes, Band-in-a-Box® 2019 64 bit version runs great on older OS's including Snow Leopard, and has identical features and operation to the newer OS's

See the full list here!

Xtra Styles PAK 7 for Mac is Here!

Xtra Styles PAK 7 for Mac is here! These work with the RealTracks & RealDrums in your Band-in-a-Box® 2019 UltraPAK, UltraPAK+ or Audiophile, and are a GREAT addition to your Band-in-a-Box® resources!

Listen to all the great new RealStyles in Xtra Styles PAK 7 for Band-in-a-Box® 2019 for Mac: click here

Xtra Styles PAK 7 and all the Xtra Styles PAKs from 1 thru 6 are on sale for only $29 each during our Band-in-a-Box® 2019 for Mac special! Learn more...

Band-in-a-Box® 2019 for Mac is HERE!

Attention Mac users...Band-in-a-Box® 2019 is HERE! https://www.pgmusic.com/bbmac.htm

There are 64 new features, including our brand-new 64-bit version of Band-in-a-Box®, which works well with the latest plugins and 64-bit OS features! There's also a new 64-bit VST/AU/AAX Plugin of Band-in-a-Box, which you can use inside your favorite DAW (GarageBand, Logic, Reaper, Pro Tools, Digital Performer, Ableton, PreSonus, etc.) to generate styles, RealTracks, RealDrums, Multi-Riffs, etc... AND SO MUCH MORE!

Watch our Band-in-a-Box® 2019 - Everything you need to know in under 6 minutes! video to see the new version in action!
Click here to watch...

PLUS... During our Band-in-a-Box® 2019 for Mac release, we're offering some AMAZING upgrade pricing - save up to 50% on most upgrades! Plus, we have a Bonus PAK full of great new Add-ons FREE! You can upgrade it to the 2019 49-PAK to receive even more NEW Add-ons including up 40 additional RealTracks... that's 242 NEW RealTracks!

Band-in-a-Box® packages: click here

Bonus PAKs: click here

Forum Stats
30053 Members
62 Forums
60010 Topics
505265 Posts

Max Online: 2434 @ 11/14/17 12:37 AM
Newest Members
smeier, Prof P, Rakejazzman, stevemac70, Auggie9000

30053 Registered Users
Top Posters (30 Days)
Icelander 305
zedd 203
JayO 183
RayL 183
Janice & Bud 176
Deryk - PG Music 136
Noel96 136
PeterGannon 135
Matt Finley 99
Pipeline 99
Today's Birthdays
jazzman174, jypi