Hi,
we will add it to the next driver release which we will provide around mid next week (14th April).
Great! My system is not exactly stable, which is possibly why I haven't yet seen the stick turn off after 15s ... quite possible that some of my software does not close right and keeps on claiming the device. So having a command to explicitly turn it off, will save hours of troubleshooting of what could be wrong with my system
We are currently investigating alternative options for HDTV channels, currently it either requires an NVidia Graphiccard or a fast PC. Lowering the resolution is not useful since the entire video is encoded in HDTV and rescaling can only be done by postprocessing and adding additional CPU power to the entire process chain. Even if you rescale it the input data is always the same, the USB Stick can handle the HDTV input data without any problem.
I agree with this, which is why I think I haven't explained myself
Ok, I assume (but am not sure) that crudely the process goes:
* stick receives a frame of a given resolution
* stick packs the frame, sends it via USB
* PC/driver receives USB packet, retrieves data, unpacks frame
* PC then decodes frame
So, lets say, I'm receiving 400x200 video (just giving some round numbers as example), I would depict it like this:
(400x200 air) => Stick => (400x200 USB) => PC (unpack, decode: 400x200)
Say I can watch this fine, but then I try HD - lets say it is 800x400; then I would depict the process like
(800x400 air) => Stick => (800x400 USB) => PC (unpack, decode: 800x400)
and the bottleneck here is that the PC cannot unpack/decode 800x400 ( I was never implying that the USB Stick cannot handle HDTV input
)
So, what I was hoping for, is that there would be some driver command, so I would set something like, say, 'hdlowres=1', in which the stick could possibly resample the frame to a lower resolution (say, by sending only every other pixel), and send it as such to PC; i.e.:
(800x400 air) => Stick => (400x200 USB) => PC (unpack, decode: 400x200)
in which case, the PC 'from the start' would receive a 400x200 frame, which it can handle
Now, I understand this is very simplified - and probably not how the actual processes occur in the stick; and of course, it depends on whether the stick itself has access to decoded pixels already - I guess it doesn't, but I just wanted to make sure...
Thanks again for the answers,
Cheers!