William Carr
Forum Replies Created
-
Maybe not exactly what you’re looking for, but it’s only 20 bucks!
https://www.digital-heaven.co.uk/fcplugins/dh_box.php
-
If you’re talking “fast” consider for a moment the learning curve.
Recently I had to crank out a simple site, and in lieu of learning the intensive Dreamweaver or eaking something non-consumery out of a cheap Mac-based website creation app, I bought a template.
Customizing its code elements was not difficult, by following simple embedded instructions. It was easier for me to hard-code some HTML than master a serious web creation app… although when I have time I would love to.There are also free templates out there; most are ugly but some gems can be found.
Below is a site for cheap templates that are perfectly functional, some are even un-ugly! You need no special coding experience nor flash tools, just a simple text or HTML editor like Taco. You can substitute Quicktimes or WMV clips where “gallery” JPEGS are situated, as per available instructions, some already have a spot for videos. See “cool” and “photographer/artist”.
https://allwebcodesign.com/setup/templates.htm
-
For me and our MBPro, a card reader worked, but barely- so slow it choked the system when the Log and Transfer window was open. Forget trying to scroll down to the 57th shot, there’s the beachball and maybe a crash.
I treat AVCHD card data like P2 data, meaning I copy to an external hard drive first then use FCP to take it from there. After I know the footage is in the project and its raw file backed up, then we reformat the card in the camera before the next shoot.
-
Just when you thought the thread was over…!
Yes, it should work, especially with straight DV, but maybe you should tell your client to pick up an express card firewire bus, they’re only 90 bucks.
When I think of transferring footage on location many miles from the nearest Radio Shack, I like to know there’s a back-up plan! And for HDV’s processor-intensive demands, it could make work go faster. -
Only with the latest Perian component for Quicktime am I able to transfer to our MBPro Panasonic AVCHD from our SD9.
-
Should work OK, but best to test real-world performance with the camera and drive you will have out in the field. I believe there’s just one firewire bus in the MBPro even though you have a 400 and 800 port.
Will you ever be laptop editing again? If so, an eSata solution would be great on location. I use a firewire 800 expresscard to get an additional bus for laptop editing, that way I can use a camera plus a RAID or two RAID drives without slowing anything down. If I could afford it right now I’d have eSATA drives instead.
-
Via software and conversions this will be a very, very processor intensive operation every time.
If you’re going to be archiving to tape all that you shoot on AVCHD consider a hardware solution, some way to get your HDMI-C out to your HD SDI in– that way at least it’s a real time transfer camera to camera without tying up a workstation.
-
Certainly Jeff is right about this, plus, QT itself won’t do batch exports and even just two clips at a time is a batch.
But if for whatever reason I’m using standalone QT Pro for exporting to a carefully figured-out setting, I find that even after quitting QT Pro it will next launch with my previous customized settings intact as long as I’m selecting the same format. This is especially helpful on the non-FCS Mac I use in my office.
-
I’ve done many DVCPROHD 720 and 1080 projects using MacBook Pro with 1TB and 1.5TB G-Raids via firewire 800. Drives perform well and prices are nicely coming down during the incremental market march to eSata, and eventually a next firewire speed.
Meanwhile, also consider a 2nd firewire cardbus if you want to use two G-Raids at once for lots of resource media and scratch space at your disposal.
Performance with intense graphics is also dependent on your Mac, for one thing if you’re G5 or Intel. My MacBook Pro way outperformed my G5 dual 2.5, even though on the laptop I use G-Raids and the G5 had a full-blown level 5 fiber-channel raid.
-
Two thoughts:
1- Perhaps the audio tracks you imported were not optimal for Final Cut, which likes 48khz aiff. Other rates may play on the timeline, but not always behave properly. Using Quicktime Pro you can make 48khz versions of your audio files with the same filenames, then reimport and relink.
2- When you edit, adjust and filter your audio tracks on a sequence, you’re likely rendering or autorendering for playback. These renders are site-specific, meaning they’re referred to when you play that particular spot on the sequence. So if you move something rendered, you may still be hearing bits of what was there before, or perhaps a weird conglomeration of past and present.
So, delete your previous audio renders with Tools>Render Manager, etc., then force a new total timeline render with Sequence>Render Only>Mixdown.Good luck…