Asus U3100mini ATSC/QAM usb tuner - scan finds NO channels

[marion]

Hi,
I'm pretty new to N-PVR. Trying to set up the npvr for the first time. In the DEVICES tab, my tuner is listed as Type: ATSC, Device: U3100mini ATSC Tuner. I'm using Comcast cable. Scan process takes several minutes and no (zero) channels are found.
What am I missing ? Should the device be listed as QAM for it to work ?

[johnsonx42]

go into Settings and view the Devices screen then post your npvr.log. sub can use the information in the log to add QAM support for that device in the next release. there's no immediate fix however. (that said I get the impression a new release is coming fairly soon)

[johnsonx42]

by the way, sub, while we're on the topic, as we get more devices that support QAM but don't show up automatically until you code an exception in the program it seems like that's going to become a support headache for you, and a point of user frustration. as it seems most ATSC devices do in fact support QAM, perhaps it would be better to just assume QAM support for all ATSC devices whether or not the driver says so; label all devices that have known working QAM support as "QAM" (same as now), then label the unknown devices as "QAM-Untested" or something like that - that would allow the user to try QAM on new devices without pestering you for a patch.

[marion]

Thanks for the help, really appreciate it.
Small problem, I can't seem to find npvr.log.
I attached a couple of screen shots from my set up, not sure if it's helpful ...

[johnsonx42]

see the sticky thread linked in my signature for help on finding and posting logs

[marion]

Thanks johnsonx42,
Found the log files. Not knowing what might be needed, I zipped up all files from log folder. There are files from several different days as I was trying the scans ...

[sub]

Thanks johnsonx42,
Found the log files. Not knowing what might be needed, I zipped up all files from log folder. There are files from several different days as I was trying the scans ...

I've made a change for the next release to enable QAM on this device.

[sub]

by the way, sub, while we're on the topic, as we get more devices that support QAM but don't show up automatically until you code an exception in the program it seems like that's going to become a support headache for you, and a point of user frustration. as it seems most ATSC devices do in fact support QAM, perhaps it would be better to just assume QAM support for all ATSC devices whether or not the driver says so; label all devices that have known working QAM support as "QAM" (same as now), then label the unknown devices as "QAM-Untested" or something like that - that would allow the user to try QAM on new devices without pestering you for a patch.

I may yet do something like. I'll keep it in mind.

[marion]

Thanks sub, appreciate it.
Any clue when you might release the next software update ?

[sub]

Its probably 2 of 3 weeks ago. Normally I'd offer to give you a patch to get you going, but my build is no longer compatible with 1.5.33.