[Technology1]

Originally Posted by dishe

No no- Qtv isn't a display driver that you install manually. Its support built into the hardware, waiting to be used. Problem is that most third party applications don't know how to use it, so they just call the standard DirectDraw set instead. If you recall, on the Mogul/Kaiser/Touch, at first people had to disable DirectDraw use to get proper video since the drivers weren't supported well by the OS/hardware. This is the opposite- the capability is there, but the apps don't use it.

Coreplayer 1.x started using Qtv overlay by default instead of DirectDraw. 1.1 only worked on GSM chips, though. The blue flicker only exists when using the overlay method to output video to an external display.
However even the older Coreplayer did a better job at decoding than TCPMP, using some more efficient code that helped drop less frames. The difference appeared on benchmarks, but wasn't dramatic until Qtv support came out.



I should probably mention that these aren't just random theories I had. This is based on information from Core Labs as well as countless threads on XDA. I noticed that a lot of the discussion never made it over here, which led to my post.



Your welcome. But, as I mentioned before, these aren't *that* kind of driver. You don't install a .dll or something to make this work. The video playing application needs to send information to the hardware decoder which is just sitting and waiting for this stuff.



Agreed. I'm not sure why Technology1 chose to take it as a personal challenge, but I'm not talking about streaming video quality here. Streaming quality, while definitely getting better these days, is still no match for encoded local content. What I'd LOVE to see is QTV eventually ported over to TCPMP.

Nothing is taken personal, but don't defame and demean another way of doing things, just because you don't perfer that method, that's all I'm saying... Stay tune for new breaking yet to be video technology for the TP coming your way very soon...