Bret Williams
Forum Replies Created
-
Could you not adjust the gamma, making most the tones live in the darker range? We do the opposite for dark pc monitors, making more of the tones live in the brighter range.
Your blacks and whites remain normal, but everything inbetween gets skewed one way or the other when playing with the gamma.
-
48.8 is KB a sec (kilobytes). It actually equates to 5 or 7K for some reason.
Anyway, your 32kb is kilobits per sec, which is resulting in 1.9 kiloBYTES a sec. So, you can actually triple or quadruple that to fit in a 48.8 modem connection.
Which just happens to be close to the standard iTunes 128kbps for stereo. If you make it mono, 64kbps is fine. If you don’t mind it sounding compressed, 32 will work for mono as well.
-
Clicking is a death sentence. Start backinug up immediately. I don’t know about REV drives, but your other drive’s time can probably be counted in days or minutes. Your procedure has been done by many of us. Clicking, dies, disk warrior, fixes, later more clicking, dead.
-
Is this your scenario? You have recorded bars with a camera. Probably a camera that lets you boost the IRE to 7.5 on DVCam (which is incorrect thing to do 99% of the time). You play back that tape in a deck that doesn’t let you boost analog output to 7.5 ire as it should (such as the DSR-11) so the bars recorded by the camera in this case come out correct. FCP’s bars out of the same deck show up as low, because the deck doesn’t allow you to boost the analog output of black to 7.5 ire.
In the above scenario, FCP is operating correctly, the deck is not, and the camera is set incorrectly. The tapes recorded from FCP would be correct, unless they came from the camera that was incorrect of course.
All digital should be 0ire. No setup. DV decks should be adding setup on their analog outputs. However, many don’t. Their output to a waveform/vectorscope is incorrect.
-
How exactly would LTC exist on a digital file? That’s timecode included on a part of an analog portion of a video tape. VITC is included in part of the video signal. I think TC on a media file is essentially neither. It’s just a part of the QT file or metadata or something like that.
-
You might want to also try using the zoom tool. Press z, then draw a square around the area to zoom on. Faster than cmd+/- and you don’t have to remove your hand from the mouse. I tend to use whatever feels appropriate at the time.
-
There’s no way to change the behavior. But when you have inadvertently zoomed in on the wrong item, just press the right or left arrow to move the playhead one frame. It will jump the view to that point, which is the point you wanted in the first place. You can also combine it with cmd+d like you’re doing. BTW – before version 4.5 cmd+d was actually mapped to “deselect all.” I have absolutely no clue as to why it was removed. They added Shift+cmd+a to deselect all, which matches other software, but they removed cmd+d and didn’t map anything else to it by default. So after 5 years of FCP I had to start remapping the keyboard. Argh.
Pressing deselect all before you do lots of things is a good idea in FCP. Other editing functions operate differently if you have items selected. For example, if you mark an in/out and do a ripple delete with something selected, the selected item overrides your mark in/out! You might even think nothing happened only to discover later a piece of your timeline is gone!
-
Oh my gosh, with h.264 (or even Sorenson 3) the file could be wonderful at 1/8th that data rate. 320×250, 15fps, 500kbps. No wait to download either if it was simply on a web page too. Click and play or right click to download.
-
Just click on “more widgets” in the manage widgets panel. That takes you to apples widgets page. Just do a quick search for it. I think they have a pro version that gives quite a bit more detail as well. iStat pro or istat nano. Adding one drive to my system didn’t change a thing.
-
I’d be curious as to what your istat nano specs are reading. It’s a dashboard widget that tells temps internally and fan rpms.
For example, right now surfing the web with 2 internal drives doing next ot nothing on a Mac Pro, one cpu is at 75