Dean Decarlo
Forum Replies Created
-
I would vote for a manual switcher app. That’s the way VT (Video Toaster) works and it was never a problem. My main issue is that Combustion won’t automatically release the Decklink when minimized but I get that same problem of the Premiere monitor popping up on the broadcast monitor while it is still minimized. The idea of automatic switching is nice but in reality it doesn’t work that well. For me at least.
-
I had to open a .sit file that someone sent. Otherwise I’d never use stuffit. I will try uninstalling it though. Thanks.
-
I have a Gigabyte 965 based board, Core Duo 2, 4gb ram, on board raid with 4 seagate drives and it smokes for uncompressed SD. I’m getting 220mb /sec. in and out so uncompressed HD should be doable although I haven’t digitized it from tape yet. Spend wisely. Buy a system you can expand. You can always add more memory, storage etc. as you need them.
-
I’ll try it but I’m coming down to the wire on a job so it will have to wait a while. Maybe it’s conflicting with some other install. I remember I had some big problem a while back and it was due to some key that Stuffit set wrong. I got a Mac .sit file and loaded Stuffit and it was the heart of many problems last time. Probably something like that.
-
Thanks for the reply. I’ve been having the problem since before 6.1.1. I think it started around 6.0 or even 5.9. It’s a real drag.
-
Not really worth getting more than 3 or 4 gb max as windows can’t even address it.
-
I’ll chime in again here. My experience was that when taking clips from FCP over to PC that the gamma of each clip was embedded so that when the clip was opened in any app that could read quicktime (in my case I was using Combustion) the gamma was read using stored gamma in the quicktime file which was a “corrected” gamma to allow the 2.2 gamma broadcast footage to display in pseudo broadcast mode on a 1.8 gamma computer monitor. So even though, as I understand it, it is intended to be a display correction it ended up screwing up a bunch of renders as the footage came in and rendered with this incorrect gamma. Apple’s solution of applying a .818 gamma correction to resolve it basically reverses the display correction but I would imagine throws out some of the luma range. Not sure of that but I don’t like adding artificial color correction to footage just to get it to look like it did on Digibeta in the first place. My solution for now it to interchange with FCP using uncompressed codec only. That doesn’t seem to have this problem. Maybe they’ll fix this in Quicktime V8. Good luck!
-
First solution is to really understand the problem. We had a lot of pain on this one. Here is Apple’s explanation.
https://docs.info.apple.com/article.html?artnum=93794
Apple is doing you the “favor” of automatically adjusting the gamma of your footage to emulate the broadcast gamma on your computer monitor. This wouldn’t be such a problem if a.) they made it clear that the software was doing it and b.) that there was a way to defeat this behavior!
I’m on PC so the problem has only been with interchange between PC and Mac. It will happen with anything that Quicktime considers a “video” codec. In that link Shake is used as the example of any normal software that doesn’t screw with the gamma upon input. Their solution of adjusting the gamma by .818 to correct it is absurd as they are changing the gamma and then suggesting you adjust it back with a color correct. How about not changing it in the first place unless requested?!? Apple making things “easy” again… grumble grumble…
P.S. They mention at the tail of that link (and I found this out the hard way) that the Animation codec is also effected by this gamma change even though not really a “video” codec. Thanks again Apple!
-
When I installed the V6 drivers I no longer had the option of rendering at 8 bit. I only have the option for 10bit. Mjpeg seems to work fine but that is of no use on this project. Premiere seems to read and write the files fine. I render out of Combustion (Blackmagic AVI 10bit) and Premiere is fine with it but Combustion can’t read it back in. When I tried to open the rendered files in After Effects it started to open then went black. Very strange and very bad. Help!
-
I keep hearing that 4 drives can’t do HD but I’ve got 4 seagate raid 0 on my P965 motherboard and the Decklink utility reports about 275 mb/sec read and write at about 33% full. If those were 4 raptors I’d imagine that could be significantly higher. Am I not to believe the Decklink speed test?