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 On 14 May 2010 10:06, Daniel James <dan...@64studio.com> wrote: > Hi Bob, > > > The only thing I can see is the <F1>. Will this cause a problem? > > I would expect so, considering that > and < have special meanings in the > bash shell. For example, attempt to create a file with <F1> in the name: > > dan...@64studio:~$ touch <F1>test > bash: F1: No such file or directory > > However I just set up a test session using <F1> and <F2> in the master > bus and track names respectively, and I was able to copy it with cp -R, > then open the new copy of the session in Ardour. > > > These are system generated files from Ardour. > > That part of the peak filename should match the audio filename in the > interchange/projectname/audiofiles/ subdirectory of your Ardour session. > If it doesn't, then you may have a corrupted session. > > If only the peak files are corrupted, then try copying the session > without the peak files. On opening the new copy of the session, Ardour > may be able to recreate the peak files for you. > > Cheers! > > Daniel >
_______________________________________________ 64studio-users mailing list 64studio-users@lists.64studio.com http://lists.64studio.com/mailman/listinfo/64studio-users
