[Chris Wright]

Red is .709 color, and if prores is old legacy quicktime, then its gamma flag is gonna be different. The players themselves with older playback codecs can cause non-playability, but if you can import the files back into AE/FCP and it works, you’re fine.

https://technicolorsoftware.hostzi.com/

[Chris Wright]

collapse transformation button maybe…

https://technicolorsoftware.hostzi.com/

[Chris Wright]

I once did a showdown with all the image sequence formats. Here’s what I discovered…

Targas give a slight pixel shift even though they’re lossless, as do png’s. For 16bpc, I looked into Tiff and PSD.

The only time Tiff is safe is if LZW compression is off, which can’t be turned off in PNG’s.

Since Tiff trillions 16bit(LZW off), is much smaller than PSD, I use it for outputing sequences. btw it’s used in animation studios and hollywood too. I would love to hear other thoughts.

https://technicolorsoftware.hostzi.com/

[Chris Wright]

this thread might help
https://forums.creativecow.net/thread/65/855556#855557

https://technicolorsoftware.hostzi.com/

[Chris Wright]

Normal size fixing thread for CS3.

https://forums.creativecow.net/thread/2/939829#951736
————–

and for strange sizes in CS4…

Since you are using strange sizes, there is no preset for you. You will have to use CS4’s custom Adobe Media Encoder.

Select Edit > Export Settings.

The Export Settings dialog box appears. This dialog box lets you perform the following actions:

Specify alternate encoding settings to deliver video for different bandwidths and applications.

Crop and resize the video clip to alter its dimensions.

-MAKE YOUR OWN PRESET FOR FREE!

There is a workaround that I have tested and works, but make backups first if you try it.
—–
Simply duplicate a *.vpr video preset file
from…

C:Program FilesAdobeAdobe After Effects CS3Support FilesPlug-insFormatMediaIO(presets)systemen_us

open the duplicate in notepad
(example…) change the Data=”1024 to Data=”1000″.

Data=”1024″ ID=”1″ Name=”Frame Width [pixels]” Size=”4″ Type=”VDataType_DWORD”Property Data=”576″ ID=”2″ Name=”Frame Height [pixels]
————————-
If you make any new spaces, then AE will probably crash.
All you have do you is make the resolutions the same, then you can change the preset’s other stuff in the render queue.

https://technicolorsoftware.hostzi.com/

[Chris Wright]

AE CS4 came out with a new plugin called time difference that will make rotoscoping that 99% automatic.

https://technicolorsoftware.hostzi.com/

[Chris Wright]

“With Glue Tools Cineon/DPX Pro for Final Cut Studio, you will be able to read and write Cineon or DPX digital images in one easy step. You no longer need to convert your source frames into another format using a separate program such as Shake, Combustion or other Open Source packages. You can work directly with the native images themselves. At last there is an easy way to load and save Cineon or DPX film (or High Def) images into QuickTime.”

https://www.gluetools.com/products_dpx.html

https://technicolorsoftware.hostzi.com/

[Chris Wright]

dpx and cineon’s advanced settings should be looked over and tested thoroughly. This includes color management.

https://magazine.creativecow.net/article/cineon-files-what-they-are-and-how-to-work-with-them

https://technicolorsoftware.hostzi.com/

[Chris Wright]

AE’s simple reinterlacing would give a different speed look than interpolating new frames. Try a demo of reelsmart’s reinterlacer too.

https://technicolorsoftware.hostzi.com/

[Chris Wright]

I guess I’ll be the first one to take a stab at this. Since AE still hasn’t updated all their plugins to 32bpc, we’ve been stuck with a conundrum. Some effects give warnings but can be somewhat protected if you use utility->hdr compander.

Think of bracketing your 8,16 warnings with 1 at the very top set as-compress range and one at the bottom set at -expand range. You can take a screenshot and compare how the compander protects color.
As for why we should ever use 16 bit if we only output milllions+ 8bit anyway, is because AE will preserve posterization calculations then spit out correct 8 bit again.

As for 32bpc, you can push,pull pixels to your hearts delight and some effects are even redundant and can be replaced, like shift instead of set channels, hue/sat instead of color hls, transfer modes instead of calculations are 32bpc.

Should I go 32bpc all the time no matter what? I haven’t seen any reasons not to if you use compander as needed. This way you can use Color Finesse onto hundreds of precomps and not worry about posterization.

The only downside I can think of is really old plugins may not work even with compander and really large images, if you don’t have enought RAM, could give you a image buffer error. 8 bit is so 1980’s.:)

https://technicolorsoftware.hostzi.com/