Content issue......

[IanH]

Perhaps somebody can shed some light.

I have attached two files below via my dropbox site.

https://dl.dropbox.com/u/30002343/problem%20files/003%20DL-Basic-Grid-CRP.mov

https://dl.dropbox.com/u/30002343/problem%20files/004%20DL-Basic-Grid-SLRP.mov

We have a number of files that are not playing back correctly on our servers and both the Op and tech are scratching their head..

Both files are on multiple servers, both files look Ok when viewed using QT but when run using Catalyst the 003 file plays back with out the blue colour...

Severs are running .359 but we have tried it on .329.

Doesn't seem to happen with any other files?

Needless to say Content team say files were fine when they sent them.....

Ian H

[SourceChild]

Ian,

This is a common issue with Catalyst.


Actually, horizontal and vertical pixel counts need to be even numbers and the horizontal counts need to be 16 pixel multiples because of the core frameworks that Quicktime uses.

The simple answer and beyond the scope of Catalyst

Is that the line count or pixel width counts are stored as 32 bit integers where 16 of those bits are the line numbers in the group and 8 of those bits are an address, the remaining 8 bits are header and checksum.

This isn't just true of Quicktime, it applies to all graphics files that are derived from OpenGL frameworks. Some codecs autocorrect for this by populating the vacant lines in a user's output with black empty lines. Other codecs simply apply null data.

Unfortunately when catalyst runs, it uses an aspect of QT which misinterprets the null data and considers it render attributes.

The 003 file is 963x1400. My suggested solution to you is to adjust your content to a width of either 960 (16x60=960) cropping 3 pixels or 976 (16x61=972) adding 13 pixels.

Now I would presume you're using exact pixel maps, right? I know you have in the past anyway. If this is the case, perhaps you can adjust your horizontal mix to a width that accommodates the extra 13 pixels of 976 and places them in a blind space. This should fix your problem.

[IanH]

Thanks Todd..

Sorry not to see you in Europe ..... I know we passed on opposite sides of that french motorway.... until the next time.

ian