Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer Avid Log Exchange file character limit

  • Avid Log Exchange file character limit

    Posted by Matt Bacon on August 31, 2010 at 7:56 pm

    Hello,

    We use Medialog to create ALE files and import these ALE files into Media Composer for editing. We often capture tape rushes and apply ALE’s to existing master clips, but we have also captured directly from ALE master clips after import.

    In either case, our clip names appear to be limited to 63 characters. Medialog (and Media Composer) does not truncate clip names when the ALE is exported, but the clip names are cutoff when imported into Media Composer 3.0.

    The Avid Help file claims that clip names for ALEs are limited to 32 characters; because we have already proven that clip names can be almost double this length, we are hoping to find a work around allowing us to have clip names of any length, still using the ALE workflow.

    Thank you for your time and energy,

    Matt Bacon

    HP Intel Xeon @ 2.6 GHz, 3.0 GB of RAM, Avid Media Composer 3.0, operating in a Unity Environment

    Matt Bacon replied 15 years, 8 months ago 2 Members · 4 Replies
  • 4 Replies
  • Michael Phillips

    August 31, 2010 at 8:41 pm

    Your workaround is not use ALE? Why not just open the bin you created from MediaLog in your MC project? – I question the export/import of ALE in this workflow.

    Michael

    Michael Phillips

  • Matt Bacon

    September 1, 2010 at 6:13 pm

    Hey Michael, thanks for the response.

    We have adopted the import/export of ALEs because we have a problem transferring bins from MediaLog. Our media loggers create unique MediaLog projects on systems which are not part of our Unity environment, when bins from these MediaLog projects are placed inside projects within the Unity environment, and then used to capture clips, media is created on the Unity server with a project association to the original MediaLog project, not the project which exists on the Unity server. Importing ALEs ensures that media captured in a given project is associated with that project.

    An alternate solution for this problem is to create new tape names once bins have been placed in a Unity project (since project association is derived from tape name metadata) but the ALE method proved less work for our assistants.

    The character limit is the only chink. I suppose we could force our loggers to be more concise, but an alternate solution would be amazing.

    Thanks again,

  • Michael Phillips

    September 1, 2010 at 7:02 pm

    Ah… After I hit send I wondered if there was a Unity thing involved and how you wanted to not only tracks sources but the project in which they are associated…

    Have you considered starting the project on your main systems, then propagating that to all your MediaLog systems to then use that as the starting point?

    I’ll look into the Tape length issue. I have done up to 32 characters with underscores and such when working with file based cameras like the SI2K, and certainly 16 characters when working with RED.

    Let me see what I can find out.

    Michael

    Michael Phillips

  • Matt Bacon

    September 1, 2010 at 7:54 pm

    I had not considered creating the projects on the Unity and then transferring them, great idea Michael.

    Any other insights you have will be greatly appreciated.

    The Internet is the best–er–the helpful and knowledgeable crew at Creativecow is the best.

    -Matt

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy