I have had more problems with this version since I bought it then the whole year with my 2016 everything pack. There is a bunch of problems. Yes, I installed yesterday the latest build 463 and nothing changes.

Here is just some of the things that never ends;

1. Songs stil stop at bar 8 after loading it... How could I ever use this for backupband on stage, if I was doing that????

2. Cannot use the dropbox for Midi.. Never a problem in 2016...

3. Yesterday, when generating a solo, it ended up in the bass track !

4. After investing in a brand new desktop with 16 gb ram, it stil start scrambling badly, if I load/unload a lot of real tracks. so I cannot even stop it, with out using ctrl-del.

5. I want to delete a track, and pressing delete on the track menu, and the track just refuse to get deleted !

6. To many thing to even remember... But EVERY day since I started using it on my old laptop it had been problems problems problems... Was thinking it was my old laptop, so I invested in a brand new desktop, and nothing got better. Then I was thinking I needed the latest build, but stil the same, even saying when I start it; "A new update is available, install it now?

So, tired of this, I will give it a last change tomorrow by uninstall it and then reinstall it... If anything turns out the same I uninstall it for good and installing 2016 again...

But, since the refund periode is over lang ago, can I copy all the new styles and real tracks over to 2016 and use it there?

Frustrated, but stil in love with BiaB and grateful for this great community...

Leo

Does this happen to one or two songs or is it every song? Also are they songs from older versions of BIAB or created with this new version?

If it only happens to one or two songs, it might be that you have a corrupt song file. It's rare but sometime it does happen that a file gets corrupted. It's not always possible to fix it but try this...

1. Open the song file in Realband.

2. Use "Save As" in Realband to save the file with a new name. You will need to change the file type from SEQ to MGU or SGU (whichever extension the old file had).

3. Load the newly named file and see if that works better.


Can you explain this a little more fully. What midi are you talking about? Is is Supertracks, midi notation of Realtracks, a Melodist generated midi file, etc. You haven't given me enough information to try and help.


It sounds like you might have had a Bass Realtrack loaded on the Soloist or Melody track. The track would have been named "Bass" because BIAB automatically names the tracks after the instruments now.

While we're trying to sort these problems, disable the automatic naming function. Disable "Autogenerate track labels" as shown in the image below.



With this disabled, the tracks will always show the same name now (Bass, Piano, Drums, Guitar, Strings, Melody, Soloist). These are the original names BIAB used to use. I always use BIAB with the autogenerate names feature turned off.

Using these names will make it easier to identify where the Soloist was located.


I'm not sure what you mean by "load/Unload a lot of realtracks". How do you load them and then unload them? Can you give a little more information please and I'll see if I can help.


It's never been possible to delete a Realtrack from a BIAB track by using the Delete button.

To delete a Realtrack, there are a couple of ways. One way to do it is...

1. Rightclick on the track in the mixer.

2. Choose "Select Realtrack".

3. From the list select "Choose no Realtrack for this track".

Note 1: some styles have a Realtrack already loaded and it's best to leave that present if a message comes up that says that the style contains a Realtrack. In that case, just turn the track's volume down to zero on the mixer.

Note 2: If you are wanting to delete a Realtrack so that you can load another one, that's not the best way to do it. Simply load your new Realtrack without deleting the previous one. The new one replaces the previous one.


For the moment, while we're trying to sort out your problems, turn off the automatic update.

1. Under the "Help" menu, click on "Check for updates"

2. When the update window opens, remove the tick from "Automatically check for updates".


Lastly, have you used the Audiophile USB drive to install the compressed version of the program on your computer's internal hard drive?


Let us know how you go.

All the best,
Noel

• my latest song : At Apollo Bay

In case your post is meant to imply that the audiophile version has anything to do with your difficulties, it does not. The core program is the same for the audiophile and 'regular' versions.

Thank's again Noel for ur always helpful and detailed help ! U should be paid by PG Music for all the hours u spend trying to help PG Music customer out... (Did u hear that Mr. Gannon ? )

