Justanoldmuso,

Good points. However, my video instructions addressed the fix based on the circumstances presented by the original poster. He used BIAB not RealBand and it appears his project likely had more than a single bar that contained fret squeaks so his situation would likely need to have multiple occasions to copy/paste or regenerate the track.

Yes, it makes perfect sense to do this in RealBand had the project been started or already resided in the RealBand program. Other than those reasons, it's more practical to do this in BIAB.

01. The time required to export just the single track in the Style and import it into RealBand would take more time than the fix would require using BIAB.
02. If he regenerated that track in RealBand, RealBand accesses and works in conjunction with BIAB to generate tracks and partial tracks. Thus, it's more logical to do it in BIAB.
03. If the poster saved the BIAB project and then opened that file in RealBand, again, that process alone takes longer than it would take to fix the problem in BIAB.
04. In addition, were the poster completely satisfied with the track other than the squeaks and had frozen that track, opening the file in RealBand would cause that frozen track to be lost because RealBand doesn't recognize and preserve tracks that are frozen in BIAB. RealBand would generate a complete new version of all the tracks upon opening the BIAB file.


An interesting point about Legacy Tracks. Because the task of copy/paste between bars on a Legacy Track can be done without using or having Utility Tracks, it has been a task that could be completed in BIAB since 2015 without using external software programs.

Last edited by Charlie Fogle; 10/12/21 01:34 PM.
BIAB Ultra Pak+ 2024:RB 2024, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.