Vu+ duo 4k Lite

[bellejt]

quote stick50jr : I have received my duo4klite with two dual DVB-T tuners internally

 

[Ev0]

quote stick50jr : I have received my duo4klite with two dual DVB-T tuners internally

Ok maybe you don't understand what I said, or maybe I didn't explain it clear enough, who knows (it is irrelevant anyway).

But either way the question was about usb tuners and as said the Duo4K Lite currently does not support them.

It also does not support Multistream channels either.

 

[el bandido]

Not the se, it is the lite.

My apologies for making a typo! It would be interesting to know if the vtuners exist

The lite shows as 8.

But the vu+ turbose usb tuner doesn't work on it and there are no drivers for the normal vu+ turbo usb tuner.

Excellent! Thanks for providing the missing piece!

The Duo 4K Lite appears to have the necessary infrastructure to support USB DVB tuners. The remaining work is getting a compatible tuner and its driver working together.

 

[Huevos]

The remaining work is getting a compatible tuner and its driver working together.

Good luck with that.

 

[el bandido]

"Good luck with that" might be better reserved ATM for someone purchasing or looking to purchase the new Vu+ Duo 4k Lite.

The Vu+ Duo 4k Lite image seems to be set where a supported usb tuner would or should work, but at the same it resembles a GigaBlue product more than a Vu+ product in the kernel variety and enigma2 image design.

One thing that may or may not matter is the driver, rootfs/home/root/platform/dvb.ko, contains the default frontend name vTuner proxyFE DVB-S (lowercase v). The OpenVix enigma2 source file, lib/dvb/dvb.cpp, searches for "VTUNER" (uppercase V) in setUsbTuner(). This may not even matter, but it is probably something simple that is keeping the usb tuner from working in the Lite.

The vuplus_tuner_turbo_driver.ko And vuplus_tuner_turbo2_driver.ko are seen in an upacked Duo4kSE image with kernel 4.1.45-1.17. The Duo 4k Lite uses kernel 4.1.20-1.9 and does not unpack with these two drivers.

 

[Huevos]

Current wisdom is drivers and firmware for that box are out of the same stable as GB 4K models. So I would look at those longer standing models and ask whether usb tuners are of any interest to them.

 

[el bandido]

Anyone can download - extract a few images and see the Duo4K Lite file structure resembles GiagBlue (gb7252). The issue is whether this particular platform is incorrectly identifying or exposing supported USB tuners, and whether that behavior can be corrected.

The Octagon SF8008 had a DVB-T, ATSC USB tuner which presented the tuners as DVB-C. Over some years, that was eventually investigated and worked around/fixed rather than dismissed simply because USB tuners were a niche use case and it would take Octagon to fix it. ( Octagon did not directly assist in this, and had to be told about it.)

It should be determined whether this is a genuine driver/interface bug in the Duo 4K Lite and, if so, where it originates. If it turns out to be closed-source driver behavior that cannot reasonably be fixed, that's useful information too. But I think it's worth establishing that before writing the problem off as unsolvable and pointing at a GigaBlue company that has no real existence.

 

[el bandido]

A small update on the GigaBlue USB tuner testing that would lead to fixing the usb tuners on Vu+ Duo4K Lite.

Despite the conventional wisdom that USB tuners no longer work properly on GigaBlue 4K receivers, I now have a Hauppauge WinTV HVR-950 working on a GigaBlue UHD UE 4K with the current OpenViX 6.9 developer image.

This is not just a case of the tuner being detected or appearing in Tuner Configuration. The attached Enigma2 log shows the complete path working:

/dev/dvb/adapter1/frontend0 is detected as the WinTV HVR-950.
Enigma2 links it through vtuner0.
It is presented as frontend / NIM 10.
The tuner obtains full frontend lock (status 0x1f).
An ATSC scan is performed using NIM 10.
PAT and VCT tables are successfully received.
Services are identified during the scan.
A scanned service is subsequently tuned.
PAT/PMT parsing succeeds.
Video and audio PIDs are opened through the demux.
VIDEO_PLAY and AUDIO_PLAY both succeed.
The decoder reports 704x480 video at 29.97 fps and 2-channel audio.
ATSC EIT/EPG data is also received.
So, at least with this particular combination:
GigaBlue UHD UE 4K + OpenViX 6.9 developer + Hauppauge WinTV HVR-950 ATSC USB tuner, USB tuner operation is working end-to-end.

I have attached what is supposed to be the full Enigma2 debug log so the actual tuner, vtuner, scan, demux and decoder activity can be examined rather than relying on my description of it.

This does not necessarily mean every USB tuner or every DVB delivery system will now work on GigaBlue 4K or Vu+ Duo4K Lite hardware, but it does show that the general statement that USB tuners cannot work on these receivers is no longer universally true.

So apparently I did have some luck with that.