To take it point by point;
1. Not every song. Seems like it is pretty ramdomly.. Just to test it out right now, before I answer this I open BiaB, selected 3 different track from the Soundtrack demo songs, and all 3 stopped at bar 8. Then I open one of my own songs, whith 5 real tracks in it, and it did not stop, but BiaB started to flicker (Don't know the right word for it) again...

2. I mean drag a real track with green line under to the midi dropbox to get the midi file from it... I also tried to save song as midi, but the song saved contain no midi... The midi is there, because I can see the notes.... I never had this problem in 2016. And I need those midi files for a project...

3. No, I had not.. It was one of the soundtrack songs I was flicking around with to try learn more about generating solos... I heard the solo, so I wanted to hear it alone. Then to my surprise I found it on the basstrack, the original one....

4. Bad wording from me... What I mean is trying out different real track.. It happens especially when I mute som of the real track... But today, right before I write this, it happens right away when I loaded and started play a song with real track.. I had this problem also before on my laptop, so I thought it had something to do with lack of ram to process all the data, but my new desktop has 16 gb ram, and a i5 6400 CPU 2.70 GHz so can't be that I guess?

5. I go to the track action menu and click erase track.. In 2016 this gave a question; Do u want to erase the real track, then after confirming, a new question came up; Do u want to erase the Midi track, and after confirming it, it was gone.. Is this not possible in 2017 ?

The new update stuff solved by follow ur tip.. Seems like if downloaded outside BiaB and installing it separately, BiaB will not recognize it as done already...

And now, when I was looking for BiaB in the uninstall menu window, the only I see there is Band in a Box 2017 (463) update. Is this the only I need to uninstall in order to install a new fresh version ?

A little update about my problems;

1. I uninstalled the Band in a Box 2017 (463) update. No more "Glitching" as long as I have used BiaB today after that...

2. The stop at bar 8, does not happen when I play the same songs in Jukebox... After I tried that I tried to load them from the soundtracks menu, and they stopped at bar 8 again...

3. When worked at a new song today, I transposed the melody up one octave. Worked. Then Embellish same melody and it went back down one octave, but the notes stayed one octave up, until I pressed play.. I tried repeatedly to transpose up, and the notes went up, but when I pressed play, all notes went back down... I then saved the song and reloaded it, generated a new melody using same melodist and the same happen. Ny idea what I do wrong here?

Trygve, I'd like to be able to repeat your process exactly as you do it so that I can test it out. To do this, though, I need step by step instructions, one step at a time, as to what you do. I need to know what style you tried and I also need to know exactly which buttons you press.

For example..

1. Enter style picker.

2. Select _CDRIVI2.STY.

3. Click on the button called....

etc.

As I said, I'd like to be able to repeat what you did exactly. Unfortunately, the information you have provided does not let me do that.




Did you generate the song before you tried this? Nothing will be saved if the song is not generated. I have build 464 with the Audiophile version and it worked fine for me.

If you want to load build 464, go to the link below and download the file. Then exit BIAB and doubleclick on the update to run it. Just check that the installation paths are correct.

http://www.pgmusic.com/support_windowsupdates.htm



If the solo was a Realtrack, it could be located on the Bass track. The tracks are simply place-holders for Realtracks. All BIAB tracks are equal in this regard.



Did you generate the song? It's not enough just to press Play. I've noticed that in 463 and 464, BIAB does not automatically generate a new Realtrack when you change one like it used to do in BIAB 2016. I reported this to the Support team a little while ago.



Again, did you regenerate the song after erasing it? It might be the pressing Play is not enough.


Let us know if this helps.

Noel

Found out about point 3. There is a setting in the melody embellisher "more" where we can set the "Adjust octave method to "Only adjust if outside instrument range" This fixed my problem...

464 now available.

Yes, I saw that today, but I'm very skeptical.. 463 made it a mess, so had to uninstall it... Guess I will wait and see...

Hi Leo

I'm running 464 with no issues, but I was running 463 with no issues also.

The problems you are experiencing, although obviously very real, have not been identified at the same extent by others, so we probably need to look at your particular set up to identify the issues.

You normally don't need to uninstall BiaB to install a new versions. Just run the installer and it will upgrade your existing version.

Trygve, could you give us more information on your system? Things like how much ram, what hard drive and what speed is the hard drive, CPU speed etc. Also have you had the computer cleaned lately; that is no viruses, malware, spyware etc on your system?
Also do you have WIFI, anti-virus or anything else running while you are using BiaB?

All of these are important when tracking down a problem that no one else is having as anyone can cause problems when using any CPU clock dependent programs like music creation, animation, and any machine that runs off the clock, i.e sewing machines, industrial machines etc.

No, I did not see anything from u... Was hoping for it.. Why u need a submission code? And approval from moderator?

And it is not working out for me yet, only the transpose problem.. Just had to use ctrl+del. again, after reinstalling BB. Was working on a song, loved it, and wanted to try Pianoteq 5 VSTi on 4 of the tracks to have it as a pure piano song... Then BANG ! started to "scramble" terrible... Impossible to stop it... Checked the CPU use, and it was 39% and the RAM was on 25%, so it cant be about my PC can't handle the load...?

Leo,

39% CPU load is extremely high, especially for your setup.

To help you track down, can you repeat all of the steps again but don't try the Pianoteq VSTi and see if the CPU load is more normal?

Running the same VSTi on 4 tracks is likely to be problematic. The same VSTi code is trying to compete with delivering to 4 tracks simultaneously.

As mentioned previously, others are not having issues such as yours.

Also, Noel's comment about moderators was related to a change in posting caused by a number of recent spammers. You probably don't need to worry about that part.

Andrew mentioned he believes the steps he took to further prevent spamming are done, and the minor glitches some of us experienced while posting should be over.

There it was ! Must have been approved after I was posting my latest one... Ok, I open BB,
1. Click melody
2. click Generate Soundtrack
3. Click load soundtrack Song
4 Whatever song I chose from there stops at bar 8
5. I open the same songs from the Soundtrack Midi Fakebook folder by the file menu, open, and they do not stop at bar 8...
6. I tried right now a couple of other BB song, and so far no one stopped...



Yes I do generate the song first, not only press play. I tried it again right now, after a fresh new installation, even clicked back to factory setting to be sure, generated a song and nothing happen when I drag a real track with green line under to the midi dropbox... I tried to save it as midi again, it saved, but only the melody that is not real track and midi drums could be heard...





No, it was not a real track, it was a solo generated by BB





Yes, I did generating the song. I always have to do...


Yes, I do regenerate the song first, and the track is stil there playing as if it was not erased....

Again Noel, thank u so much for trying to help me out with this problems...

I have no idea why I have this problem at all.. But ok, later today I will try to install 2017 on my old laptop that I reformatted last week and see if the same problem happens also there. IF it does, then it most be BiaB that have som corrupted files on it or what ever... Will try also to download 464 and install and see if anything work after that... IF not, I want a new one from PG music ! Do I have the right to that?

I believe PG Music has the ability to generate a checksum so you would be able to ensure a successful (uncorrupted) download. As each new update is cumulative and works with any version of 2017, any update that downloads without corruption should work.

Trygve, I've seen this behavior in the past, when I built computers for a living.

There are two probable sources for this to happen:

1. some faulty component(s) in your new computer. Either the RAM or the HD.
2. some (all?) audiophile RTs are from corrupted downloading.

Both causes leads to the same erratic behavior: the data read from the disk, is not the same than the one delivered to the CPU to process, so the outcome can simply not be the one expected, 'cause the RAM stick(s) are not handling the file's checksums well due to faulty timing, or the sectors where the data was written are bad.

That's the beast I can do without actually opening your machine to test.

HTH,

Ok, thank's a lot VT, I did not know that was extremely high...
Was suspecting it had something to do with Pianoteq on 4 tracks, so I changed it to be the Default synth, so all tracks played piano, and that seems to run without problem, except for when I tried to save the song. Then it came up an box with red X saying "Out of memory at 00A1F6C7"... But I could export is as WAV file...When I check the CPU use right now, having BB open, but not running it, the cpu is 3 %, when I start play the cpu vary from 14-18% RAM at 21% whether I play or not.... So I wonder how can I be out of memory when it was only at 25% when I checked it after getting that message box?

Thank's Matt, Will ask PG Music for that, so that next time, I can ensure for that...

Thank's Kojak ! That makes a lot of sense to me.. Actually, it was a friend of me that bought this PC for me in parts, and assembled it. He is a computer technician, but I have had a feeling from the very start that something might be wrong.. Because the first I did, was to unzip some of my old RAR filesstuff to get it on the my new PC. But, when I did, I observed that it started to unzip, then hang a little, then continue, then hang a little again, a.s.o. It has never done that before... Fortunately, I have a warranty for all the parts, so I guess I can get it fixed if it turns out to be a RAM problem or something...

Will install 2017 on my laptop tomorrow and see if the same problems occur there...

Thank's a lot all of u for ur assistanse to help me out ! What would PG music be doing without this great forum????

Trygve,

The above is exactly the information I needed. The section of BIAB that you are working in is designed by PG Music to be used for creating mood music for backings of slide shows, home movies, etc. It is not part of the commonly used area of BIAB (which is what I thought you were talking about).

Just so others can see where you are spending your time, I'll paste an image (it's the upper image at the end of this post).

