Frank Smith wrote: > HI All > Thanks for the replies. > > I think this is the only session that I have frozen the tracks. > I think there may be errors when re editing a frozen track. > > This is where the <F1> and such seems to have appeared. > > When a track is frozen is not then meant to be 'unfrozen'? > > I was using this to make sure all tracks were in time to add some > imported wav files. > > This may have corrupted the files. > Any ideas? > > Cheers Bob
No idea, but I succeed it with interested. I don't use Ardour, but I'm missing a freeze-option for other apps I'm using. I guess you know that you could run 'cp' and copy the whole directory + files in /home ;). I'm not sure if I'm able to translate this ;) ... "When a track is frozen is not then meant to be 'unfrozen'?" ... My question and I guess you still checked it: Did you try to unfreeze any track before you do the (backup-)copy? Btw., I guess you're using a copy function given by Ardour to be safe, but perhaps "cp" from the command line might be more safe. It makes me wanna puke ;) ... there seems to be no OS, started at Atari times, that simply won't save AND COPY the current state OF ALL settings. -Ralf _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
