[Tristan Summers]

My thoughts, having just been given similar footage.
As this is “5k” 16×9, I would make a UHD 3840×2160 comp and scale the footage to that. You then have a standard “4k” frame size that ProRes and DnxHD will be happy with, and fits DCP standards. This is what I would assume would be the intent of shooting at that resolution.
If you are just cutting it for a later conform, do it at HD, from transcodes
I am only just realising that cameras basically make their frame sizes to maximise their sensors, and give people crop room for later. Unfortunately nobody pays attention to the framing guides…

Tris

[Tristan Summers]

I too once shared your sweet naive belief that quicktime displayed files properly. but in fact it displays nothing properly. pro res files on a pc look so washed out but they are fine on a mac. yet everyone is happy to use it.

The above is entirely incorrect however. IF you use x264 and set a correct 2.2 gamma tag, the h264 file will look exactly the same, which is why it is used by vimep, youtube, , in quicktime, everywhere. well, not in the FCP7 viewer that is still thinking all content is 2.2 and all macs are 1.8.

the big problem is Apple do not let you set the gamma tag correctly, and quicktime performs incorrect conversions based on filetype interpretations.

[Tristan Summers]

Do you have any version of ffmpeg, broadcast ffmpeg etc? I wonder if it is that interfering with things. I know I was trying out ProRes exporters.

I have it too. I have Windows 7 pro, I think, depends what comes on a Z820.

Quicktime is just a joke. I just assumed it was a PC thing.

mp4s render a thousand times faster but have started tearing, using presets from AME that worked before. with or without GPU encoding.

I can export h264 from Quicktime, though it takes longer than my Gen1 Mac Pro

ROLL ON MOX

[Tristan Summers]

HOw does this work if you are combining different things? Position, 3d rotation 2 effects one with expression to custom named slider. NOrmally = UU+select all
so Now, select JUST the effect Name, does this take all the values?
confused

[Tristan Summers]

BRILLIANT

HI.
I added this to a text script, sorry can’t remember whose, maybe greymachine or Alvarez, but this means I can now count up, with a percent sign and the sign not move around:

n = effect(“Text VAlue”)(“Slider”);
// add two zeros, and make it an unsigned string — we’ll add the negative back later if it’s supposed to be negative
nScaled = Math.abs(Math.round(n * 100));
s = “” + nScaled.toString();
// pad low values with leading zeros to ensure at least 3 digits after we move the decimal point
while (s.length < 3) s = “0” + s;
// if it was negative, add the – sign back
if (n<0) s = “-” + s;
// insert the decimal place before the last two decimal places
s = s.substr(0,s.length-2) + “.” + s.substr(s.length-2,s.length)+”%”

THANKS EVERYONE

Tris

[Tristan Summers]

My two cents, based on what I do for after effects.

If you are rendering for intermediate use, set gamma correction to none.
It will look right in After effects, it is right, BUT it is wrong in Quicktime, with or without the FinalCut Compatibility check box.
If you want to make Pro Res for viewing purposes only, set gamma correction to automatic. Quicktime will now display it properly, however the file itself will be wrong.

If only you could manually set gamma tags in all quicktime files.
If only Quicktime would stop trying to “help” and just display the file exactly as is.

In a year or so it will hopefully have died the death it deserves anyway.
Unless someone else can come up with a movie container that lets you set all the metadata properly.

[Tristan Summers]

When I deleted the audio track, then hit UNDO, Premiere began playing again.
Perhaps this could offer a clue as to what was causing it.
Are those with the problem running 64bit systems on relatively recent graphics cards?
Tris

[Tristan Summers]

I had this issue.
I deleted the audio track.
I hit undo.
It now plays.
try it, you never know.
I am also now trying it with 48hz instead of 44.1, just in case.

[Tristan Summers]

There is a recent firmware upgrade to these SSDs which is meant to have improved things immensely.

OCZ firmware upgrades only work when the drive is internally mounted in a PC which is a bit of a hassle for mac users.

Hopefully BMD are updating firmware before testing, and OCZ are still improving firmware to make these drives usable

Tris

[Tristan Summers]

And When Speedgrade gets better…