Dan Montgomery
Forum Replies Created
-
If you’re doing it in house, and the MXFs will be accessible on disk, you can use a product like HDLog to do this.
HDLog was the first Mac P2 viewer. It imports the P2 virtual cards into a template of your choosing. So, for your example, simply add a “Transcription” field to your P2 template and type away. There’s also a handy “Jump Back” button (and keystroke) to allow going back a few frames and playing from that point…it’s meant for those of use whose hands can’t keep up with realtime conversations.
Use “SAVE AS…ALIAS” to save the log file and text with just small pointers to the MXFs. This saves disk space by not converting the large full resolution QT files.
Once all the clips have been logged and transcribed, use the “Multi-File Search” function under the Clips menu to search for clips of interest. Drag and drop into an output list and export to FCP, etc, etc.
To setup, start with the “Panasonic P2” template which has all the matching fields to the camera. Click Edit View. Remove fields you don’t use/need, and add the Transcription field. In the field properties you can limit the text entry in a field if desired, otherwise leave it as “0” and you may type unlimited text.
Hope this helps. Try out the demo: https://www.imagineproducts.com/hdlog.htm
Video logging is just the beginning…
-
Jerry,
Have you been able to resolve this issue?
You might try converting the clips with a program like P2Log Pro or Raylight. This would give you FCP XML’s with associated QT files that you open directly, avoiding the tempramental “Log and Transfer” window.
https://www.imagineproducts.com/P2log.htm
Video logging is just the beginning…
-
FYI: P2Log Pro can often import and convert clips to QT that FCP won’t. https://www.imagineproducts.com/P2log.htm
There’s also a “Repair Tool” to rebuild Contents folders should something go awry.
Video logging is just the beginning…
-
From what we’ve seen, the problem is related to the card being totally full and the Mac trying to write those resource forks to it…and/or…perform the Spotlight indexing.
In any case, the corrupted files I’ve personally examined were only damaged at the end of the file. In other words, it appears to have been ‘pushed’.
We’ve had some success in importing these files into our software, converting to QT files, and trimming the ends of the files a few frames to get back pristine files.
I think this corruption is different from the random pixelated frames you’re talking about. In other words, there are likely two phenomena going on.
Dan http://www.imagineproducts.com
-
When you say “come over”, are you trying to use Drag & Drop in the Finder?
Try an offload product like P2 Genie or HD Log (www.imagineproducts.com). These will sense the P2 Store and copy the files for you automatically. I’d be interested in seeing how the HD Log demo performs for you (or if there’s a hardware failure lurking?)
Dan
-
Try the P2 repair wizard in Mac applications P2Log Pro, HD Log. Or Windows application TEP HD. These can rebuild entire P2 Volumes from a single MXF or multiple MXF files.
We’ve also had some luck in rescuing corrupt files by converting them to QT and trimming the end. This is effective if the MXF was damaged due to inserting a P2 Card in a Mac without first locking it.
If the file is truly corrupt due to HHD/or card formatting issues, there’s a possibility it can be rescued by law enforcement type forensic tools which we have access to. Please give us a call or email. http://www.imagineproducts.com
-
Barry,
Mystery solved…
The problem is the DV100 stream doesn’t support AVC commands back to the camera. FCP (and HD Log) are designed to get the timecode from the device, instead of the embedded timecode in the video frames.
Genernally only consumer devices don’t accept AVC protocol for the timecode acquisition.
We may choose to implement this to allow customers a way to digitize HD from the camera into HDLog with timecode since FCP doesn’t support it. I’m guessing they may elect not to support this mode either since it’s a bit non-standard.
-
I said “apparently” Barry, because we couldn’t get it setup and other customers reported no TC recording via FireWire into FCP.
Could you explain exact camera settings for this novice (I’m not a shooter, remember?), how to get TC on the FireWire output?
I’d like to see whether HD Log can record it, since the logger can digitize. Doing so in HD Log would mean having the TC, HD clips directly in QT, and automatically indexed clips with metadata.
Video logging is just the beginning…
-
Paul,
Last week we added a few more features including:
-P2 Sub Clipping
-SD card metadata editingThe delay in adding subclips was the lack of a standard within the P2 format itself for storing sub clips. We weren’t crazy about adding something that’s “non-standard”, but as long as it doesn’t affect other apps reading the modified P2 files it is fine.
By Sub Clipping I mean the ability now to select alternative TCs within a given clip. OR, you can create a new clip that’s linked to a playing P2 file. In other words, you can make multiple clips from within a single recorded one.
If you SAVE the P2 volume within HDLog, it will modify the original. If you SAVE AS, you can save the HDLog file and all the attached clips will be converted to QT files. If you EXPORT just selected clips to FCP XML for example, it will only output those clips (and make the short QTs of subclips that you’re looking for).
—
SD Card editing gives you a way to pre-load the SD card with metadata such as Project, Reel, etc. I believe you can also add clip naming conventions this way as well, so when you shoot the P2 cards come out with desirable metadata.
Video logging is just the beginning…
-
Rick,
I can answer the last part of the question…there isn’t a FireWire to BNC adaptor on the market. This was something Imagine Products was considering a few years ago but couldn’t drum up any interest. That’s mostly because if you have a DV signal you normally can just connect it to the computer to extract the TC.
Decoding DV isn’t a small task. A FireWire timecode reader would pretty much require a full blown mini-computer which ultimately is cost prohibitive.
It may be a mute point, since the FireWire connection the the HVX appears not to pass timecode….
Video logging is just the beginning…