<snip>
> I've searched a workaround to this problem on the Net, and found only
> a very short mention (I seem to remember by Uli Franke) of a command
> that tells Saracon to retain original metadata in the process. As it
> appeared (and unfortunately without any further explanation), it
> seemed only possible with Saracon used in CLI mode (for which neither
> me or my assistants are well versed at all). As a thorough check did
> not reveal any such information in the Saracon user manual, I'm asking
> here in this group if someone has any information to share about it.
>
> Ideally, we might even venture and try to run Saracon from a terminal
> window if a step-by-step process explanation was available, but that's
> maybe too much to ask. Lacking any such means, and with no possibility
> to instruct Saracon to retain original metadata via its GUI, I'll be
> forced for time reasons to adopt a lesser-quality SRC solution (which
> definitely bothers me, having such a sonically-wonderful tool at hand
> that Saracon is).
Saracon has a few metadata transfer functions built in but not as
complete as in consumer converters as metadata plays little or no role
in professional audio. But there's hope for your headache. You can use
"Post-processing" within Saracon to transfer the metadata from the
source to the target file. But for further support I have to collect
some additional information
* Which version of Saracon you're employing at the moment
* Which OS you're running Saracon on
* The type of files you're converting (probably FLAC or aiff?)
Regards
Uli
Ok, this answer is better than the previous one because the in/resp
output formats are now clearly defined.
I assume you use Vorbis tags on FLAC files (input and output) and ID3
tags on AIFF files.
The solution I suggest is the following: We hook a small tag transfer
program/script into the post-processing feature within Saracon.
Fortunately you're on OS X which makes the whole process less a PITA as
we can use bash scripting.
How urgent is it? I'd have to write a tag reader which supports the aiff
ID3 tags as they are not that common which could take some time as we
have a full schedule here.
Could you please provide me with a list of the tags which you'd like to
get transferred?
And: You'll probably need a more recent version of Saracon. I'll send
you a pointer to it as soon as we'll get to the real thing.
Regards
Uli
Note: Please
a) post back to the mailing list by responding to the original message,
this way the thread won't get destroyed and others can profit from our
discussion as well
b) reply to the bottom of the mails as I usually read from top to bottom
Thanks!
--
Uli Franke -- R&D Engineer Dude
WEISS ENGINEERING LTD.
Professional Digital and Analog Audio Products
Florastrasse 42, 8610 Uster Switzerland
phone: +41 44 940 20 06, fax: +41 44 940 22 14
email: uli.f...@weiss.ch web: http://www.weiss.ch
"To define recursion we first have to define recursion."
"What you boot is what you get."
> � restrict source files to .FLAC ONLY, FORGET ABOUT AIFF!
Great, good idea
> � can't say if tags are VORBIS, sorry, it's what PhileAudio/Max/
> Foobar2000 tag them with by default.
Perhaps you could make me a short file available from a public download
location in order I can investigate.
> � single albums are: %artist%_%date%-%album%-%track%.%title%-[%composer
> %].flac
> � double album are %artist%_%date%-%album%-%disc%.%track%.%title%-
> [%composer%].flac
That's just the file name. I'd like to know which tags are to be transferred
artist
album artist
title (aka track)
tracknr
composer
disk/part of set
date/year
picture ?
...
> � waited so long until now, can wait.
Great. This way I'll definitely find a quiet moment to implement this.
Regards
Uli