You are one of the very few people that I've encountered who use this section of BIAB. It's a great area to play around in! Unfortunately, it was not something I thought of from your earlier descriptions.

Now that I know where you are creating your music, I can confirm that it only works for 8 bars for me, too. There's DEFINITELY a problem here. I have reported it to PG Music developers so it will be fixed as soon as they have isolated the cause.

Also... in relation to your other post on copyright.... if these are the melodies that you are talking about when you create your songs, then you are ok. PG Music indicate under the "Help" button, that this music is royalty-free and can be used freely (see the lower image below).

I will add this to your other post too in case others find the information useful.

Regards,
Noel

P.S. I loaded a songfile of mine in that I've been working on and, after using the Soundtrack Generator, it stopped at bar 8 too! When I exited BIAB and restarted it, the file played fine.

I have never in all the years gone here! As I read this thread I thought maybe these are loops So I went directly into the file folder in explorer and just selected one file. It opened in BIAB and OMG what I am hearing? It appears to be a collection of layered synth pads producing a atmosphere backing. It was really really cool! Did not even sound like BIAB. And by the way, it played through with no stopping on bar 8.

Sorry you are having troubles, but Thanks for the heads up.


Mystery2.sty demo "The Quest"

Soundtrack Style
3/4 Background style

mysterious and dark style featuring ostinato harp 8ths and pads

