|
Forum List
>
Café LA
>
Topic
New Free Utility: Renames Media Files Same Name as ClipsPosted by Kevin Monahan
Hey Folks,
Since the SF Cutters List-Serve is not online for non-subscribers, you may be missing cool info and freebies that are posted regularly. Sign up for our list here: www.sfcutters.org/pages/list.htm Our latest freebie is a utility to rename media files associated with FCP clips. Pretty cool, so read the warnings and then check it out if you like. Might be just what you are looking for. Cheers.
Kevin Monahan Social Support Lead, DV Products Adobe Adobe After Effects Adobe Premiere Pro Adobe After Effects and Premiere Pro Community Blog Follow Me on Twitter!
Thanks. I'll let Robert know.
Kevin Monahan Social Support Lead, DV Products Adobe Adobe After Effects Adobe Premiere Pro Adobe After Effects and Premiere Pro Community Blog Follow Me on Twitter!
i just downloaded it, but Robert must be tweaking it.
i got this message when i tried to use it: "This alpha has expired. please contact etc, etc... for an updated version" FWIW you can do this all within FCP, using the Media Manager use MOVE mode, DONT delete unused Base media file names on: CLIP NAMES BROWSE to your existing capture scratch, i used to have some problems with it, but it seems to be working in 5.04 however, you need to only do one drives worth of clips at a time. if the new app works it could be an improvement. nick
I'll try to field problems as they come:
Tom: Are you choosing an XML export from a Final Cut 5 project? I haven't tested it with exports from older ones. If you give me a detailed description of what you've tried, I can probably figure out what's going on. Nick: This version is set to expire July 1st. Is the date on your computer set wrong by any chance? If the month were set to July or later (regardless of the year) you'd get that message, otherwise it's quite odd... Please post bugs with details, or I can't fix them... Thanks, Robert Arnold
rda wrote:
> Please post bugs with details, or I can't fix them... Hi Arnold, Great idea. I tried the app with a project XML and it took about three or four hours to tell me the same thing Nick got. Maybe the date settings from your location, Nick's and mine don't match. A US date of 07.01.2006 won't match a german 01.07.2006, if you compare the date strings. I don't know how you do parse the XMLs, but even a big one shouldn't take more then 30 minutes (for the above mentioned huge one), even if you compare and modify node entries. I tried that XML with an app of mine, that read the complete XML, indexed each node, converted all frame entries into different absolute and relative timecodes, calculated durations, retrieved all entries for clips, subclips, markers, filters and filter groups and verified each source file for online/offline. So maybe you could try another parser, or some more effective use of the XPath options your parser uses. Let me know if I can help. Regards Andreas Some workflow tools for FCP [www.spherico.com] TitleExchange -- juggle titles within FCS, FCPX and many other apps. [www.spherico.com]
Ah, I built it to work with exports of entire projects, so it's expecting to drill down through at least one bin in the xml. I'll rewrite so it can handle what you tried, but in the meantime, throw those clips in a bin in a new project, export, and give that a try.
- Robert Tom Wolsky wrote: > I selected a groups of clips and subclips in the browser, > exported to XML2 from FCP5.1.1. >
> Great idea.
> I tried the app with a project XML and it took about three or > four hours to tell me the same thing Nick got. > Maybe the date settings from your location, Nick's and mine > don't match. A US date of 07.01.2006 won't match a german > 01.07.2006, if you compare the date strings. Yes, that's exactly the problem with the expiration function. At any rate, I'm doing a major rewrite of the whole thing. It was working fine for the little XML files I was testing on, but now I've found a much better parser engine that can handle bigger (and more varied) XML files, so I'm revamping. Just leave it alone until I post a new, vastly better version. Thanks, - Robert Post Edited (06-17-06 01:13)
rda wrote:
> At any rate, I'm doing a major rewrite of the whole thing. It > was working fine for the little XML files I was testing on, but > now I've found a much better parser engine that can handle > bigger (and more varied) XML files, so I'm revamping. Just > leave it alone until I post a new, vastly better version. Have a look at the XPath stuff first and the tutorials for that on the web, a good XPath handling can dramatically simplify something like your app. Regards Andreas
Sorry, only registered users may post in this forum.
|
|