Hauppauge Dual HD Tuner V2 - U4 Problem

[KEL]

My response back to Hauppauge.
(hopefully I've got most of my facts correct)

Jerry,
Not as simple as you suggest (ref kernel version issues) perhaps.

An older version of the Hauppauge dual tuner also worked OK with the Beyonwiz; before this latest 316 version.
Not sure which dual Hauppauge model it was. But Beyonwiz V2 and U2 were sold with them as an option.
versions
You used to be able to buy it with the Beyonwiz (advertised as such) and it would upgrade the Beyonwiz V2 from two to four tuner capable.

That is why I went for the Hauppauge in the first place, because I had assumed it was still compatible.

Kurt

[prl]

An older version of the Hauppauge dual tuner also worked OK with the Beyonwiz; before this latest 316 version.

The Hauppauge tuner I have from Beyonwiz identifies as "Hauppauge model 204109, rev C2I6" in /var/log/messages.
I think that the model you have is C3I6 (rather than C316: capital-I, not digit-1).

The one I have also has the model/revision number on a sticky label on the back of the tuner, as "204109 LF Rev C2I6" above the barcode. It also has the tuner's serial number on the far right below the barcode.

[KEL]

Yep,
as previously provided, attached is my file: /var/log/messages - (and commented on, below, in previous post, by Grumpy_Geoff):

Yes, I have the rev C3I6, unfortunately.!
Label on the back of mine, reads:
204209 LF Rev C3I6 0122
-BARCODE-
DVB-T/T2/C ******53
Product of Indonesia

My Hauppauge tuner is not working at all now, none of the tuners are operating, but showing up as "enabled" still.

I checked and the old 204 byte dvb-demod-si2168-d60-01.fw is installed again.

I rebooted (switched power off/on several times) to clear the Hauppauge memory of the larger driver, as you suggested (at least I hope that is what you meant by clearing that memory??).
Question: any other way to clear the Hauppauge memory, or should I have done it differently
(and even check it has the correct driver installed - suppose that part can't be accessed?)?


The V2 now even hangs up if you have two channels selected for recording and you want to look at one of the channels you are recording (at the same time).

I substituted a different single, mini-tuner and it works fine and displays/records 3 channels available/operating at the same time, as expected.

Question:
Anything else I can do/try at this stage, or am I wasting my time on the Hauppauge's - till there's a V2 firmware system upgrade, or is that never going to happen?

WHAT NOW
(apart from using say one or two of the min-tuners in the interim, other ...) and having a beer, then a bottle of wine to clear/reset the brain?

thanks,
Kurt

---------------------------------------------------------------------------------
Re: Hauppauge Dual HD Tuner V2 - U4 Problem
Post by Grumpy_Geoff » Sat Feb 26, 2022 15:37

Both tuners in the Hauppauge dongle appear to be in isoc mode and detected/attached okay -
Code: Select all

Jan 1 10:00:34 beyonwizv2 user.info kernel: em28xx: New device HCW dualHD @ 480 Mbps (2040:0265, interface 0, class 0)
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28xx: DVB interface 0 found: isoc
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28xx: chip ID is em28174
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x7ce0c6c8
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: EEPROM info:
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: microcode start address = 0x0004, boot configuration = 0x01
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: AC97 audio (5 sample rates)
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: 500mA max power
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: Identified as Hauppauge WinTV-dualHD DVB (card=98)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 4-0050: Hauppauge model 204209, rev C3I6, serial# 14318853
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 4-0050: tuner model is SiLabs Si2157 (idx 186, type 4)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 4-0050: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 4-0050: audio processor is None (idx 0)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 4-0050: has no radio, has IR receiver, has no IR transmitter
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: dvb set to isoc mode.
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28xx: chip ID is em28174
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: EEPROM ID = 26 00 01 00, EEPROM hash = 0x7ce0c6c8
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: EEPROM info:
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: microcode start address = 0x0004, boot configuration = 0x01
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: AC97 audio (5 sample rates)
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: 500mA max power
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: Identified as Hauppauge WinTV-dualHD DVB (card=98)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 6-0050: Hauppauge model 204209, rev C3I6, serial# 14318853
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 6-0050: tuner model is SiLabs Si2157 (idx 186, type 4)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 6-0050: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 6-0050: audio processor is None (idx 0)
Jan 1 10:00:34 beyonwizv2 user.info kernel: tveeprom 6-0050: has no radio, has IR receiver, has no IR transmitter
Jan 1 10:00:34 beyonwizv2 user.warn kernel: em28xxdvb ts2 set to isoc mode.
Jan 1 10:00:34 beyonwizv2 user.info kernel: usbcore: registered new interface driver em28xx
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: Binding DVB extension
Jan 1 10:00:34 beyonwizv2 user.info kernel: i2c i2c-4: Added multiplexed i2c bus 7
Jan 1 10:00:34 beyonwizv2 user.info kernel: si2168 4-0064: Silicon Labs Si2168 successfully attached
Jan 1 10:00:34 beyonwizv2 user.info kernel: si2157 7-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
Jan 1 10:00:34 beyonwizv2 user.info kernel: DVB: registering new adapter (em28174 #0)
Jan 1 10:00:34 beyonwizv2 user.info kernel: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)...
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #0: DVB extension successfully initialized
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: Binding DVB extension
Jan 1 10:00:34 beyonwizv2 user.info kernel: i2c i2c-6: Added multiplexed i2c bus 8
Jan 1 10:00:34 beyonwizv2 user.info kernel: si2168 6-0067: Silicon Labs Si2168 successfully attached
Jan 1 10:00:34 beyonwizv2 user.info kernel: si2157 8-0063: Silicon Labs Si2147/2148/2157/2158 successfully attached
Jan 1 10:00:34 beyonwizv2 user.info kernel: DVB: registering new adapter (em28174 #1)
Jan 1 10:00:34 beyonwizv2 user.info kernel: DVB: registering adapter 2 frontend 0 (Silicon Labs Si2168)...
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28174 #1: DVB extension successfully initialized
Jan 1 10:00:34 beyonwizv2 user.info kernel: em28xx: Registered (Em28xx dvb Extension) extension
I note that your unit reports as "rev C3I6", whereas others I've seen report as "rev C2I6".

Then we appear to get to the point where the poo hits the fan "unknown chip version Si2168-D60" -
Code: Select all

Jan 1 10:00:38 beyonwizv2 user.err kernel: si2168 4-0064: unknown chip version Si2168-D60
Jan 1 10:00:38 beyonwizv2 user.info kernel: si2157 7-0060: found a 'Silicon Labs Si2157-A30'
Jan 1 10:00:38 beyonwizv2 user.info kernel: si2157 7-0060: firmware version: 3.0.5
Jan 1 10:00:38 beyonwizv2 user.notice kernel: vtunerc0: setting DVB-T tuner vtype
Jan 1 10:00:38 beyonwizv2 user.warn kernel: vtunerc0: frontend initialized as type=4
Jan 1 10:00:38 beyonwizv2 user.info kernel: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
Jan 1 10:00:38 beyonwizv2 user.warn kernel: vtunerc0: usb frontend initialized as type=4
Jan 1 10:00:38 beyonwizv2 user.info kernel: DVB: registering adapter 0 frontend 0 (dualHD)...
Jan 1 10:00:38 beyonwizv2 user.err kernel: si2168 6-0067: unknown chip version Si2168-D60
Jan 1 10:00:38 beyonwizv2 user.info kernel: si2157 8-0063: found a 'Silicon Labs Si2157-A30'
Jan 1 10:00:38 beyonwizv2 user.info kernel: si2157 8-0063: firmware version: 3.0.5
Jan 1 10:00:38 beyonwizv2 user.notice kernel: vtunerc1: setting DVB-T tuner vtype
Jan 1 10:00:38 beyonwizv2 user.warn kernel: vtunerc1: frontend initialized as type=4
Jan 1 10:00:38 beyonwizv2 user.info kernel: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
Jan 1 10:00:38 beyonwizv2 user.warn kernel: vtunerc1: usb frontend initialized as type=4
Jan 1 10:00:38 beyonwizv2 user.info kernel: DVB: registering adapter 0 frontend 0 (dualHD)...
Jan 1 10:00:38 beyonwizv2 user.err kernel: si2168 4-0064: unknown chip version Si2168-D60
Jan 1 10:00:38 beyonwizv2 user.err kernel: si2168 6-0067: unknown chip version Si2168-D60

[KEL]

Perhaps as an interim project I should get a Raspberry Pi and interface the Hauppauge tuner via it, to the Beyonwiz V2.

At least we know they work with the C3I6 rev - and keep their operating firmware up-to-date still (at the moment).

Just a thought.
What think you?


thanks.

[prl]

Question:
Anything else I can do/try at this stage, or am I wasting my time on the Hauppauge's - till there's a V2 firmware system upgrade, or is that never going to happen?

I'm not sure quite what configuration you're using when you say that " The V2 now even hangs up if you have two channels selected for recording and you want to look at one of the channels you are recording (at the same time)." If that's with the Hauppauge installed, just stop using it and use the single USB tuner instead.

If that happens without the Hauppauge installed, it sounds like something may have been damaged in the firmware (file inadvertently deleted, or altered). In that case, I suggest that you do a USB firmware install using the 20211010 installer. It should be OK to restore your backed up settings.

[prl]

Perhaps as an interim project I should get a Raspberry Pi and interface the Hauppauge tuner via it, to the Beyonwiz V2.

OK, so now you have a Raspberry Pi with dual USB tuners. How do you want to get the Beyonwiz to use those tuners? Can the Pi run enigma2 and offer them as remote tuners? Or is there software for the Pi that will allow it to offer the USB tuners as enigma2 remote tuners without actually running enigma2?

[KEL]

Thanks,
shall do a USB firmware re-install using the 20211010 installer as suggested.

I could also (seeing I have two Hauppauge twin tuners) install them in parallel if the above fix works.?

Trying to make the V2 have the same capability (and look the same for the user, my wife included) as our T4 setup.

As previously discussed, do you have any future plans to upgrade Linux version (kernel?) to a later version, in a future 202111010 operating system, to include: the new Hauppauge driver, and other potential tuners/devices - or is there too much work/testing, lack of need involved ?

Kurt

[MrQuade]

Kernel upgrade is highly improbable.
A driver fix/backport should be possible, but would have to come from someone outside of Beyonwiz developers.

[KEL]

Thanks for your candour.

Question: Is the driver fix something I could talk to Hauppauge about (again, excuse my ignorance) ++
- I just told them current support of wiz of their earlier Hauppauge tuner versions do work, despite the possible waffle about kernel versions?
++ Don't know if that would help? Just trying to do my bit for the cause. Await their response.

Who/what would be involved with that (i.e. your statement, "A driver fix/backport should be possible ..." ) ?
Understand obviously, resources/funds are final factors.
Ignorance showing again: I don't understand the Beyonwiz market/company model.?

Question: I note the Kernel version of the V2 is lower than the U2?
Correct?
Does that suggest the V2 is a lesser product c/w the U2 ( which may be based on the Octagon perhaps ???):;
see:
https://www.satfreax.de/en/tv-receiver/ ... o-receiver

Wish I had in hindsight (a marvelous thing), bought a U4 when available! for my current obvious reasons!

The whole experience with the wiz makes me wonder about the long-term viability of the Beyonwiz brand, which I think is a fantastic product and want to support.

Kurt

[adoxa]

You could try another version of the firmware here - it's 3.27K.

[KEL]

Thanks will give it a go too.

[KEL]

Undertook USB firmware re-install using the 20211010 installer.

No change.
Same problem with external Hauppauge C/D tuners not picking up, even though enabled.
Can't perhaps get them back to their original interface software (in Hauppauge) state - even though hard reboot (powered off/on) done numerous times

Also
(1) will check performance of V2 with no Hauppauge and see if it allows recording two different freq stations and looking at in real-time one of these. Currently, with Hauppauge connected, still can't do that... strange.

(2) Perhaps I'll do a message list and see how different it looks (if at all) to previous provided one.

(3) Will also try other driver as suggested by "adoxa".

[MrQuade]

Same problem with external Hauppauge C/D tuners not picking up, even though enabled.
Can't perhaps get them back to their original interface software (in Hauppauge) state - even though hard reboot (powered off/on) done numerous times

I'd try installing the Windows drivers on your PC and plugging it in there to see if you can at least get it talking again.

A bit strange that it is not even being detected any more even after a firmware re-install.

[KEL]

Yes the Hauppauge is communicating okay with the Windows 10 laptop.
See attached enquiry on it, to check status.
Happy with that or do you need more?

For the TV display, it shows A B C D.
Now, only A and B are ever used/colour-illuminated.

Also the MENU shows A, B, C and D are enabled.

Is it possible that the issue is the latest version (2021) of the operating system?
That's the only thing that makes the most sense to me - based on what I've tried so far and what Hauppauge have said about support for single/double tuner access...? See further following.

I have to go back to the sequence of events (posts) what date last month I updated and when it became obvious to me that none of the two tuners in the Hauppauge were accessible now.

I know (pretty sure) with the earlier version of the software the system could use one of the two tuners.
I think at that time when I posted I was displaying the Hauppauge dual tuner as one tuner only.
It was not displaying as two individual tuners.

Again, I have to go back through the posts.
At the time when I updated the Beyonwiz firmware I was elated to get the Hauppauge up twice, namely C and D.
Then I didn't thoroughly check /test straight away.

However, when I did try to use/test a few days layer I noticed it was not allowing me to record multiple channels. (also prompted by another post with a similar issue, to get of my butt again and properly check). I needed a break, because the issue was driving me nuts.

Hence I bought another Hauppauge (stupid now in hindsight!) thinking that the first one I bought had developed a hardware fault.
I was using this to compare, and they were both experiencing the same issue.

Stupid question perhaps and you might think it's a no-no.
Can my BeyonwizV2 be reloaded with the earlier version again and check the above?
Save me going through a bunch of posts and not having enough info to verify/assist when things went left-field.

[prl]

Can my BeyonwizV2 be reloaded with the earlier version again and check the above?

Yes, but if you go back to a much earlier firmware version, like one before the 19.3 series, it's probably better to not restore settings.

It seems unlikely to me that an older version of the Beyonwiz firmware will better support newer hardware, but I guess there's some small chance that it might.

[Grumpy_Geoff]

Yes the Hauppauge is communicating okay with the Windows 10 laptop.
See attached enquiry on it, to check status.
Happy with that or do you need more?

Kurt,

You have two dualHD tuner dongles that identify themselves differently.

One identifies as USB VID (Vendor ID) "2040" PID (Product ID) "0265".
The other as VID "2040" PID "8265".

The first one you showed us here was USB ID "2040:8265" (8/2) - viewtopic.php?f=67&t=15000#p198381
Originally, it only identified one tuner.
Subsequently you stated it was working after resetting the mode - viewtopic.php?f=67&t=15000#p198389

You showed it again here, but the mode was wrong - viewtopic.php?f=49&t=15014&p=198523#p198528

All four tuners are shown here - viewtopic.php?f=49&t=15014&p=198523#p198543

You then used the "other" dongle as the messages file identifies the dongle as having USB ID "2040:0265" -

Code: Select all

Jan  1 10:00:34 beyonwizv2 user.info kernel: em28xx: New device HCW dualHD @ 480 Mbps (2040:0265, interface 0, class 0)

You showed that second dongle again here - viewtopic.php?f=49&t=15014&start=49#p198669

[KEL]

Just double-checked.
The Hauppauge toggles PID number, for both dual tuners, depending on mode set:
BULK PID= 0x8265
ISOCH PID= 0x265

I am sure I set them to the correct ISOCH setting and will double-check.

I'll check/respond to Grumpy_Geoff posts shortly.

For previous version exercise, I only wanted to temporarily return to previous Beyonwiz system firmware to follow-up on when I could access one of the tuners.

thanks,

Kurt

[KEL]

Grumpy_Geoff
KEL wrote: ↑
Sun Mar 06, 2022 13:05
Yes the Hauppauge is communicating okay with the Windows 10 laptop.
See attached enquiry on it, to check status.
Happy with that or do you need more?

Kurt,

You have two dualHD tuner dongles that identify themselves differently.

Does separate email answer this?
Both of the two dual-tuners (serial number ******78, and ******53) toggle between PID= 0x265/0x8265 these number based on whether IOSCH/Bulk is selected.

One identifies as USB VID (Vendor ID) "2040" PID (Product ID) "0265".
The other as VID "2040" PID "8265".
As above?

The first one you showed us here was USB ID "2040:8265" (8/2) - viewtopic.php?f=67&t=15000#p198381
Originally, it only identified one tuner.
Subsequently you stated it was working after resetting the mode - viewtopic.php?f=67&t=15000#p198389

You showed it again here, but the mode was wrong - viewtopic.php?f=49&t=15014&p=198523#p198528

Apologies. I was over enthusiastic and premature in my excitement and hadn't checked/tested properly obviously at this stage - see my other email.

All four tuners are shown here - viewtopic.php?f=49&t=15014&p=198523#p198543

Yes, it shows they are "enabled", but you can only access A and B and not Hauppauge C and D - thought I had covered this several times?
Please advise if you need any more evidence info which might help, or have I got your comment wrong?

You then used the "other" dongle as the messages file identifies the dongle as having USB ID "2040:0265" -
Code: Select all

I was demonstrating that at last I knew what I was doing and had to show you I was using the correct utility program to properly set the mode for the dual-tuner.
Please advise if you need more info and/or I interpreted your comment correctly?

Jan 1 10:00:34 beyonwizv2 user.info kernel: em28xx: New device HCW dualHD @ 480 Mbps (2040:0265, interface 0, class 0)
You showed that second dongle again here - viewtopic.php?f=49&t=15014&start=49#p198669

Does the above mostly cover and/or do you need more info to set me straight please?

many thanks,
Kurt
(your humble Apprentice)

[Grumpy_Geoff]

Just double-checked.
The Hauppauge toggles PID number, for both dual tuners, depending on mode set:
BULK PID= 0x8265
ISOCH PID= 0x265

Okay, I understand.

Have you at any stage had any live TV/recording working through at least one tuner (likely "C") from either of the Hauppauge tuner dongles?

[KEL]

Yes I did.
Yes, there was one tuner in the dual external working.
By that I mean -the screen displayed A, B C. Think it even displayed D, but it was never colour-illuminated (being accessed).
See also ++ below.

That above is/was what I was trying to get back to (and demonstrate), and then go from there with some further logical steps [and reload new operating system - then try the other dvb firmware (~ 4K version) suggested by a recent post; then, other?]
(may not help - but at least I'll know where the extra proverbial further hits the fan).
Who knows, could help/point-to a future potential fix or other issues ......

I couldn't remember the sequence of events because I was stuffing around with too many things at once and didn't keep a proper check/test /procedure record.
Didn't think I had to, because I guess I thought it was going to be a possible quick fix.

++ I wanted to revert temporarily to the previous Beyonwiz firmware operating system to check whether that was the occasion I had that single tuner of the dual tuner working.
Unfortunately I don't recall taking a screen shot with my phone - I can't provide any evidence (apart from a possible clue in the wording/data of some of my posts).
[None of them (for me) are working now with the new Beyonwiz operating system update and this model/revision of the Hauppauge dual-tuner]

I didn't want to trawl though all my posts to try and work out that moment (maybe I should) - I was also a lot dumber/less-knowledgeable in what I was doing at that stage - this has provided me a crash course in "Beyonwizery"

[Grumpy_Geoff]

I didn't want to trawl though all my posts to try and work out that moment (maybe I should) - I was also a lot dumber/less-knowledgeable in what I was doing at that stage - this has provided me a crash course in "Beyonwizery"

8-Feb - isoc mode, "works"
viewtopic.php?f=67&t=15000#p198389

25/2 - in this current topic, 4 tuners available, only 3 work, you'd updated to 20211010 firmware -

I thought it was set up okay, because 4 tuners are displayed as available.

When it comes to recording though, it too only recognises one of the dual tuners.

I set it to the correct as suggested mode (isochronous);
Have updated to the latest 2021 firmware.

[KEL]

Thanks for finding my own words.

Will have to learn how to do a cut/paste with this system so I can respond to the points more professionally (using this forum's tools)
_topic how to do under FAQ I presume? <sigh> ?

What can I say, other than I don't trust them when it comes to - the date when (a) I made the comments about the number of tuners working and (b) included the comment on the latest 2021 Beyonwiz firmware I am now using.

If everything is the same as before, since I reloaded the Beyonwiz operating system, then I presume I should be seeing the third tuner which I'm not?
I haven't changed anything and the system should be back to square one for the 2021 version now.

A real puzzle.
Will continue investigating/checking/pondering.

Anything else I should/could do?

Which also brings us back to the topic:
How likely are the Hauppauge's being in a different state than they were originally (I changed their driver from the 0.2K to the ~ 10K; now back again). Thought the Beyonwiz firmware reload (which includes the original dvb firmware driver) was supposed sort that too.

Then at some stage if nothing - will revert temporarily to the previous version and check that out again.

Round and round we go ...


--------------------------------------------
KEL wrote: ↑
Sun Mar 06, 2022 19:30
I didn't want to trawl though all my posts to try and work out that moment (maybe I should) - I was also a lot dumber/less-knowledgeable in what I was doing at that stage - this has provided me a crash course in "Beyonwizery"
-----------------------------------------------
8-Feb - isoc mode, "works"
viewtopic.php?f=67&t=15000#p198389

25/2 - in this current topic, 4 tuners available, only 3 work, you'd updated to 20211010 firmware -
KEL wrote: ↑
Fri Feb 25, 2022 23:21
I thought it was set up okay, because 4 tuners are displayed as available.

- Don't trust this because I could have been including previous issue and just notifying I'm using the latest version of the operating system.

When it comes to recording though, it too only recognises one of the dual tuners.

I set it to the correct as suggested mode (isochronous);
Have updated to the latest 2021 firmware.

[KEL]

I reinstalled the previous 2019 Beyonwiz V2 firmware operating system.

It now recognises and records using one of the Hauppauage tuners. Have A B and C available.

It can record on three different frequency channels simultaneously and you are able to view in real-time one of those three being recorded.
It freezes when you try and view a different frequency channel, as expected for three tuners.

So it looks like the issue has crept in (no Hauppauge tuners being available) with the update.

I'll send you the evidence via photos taken from the TV screen.

Kurt

[MrQuade]

So it looks like the issue has crept in (no Hauppauge tuners being available) with the update.

I'll send you the evidence via photos taken from the TV screen.

It might be worth experimenting with that again before you are fully settled in.

Can you try performing an online update to the latest firmware now (rather than a USB update). I'd be interested to see if this still breaks the tuner function.

All very strange!

[KEL]

Okay; shall do an online upgrade ASAP.

Might be a few days delay; now have a couple of other things to sort. when it rains it pours ... !

[KEL]

Did an online update (instead of USB stick).

No change, same issue.

Previous results attached (Screenshots).

[MrQuade]

Ok, the latest update seems to have introduced a regression of some sort. How odd.

Looks like the driver needs some proper love and attention in any case, since no firmware version seems to be able to access the fourth tuner of this new USB model tuner anyway.

I really don't think there is much left to do other than to petition the folks in one of the upstream projects to work on the drivers (someone who is savvy with working with software at that low level and has the appropriate contacts).

[KEL]

Understood.

Hope you manage to find a suitable candidate(s) to resolve the issue.

I haven't tried the other 4K driver to replace the 0.2K version firmware, suggested by "adoxa".

Perhaps I'll also give that experiment a go too, … nothing to lose …

thanks again.