Frozen 1st Frame on PC TEMP FIX

[Jay A. Kelley]

Ok thanks to "Chaos" I am getting some progress with the first frame issue. I really owe him a lot since he supplied a fix for this and no one from RED team (to my knowlege) has offered one.

I cannot say this will work for everyone, but here's what I am seeing:

Before I begin let me say: "QUICKTIME SUCKS SWAMP WATER" it's a horrible little program, full of all the "Apple" crap I have come to know and love. /hate. If their other stuff is like Quicktime, they will NEVER see me as a customer. :ranting2:

Ok Rant over.. Back to it: This involved Cineform's little program "HDLink". Basically I rendered a 1080 file using the quicktime alternative, then I output that file to an AVI file using HDLink. The codec I used was DVCPRO NTSC

It played perfectly. Sadly for Cineform, I am still getting a "Cannot write to frame #". But I am just happy to see SOMETHING work.

Now I don't know if it's the quicktime alternative that's making the difference, or HDLink.. So I am going to check that now.

Jay

 

[Simon Blackledge]

This is getting really messy.. very quickly.. to many things to have to do to see a moving image..

 

[Paolo Tinari]

Followed Jay procedure (inst first QT then Redcine) and now outputting QT Dvcpro (orrible results at Lossless). Still no Cineform, maybe installing it somewhere before Redcine?

I have to remind that my system was working smooth and silky until upgraded QT and Cineform (yesterday)

 

[Jay A. Kelley]

So changing the order of install did work? Please confirm

Jay

 

[Jay A. Kelley]

I have seen low quality on DVCPro as well, but I have also had some very nice files from there. Not consistant, but we're moving further than we did yesterday!
Jay

 

[Cail Young]

If their other stuff is like Quicktime, they will NEVER see me as a customer. :ranting2:

It isn't. However, I occasionally get the frozen 1st frame on OS X, so... ?!

 

[galexander]

Followed Jay procedure (inst first QT then Redcine) and now outputting QT Dvcpro (orrible results at Lossless). Still no Cineform, maybe installing it somewhere before Redcine?

I have to remind that my system was working smooth and silky until upgraded QT and Cineform (yesterday)

think Jay used the QT alternative libs, not QT.

 

[galexander]

Followed Jay procedure (inst first QT then Redcine) and now outputting QT Dvcpro (orrible results at Lossless). Still no Cineform, maybe installing it somewhere before Redcine?

I have to remind that my system was working smooth and silky until upgraded QT and Cineform (yesterday)

Ouch! can you roll back?

 

[galexander]

I'm still downloading those files from RedRelay so in the meantime. Someone who has a working system now, please post comments on following:

1. Did changing the pixel aspect ratio with QT libs work?


2. Did you uninstall QT and go with the QT alternative?


3. Did you do both 1 and 2?


4. Here is a site where you can get old versions of QT. I don't have Cineform, but if anyone else has success with older versions please post.

http://www.oldversion.com/program.php?n=quicktime


5. What are these files only 8-bit???


6. I'm always happy to lend a hand and hack through these kinds of problems. To me, this is fun and a challenge ;-) You guys are paying a shitload of money for your Red gear. I find their lack of a responding that to me is a showstopper very interesting. Arno, in another thread, originally posted back around Jan 1 that he was having problems.

 

[galexander]

4k pixels vs aspect ratio

4k pixels vs aspect ratio

maybe it is something as simple as a disconnected between the pixel aspect ratio and the frame container???

i was looking through Jay's log again and maybe i missed something but what is the aspect ratio of the frame? is the frame "flat"? or S35? cinescope?

in Jay's log the frame is 4095x2048=1.99951171875:1, maybe adjust the image an extra line to get 4096x2048=2:1 or if you can't increase then perhaps chop it down to one of the following.

these are for square pixels.

shouldn't ...

cinescope,35 mm anamorphic, be 4042 x 1720 for the 2.35:1?

flat would be 3774 x 2040 for 1.85:1?

Super 35mm, 2720 x 2040 for 1.33:1?

widescreen, 3616 x 2034 for 16:9?

..... .. 4042x1720 for 2.35?

maybe it is as simple as redefining your image.

 

[Arnaud Paris]

Galexander,
Maybe I was not specific enough but I don't have a stuck frame right away when I export DNxHD. It happens after about 5500 frames and I'm pretty convinced it has to with some GPU overload. And by the way I've worked with many clients trying to resolve their RedCine issues it is clear this program is working better on PCs than on Macs. My system is a quad core with FX5500.
Arno
www.locared.com

 

[J.D. Frey]

Galexander,
Maybe I was not specific enough but I don't have a stuck frame right away when I export DNxHD. It happens after about 5500 frames...

Getting the same thing on an 8 core mac pro with 6GB of ram running OSX Leopard 10.5.1 using quicktime 7.3.1