Intel Encoder SDK (Quicksync for adobe) color

[Crucio]

Hey has anyone played around with the intel sdk encoder plugin for premiere/media encoder? It's fast and looks great, but the colors are noticeably more red, plus the bitrate controls don't do anything and there is no way to set keyframe distance.

Has anyone experimented with other solutions for using intel's h264? Is it only usable with the mainconcept codec?

Am I better off using graph edit?

Is the color change from a yuv>rgb conversion I don't know about?

Thanks guys.

[hajj_3]

i think quicksync for sandy bridge only has 1 setting, you can't increase quality. Quicksync for ivy bridge will have 2 different quality settings, 1 is the same as sandy bridge but it will be alot faster and another setting which will be alot better quality wise which is slightly faster than the quicksync in sandy bridge.

[CruNcher]

you have different possibilities to set it up (3 different Motion Search Setups) (different bitrate, including custom) it has nothing todo with SB or Ivy Bridge but how the ISVs implement it

[Crucio]

Cruncher, can you please elaborate?

Also is your post pertaining to adobes Intel plugin, or is it just Intel sdk encoder in general?

Is what you're saying an option thatbwouod cause the color to notable be modified?

Thanks

[CruNcher]

Sure the SDK Encoder API gives you the possibility to setup different Motion Search Qualities and Bitrates also Key Frames could be changed it's just depends on how someone implements it (sure you cant go deep down to its core only Intel can do that partly via driver changes) :)

but the colors are noticeably more red
This could have many issues without a sample of the source and something that shows the difference it's hard to tell whats going on exactly but a unintended conversion somewhere is the most probable as you said :)

[Crucio]

Sorry. Android is great, but sometimes not for typing. Should have looked before I sent.

[Crucio]

http://software.intel.com/en-us/forums/showthread.php?t=102504

There are pictures of the problem there if you care to look.

It was really nice being able to output an h264 file faster than uncompressed from mixed adobe products. I had premiere after effects and Photoshop in one encode,where before I used to have to output an intermidiary file from each.

Wish the plugin could get fixed.

[Crucio]

Just read that nv12 color space not supported so there is a color space transformation. That must be it?

[Asmodian]

That does look like rec.601 viewed at rec.709 to me. It must be doing a unexpected conversion to RGB.

It was really nice being able to output an h264 file faster than uncompressed from mixed adobe products. I had premiere after effects and Photoshop in one encode,where before I used to have to output an intermidiary file from each.

I wouldn't use h264 from quick sync as an intermediate file, it is fairly lossy.

[CruNcher]

why not if you configure it like AVC-Intra 50/100 it would make sense :)

[Crucio]

Asmodian, not using h264 as an intermediate file... I am using adobe's Dynamic Link. For some reason, the quick sync is still faster than outputting say an uncompressed or quicktime animation when using multiple sources mixed in one premiere timeline. So if I have 30 photoshop documents, some DVCPro HD, mpeg 4 avc, and a few after effects time lines thrown in, it might be 7 minutes for the uncompressed and 1 minute quicksync.

I would never use h264 between projects :)

[Crucio]

What it looks like is a limitation of the adobe api, that doesn't allow nv12 color space.