The clock ticks do seem to be resolved with this version. CPU utilization has increased back up to the level it was before this issue got introduced (I think that was 0.10.1- remember how odd the low utilization with PIO seemed at that time, Hans?). I do have an issue with the driver though. My dmesg fills up with the following error as many as 10 times a second: ivtv0 warning: encoder VBI: Couldn't find start of buffer within the first 256 bytes I'm running an AMD Turion64 and using PIO mode for encoding. Everything is working perfectly, so I'd consider this error pretty cosmetic.
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
