Sean Oneil
Forum Replies Created
-
[Shane Ross] “No computers that I know of have a direct HMDI output. That is not a computer connection, but rather one from DVD players and digital receivers to HDTV sets”
Lot’s of newer computers (PCs not Macs) have HDMI instead of DVI.
They’re essentially the same thing (DVI is limited to 8-bit and carries no sound). Both are 100% forward and backward compatible with each other. You just need a cheap adapter. At my place our G5’s are located in a machine room. We use 50ft. HDMI cables w/ boosters to connect them to the edit bays.
Samah, go to monoprice.com and buy a DVI to HDMI adapter and/or cable. The adapters are like $5 there.
Keep in mind this is for your computer desktop display, and you’ll be limited to “Cinema Display Mode”. This does not give you a broadcast quality playback. You need a Kona or Blackmagic for that. As mentioned by these guys, if your G5 supports PCI Express, you can get a Blackmagic Intensity card.
-
Good to know. Thanks.
-
I’m not in front of FCP right now. Based on what you’re saying, it sounds like the TC reader filter doesn’t work properly with subclips.
Personally I don’t like or use subclips. I just break up the actual clips. Nice and simple. The only disadvantage is you can’t re-name them without first making them independent clips (pain in the ass). So instead I just use the description field for naming.
-
[strypes] “But, my question here is… if you import a clip at dvpal (via dv stream), because it’s recorded on mini dv, which is dvpal… you add some effects in final cut, and render, does it go through a 2nd dvpal compression?”
Yes.
-
[Flavio G. Garc
-
[strypes] “hmm… rendering compromises quality? That’s a thought to ponder… “
Uhh, yeah. You’ve got a lot to learn my son :).
Any lossy codec is just what it says. ProRes is slightly lossy. DVCProHD is more lossy. DV and HDV are extremely lossy.
Like Dave said, only Uncompressed and lossless are “lossless”.
Rip a CD to MP3 using iTunes. Then burn it to a CD. Now rip that new one. Repeat one more time. It will sound like absolute like garbage.
-
[PaulD] “That’s my through-a-glass-darkly perception of why these things are so hard to fix… 😉
“I’m not going to pretend to know how hard or easy it is to fix. But I will say with the utmost confidence that they have more than enough resources to make it happen – regardless of how hard it is.
That said, if they do feel it’s too hard to fix, then they have to accomodate that into the program. Like what I said before. Show a warning message before you try to MM something with speed changes.
-
[walter biscardi] “Actually, that’s a User Pref, just turn that off and it goes back to cropping it like before. I found that FCP kept scaling my still images when I didn’t want it to. Now it leaves them alone like before.
“Yeah but I like that preference. That’s how FCP has always worked, and it’s very convinient. It also takes the guesswork when using the new multiformat feature (at least its supposed to). But it shouldn’t do it in this case. 486-480 isn’t meant to be scaled. Ever.
FCP 4-5 didn’t have this problem. It was aware of the concept. Remember the message “You are about to transcode between 486 and 480, do you want to perserve the proper frame size”?
-
It is a higher quality codec. Higher bitrate and more advanced compression techniques.
You won’t see some kind of major improvement on your DV footage (if any improvement at all). The advantage is that each generation loss will take less damage. By the time your video is broadcast, on the web, or on a DVD, it will look better. This is especially important if you are doing a round-trip to Color, After Effects, etc. Each time you re-render it, it takes a hit. The damage is less when using ProRes (and there’s no damage at all using uncompressed).
-
It’s a huge problem. There are tons of know issues and they don’t fix them or even acknowledge them. The worst are the simple design errors they don’t fix. Like the idiotic design of what happens when you put 486 clips on a 480 timeline (it scales it instead of cropping it).
I’m with Jeremy on Media Manager. I think it’s great You can do anything and everything with it if you know how it works. They can fix whatever they want in it. The choose not to. Simple as that. There is not some weird XML limitation. They just haven’t spent enough on development and QC.
The worst aspect of it all is that the problems aren’t acknowledged by them. If you use MM and the clip has speed changes, it shoudl warn you “Speed changes cannot work with this process, press OK to continue anyways, or press Cancel”.
When you nest a sequence that has a multiclip, it should warn you of possible problems. When you export to Color, it shoud say “Sorry, Multiclip sequences cannot be sent to Color”.
Instead, it lets you do all these things that don’t work. It’ really annoying. It’s like they don’t want to admit bugs or limitations. I honestly wish Final Cut Studio was a product of a 3rd party developer.