Broadcastify Raspberry Pi Feed Appliance Image v1.0 (BETA)

[pagerman0219]

And - WORKING
I needed to run that script and blow out all the old configs.
Started over and it works!
Thank you so much for your help!

 

[pagerman0219]

Here is the setup:

 

[blantonl]

OK, I've rolled out a fix v1.04 which will add this config entry for USB changes.

However, running more than 3 feeds on a Rpi has always been problematic. Your mileage may vary based on soundcards, power supplies, and use of external hubs.

Thanks for your help troubleshooting. If for some reason an issue crops up try disabling feed #4. I've always had problems running more than 3 feeds on Rpi hardware.

 

[jodfie]

@blantonl could this script be modified to run on 64bit? Any of the default installed things require 32bit?

 

[blantonl]

@blantonl could this script be modified to run on 64bit? Any of the default installed things require 32bit?

I don’t have any plans to roll out 64 bit support at this time, I’m sorry.

 

[DC31]

Just some notes from my experimentation, Lindsay:

This is on an old Pi2.

1. Set up a single stream from a usb sound card using darkice. Worked fine. I had the card enumeration problem at first but this seemed to have corrected itself without updating.

2. Much to my surprise GQRX would load and run on this pi2. The processor load was quite high but it ran and showed the waterfall at low sampling rates. I never thought that GQRX would run on a pi2. I thought that it required a pi4.

3. I then tried rtl_airband. This also ran quite well with much more acceptable processor load (~50%).

4. Both 2 & 3 above were using the first image you posted for downloading. This morning I read the rest of the forum posts and ran the update utility. Now both GQRX and rtl_airband lock up just after starting. The pi remains responsive but neither of the programs.

5. I had saved the original image to disk. So I reflashed the SD card with the original image and now both GQRX and rtl_airband are again working. It might have been some little setting that I had tweaked that was keeping them from working, but I made numerous attempts and checked all of them I thought.

JIm

 

[blantonl]

DC31, the lockups are probably due to the USB changes I rolled out for more than 2 feeds on the device.

I'm going to back out those changes in the update and make it a manual configuration item. The use case where someone is providing more than 2 feeds is going to be extremely rare.

 

[racer38]

I have read through everything and for some reason I cant get both feeds operational. I only have 2 feeds, I am using the recommended Sabrent sound cards. Here is a screen shot of the status page.

 

[blantonl]

I have read through everything and for some reason I cant get both feeds operational. I only have 2 feeds, I am using the recommended Sabrent sound cards. Here is a screen shot of the status page.

Questions:

1) What raspberry Pi are you using?
2) Have you updated the BCFY shell to the latest version?
3) What does the darkice log report for your feed that isn't working? (/home/pi/bcfy/logs)

 

[racer38]

Flashed a new image, did the update. Using a Pi 3B+ Configured for single feed for now. Below is the log. Now just a single feed doesnt work.

Using config file: /home/pi/bcfy/configs/darkice/darkice_1.cfg
20-Apr-2021 13:33:51 Using ALSA DSP input device: plughw:1,0
20-Apr-2021 13:33:51 buffer size: 441000
20-Apr-2021 13:33:51 encoding
20-Apr-2021 13:33:51 Using POSIX real-time scheduling, priority 4
DarkIce: DarkIce.cpp:1272: can't open connector [0]
20-Apr-2021 13:33:51 HTTP/1.0 200

 

[blantonl]

Flashed a new image, did the update. Using a Pi 3B+ Configured for single feed for now. Below is the log. Now just a single feed doesnt work.

Using config file: /home/pi/bcfy/configs/darkice/darkice_1.cfg
20-Apr-2021 13:33:51 Using ALSA DSP input device: plughw:1,0
20-Apr-2021 13:33:51 buffer size: 441000
20-Apr-2021 13:33:51 encoding
20-Apr-2021 13:33:51 Using POSIX real-time scheduling, priority 4
DarkIce: DarkIce.cpp:1272: can't open connector [0]
20-Apr-2021 13:33:51 HTTP/1.0 200

Can you open a shell and report back the results for the two commands:

arecord -l

aplay -l

Paste the output and let me know.

 

[Mark181]

How can I get Broadcastify Shell without installing the image? Or is that not possible?

Or is there no point.

 

