Importing DPX files of "Filled B" type
I have title overlay files in DPX format that are in a Big Endian, Filled B format. When I import them into Phoenix, they do not display correctly. What's the trick to get these to load properly?
-
Are these Mono DPX's if so you might have to add some parameters into the clips.pref file
you can find the the file in c:\Phoenix\current version\root\Users\AllUsers
Using Mono DPX - Settings
In addition to the overview in our File Format page, the DPX format also has some preference settings to help with loading monochrome DPX files.
This is particularly useful for compatibility with film scanners like Golden Eye.
You can add to the Clip.prefs file :
DPX
{
luma10PadLines BOOLEAN
luma10MSBFirst BOOLEAN
RGB12as2011 BOOLEAN
luma10NeedsShifting BOOLEAN
}
Where BOOLEAN can be "true" or "false" (without the quotes).
The Clip.prefs file may exist in more than one place under your ROOT folder.
See User Preferences and Preference Load Order.RGB12as2011
Compatibility mode for 12 bit packed RGB DPX images. If set to "true", uses previous mechanism for creating these files (2011 and earlier).
Default : false
luma10PadLines
10 bit luma packing mode. If set to "true", pack luma scan lines to 32 bit boundaries.
Default : true
luma10MSBFirst
10 but luma packing style. Id set to "true", first pixel if placed in MSB (most significant bit)
of the 32 bit word.Default : false
luma10NeedsShifting
On load, shift data bits to enable proper loading of monochrome DPX files.
This was added in version 2015.2.018.
Default : false
For complete compatibility with version 2011.2 and earlier, you should set :
DPX
{
luma10PadLines false
luma10MSBFirst true
RGB12as2011 true
}
Scanner Compatibility
Setting
Goldeneye
Scanity
luma10MSBFirst
false
true
luma10PadLines
true
false
luma10NeedsShifting
false
true
Notes
To diagnose mono-DPX load and display issues :
- If the image is skewed, luma10PadLines is probably wrong.
- If the pixels are in the wrong (p2 p1 p0) order, luma10MSBFirst is probably wrong.
- If the image looks corrupt (areas that are super bright/dark etc), then luma10NeedsShifting is probably wrong.
-
Björn Thank you so much! That was exactly the information I needed. It's working now!