![]() ![]() I'd give it a go with GUI first with the 64-bit OS and see how it goes. Running 24/7 so far without any hiccups nor crashes. Still within spec and I believe throttling tends to occur at 80c and above. ![]() It is working rather hard and the CPU temperature varies between 67-70c at the moment. Yes the GUI definitely introduces an overhead, but as things stand with the GUI, ST, Liquidsoap, Icecast all on the same box, there's no buffering issues or any kind of CPU throttling so far, but I'd like to eventually move Liquidsoap and Icecast on to a different box to relieve the CPU of load. Liquidsoap receives the audio and sends it to Icecast. #Stereo tool keygen crack pro#So in my set up the HifiBerry DAC ADC Pro receives an analogue line in feed, this is picked up by ST, ST then outputs into Alsa Loop. I didn't have much fun with jack either so ended up using alsa-loop instead. Resampling not only loaded the CPU (looking at you pulseaudio!), it also ruined the sound quality. Would RTPL16 allow me to feed the output of ST via IP to my other box, which can then encode the feed etc? If it can deal with 48Khz sampling rate, I'm in, as I encode at 320K AAC 48Khz sampling rate and also had to make sure the entire audio chain is 48Khz. I'd like to move the encoder Liquidsoap and web streamer Icecast2 off the ST box on to my other box which has loads of spare CPU capacity. I'd also be interested to know more about RTPL16. It squeezes more performance out of the Raspberry Pi and even raises the CPU speed to 1.8Ghz from 1.5Ghz. If the command line can indeed deal with live audio feeds, I'd be willing to see if I can get it to work and share what I did if it's helpful for you.Īre you using the 32-bit OS or the 64-bit one? I found things run a bit smoother when I upgraded to Raspberry Pi 64-bit. So I've stuck to the GUI version since then, left minimised but with the desktop left open. I might be wrong of course! But I'm going by my initial attempts to try moving to the command line version in order to see if I can do away with the GUI/X-Windows. I've never tried running the command line version as I was under the impression it doesn't deal with live audio feeds, only files. I've found it helpful to get round the limitations of the web browser interface by using VNC to remote control the Raspberry Pi to make any tweaks to ST etc. Is it possible someone might be able to help me with the above issues? Very happy to provide. Other than this, it does seem to be working, and with the aid of ffmpeg and an extremely horrifying bash script, it has stayed on air for a while. I'm unable to verify for certain, but it also seems the processing may be ignoring many of the settings we gave it through the config file. Looking at the web inspector, the websocket seems not to want to connect at all, meaning that any attempt to tweak settings is largely pointless. Secondly, the web interface really doesn't seem to work that well for us when accessing it from a non-localhost address. This has given us a whole bunch of issues.įirstly, when we upgraded to the latest command line version of the Rpi StereoTool, it stopped recognising our licence key when input through the command line, or the config file, or both! So we've had to revert to not using any licensed settings to stop the beeping (which is of course non-ideal after we paid for said licence). We were hoping to be able to configure the processing remotely using the web interface so we could better tune it to real radios and dial the output gain to not over-deviate the transmitter. With the default settings the processing is sounding really good, and our FM feed sounds so much better than it used to already! I've successfully got a Raspberry Pi 4B taking a feed over RTPL16 across the campus network for a University Radio Station I help out at (I will publish some information on doing this shortly, as I bet it will be helpful to a few people). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |