[rfehr]

You are using a USB-Soundcard ?

I unplugged it already to focus on the USB audio hub problem.

?

what audio ouput device you want to use

[gr4vity]

You are using a USB-Soundcard ?

I unplugged it already to focus on the USB audio hub problem.

?

what audio ouput device you want to use

I want to use the Logitech USB audio hub

[  763.865077] usb 1-3: new high-speed USB device number 8 using ehci-pci
[  763.984506] usb 1-3: New USB device found, idVendor=05e3, idProduct=0607
[  763.984507] usb 1-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[  763.984509] usb 1-3: Product: USB2.0 Hub
[  763.984922] hub 1-3:1.0: USB hub found
[  763.985256] hub 1-3:1.0: 4 ports detected
[  764.256156] usb 1-3.4: new full-speed USB device number 9 using ehci-pci
[  764.351724] usb 1-3.4: New USB device found, idVendor=046d, idProduct=0a0e
[  764.351726] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  764.351727] usb 1-3.4: Product: AudioHub Speaker
[  764.351728] usb 1-3.4: Manufacturer: HOLTEK
[  764.374155] input: HOLTEK  AudioHub Speaker as /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.4/1-3.4:1.2/0003:046D:0A0E.0004/input/input15
[  764.426269] hid-generic 0003:046D:0A0E.0004: input,hidraw0: USB HID v1.10 Device [HOLTEK  AudioHub Speaker] on usb-0000:00:1d.7-3.4/input2

By the way that audio hub volume control works fine on Ubuntu and Raspbian stretch.

[rfehr]

Hi gr4vity,

do you know which driver is necessary for linux,
for your usb-audio devive?

Because I think that's the problem, that the correct driver does not exist.

best regrads
  Roland

[clausmuus]

Since it works with xineliboutput, it can't be a driver problem.
And why do you want to use PT?

[gr4vity]

Since it works with xineliboutput, it can't be a driver problem.
And why do you want to use PT?

Because xineliboutput works with PT USB, if PT isn't used it won't work.

Edit: Now i can't change volume using keyboard either.

I think it's a driver problem as Roland wrote.

I deleted the previous reply because i think it looks silly.

[MarMic]

I am with claus! it can't be a driver problem!

I am not sure if you are 100% clear with the PT definition?! PT means that the whole audio is PASSTHROUGHED to the audio decoder device (AVR or something else)
You are not able to change audio volume or something else on the VDR side because "in hard words" the VDR has no more audio data on its side.
The audio is fully transfered to the audio decoder. In your case USB speakers.

Are you sure you want PT? or just audio on the USB speakers?

Best regards

MarMic

[gr4vity]

If it's not a driver problem then how come it's fully working on Ubuntu and Raspbian stretch?
The audio hub volume control and mute button works.

Regarding MLD, it works with xineliboutput by selecting PT USB and i used to control the volume using keyboard but this doesn't work anymore.

With SHD there is no audio.

I just need it to work with PT or without it ... it's not the issue.

Is xineliboutput and SHD are using the same alsa?or the latter using pulseaudio?

@rfehr, how to determine which driver is necessary for linux?
Is it by using lsusb -t
?

Best regards

[MarMic]

If it's not a driver problem then how come it's fully working on Ubuntu and Raspbian stretch?
The audio hub volume control and mute button works.

init scripts - other backends - WHATEVER.

try it with everything default settings AND just change the alsa output device in webif (xorg restart/vdr restart needed)

[gr4vity]

If it's not a driver problem then how come it's fully working on Ubuntu and Raspbian stretch?
The audio hub volume control and mute button works.

init scripts - other backends - WHATEVER.

try it with everything default settings AND just change the alsa output device in webif (xorg restart/vdr restart needed)

Okay, i will do that.
 
Here is lsusb -t on RP.
pi@raspberrypi:~ $ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
        |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 4: Dev 6, If 1, Class=Audio, Driver=snd-usb-audio, 12M
            |__ Port 4: Dev 6, If 2, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 4: Dev 6, If 0, Class=Audio, Driver=snd-usb-audio, 12M

Best regards

[gr4vity]

It finally worked! 
I had to select USB and Analog to make it work as in screenshot.

I can control volume using keyboard (that controls volume for the headphones and the USB audiohub at the same time).

It's strange but better than no sound at all!

Thanks to you all for helping.

If there is anything i can do to use the USB audiohub volume control please let me know.

Note: basically if i want to use keyboard to control the volume i have to select "Volume control : Software" in xineliboutput and SHD
If i selected Hardware i won't be able to decrease the volume because the USB audiohub volume control is not recognized.

Best regards

[clausmuus]

That's often normal, that you must select "software" for volume control.

[gr4vity]

That's often normal, that you must select "software" for volume control.

I got it,
I tried another USB headset, i still can't use the hadrware volume control.
So the problem isn't related to that USB audiohub, it seems that MLD can't recognize any USB volume control (whether it's a USB headset or else)

I had included the USB headset and volume control pictures in the attachments.

[MarMic]

Maybe there are some Missing Hid drivers. But maybe there is Just No Event recognitian. Have you Made some Tests with evtest?

[gr4vity]

Maybe there are some Missing Hid drivers. But maybe there is Just No Event recognitian. Have you Made some Tests with evtest?

Thank you for replying MarMic,
I tried evtest
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0xa18 version 0x100
Input device name: "Logitech Logitech H360 Headset"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1516141136.673625, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1516141136.673625, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1516141136.673625, -------------- SYN_REPORT ------------
Event: time 1516141136.801649, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1516141136.801649, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
Event: time 1516141136.801649, -------------- SYN_REPORT ------------
Event: time 1516141137.729791, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00ea
Event: time 1516141137.729791, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1
Event: time 1516141137.729791, -------------- SYN_REPORT ------------
Event: time 1516141137.857815, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00ea
Event: time 1516141137.857815, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0
Event: time 1516141137.857815, -------------- SYN_REPORT ------------

Volume Up & Down events are recognized but VDR doesn't respond at all and the volume bar isn't shown when i hit any of them.

So is it missing Hid drivers?

Best regards

[gr4vity]

Here is evtest for the USB audiohub

Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0xa0e version 0x110
Input device name: "HOLTEK  AudioHub Speaker"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1516142596.240987, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1516142596.240987, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1516142596.240987, -------------- SYN_REPORT ------------
Event: time 1516142596.273008, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1516142596.273008, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
Event: time 1516142596.273008, -------------- SYN_REPORT ------------
Event: time 1516142598.930462, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00ea
Event: time 1516142598.930462, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1
Event: time 1516142598.930462, -------------- SYN_REPORT ------------
Event: time 1516142598.962480, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00ea
Event: time 1516142598.962480, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0
Event: time 1516142598.962480, -------------- SYN_REPORT ------------
Event: time 1516142603.028681, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e2
Event: time 1516142603.028681, type 1 (EV_KEY), code 113 (KEY_MUTE), value 1
Event: time 1516142603.028681, -------------- SYN_REPORT ------------
Event: time 1516142603.028692, type 1 (EV_KEY), code 113 (KEY_MUTE), value 0
Event: time 1516142603.028692, -------------- SYN_REPORT ------------