AATON Cantar metadatas

[Dorian]

Hi folks,

I can see some of the Cantar metadatas are not handled by Soundminer
v4Pro, like "Channel Names", "Circled", etc. Pro Tools does support
them, though (at least v8 i'm using here).

Do you plan to integrate them in a future SM release? That would be
great for dialog editing, IMHO.

Bye.

PS: i can provide a Cantar rushe audio file, if needed.

[stevep]

Dorian

Did you try to make a DIALOG database in Soundminer? (the kind of DB
you create has an ffect on the fields and metadata it looks for.

This will create special iXML fields and that info should come in. If
it doesn't please post an example for us to try.

Steve

[Dorian]

You're right, i can see a "ixmlTrackLayout" field which corresponds to
the "Channel Names" in Pro Tools (and Majax).

Thanks for the hint.

Bye.

[Dorian]

Someone on our website said that importing Cantar sound files in SM
just "destroyed" them, and that they can't be used anymore with the
AATON utility Majax. Apparently, SM would "touch" them in a slight
way, so that the filesize is not the same anymore (Majax would say
"size mismatch" or something similar).
Any hint about this issue?

Bye.

[stevep]

Don't honestly know since we don't have those utilities but if you
embed v4 data it will change the file size by a very slight amount to
account for our data chunk. Otherwise it is untouched. If the
tolerance level in the utility doesn't allow for this, I don't know
what we could do.

s.

[pugnax]

I´ve doene this a lot of times when editing dialogue without any
issues. I dropped the Cantar-Files into a fresh SM DB and juat worked
away. No issues whatsoever.

As long as you don´t re-embed back to files I see no reasons why SM
would "destroy" the files.

I know that Majax only works with original Catar-FIles because they
hide some secret data in the BWAVs and don´t want Majax to end up as a
helper for Deva-Owners.

Frank.

Steve: Majax is a free download at aaton.com but will ONLY work with
BWAVs from the cantar. So I´m not sure if it will help to find the
error. Since aaton uses some secret info to restrict the usage I
doubt, that they will undisclose the trick that will make BWAVs
readable for Majax.

[Jeremiah Moore]

BTW - in addition to embedding metadata, building overviews also
writes to the files.

-j

--
-----------------------------------------------------------
jeremiah moore | SOUND | jmo...@northstation.net
http://www.jeremiahmoore.com/
http://babyjane.com/timeweb/

[Dorian]

Thanks for the inputs guys, i'll pass the info.
I think the overview is the culprit here...

Bye.

[Jeremiah Moore]

a solution - (with my er software developer kibbutz hat on!)

If it's a big enough issue for enough users, one solution would be for
the app to optionally cache waveforms in the database instead of
writing them to files as metadata.

-jeremiah

[Dorian]

I totaly agree with you Jeremiah. Nothing should be touched until you
decided it, IMHO.
But the Pro Tools's Workspace seems to act differently also.

Bye.