George Strother
Forum Replies Created
-
“Do you have the latest Quicktime player installed?” I do now. QT Pro 7.7.3
Apple update asked to be updated a couple weeks ago. I foolishly clicked update.
Lots of earlier versions available on Old Apps or Avid’s forum.
Is there a tutorial on backdating QT on Win 7?
I’ve done it years ago on a Mac. There were lots of hidden files that had to be removed
George
Light Images -
Customizing the EX 60i template and changing the Field Order to “Progressive” lets Vegas render to about 17% of the the 1h 24m movie.
Then the progress bar stops, approximate time left counts down to zero and the elapsed time keeps counting.
Clicking cancel has no effect, clicking the red X close gadget brings up a screen with “A background process is currently in progress”. Clicking Yes does not end the process.
I have to go to Task Master and use End Task. I can’t stop the render or close Vegas any other way.
Several non-EX templates, modified to equally large file size, work on the same project.
Ideas?
(btw – I’ve been using Final Cut Pro since v1.0, so I’m all thumbs with Vegas so far)
George
Light Images -
—-Video Format——
Frame Rate 60/30
REC – HDV-SD60PHDV – SD60p is a wide screen SD format, not an HD format. For HDV you can choose 720p30 or 720p24. Those are the only HD choices on an HD110U.
George
Light Images -
Walter
It’s probably not your long cable runs. Apple has already replaced the 4870 card in new MacPro 8core, then replaced the whole Mac for the same problem.
I’m connected by DVI-D to a Dell 30″. The same monitor and cable work fine with my retired G5 and 3 yr old HP.
Changing the 4870 card had no effect and the replacement MacPro blinks less often but snows much more than the first MacPro.
Connecting the MacPro (first or replacement) to my JVC 20″ LCD production monitor by DVI-D shows the same blinking and snow problems in spite of it’s lower resolution.
Here is a thread about the problem in the Apple support forum – https://discussions.apple.com/thread.jspa?threadID=1947029&start=0&tstart=0
No real answers in the thread, but at least you know you are not alone.
The consensus seems to be firmware and drivers that are not compatible with legacy or third party monitors.
George
Light Images -
Wanted to mark the subject line, for those who might want to know.
George
Light Images -
Seems to work fine.
I talked to support @ AJA and they confirmed that all of the SDI and HDMI ports on the box are just pass throughs.
3GB might need higher grade cables between the box and the card, but the internal jumpers are probably too short to be trouble. If they seem to causing a loss, the high grade 3G cables could be plugged directly into the card. And you would need to bend down and plug HDMI cables into the card directly.
Support didn’t know if the Control Panel would identify the box correctly, but said it’s all the same pin-outs, so it shouldn’t hurt anything to try.
Control Panel does still identify the system as LHi and appears to have full control.
Of course I don’t have the real box to compare, so something might be missing, but all screens in the manual show up in control panel.
I will report back if the fire department has to visit.
George
Light Images -
Maybe not so very different. I have both cards, with both snakes and The Box KL on the floor right now.
LH card has 1 multi pin connector and 3 SDI, 1 in, 2 out.
LHi card has the same multi pin and 2 SDI, 1 in, 1 out.The snakes are identical. Not only do they look identical, they have the same part number.
With 2 SDI cables to the Box, 1 SDI out would not be active. Since there is only 1 SDI out at the card, this is no loss.
Hmm. Since the snakes have the same part numbers, then the cards must have the same pin-outs on the multi plug.
The box has no external power connection and appears to be a straight through patch bay. (So far, too lazy to open it and look.)
Not being quite brave (dumb?) enough to just plug it in and see if smoke comes out, I thought I would see if someone has actually tried this yet.
George
Light Images -
Viewer and canvas do change the v-scope vector targets to HD/709 colorspace.
The “live waveform monitor and vectorscope” come up in Log and Capture and they do not follow the timeline settings or the capture format. They stay in NTSC, possibly converting the HD colorspace to NTSC colorspace to match the vector targets.
I’m asking if there is a way to change the setting of the “live … vectorscope” colorspace settings used in Log and Capture to HD/709.
George
Light Images -
Ive tested the JVC 20″ production LCD with component and HD-SDI. There is quite a bit of difference between the two connections.
But I will be recording to SxS cards and even real 1902x1080p does not come off of the cards as sharp as the HD-SDI signal. HD-SDI monitoring might be setting expectations higher than I could deliver without dragging around a Mac and a raid.
Ultimately I chose the component version of the monitor which seemed to match what came back off of the SxS cards.
George
Light Images -
It’s the client’s red that I have already toned down more than they want, but at least it’s in the bottom of the red box instead of off the scope like the PMS color. Maybe I can talk them into a nice pale yellow or blue, possibly beige?
I’ve tried the Photoshop alpha method without improvement.
My current focus is why renders come out worse now than a month ago. The red and the font haven’t changed, so something in my system probably has.
George
Light Images