Originally Posted By: TomSarge
Originally Posted By: jford
You didn't say which application you are doing this in (BIAB? RealBand? PowerTracks? Something else?).


I am using BIAB2019 Pro 64bit


Is your audio interface set to 44.1kbps or 48kbps? All the PGMusic content is 44.1, but if you process it as 48, your audio is going to drift.


I don't know the answer but believe I'm good since it works find unless I save to disk and then try to change it.


This actually DOES matter. Band in a Box has only one track for you to use to record audio. Real Band allows more. A third party DAW also allows multiple tracks.

Both audio and midi are able to be used in all 3.

When people say they have horrible latency on recorded stuff on playback, it's generally caused by just a few things. The most common is the use of a less than optimal driver, the hardware, or settings.

Some interfaces use wrappers and codecs and proprietary drivers. That can cause serious latency unless set up correctly, and can still be a pin when set up correctly. ASIO is the preferred driver mode if the interface hardware supports it. Generally, if the project is 100% true audio, there are little to no issues in recording or playback. Even MME seems to be able to handle 100% audio projects fairly well. It's where you either have existing midi and synths or introduce soft-synths to the mix with audio, that you encounter issues with latency and the cheaper drivers.

My old laptop would run BB perfectly. No issues, no latency. However, when I tried to run the project in Real Band and added audio tracks, the latency was off the charts bad when I ran it using the default laptop audio driver MME. I could connect my Focusrite interface and use ASIO and the sync was perfect no matter what kind of tracks I used.

Also, variations in the audio track sample rate WILL cause audio tracks to drift of of sync. THis can happen but is not a common issue unless you are getting tracks from outside sources. Everything recorded in your software will have the same settings by default. 44.1 and 16 or 24 bits is standard. 16 or 24 bits are generally 100% compatible and even in the same project will play flawlessly. It's the 44.1khz sampling rate that needs to be the same. I record all my tracks at 24 bits and the software converts them instantly to 16 where needed. 44.1/16 is CD quality and is good for 99.9% of everything you need to do.

First determine the program you are using when you experience this latency. Check the settings to see what driver is in use with the interface you are using. If it supports ASIO, by all means, use it. You will need to experiment to find the problem.

EDIT: I researched this interface and like I suspected, I could not find a single place, including Behringer's website where they stated that this interface used true ASIO drivers. On one, (not the Behringer site) reference was made about ASIO4ALL as a driver but.... A4A is simply a wrapper to use MME and try to fool the hardware into thinking it's running ASIO rather than MME. I would never use any interface that did not support true ASIO. IN other music forums sites, the folks who had the most difficulty with latency were the ones who were often using interfaces that only ran codecs and proprietary drivers and A4A. The solution is to get an interface that runs ASIO. Perhaps you can get the UMC22 working... you can try. And we will help if we can. Settings and check the things mentioned. Good Luck.

Last edited by Guitarhacker; 05/22/19 04:10 AM.
You can find my music at:
www.herbhartley.com
Add nothing that adds nothing to the music.
You can make excuses or you can make progress but not both.

The magic you are looking for is in the work you are avoiding.