original metadata

258 views
Skip to first unread message

Sallustio Pinzauti

unread,
Feb 28, 2012, 2:11:06 AM2/28/12
to Weiss Engineering Saracon Users
Hello everyone in the Saracon group.

I can't find a solution to a problem that's causing me to waste a
considerable amount of time around converting the sample rate of (a
lot of) audio tracks with Saracon.

For reasons too long to explain (and not at all related to the purpose
of this [google] group), I need to use a specific make and model of
amplifier that has its own DSP on board, hence AES/EBU digital input.
Being this device developed by its manufacturer for pro audio
applications, the AES/EBU input accepts 24-bit wordlength signals with
sampling rate 48 or 96 kHz (not 44.1 or else).

For testing purposes, I need to send it a digital audio feed of select
music tracks that might still be 16-bit deep (albeit not exahusting
the dynamic range of the device), but can't of course be 44.1 kHz in
sampling rate.

Since these tests must be repeatable, if needs be by different
workgroups in different places, the sample rate conversion process has
been decided to happen at non-realtime, not hardware-based, but with a
once-for-all software-made process. This resulted in converting audio
files originally in 44.1 kHz sampling rate to 48 kHz, which is
considered acceptable as far as quality matters for our purposes,
while it proved reasonably reliable with the vast majority of existing
AES/EBU or DMX 110 Ohm commercial cables over long runs (while 96 kHz
obviously showed more failures over high distance transfers without
specific ancillary devices).

That's the background story on why I got to use Saracon in the end,
and from a sonic perspective I don't regret any of it, it simply
proved itself to be the most reliable SRC software tool we could find
and try.
From a "librarian" perspective, though, it's a considerable waste of
time having to manually re-type all the metadata content for each and
every audio CD that I plan to use in our project, as the Saracon
sample rate conversion process wipes off any existing metadata from of
the files we throw at it.

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).

Would someone be of help to us, please?
Wholehearted thanks in advance.

Sal

Uli Franke

unread,
Feb 28, 2012, 5:14:51 AM2/28/12
to saraco...@googlegroups.com, Sallustio Pinzauti, Daniel Weiss
Hi Sallustio

<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

Uli Franke

unread,
Feb 29, 2012, 11:20:15 AM2/29/12
to saraco...@googlegroups.com, Sallustio Pinzauti, Daniel Weiss
> thank you for such a fast reply!
> I was sure to have answered your message yesterday night, but not seeing any such thing in my Sent mailbox makes me wonder what went wrong. I'll write you again, if you receive both messages just toss whichever one.
>
> I'm running Saracon 1.61.27 Standard License on Mac OS X 10.7.3.
> The files I'm processing are normally .flac, although depending on what application is generating them, it might be also .aiff.
>
> When in a hurry and unable to retain the original metadata under Saracon, I've used Foobar2000 to generate .flac files, although this requires maintaining a Windows installation into Parallels Desktop, something I'd be happy to get rid of soon.
> That's why, ff Saracon could retain the original metadata, I would try to run the entire process natively under Mac OS, namely with C7 Software's PhileAudio, or Simon Booth's Max, to obtain CD content and tag it before Saracon does its SRC magic.
>
> Be it .aiff or .flac the source files, one thing is sure: output must alway be .flac.

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."

Sallustio Pinzauti

unread,
Feb 29, 2012, 2:55:44 PM2/29/12
to Weiss Engineering Saracon Users
>  email: uli.fra...@weiss.ch web:http://www.weiss.ch
>
>  "To define recursion we first have to define recursion."
>  "What you boot is what you get."

Hi Uli

Let's make it as easy as possible:
· restrict source files to .FLAC ONLY, FORGET ABOUT AIFF!
· can't say if tags are VORBIS, sorry, it's what PhileAudio/Max/
Foobar2000 tag them with by default.
· single albums are: %artist%_%date%-%album%-%track%.%title%-[%composer
%].flac
· double album are %artist%_%date%-%album%-%disc%.%track%.%title%-
[%composer%].flac
· waited so long until now, can wait.

Thank you,

Sallustio

Uli Franke

unread,
Feb 29, 2012, 3:14:41 PM2/29/12
to saraco...@googlegroups.com, Sallustio Pinzauti

Hi Sallustio

> � 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

Reply all
Reply to author
Forward
0 new messages