"A" section:

low synth strings play bass notes
shaker plays 8th notes
harp ostinato 8th notes
pad sweep plays offbeat 8th ost. pattern

"B" section

add more drums/perc
bass strings play octaves, louder

melody=koto/flute in unison

tempos = 75-140

By the way when I load from within BIAB only 8 bars played, but loading from Explorer all played fine.

OK, now I'm starting to follow better, I tried it and got some similar results, although mine did a (not very good timing) restart after 8 bars.

Checking further I noticed the settings as shown below which might account for the restart.

Also, I tried Arctic Trail and the song restarted after 8 bars but the side stick then went - how do I say? - whacky

Update:
I tried the same song as above (Arctic Trail) on 2016 Build 437 and it did not exhibit the same problems. Also restarting the Generate Soundtrack function was OK after the number of bars was increased from 8.

Videotrack's picture makes me think the default setting makes this like a demo - a sample, for quick preview?

Trev,

That's some nice detective work, there!

I've highlighted those areas on the image below that affect how many bars the song plays.

=======

Trygve,

Following on from Trev's discovery... on the image below, I've highlighted those settings that control playback behaviour.

Regards,
Noel

Actually, what I was referring to regarding Copyrights was not the song I can create using this Tool, but the songs loaded from the option "Load Soundtrack Songs" I liked most of those very much, and as mentioned in my first post, uploaded some to soundcloud.. Just used some different VST and added some real tracks for the backing. But the melodies and solos I did not changed or replaced with anything... So that was my question if we are allowed to do... Perhaps it is OK if I add in the song description; Melodies and Solos created by PG-Music ? Perhaps PG-Music could be kind to come in here with some guidelines for this question??

