[Jay Bloomfield]

The official power draw under load for the 580 GTX 3GB is 244W, but some of the overclocked versions are even higher. I have the EVGA version.

[Jay Bloomfield]

Go to the COLOR screen and then right click on the clip displayed in the top left of the screen. You’ll see a bunch of check boxes for each scope. It would be better if they docked somewhere or maybe I’m too stupid to figure out how to do that.

[Jay Bloomfield]

Resolve has a pretty non-intuitive user interface. In the Color screen, all 4 scopes are available by right-clicking on the clip (RGB Parade, Vectorscope, Histogram and Waveform).

[Jay Bloomfield]

You need either an external SATA dock or some way of plugging in the SSD directly to an internal SATA port on the computer. You presently cannot use the USB connection for anything except running the Hyperdeck utility either to change the output format or upgrade the firmware.

[Jay Bloomfield]

Thanks, I figured it was something like that, although it is odd that Resolve won’t open the Shuttle’s own MOV files, but Cineform and others are fine.

The reason that I posted it here was that the Shuttle 2 DNxHD MOV files also don’t open properly in AE CS5.5, even though AE has no problem with other DNxHD MOV files. I’m guessing that it must have something to do with the 16 audio tracks, because both PPro and AE CS5 (not CS5.5) will not open the Shuttle’s DNxHD MOV files for that reason. That problem has been posted on various Adobe message boards.

[Jay Bloomfield]

I was confused a bit at first by this too, because most of the presets in PPro are YUV and have max bit depth unchecked. So once I got over that hurdle, I noticed that I had three options for the “player” in the program Preferences menu. The default Adobe player, Blackmagic Design’s player and Cineform’s player.

Player Settings preferences

In the Player Settings pane of the Preferences dialog box, you can select the default player. Premiere Pro uses the player to play media from clips and sequences for the following:
Source Monitor
Program Monitor
the preview area at the top of the Project panel
Trim Monitor
Multi-Camera Monitor
the video transition preview in the Effect Controls panel.
You can choose the default player for your computer, or a third-party plug-in player for Premiere Pro. Third-party players are installed with some capture cards.

If you only have the Adobe player, then that isn’t the problem.

[Jay Bloomfield]

[Evan Burns] ”
Looks like I’m encountering the same problem in CS5.5. Just to be clear, can I fix this with color correction or is the information being clipped in some way?”

How are you importing the DNxHD MXF file to CS5.5? Or is that a DNxHD MOV version? If it’s MXF format, you have to be using an 3rd party importer like MainConcept or Calibrated{Q} and they both have settings that can affect the color range. I tried the demo of the Calibrated {Q} Importer and it worked fine with Premiere Pro CS 5.5.

If it’s DNxHD MOV format, check the settings on both your sequence and your player that you are using for preview. They both have to be set to “maximum bit depth”. I haven’t seen that problem with the MOV wrapper and CS5.5, but I will look again at a few more files.

[Jay Bloomfield]

I’m trying to figure out whether it is worth writing a C program using MXFLIB or maybe just using a hex editor to change the three values and see what happens. Maybe BMD will fix this with the final version of the 2.5 firmware.

Update: Well, I’m a bit baffled. I manually changed the Black Reference Level to 0, White Reference Level to 1023 and Color Range Levels to 1024 and it made no difference in DaVinci Resolve Lite (Win 7 x64). Both the original and full range file displayed 0-1023. I don’t have Avid MC, so there is no other way that I can look at the BMD Shuttle MXF file. I’m guessing that it must be up to the NLE as to what to do with those settings, if anything. If anyone wants to download DaVinci Resolve Lite (freeware) and see what they get with their MXF files, let me know.

[Jay Bloomfield]

I’m trying to figure out whether it is worth writing a C program using MXFLIB or maybe just using a hex editor to change the three values in a test MXF file and see what happens. Maybe BMD will fix this with the final version of the 2.5 firmware.

[Jay Bloomfield]

I tried to upload a complete metadata listing for a BMD Shuttle 2 DNxHD MXF file, but I’m not sure where it ended up. Anyway, here’s the snippet that describes the video essence:

CDCIEssenceDescriptor
InstanceUID = {daa94d91-6dd8-fae0-e4a2-739abd196d03}
ContainerDuration = 1377
SampledWidth = 1920
SampledHeight = 1080
StoredWidth = 1920
StoredHeight = 1080
DisplayWidth = 1920
DisplayHeight = 1080
SampleRate = 30000/1001
ComponentDepth = 10
PictureEssenceCoding = [060e2b34.0401.010a.04010202.71070000]
ColorRange = 897
WhiteReflevel = 940
BlackRefLevel = 64
ColorSiting = 4
VerticalSubsampling = 1
HorizontalSubsampling = 2
ImageAlignmentOffset = 8192
AspectRatio = 16/9
VideoLineMap
VideoLineMapEntry = 26
VideoLineMapEntry =
FrameLayout = 0
DisplayYOffset = 0
DisplayXOffset = 0
SampledYOffset = 0
SampledXOffset = 0
EssenceContainer = [060e2b34.0101.01ff.4b464141.000d4d4f]

As you can see, the range is from 64-940, not 0-1023.