SgtRumpel

Yeah, I would do it, but these are large projects with copyrighted data from clients. I am not comfortable sending these files away ...

Hi there! I use bandlab for large projects (radioplays, podcasts), and every once in a while I have problems with the clip automations when exporting. Sometimes bandlab cuts off samples earlier than it should, sometimes it does not follow the automation correctly, so that clips are too loud or too silent or the fadeout happens too soon or too late. The strange thing is, when I listen to the project inside bandlab, everything sounds correct. Also, when I freeze the track, the resulting audio is correct. Only when exporting, the clip automation is incorrect with SOME clips, not all clips. These errors are replicable, that is they are not a glitch, but they come out wrong every time I export the project. What I also noticed several times (and I think these problems are connected) is that when I copy a clip in a project, the new clip sometimes has some weird behaviour - like it references the original clip, and if I move it, the waveform-graphic is being moved, but the clip still is to be heard at its original position. Normally when this happens, I delete the clip and copy it again. Of course I am not sure, if these two behaviours are related, but it is very strenuous to not be sure that the export reflects the automation in the project. When exporting large projects of ~ 1 hour you will have to listen to everything carefully, hoping to not miss any errors that ocurred during export. Is there anything I can do to avoid these problems?

Hi David, thanks for getting back to me. I did reasearch a little bit more and found out that some of the files I used where automatically converted (e.g. form 48 to 44.1 KHz). I work with a lot of small SFX files for the radioplays, where the files all have different formats. When I selected the original file with 48kHz, Bandlab would not tell me that the file is in the wrong format, in fact it did not five me any feedback at all, but it seemed that everything is fine. Only when I get into project I find out that the clip is empty and has no reference - and now I can't even correct the mistake, because there seems to be no way to reconnect a file manually. I think in genereal the program handles the import and connection correctly, but it is the interface, the somewhat limited options I have to reconnect a clip and the missing error reports that make this prone to errors.

Hi there, I work with quite large projects, as I am mostly editing radioplays and podcasts. Sometimes I have to change the location of source-files (for example, Bandlab copied the File to C://Programs/Cakewalk/ProjectA and I want the original file to be referenced that is on another Drive (D://MyProjects/ProjectA). As there is no possibility to manually reference a new file (which, I think, there should be!), the only possiblity I have is to delete the files from the folder and start up Bandlab, so it asks me where the files are when I open the project. So far so good. Inconvenient, but it works. Now I have three options when selecting the new file: - Move the file to the project folder - Copy the file to the project folder - connect the file from the current location The first two options work, but do not render the desired result - I want to reference the file on a different location. So I choose the third option - which does not work! After selecting the correct file, the parts of this file are being replaced with silence. Also, the reference to the Audiofile is lost (no entry in the window: right mouseclick->connected audiodata). If the file has not the identical filename, a warning appears, but the reference will still not be safed. I think this is quite an important bug, as Audiofiles can always be corrupted and have to be replaced by a working file. There simply is no way to do that atm in bandlab. Some further remarks: - The 'Search' Button for the audiofile would be way more useful, if you could specify a folder to search in. - The standard selection for this action should be 'Copy the file to the project folder', not the 'Move to ...' Option!!!