My next question here is; IF those melodies WAS created entirely by using the melodist and Soloist, WHICH melodist/soloist was used??? Because, there is some pretty unusual phrases there that I have not be able to, so far, to find any melodist doing. For instance in the Dark Places melody.



Yeah, I thing that would be very helpful...


Seems like something "Sits in the system" after using the soundtrack generators default setting... Hopeful all the problems with stopping at bar 8 will be gone after resolving this--

Thank's again Noel !

Happy u discover it also MusicStudent !

Wow ! I bang my head in the wall ! Why have I overlooked this ???
Never stroked my mind it will affect also those demo songs...
Thank's for discover it VT !

Leo, You're very welcome. We all learned something from this little exercise!

I play around with this feature quite a lot and you can load any BIAB sgu file and create a custom soundtrack to any length desired. Using the Load Existing Song button and navigate to the folder location of the song you desire to make into a soundtrack and using the Desired Duration Button which un-grays the selection buttons below the Desired Duration Button. You can select and deselect specific tracks as desired also.

It's a great feature.

Thank's a lot again Noel ! U r a really great help and inspiration for me !

I wanted to circle back to this old thread. No intention to beat my own drum (I don't make any money on play count ), but I did spend sometime getting to know this BIAB Feature and was really happy with the outcome. So this is simply another testimony to what is hidden in BIAB for those who explore.

River Winding

The next time someone asks about what files and styles they can delete cause they don't "... use any of that stuff", tell them there is gold in them there mountains.

Dan,

You've created a really lovely piece of music, here. It's wonderful!

All the best,
Noel

Really excellent Dan, you've made great use of this feature, for sure.

Hello Thrygve ... Meanwhile 466 jumped out of the magicians hat, fixed quite a bit of issues i had, especially regarding bar count changes it seems (like a 2/4 measure inserted in a 4/4 song), and VST problems with some plugins I think also. But i still find some RTs missing a bar, especially the soloist type versions.

I take it your on Windows, not MAC.

Hardware: If you use Windows 10 and an external USB drive like the USB 3.0 WD one your Audiophile came with, problems are often USB related. First of all use a quality cable, but the one from WD seems adequate when tested for speed. Then look at the USB port you use. I had and have problems regarding the chip brand and drivers with an RME audio interface. Found that ASmedia chips with USB 3.0 and 3.1 suck, and NEC (Renessas) work far better regarding hiccups, dropouts and distortion. Un plugging and re plugging (wait at least 30 seconds, using a power switch to 'on-off' is better) an USB drive or -audio interface often fixes realtime issues too since the drivers are loaded again.

If you use a laptop in might be an idea, as you cannot plugin some other brand PCIe USB 3.0 card, to remove the USB drivers (uninstall them all, also the "HUB" ones, in Device Manager) let Windows re install them again. Further more: NVDIA graphics can cause problems with USB Audio. Switch off acceleration and other gamers' software gizmos, or try to find the LATEST barebone drivers, UNINSTALL the old ones, preferably use a cleanup tool like ATI has at their site). I have an ATI Radeon, but found i had to do the same, and bingo, my "realtime" USB performance was a lot better. Also find the latest Chipset drivers and mainboard BIOS (also for a stand alone PC).

Software: Some VST plugins can cause en extensive load on processing power also due not so efficient programming maybe. F.I. Yamaha Vocaloid is almost unusable because of this on Windows 10 64bit in my situation.

I had a bought Bitdefender 2017 Total Security causing serious problems with USB and my RME USB audio interface, and think they were firewall related. I now bought 360 TS and use it with Zonealarm free (firewall only). You can easily mark a whole (USB) drive as being safe with no need to be scanned. All virus killers seem to think that any external USB drive is a prime suspect for computer crimes aboard, courtesy of Kim Il Jung (oops, no politics). F

Really beautiful version of this beautiful melody...Well done Dan !