OP25 Boatbod Success! Almost...

Status
Not open for further replies.

sqlgeek

Member
Joined
Jun 21, 2014
Messages
33
Location
Griffin, GA
I've tried all of the suggestions but I still cannot get the op25-liq.service to start automatically. I can start it manually after re-boot and it works fine and the stream starts. The service is loaded and enabled but it never goes active. The OP25-rx service is working fine...Otherwise I get this when checking the op25.liq systemctl status:

systemctl status op25-liq.service
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset:
Active: inactive (dead) since Sun 2019-09-15 14:11:08 CDT; 11min ago
Process: 435 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status
Main PID: 435 (code=exited, status=0/SUCCESS)

Sep 15 14:11:04 raspberrypi systemd[1]: Started op25-liq.
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:08 >>> LOG START
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:06 [main:3] Liquid
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:06 [main:3] Using:
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:07 [gstreamer.load
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:07 [dynamic.loader
Sep 15 14:11:08 raspberrypi liquidsoap[435]: strange error flushing buffer ...
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:08 >>> LOG END
Sep 15 14:11:08 raspberrypi systemd[1]: op25-liq.service: Succeeded.
lines 1-15/15 (END)...skipping...
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2019-09-15 14:11:08 CDT; 11min ago
Process: 435 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status=0/SUCCESS)
Main PID: 435 (code=exited, status=0/SUCCESS)

Sep 15 14:11:04 raspberrypi systemd[1]: Started op25-liq.
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:08 >>> LOG START
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:06 [main:3] Liquidsoap 1.3.3
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:06 [main:3] Using: bytes=[distributed with OCaml 4.02 or above] pcre=7.2.3 dtools=0.4.0 duppy=0.7.2 duppy.syntax=0.7.2 cry=
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:07 [gstreamer.loader:3] Loaded GStreamer 1.14.4 0
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:07 [dynamic.loader:3] Could not find dynamic module for fdkaac encoder.
Sep 15 14:11:08 raspberrypi liquidsoap[435]: strange error flushing buffer ...
Sep 15 14:11:08 raspberrypi liquidsoap[435]: 2019/09/15 14:11:08 >>> LOG END
Sep 15 14:11:08 raspberrypi systemd[1]: op25-liq.service: Succeeded.

Can you post what you get running the same command after startup but before you manually run the .liq? Trying to see what errors it is giving you.
 

DMBFireman

Member
Feed Provider
Joined
Dec 19, 2002
Messages
129
Location
Flower Mound, TX
This is not the issue because I get the same exact error whether I run it manually or by service and my audio feed never fails - it works fine without having the AAC codec. His audio is working when he runs it manually but not when he starts it as a service, so if the missing codec were the issue it wouldn't work ever.

@DMBFireman - what are the permissions set to on your .liq file
Code:
ls -lt *.liq
And are you logged in as pi when you run it manually?

when I check the permissions using your command I get the following:

-rxwr -xr -x 1 pi pi 1259 Sep 8 17:25 LFD_Stream.liq
 

DMBFireman

Member
Feed Provider
Joined
Dec 19, 2002
Messages
129
Location
Flower Mound, TX
Also here is what I get running systemctl status right after startup before I manually start the .liq file:

systemctl status op25-liq.service
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset:
Active: inactive (dead) since Thu 2019-09-26 11:08:29 CDT; 7min ago
Process: 438 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status
Main PID: 438 (code=exited, status=0/SUCCESS)

Sep 26 11:08:24 raspberrypi systemd[1]: Started op25-liq.
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:29 >>> LOG START
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:27 [main:3] Liquid
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:27 [main:3] Using:
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:28 [gstreamer.load
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:28 [dynamic.loader
Sep 26 11:08:29 raspberrypi liquidsoap[438]: strange error flushing buffer ...
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:29 >>> LOG END
Sep 26 11:08:29 raspberrypi systemd[1]: op25-liq.service: Succeeded.
lines 1-15/15 (END)...skipping...
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2019-09-26 11:08:29 CDT; 7min ago
Process: 438 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status=0/SUCCESS)
Main PID: 438 (code=exited, status=0/SUCCESS)

Sep 26 11:08:24 raspberrypi systemd[1]: Started op25-liq.
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:29 >>> LOG START
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:27 [main:3] Liquidsoap 1.3.3
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:27 [main:3] Using: bytes=[distributed with OCaml 4.02 or above] pcre
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:28 [gstreamer.loader:3] Loaded GStreamer 1.14.4 0
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:28 [dynamic.loader:3] Could not find dynamic module for fdkaac encod
Sep 26 11:08:29 raspberrypi liquidsoap[438]: strange error flushing buffer ...
Sep 26 11:08:29 raspberrypi liquidsoap[438]: 2019/09/26 11:08:29 >>> LOG END
Sep 26 11:08:29 raspberrypi systemd[1]: op25-liq.service: Succeeded.
~
~
~
~
~
 

sqlgeek

Member
Joined
Jun 21, 2014
Messages
33
Location
Griffin, GA
That's really odd - it appears that it is working. If you that command again the next time you start up, change the 438 out to whatever PID it shows on the fresh start up and do a:
Code:
ps -e | grep 438
but replace the 438 with the new PID number.
 

DMBFireman

Member
Feed Provider
Joined
Dec 19, 2002
Messages
129
Location
Flower Mound, TX
That's really odd - it appears that it is working. If you that command again the next time you start up, change the 438 out to whatever PID it shows on the fresh start up and do a:
Code:
ps -e | grep 438
but replace the 438 with the new PID number.

what command are you talking about? I don't really understand what you posted but yes this is very frustrating. Everything is working except the stream will not start until I manually start the .liq file. I wanted to image the SD card so I would have a working image of this to use in the future but I'd really like the auto-start to be working first. Thanks for your help!
 

sqlgeek

Member
Joined
Jun 21, 2014
Messages
33
Location
Griffin, GA
what command are you talking about? I don't really understand what you posted but yes this is very frustrating. Everything is working except the stream will not start until I manually start the .liq file. I wanted to image the SD card so I would have a working image of this to use in the future but I'd really like the auto-start to be working first. Thanks for your help!
Sorry - I was talking about this one:
Code:
systemctl status op25-liq.service
If you've already started it manually you would need to wait until the next time you reboot the Pi.
 

DMBFireman

Member
Feed Provider
Joined
Dec 19, 2002
Messages
129
Location
Flower Mound, TX
I followed your directions and changed the PID but it didn't do anything. Still will not start up when I re-boot. Only way the stream starts is if I manually run the .liq file. I guess it's just not going to auto-start. The only thing different I noticed is after startup the PID had changed to a different number but the rest of this still looks the same:

systemctl status op25-liq.service
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset:
Active: inactive (dead) since Wed 2019-10-09 09:39:21 CDT; 1min 21s ago
Process: 428 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status
Main PID: 428 (code=exited, status=0/SUCCESS)

Oct 09 09:39:17 raspberrypi systemd[1]: Started op25-liq.
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG START
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Liquid
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Using:
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [gstreamer.load
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [dynamic.loader
Oct 09 09:39:21 raspberrypi liquidsoap[428]: strange error flushing buffer ...
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG END
Oct 09 09:39:21 raspberrypi systemd[1]: op25-liq.service: Succeeded.
lines 1-15/15 (END)...skipping...
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2019-10-09 09:39:21 CDT; 1min 21s ago
Process: 428 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status=0/SUCCESS)
Main PID: 428 (code=exited, status=0/SUCCESS)

Oct 09 09:39:17 raspberrypi systemd[1]: Started op25-liq.
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG START
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Liquidsoap 1.3.3
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Using: bytes=[distributed with OCaml 4.02 or above] pc
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [gstreamer.loader:3] Loaded GStreamer 1.14.4 0
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [dynamic.loader:3] Could not find dynamic module for fdkaac enc
Oct 09 09:39:21 raspberrypi liquidsoap[428]: strange error flushing buffer ...
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG END
Oct 09 09:39:21 raspberrypi systemd[1]: op25-liq.service: Succeeded.
 

sqlgeek

Member
Joined
Jun 21, 2014
Messages
33
Location
Griffin, GA
I followed your directions and changed the PID but it didn't do anything. Still will not start up when I re-boot. Only way the stream starts is if I manually run the .liq file. I guess it's just not going to auto-start. The only thing different I noticed is after startup the PID had changed to a different number but the rest of this still looks the same:

systemctl status op25-liq.service
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset:
Active: inactive (dead) since Wed 2019-10-09 09:39:21 CDT; 1min 21s ago
Process: 428 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status
Main PID: 428 (code=exited, status=0/SUCCESS)

Oct 09 09:39:17 raspberrypi systemd[1]: Started op25-liq.
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG START
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Liquid
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Using:
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [gstreamer.load
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [dynamic.loader
Oct 09 09:39:21 raspberrypi liquidsoap[428]: strange error flushing buffer ...
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG END
Oct 09 09:39:21 raspberrypi systemd[1]: op25-liq.service: Succeeded.
lines 1-15/15 (END)...skipping...
● op25-liq.service - op25-liq
Loaded: loaded (/etc/systemd/system/op25-liq.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2019-10-09 09:39:21 CDT; 1min 21s ago
Process: 428 ExecStart=/usr/bin/liquidsoap LFD_Stream.liq (code=exited, status=0/SUCCESS)
Main PID: 428 (code=exited, status=0/SUCCESS)

Oct 09 09:39:17 raspberrypi systemd[1]: Started op25-liq.
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG START
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Liquidsoap 1.3.3
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:19 [main:3] Using: bytes=[distributed with OCaml 4.02 or above] pc
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [gstreamer.loader:3] Loaded GStreamer 1.14.4 0
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 [dynamic.loader:3] Could not find dynamic module for fdkaac enc
Oct 09 09:39:21 raspberrypi liquidsoap[428]: strange error flushing buffer ...
Oct 09 09:39:21 raspberrypi liquidsoap[428]: 2019/10/09 09:39:21 >>> LOG END
Oct 09 09:39:21 raspberrypi systemd[1]: op25-liq.service: Succeeded.
I wish I could be of more help but I've exhausted my limited knowledge on this - hoping someone else can help...
 

boatbod

Member
Joined
Mar 3, 2007
Messages
3,316
Location
Talbot Co, MD
It's almost certainly something trivial that is wrong, but I don't have much in the way of debugging suggestions beyond having someone log in remotely and take a look.
 

mkmer

Member
Joined
Jun 11, 2019
Messages
7
I'm curious if you have figured out the "robot" sound problem. I've recently copied a working copy of OP25 from a RPI3 to a RPI 4 and have the robot for audio problem. I'm thinking it's an RPI4 issue.
 

sqlgeek

Member
Joined
Jun 21, 2014
Messages
33
Location
Griffin, GA
I'm curious if you have figured out the "robot" sound problem. I've recently copied a working copy of OP25 from a RPI3 to a RPI 4 and have the robot for audio problem. I'm thinking it's an RPI4 issue.
I purchased a cheap USB sound card from Amazon after reading a post that stated it helped them and that was the solution for me. It's something to do with the internal audio. This was on a RPI3B+

DSYJ Channel USB External Sound Card Audio Adapter
 

mkmer

Member
Joined
Jun 11, 2019
Messages
7
Thanks for the update. I can report that there is an issue with the built in audio player on RPI4. Simply connecting to the udp stream produces perfect audio, while the internal player sounds like a slow robot. Fairly simple work around.
 

boatbod

Member
Joined
Mar 3, 2007
Messages
3,316
Location
Talbot Co, MD
Thanks for the update. I can report that there is an issue with the built in audio player on RPI4. Simply connecting to the udp stream produces perfect audio, while the internal player sounds like a slow robot. Fairly simple work around.

How are you connecting to the UDP stream? Are you using audio.py or some other method?
 

mkmer

Member
Joined
Jun 11, 2019
Messages
7
I'm running a seperate thread of "nc | aplay" method, on the same RPI4 (not remote).
 
Status
Not open for further replies.
Top