David Gallessich
Forum Replies Created
-
Bala –
From the docs, it looks like leaving a battery in the camera is OK.
Myself, I plan to use an uninterruptible-power-supply, so a battery should not add any security.
This is from the v1.15 instructions (EX3)-Notes on performing upgrade
• If you are using a Windows computer, you must have
the standard device driver supplied with Windows.
• If the computer’s OS is Windows Vista or Windows 7,
then you must have administrator privileges.
• If the computer’s OS is Windows XP, then the
Microsoft .NET Framework runtime is required.
• Only connect one PMW-EX1/EX3 camcorder to the
computer for upgrade.
• Use the BC-U1/U2 Battery Charger to connect the
PMW-EX1/EX3 to an AC power source. You can
mount the battery pack at the same time to prevent
problems in case the AC power source is interrupted.
• If you interrupt the upgrade process, you must start over
from the beginning. You cannot interrupt the process
after installing some of the modules, and then resume
the process where you left off. -
Daniel – I would check Ian’s response in this thread:
https://forums.creativecow.net/readpost/142/876092
And in your case, I would probably call that phone number in my post.
(When phone menu starts getting specific, select menu item 4.)
In my case, the wait-time was reasonable and the tech was pretty helpful.
They may know what you should do if you already installed 1.26 using a bad installer. -
Ian – that was fast! Thanks.
So meanwhile… do you agree w/ phone support (proceed to EX3 v1.15),
or should I stick with SxS and/or Class6-SDHC until I hear more?
dg
-
Craig -Thanks!
I should have clarified:
The problem was evident on the SDHC but I hadn’t noticed. Clip length was not right.
The copy process inside the EX3 (SxS to SDHC) produced the error.
It wasn’t operator-induced as far as I can tell (I didnt remove the sleeve too soon)If you didn’t use ClipBrowser with CRC On, that was your mistake. CRC confirms the bits on the copy match the bits on the source.
I don’t have a reader for SxS, and I don’t connect USB to camera. So my workflow involves recording to SDHC then use SDHC reader to copy BPAV to the Mac. Or I record to SxS, then copy in-camera to SDHC, then to computer as above.
I guess I should take your advice on using clip browser to copy — but I don’t believe this would have mattered in the above situation. -
Recent near-miss:
1. Recorded to SxS.
2. Copied clips from SxS to SDHC+hoodman (Copy from slot A -> B inside my EX3).
3. Copied BPAV from SDHC to MAC.
One of the clips was clearly too short (several minutes missing!) and couldn’t be transferred in Log&Transfer.
OK – We’re in full-blown panic mode now.
Went back, deleted clips on the SDHC, re-did steps 2,3 — and this time the clip was fine.My takeaway:
A. Always xfer to .mov and review BEFORE clearing the camera media.
B. Seems possible the sdhc card has issues.
C. Maybe I also need to go ahead and do that firmware upgrade
(mine were manufactured approx May 2009). -
Michael – thanks much.
My main concern is for what i’m exporting to broadcast & dvd.
It was a bit of a shocker to see what I saw (see first post).
—If you transcode to H264 either as export quicktime movie or quicktime conversion, it basically just uses quicktime pro to do the conversion. Compressor should yield better results.
Actually FCP appears to be calling Compressor not QTpro when it does EXPORT->QT-conversion.
Maybe I’m wrong, but the dialogue window says “Compressor Settings” and appears identical to the Compressor dialogue.
—-
FYI
I’ve gone back and used SEND-to-compressor, with compressor at
same settings as the (B) picture (High), and with the frame controls as you said. The filesize on the left is about 8Mb, compared with about 6 on the right.I think the smaller filesize (QT conversion, on right) looks slightly more crisp, while the left is a bit more saturated (and a bit warmer).
In the end, this time, I went with Compressor.
-
Jeff –
Excellent point.Seems pretty silly since it’s a fairly robust machine with 8Gb (most of which is dedicated to Premiere)- but the PC lives a dual life as a home office machine,so there is bound to be some amount of windows-rot and other burdens on the CPU (Vista OS).
I haven’t even begun to look at that situation in any depth.
My friend would prefer to try and make hardware adjustments, rather than mess too much with his installed software.I think the best answer for him might be to create a new, cleaner boot disc for editing.
dg
“The real question would be what is causing sluggishness when editing DV? Pretty much any computer can edit DV with ease – there shouldn’t be a need to reduce resolution when editing standard definition footage”
-
Wow – that was fast.
Throughput on this COW machine is awesome!
Thanks. -
to David Ruf –
I’m out of town travelling at the moment –
not seeing my email regularly until Nov 20.
You may contact me via dg(at)basinvideo.com
Yes I have footage of Wam but it is on very old betaSP tape.
dg -
What Don said! Max Reid got it just right.
When you get into a bit of lens-flare situation, better make sure it’s very clean. Huge depth of field.It seems a bargain to me, esp when you consider that the “zoom-through” focus on this converter is far superior to the similarly-priced “adapters.”
If possible, try it out — you should see for yourself.
It does increase the camera weight quite a bit.