2011/3/21 Vieri <[email protected]> > > There doesn't seem to be any .asoundrc file. > > My FHM1.liq script is now: > > #!/usr/bin/liquidsoap > set("log.file.path","/tmp/FHM1-radio.log") > myplaylist = playlist("/SAMBA/MediaStream/radio1/playlist.txt") > security = single("/SAMBA/MediaStream/radio1/announcement1.ogg") > radio = myplaylist > radio = fallback(track_sensitive = false, [radio, security]) > output.alsa(radio, device="hw:0,0") >
I've seen strangeness in the way liquidsoap accesses audio devices by name. And there's not very good error output unless you're using gdb, which I've also resorted to many times. Using .asoundrc in the liquidsoap user's directory has helped me, but even then with complex .asoundrc files I still get some errors in resolving alsa devices which result in the unknown error. Almost seems like if I use dmix in my .asoundrc I get failures (that's not relavent to your problem though) > > 2011/03/21 10:27:13 [src_5048:3] Switch to playlist(dot)txt with transition. > 2011/03/21 10:27:13 [output(dot)alsa:3] Using ALSA 1.0.21a. > 2011/03/21 10:27:13 [threads:1] Thread "output(dot)alsa" aborts with > exception Alsa.Unknown_error(2)! > 2011/03/21 10:27:13 [main:3] Shutdown started! > 2011/03/21 10:27:13 [main:3] Waiting for threads to terminate... > 2011/03/21 10:27:13 [stderr:3] Thread 5 killed on uncaught exception > Alsa.Unknown_error(2) > 2011/03/21 10:27:13 [stderr:3] Raised at file "", line 0, characters 0-0 > 2011/03/21 10:27:13 [root:3] Shutting down sources... > 2011/03/21 10:27:13 [src_5045:3] Finished with > "/SAMBA/MediaStream/radio1/announcement1.ogg". > 2011/03/21 10:27:13 [playlist(dot)txt:3] Finished with > "/SAMBA/MediaStream/radio1/fpm-sunshine.ogg". > 2011/03/21 10:27:13 [threads:3] Thread "root" exited (0 remaining). > 2011/03/21 10:27:13 [main:3] Cleaning downloaded files... > 2011/03/21 10:27:13 >>> LOG END > > I don't know what Alsa.Unknown_error(2) is. > > # aplay -l > **** List of PLAYBACK Hardware Devices **** > card 0: SB [HDA ATI SB], device 0: HDA Generic [HDA Generic] > Subdevices: 1/1 > Subdevice #0: subdevice #0 I suggest using the aplay external output wrapper if you're still having problems. http://savonet.sourceforge.net/doc-1.0.0-beta1/external_encoders.html That has worked very well for me to use things like dmixed outputs (or just plain ugly .asoundrc configs). I still can't grasp alsa syntax after all these years. Another thing that has helped my alsa outputs is using output from 'aplay -L' and then specifying those devices with a plug:<device>, like so: [user@lx-megastation ~]# aplay -L null Discard all samples (playback) or generate zero samples (capture) analog Analog Output - Use analog outputs, converting samples, format, and rate as necessary. mixed-analog Mixed Analog Output - Use analog outputs, converting samples, format, and rate as necessary. Allows mixing with system sounds. digital Digital Output - Use digital outputs, converting samples, format, and rate as necessary. mixed-digital Mixed Digital Output - Use digital outputs, converting samples, format, and rate as necessary. Allows mixing with system sounds. front:CARD=ICE1724,DEV=0 ICEnsemble ICE1724, ICE1724 Front speakers surround40:CARD=ICE1724,DEV=0 ICEnsemble ICE1724, ICE1724 4.0 Surround output to Front and Rear speakers surround41:CARD=ICE1724,DEV=0 ICEnsemble ICE1724, ICE1724 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=ICE1724,DEV=0 ICEnsemble ICE1724, ICE1724 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=ICE1724,DEV=0 ICEnsemble ICE1724, ICE1724 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=ICE1724,DEV=0 ICEnsemble ICE1724, ICE1724 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=ICE1724,DEV=0 ICEnsemble ICE1724, ICE1724 IEC958 (S/PDIF) Digital Audio Output Then specify the device in liquidsoap like this: output.alsa(device="plug:front") -OR- output.alsa(device="plug:iec958") -- Chris Everest ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
