Bonjour. je suis désolé, je parle et écris très mal l’anglais. je m’aide avec un traducteur.
je pose la question ici car je ne trouve pas la solution sur les site en français.
je veux faire un serveur avec un RPI3 et volumio 2.348.
je voudrais faire sortir le signal par un port usb du RPI et le faire aller vers l’entrée usb de mon lecteur cd (Métronome technology CD8). le dac du lecteur cd n’est pas reconnu. comment faire?
merci pour l’aide.
Hello. I’m sorry, I speak and write English very badly. I help myself with a translator.
I ask the question here because I do not find the solution on the site in French.
I want to make a server with a RPI3 and volumio 2.348.
I would like to output the signal via a USB port of the RPI and make it go to the USB input of my CD player (metronome technology CD8). the dac of the cd player is not recognized. how to do?
thanks for the help.
I have the impression that the dac is not recognized.
before doing the command aplay -l, I had reset the system. there is an external USB mounted hard drive containing the music and I have assigned an ipfixe. I disabled the wifi, hotspot and custom dns.
sorry, I do not know much about linux. you just have to explain things to me. :mrgreen:
hm… it seems indeed that the DAC is not recognized. At least not by Alsa. You use ‘lsusb’ (with -v option for more details) to see if something is seen at USB device level.
I never heard of your CD player so I had to look it up, impressive!. Quick info I found:
The Amanero chip should be supported as it is used in more DAC’s, etc. that do work.
You might want to consider try using the S/P DIFF input (with something like the Allo DigiOne for example) as an alternative.
In theory Async USB could be better but that really depends on the USB to I2S implementation and where the main clock signals are generated. And I do not know enough about the implementation in your CD-player/DAC.
the cd8 (hifilink.fr/boutique/source … logie-cd8/) have a usb digital input (USB type B asynchronous allowing to stream directly music files stored on a computer (Mac & PC) and compatible with high resolution signals such as the HD_Master (24bit / 192kHz).
the cd8 have a digital output RCA S/PDIF 75 Ohms 16bit/44.1kHz.
with the command Iusb -v here is the answer
Bus 001 Device 005: ID 0480:a202 Toshiba America Info. Systems, Inc.
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0480 Toshiba America Info. Systems, Inc.
idProduct 0xa202
bcdDevice 3.15
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Bus 001 Device 004: ID 249c:9002
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x249c
idProduct 0x9002
bcdDevice 0.01
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 0
iConfiguration 0
bmAttributes 0x60
(Missing must-be-set bit!)
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0xec00 SMSC9512/9514 Fast Ethernet Adapter
bcdDevice 2.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 2 TT per port
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0x9514
bcdDevice 2.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 1 Single TT
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 2 TT per port
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.09
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Your DAC/CD appears to be the second device in the USB list (idVendor: 249c, idProduct: 9002) and it’s referenced in the linux kernel config here.. Now what I don’t know is how that is translated into getting ALSA to recognise it … hopefully someone more knowledgeable will be able to chip in.
thank’s chsims1, it’s reassuring if the dac is spotted. now you have to turn that into lines of code, I think. I followed the link but … I need help to intervene. I am obliged to be absent until 4 pm.
@dom2, if you run the ‘lsusb -v’ command with root privileges (do ‘sudo lsusb -v’) you get some more info.
So your CD-player/DAC is not using the Amanero but the M2Tech hiFace USB-SPDIF converter which translates the USB signal to S/P DIFF and further down the chain, the S/P DIFF signal gets translated to I2S to be processed by the actual DAC chip.
As the signal does get converted to S/P DIFF anyway (and not directly to I2S), I would suggest feeding it S/P DIFF directly instead of via USB (also taking out a conversion step). Also as the Raspberry Pi is known in a negative way for its not so good USB signals (the Pi has internally an on-to-go USB adapter and not a fully implemented USB stack).
In theory, it could work but I do not know also how to solve the Alsa issue.
But I think even if you get it to work, feeding your high-quality CD-player/DAC with a quality S/P DIFF signal will give you a more satisfactory result
As the device is recognized, the question is if the correct driver(s) can be loaded. Can you do a ‘sudo lsmod’ to see which modules are loaded into the kernel. We need to see if the correct kernel module can be found, if their is one present on the system anyway.
sorry, I do not know what happened to have a duplicate message.
edit : on this page (m2tech-hiface-dac-t7248.html) it is noted ; ‘The M2TECH hiFace DAC USB is playing fine with RasPi1 under Volumio 2.246’ but i’s not indicated v1 or v2
Hi, unfortunately older versions of Hiface USB transport are not working with Volumio Out of the box.
You can however recompile the drivers for Hiface 1 (I think this is your case), by doing
volumio kernelsource
from ssh
and then carriying on with the instructions on the repo you linked. Linux skills are definetely a must here, since its quite a complex task…
Let us know how it goes
ok, michelangelo. so if I understand correctly, the cd player has a Hiface v1 interface that is not compatible with the Hiface v2 interface. I would have to recompile v1 in v2 … which I do not know how to do. I can do things but that’s too complex for me. I will inquire.
EDIT : I give up for the moment. I’m going to settle for a dac hifiberry. I contacted Metronome Technology and he should give it an answer in 3-4 days. a few months ago i had work the dac of cd8 with rapsberry but with raspian if my memories are good. I will retry and communicate to you the manipulations; so you will tell me if I can transpose, thanks for your help.
