Paulo Jan
2
COW Coins
Forum Replies Created
-
Well, it wasn’t so much “bad clips” as clips from a previous shooting that nobody had bothered to delete, so they would have been duplicated. And yeah, disk space is cheap… but it adds up (specially because it isn’t the first time people don’t bother formatting a card before starting to shoot). The error, of course, was in trying to delete them in-camera, instead of on the computer, once they were safely copied.
As for the cards, I called two different companies, and they both told me that the only hope was to send it to Panasonic’s factory, either in Germany or Japan, where they have special equipment originally developed to save footage from defective cards, that it could take up to six months, and that there were no guarantees. I did try on my own with Data Rescue too, but all it could save were two thumbnails from two clips.
So, moral of the story? Go back to Umatic tapes, guys; this whole non-linear, “tapeless workflow” thing is a scam… 🙂
-
Yeah, I’m also surprised at the amount of people reporting problems with the Duel. There was a time (back when I was first researching this stuff, 3 years ago) when it was recommended as the best solution for MacbookPros with ExpressCard…
I don’t use mine very frequently; I have perhaps one shoot every 3 months where I have to use it, and I’ve never had any problems. As for Snow Leopard, my understanding was that Apple had ripped all support for PCMCIA in the OS, which made it impossible for them to write drivers for it. If lack of support on Macs is the biggest problem, I guess I can live with it
-
Well, I already have one DuelAdapter (for my personal use, not for my employer), and it works quite well with my Macbook Pro (on Leopard). I’ve never had any problems with it (though I haven’t used it intensively either), and this is why I was thinking of one for the new laptop.
-
Do they still make those?
(The laptop will be used primarily for other stuff, for which we’d prefer to get a new laptop, not an old second-hand one with PCMCIA, if that’s what you mean).
Paulo.
-
When Apple decided to switch to Intel years ago, people blamed Adobe and other third-party software houses for not having Intel versions of their software right out of the gate.
Now Adobe decides to switch to 64-bit only, and people are blaming Adobe, instead of third-party plugin vendors.
I’d say that what Adobe needs is a reality distortion field.
-
There’s a tutorial by Eran Stern here on the COW, called “Crime and Chaos”. Have a look and tell us if that’s the effect you’re looking for.
-
Well, yeah, but if you don’t deinterlace properly you risk losing half of your resolution (just as an example, FCP’s own deinterlace filter will do that). As for computers, any decent software DVD player should do its own deinterlacing on-the-fly (though of course, there are plenty of “indecent” software players out there…).
-
Since 480×320 isn’t a standard resolution, you’ll have to crop it while exporting. Compressor has the option to add a crop filter while exporting, but you might find it easier to use MPEG Streamclip. Just feed it the original Quicktime, select your resolution and select the “crop” option, and decide how much you’re going to crop from the sides.
How much to crop? Well, let’s see: the HVX-200 footage is 16:9 or 1.777, while 480×320 is 1.5. Therefore, a movie with 320px height and 16:9 aspect ratio should have 568px of width. You want 480px of width instead, so… well, now you know how much you should crop.
-
Premiere did reconform the audio files again after deleting the folder in question, but no, the audio tracks in question weren’t fixed.
However, I’ve managed now to solve it in another way, as per this thread in Adobe’s forums:
https://forums.adobe.com/message/1951787
Basically, I selected each of the “silent” audio tracks, did a match frame on it… and that was it. I didn’t even have to add the track again to the timeline. Simply doing a match frame seems enough for Premiere to “find” the audio. I’ve now closed and opened the program again, and… it still works (!).
I have another possible bug, relating to getting video out of the FW port in DV-sequences-with-non-DV-footage, but I’ll post it in another thread later if I can’t solve it on my own.
(BTW, if you believe the thread mentioned above, the bug is *still* in CS4…).
-
Nope, didn’t work. The audio is audible when you load the clips into the source window; the problem happens only in the timeline.