Backing up Ardour Files
 

HI AllTrying to backup my*multi-track*files from Ardour *and I keep getting <F1>Name of file ect *as invalid*file name*and cannot back up the whole Dir.
This means I'll have missing audio when I come to replay the session.

Anything I can do?
CheersBob



_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Backing up Ardour Files
 

On Wed, May 12, 2010 at 1:22 PM, Frank Smith <frsmith@gmail.com> wrote:

HI AllTrying to backup my*multi-track*files from Ardour *and I keep getting <F1>Name of file ect *as invalid*file name*and cannot back up the whole Dir.
This means I'll have missing audio when I come to replay the session.


Anything I can do?
Do any of the files you created have names including ,:;'"/?$%&#! or | ?
There are others that can cause problems but I think I caught all of the most likely ones in that string.


-Neil
--
DJ Dual Core's Blog
http://oldmixtapes.blogspot.com/

_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Backing up Ardour Files
 

HI Niel
Thank you for your reply.
The only thing I can see is the <F1>. Will this cause a problem?
These are system generated files from Ardour.
Has this problem been documented? I can find nothing on the net.


Cheers
Bob



On 13 May 2010 21:33, Neil Clopton <djdualcore@gmail.com> wrote:



On Wed, May 12, 2010 at 1:22 PM, Frank Smith <frsmith@gmail.com> wrote:


HI AllTrying to backup my*multi-track*files from Ardour *and I keep getting <F1>Name of file ect *as invalid*file name*and cannot back up the whole Dir.
This means I'll have missing audio when I come to replay the session.



Anything I can do?
Do any of the files you created have names including ,:;'"/?$%&#! or | ?
There are others that can cause problems but I think I caught all of the most likely ones in that string.



-Neil
--
DJ Dual Core's Blog
http://oldmixtapes.blogspot.com/



_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Backing up Ardour Files
 

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:

daniel@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

Backing up Ardour Files
 

Daniel James wrote:
>> 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:
>
> daniel@64studio:~$ touch <F1>test
> bash: F1: No such file or directory
>

Using the correct syntax handling this special characters shouldn't be
an issue for any application: $ touch <F1>
File names are allowed to use any sign excepted the /, NUL, * and ? in
Linux file names. I don't know any trick to handle the - as first sign
for a file name:

$ ls -al
-rw-r--r-- 1 spinymouse-sudo spinymouse-sudo 5 2010-05-14 11:35 -n

E.g. try to run $ cat ;). It might be better not to use the - as first sign.

Apart from that I couldn't find information about forbidden signs for
Linux file names. If < and > aren't allowed when using Ardour, Ardour
should inform about it and ban those signs. IMO this would be a serious
issue and should be reported to Ardour devs.
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Backing up Ardour Files
 

> Daniel James wrote:
>>> 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:
>>
>> daniel@64studio:~$ touch <F1>test
>> bash: F1: No such file or directory
>>
>
> Using the correct syntax handling this special characters shouldn't be
> an issue for any application: $ touch <F1>
> File names are allowed to use any sign excepted the /, NUL, * and ? in
> Linux file names. I don't know any trick to handle the - as first sign
> for a file name:
>
> $ ls -al
> -rw-r--r-- 1 spinymouse-sudo spinymouse-sudo 5 2010-05-14 11:35 -n
>
> E.g. try to run $ cat ;). It might be better not to use the - as first
> sign.
>
> Apart from that I couldn't find information about forbidden signs for
> Linux file names. If < and > aren't allowed when using Ardour, Ardour
> should inform about it and ban those signs. IMO this would be a
> serious issue and should be reported to Ardour devs.

Correction:

spinymouse-sudo@64studio:~$ cat ./-n
test
spinymouse-sudo@64studio:~$ cat -n ./-n
1 test
spinymouse-sudo@64studio:~$ rm ./-n

Using the - as first sign shouldn't cause trouble. But I guess using the
$-sign could cause an issue.
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Backing up Ardour Files
 

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 <daniel@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:



daniel@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

Backing up Ardour Files
 

On 2010-05-14 11:47 +0200, Ralf Mardorf wrote:

> File names are allowed to use any sign excepted the /, NUL, * and ? in
> Linux file names.

Unix forbids exactly two characters in file names : NUL and "/".
"*" and "?" are legal ; they just need to be quoted or escaped if
they appear on a shell command line. Just like white space, ";",
"(", ")", "|", "<", ">", "&", and a few others.

The problem is that many shell scripts don't bother quoting
variable references. Whenever you see stuff like

cp -p $foo $1

in a shell script, you have a (latent) bug. That should be written

cp -p -- "$foo" "$1"

The "--" is important. It tells cp that the following arguments
are not to be treated as options, even if they look like one (i.e.
begin with a "-"). The "--" convention is not specific to cp, by
the way. It works with any program that parses its command line
with getopt, i.e. most of them.

--
André Majorel http://www.teaser.fr/~amajorel/
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Backing up Ardour Files
 

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
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Backing up Ardour Files
 

Andre Majorel wrote:
> On 2010-05-14 11:47 +0200, Ralf Mardorf wrote:
>
>
>> File names are allowed to use any sign excepted the /, NUL, * and ? in
>> Linux file names.
>>
>
> Unix forbids exactly two characters in file names : NUL and "/".
> "*" and "?" are legal ; they just need to be quoted or escaped if
> they appear on a shell command line. Just like white space, ";",
> "(", ")", "|", "<", ">", "&", and a few others.
>
> The problem is that many shell scripts don't bother quoting
> variable references. Whenever you see stuff like
>
> cp -p $foo $1
>
> in a shell script, you have a (latent) bug. That should be written
>
> cp -p -- "$foo" "$1"
>
> The "--" is important. It tells cp that the following arguments
> are not to be treated as options, even if they look like one (i.e.
> begin with a "-"). The "--" convention is not specific to cp, by
> the way. It works with any program that parses its command line
> with getopt, i.e. most of them.
>

Linux lesson :)

ok, I didn't know about the '--' vs '-' argument. If a file name starts
with an '-' the simple trick is to add the path first, IOW, if we are in
the wanted path, we anyway need to add './' first ... regarding to your
information ...

spinymouse-sudo@64studio:~/Desktop$ cat ./-n
test
spinymouse-sudo@64studio:~/Desktop$ cat -- -n
test

... wow, it works. Do you know that most information about issues
similar to this one don't have good explanations in the web?

Thanks,

Ralf

And pardon that it might be a little bit OT.
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users