10-18-2022, 02:45 PM
@felix
Aha, you have some Linux command-line skills.
Here's some nitty gritty details. Yours should be substantially similar in name, location, permissions, etc.
Preliminaries
1. The install script places two files in the directory /etc/systemd/system
Example from my player
The script also places two files in the directory /usr/local/bin
When the USB CD drive is plugged in
The syslog (/var/log/syslog) or dmesg output should show it has been recognized. Here is the relevant dmesg output when I plugged in the LG drive mentioned in the github README.
Note that it is identified as sr0 and includes "cdda" (audio CD) and "tray" among its attributes.
Note also, the cdrom driver is invoked. When an audio CD is inserted in the drive, a new device link should appear. For my system
As you can see, it is a symlink to the correct drive.
When an audio CD is inserted in the drive
The addaudiocd.service should be invoked. Here is a snippet from my system log (/var/log/syslog)
[Probably should fix the harmless UNIT issue but as the syslog shows, it's ignored.]
MPD proceeds to index the tracks on the audio CD.
and that's what appears on the moOdeUI display.
Regards,
Kent
Aha, you have some Linux command-line skills.
Here's some nitty gritty details. Yours should be substantially similar in name, location, permissions, etc.
Preliminaries
1. The install script places two files in the directory /etc/systemd/system
Example from my player
Code:
pi@m82x64b:~ $ ls -l /etc/systemd/system/*audiocd*.service
-rw-r--r-- 1 root root 138 Oct 15 22:38 /etc/systemd/system/addaudiocd.service
-rw-r--r-- 1 root root 137 Oct 15 22:38 /etc/systemd/system/remaudiocd.service
The script also places two files in the directory /usr/local/bin
Code:
pi@m82x64b:~ $ ls -l /usr/local/bin/*audiocd*
-rwxr-xr-x 1 root root 503 Oct 15 22:38 /usr/local/bin/addaudiocd.sh
-rwxr-xr-x 1 root root 341 Oct 15 22:38 /usr/local/bin/remaudiocd.sh
When the USB CD drive is plugged in
The syslog (/var/log/syslog) or dmesg output should show it has been recognized. Here is the relevant dmesg output when I plugged in the LG drive mentioned in the github README.
Code:
[ 124.040149] usb 1-1.3: new high-speed USB device number 5 using xhci_hcd
[ 124.145609] usb 1-1.3: New USB device found, idVendor=0e8d, idProduct=1887, bcdDevice= 0.00
[ 124.145627] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 124.145633] usb 1-1.3: Product: Portable Super Multi Drive
[ 124.145639] usb 1-1.3: Manufacturer: Hitachi-LG Data Storage Inc
[ 124.145644] usb 1-1.3: SerialNumber: M03J3E12019
[ 124.149939] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 124.151509] scsi host0: usb-storage 1-1.3:1.0
[ 125.185580] scsi 0:0:0:0: CD-ROM HL-DT-ST DVDRAM GP65NB60 PF00 PQ: 0 ANSI: 0
[ 125.202724] scsi 0:0:0:0: Attached scsi generic sg0 type 5
[ 125.223416] sr 0:0:0:0: Power-on or device reset occurred
[ 125.232137] sr 0:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 125.232152] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 125.238856] sr 0:0:0:0: Attached scsi CD-ROM sr0
Note that it is identified as sr0 and includes "cdda" (audio CD) and "tray" among its attributes.
Note also, the cdrom driver is invoked. When an audio CD is inserted in the drive, a new device link should appear. For my system
Code:
pi@m82x64b:~ $ ls -l /dev/cdrom
lrwxrwxrwx 1 root root 3 Oct 18 10:10 /dev/cdrom -> sr0
As you can see, it is a symlink to the correct drive.
When an audio CD is inserted in the drive
The addaudiocd.service should be invoked. Here is a snippet from my system log (/var/log/syslog)
Code:
Oct 18 10:10:25 m82x64b systemd[1]: /etc/systemd/system/addaudiocd.service:1: Unknown section 'UNIT'. Ignoring.
Oct 18 10:10:25 m82x64b systemd[1]: Started addaudiocd.service.
Oct 18 10:10:25 m82x64b systemd[1]: addaudiocd.service: Succeeded.
[Probably should fix the harmless UNIT issue but as the syslog shows, it's ignored.]
MPD proceeds to index the tracks on the audio CD.
Code:
pi@m82x64b:~ $ mpc playlist
cdda:///1
cdda:///2
cdda:///3
cdda:///4
cdda:///5
cdda:///6
cdda:///7
cdda:///8
cdda:///9
cdda:///10
cdda:///11
cdda:///12
cdda:///13
cdda:///14
cdda:///15
cdda:///16
cdda:///17
cdda:///18
and that's what appears on the moOdeUI display.
Regards,
Kent