[blantonl]

How can I get Broadcastify Shell without installing the image? Or is that not possible?

Or is there no point.

i'm not supporting the BCFY Shell anywhere other than the the image. you are completely on your own for that.

 

[Mark181]

i'm not supporting the BCFY Shell anywhere other than the the image. you are completely on your own for that.

And what are the benefits of having the BCFY Shell?

Also, do you plan on adding TTD to the image in the future? As well as automated starting and restarting of the applications?

 

[DC31]

And what are the benefits of having the BCFY Shell?

Also, do you plan on adding TTD to the image in the future? As well as automated starting and restarting of the applications?

Moshe,

image a card and take it for a test drive. And read the WIKI, it us pretty obvious what the advantages are. It makes it much easier for a beginner to get started. Auto start and restart is included.

 

[racer38]

Can you open a shell and report back the results for the two commands:

arecord -l

aplay -l

Paste the output and let me know.

Here ya go. Sorry I had to step out for a bit ..

**** List of CAPTURE Hardware Devices ****
card 0: D1 [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: D1 [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0

**** List of PLAYBACK Hardware Devices ****
card 0: D1 [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: D1 [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 2: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

I also just added the second sound card and my 2nd instance started right up. I tried to reconfigure the 1st and here is what I got

>>> Enabling darkice_1 to start on boot
Done. Press [Enter] to continue...
Configuration Finished!
Do you want to start this darkice broadcast now? [N/y]: y
Starting darkice_1...
● darkice_1.service - Darkice Instance 1 Service
Loaded: loaded (/etc/systemd/system/darkice_1.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2021-04-20 16:43:54 CDT; 1s ago
Process: 1083 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
Process: 1084 ExecStart=/usr/bin/sh -c /usr/local/bin/darkice -v5 -c /home/pi/bcfy/configs/darkice/darkice_1.cfg > /home/pi/bcfy/logs/darkice_1.log 2>&1 (code=exited, status=255/EXCEPTION)
Main PID: 1084 (code=exited, status=255/EXCEPTION)
Press [Enter] to return to the main menu...

 

[blantonl]

Here ya go. Sorry I had to step out for a bit ..

card 2: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0

It looks like something has already captured your first soundcard for use

EDIT: I think I've found the problem and will be releasing a fix shortly for this 3B+ issue. Stay tuned.

 

[blantonl]

Ok, for this 3B+ issue, I need you to edit the /etc/pulse/default.pa file and comment out a line as shown below.

sudo nano /etc/pulse/default.pa

### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
load-module module-alsa-sink
load-module module-alsa-source device=hw:1,0
#load-module module-alsa-source device=hw:2,0     <<<<<< COMMENT OUT THIS LINE AS SHOWN BY ADDING A # IN FRONT
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink

Then save the file, reboot, and try to bring the feeds up.

 

[racer38]

Ok, for this 3B+ issue, I need you to edit the /etc/pulse/default.pa file and comment out a line as shown below.

sudo nano /etc/pulse/default.pa

### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
load-module module-alsa-sink
load-module module-alsa-source device=hw:1,0
#load-module module-alsa-source device=hw:2,0     <<<<<< COMMENT OUT THIS LINE AS SHOWN BY ADDING A # IN FRONT
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink

Then save the file, reboot, and try to bring the feeds up.

Still not starting feed one. Log still shows the same thing

Using config file: /home/pi/bcfy/configs/darkice/darkice_1.cfg
20-Apr-2021 18:53:50 Using ALSA DSP input device: plughw:1,0
20-Apr-2021 18:53:50 buffer size: 441000
20-Apr-2021 18:53:50 encoding
20-Apr-2021 18:53:50 Using POSIX real-time scheduling, priority 4
DarkIce: DarkIce.cpp:1272: can't open connector [0]
20-Apr-2021 18:53:51 HTTP/1.0 200

I think you may be on to something, but I am not that fluent in linux.

 

[racer38]

Here is the aplay arecord again with both sound cards plugged in

**** List of PLAYBACK Hardware Devices ****
card 0: D1 [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: D1 [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Device_1 [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
pi@bcfy-1fc4940e:~ $

**** List of CAPTURE Hardware Devices ****
card 0: D1 [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: D1 [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 2: Device_1 [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0