PeteL

Yes, I think it would be possible. Although designating archive folder (with sub folders) it's more feasible. I thought about it before. I have some archived shows that should be stored in different location. Thanks for the suggestion.

Try different browsers and see if problem persists. Reload WebUI by clicking keyboard buttons on Windows machine Control + F5 and on Mac Shift + Reload icon in the top bar Click F12 on your keyboard to open web dev panel and look for any errors in Console tab One more thing. 404 error. Wich pne applies: You cannot connect to WebUI at all and browser throws 404 error You can connect to WebUI but instead of seeing Home page you see 404 error

Hi. I'm glad you enjoying the app. I'm not sure if I used rss validator, however when I created rss feeds they were set to be compatible with Apple devices. I looked at YouTube Music podcast section on my iPhone. How do you add rss feed to this app? From what I understand YT Music is just a shell for content available on regular YT. Can you provide sample rss feed that works for you? Since you are using Cloudflare tunnel you could open rRadio on your phone browser and stream it this way too. The app scales to the phone screen.

I'm glad you are enjoying the app. Paypal donate button worked initially but for some reason Paypal requires right now to convert personal account to business account for some reason. I'm not interested in doing this. I consider rRadio to be my personal project therefore I'm not planning to make git repository to be available to public. I have still some ideas for further development and I welcome any suggestions too.

I apologize, somehow I missed this question. On your phone, in the web browser navigate to http://your.server.ip:port/rradio Go to Feeds page Select link for show you want to add to podcast app Press on show link and hold for couple seconds Small menu will show up. Select option Copy link In podcast app there should be an option to add url manually Paste copied link Show feed should be added to your podcast app rRadio creates and updates feeds every time new recording is added You can also trigger creating feeds by clicking on icon Reload Feeds at the top of the Feeds page

The first code 137 happens when recording is canceled manually. I'm not sure why would FFMPEG send this code when signal is dropped Please take a screenshots of the scheduled jobs. Also, please provide URL of the station that gives you problem. I would like to test it. It seems that somethings has changed if you experience the same problems across various stations. Tell me more about your setup. I recommend /config directory to be stored on cache drive. /mnt/cache/appdata/rradio

Do you see any exit code for this job on Jobs page in the recording log? Do you experience the same signal dropouts for other radio stations? Did this job ever recorded properly in this version of rRadio 2.0.1 ? I do get some signal disconnections from time to time. There could be different reasons for loss of signal. Maybe you can find different URL for that station. You can still use previous version of the app. To do that you need to pull image with following tag docker pull mpcdigitize/rradio:build-2503

New release is available version 2.0.1 build 25.05 Additions:Direct Stream --> Mp3 Scheduling recording has new bitrate option that allows saving stream to MP3 without re-encoding. Source URL must be in MP3 format. Sources that are in other formats like AAC of FLAC will be re-encoded to MP3 with default bitrate 128kbps. Settings page containes option for scheduling database maintenance Updated Hangfire to version 1.8.18 Removed duplicate ffmpeg -c flag

I didn't notice that -c flag was used more than once. Thank you for pointing this out. I think preserving original stream without re-encoding is possible. I did some test already with FLAC output. Potential problem is that some users may not know what stream format is being used. It may also cause some compatibility issues with some web browsers. Anyway I think this feature can be implemented.

It’s been a long time since the first release of the rRadio. I’ve been working on new features and improvements and finally I think it is ready to be released into the wild. There are some major changes that would make application easier and more enjoyable to use it. Let me highlight some of the things that are included in this release. * All the recordings are divided right now into two categories Added and Played. Accessing previously played shows is a breeze. Bear in mind that playing recording will not prevent deleting it when its default Keep value expires. * To prevent deletion there are two options. First is adding recording to Favorites and second is adding it to Archive. When file is added to Archive it will only be accessible through Archive. This is a great feature if you want to preserve some recordings * Job scheduler has a new feature One-Time recordings. It’s possible to set recording for specific date, but it’s also possible to set recordings for different dates and group them. Fo this to happen, we need to create different One-Time jobs with the same name. * New Activity page displays progress of jobs that are being currently recorded. In addition Upcoming tab shows queued jobs for Today and Tomorrow. Please note that scheduled recording times are displayed in user’s Time Zone local time * Support for different Time Zones. No more calculating time offsets between different Time Zones is required. Set Radio Station Time Zone and use its local time to schedule recordings. Great benefit of this approach is the we do not have to worry about adjusting jobs to Daylight Saving Time. If you have already existing Sources and Jobs, you have to change Time Zone and adjust manually scheduled jobs to local time of that Time Zone. This is not done automatically. * Jobs page has new actions too. Job can be suspended if for some reason we do not want record it right now. Also, job can be triggered. The feature should be used for testing purposes only if we want to find out if scheduled job would run properly. It will not in any way affect saved scheduled job. * Settings page. I understand that date format was annoying for some the users. Now you can select your preferred format. This would apply to future recordings, but new Maintenance page has a button that would allow renaming all existing titles. Depending on how many recordings are present in your database it may take few seconds. Please be patient. * Maintenance page contains buttons that initiate database related activities. Every once a while station’s URL may go rogue. It’s possible right now to look for failed URLs. * I have to say I got little bit bored looking at the default colors of the application. I included 15 more additional Color Themes that can be selected in Settings page. My favorite right now is Chinese Violet. * For new users that will use application for the very first time. They will be taken directly to the page where they have to setup new source radio station. * Since this is an update, WebUI may experience some odd behavior. There are new script and elements that did not exist before. Please use on your keyboard Ctrl+F5 keys to reload page’s resources. This applies to browsers on Windows machines. On Mac, you should hold Shift button and click reload icon on top next to previous and next page buttons. * There are numerous bug fixes and improvements. I’ve been beta testing application for last 3 months working diligently on squashing them and I think we are ready to use new version of rRadio.

1. If you look at the log you can see the container internal Time Zone 2024-12-04 07:15:41 [TIME_ZONE] (UTC+01:00) GMT+01:00 2024-12-04 07:15:41 [INFO] (Checking database) It's possible to set the time zone by including additional ENV variable in container template. There was someone else with the same issue. Please refer to the earlier posts on how to do it. 2. 2024-12-04 07:20:12 [INFO] (Arguments: -i "{URLHERE}" -c copy -t 73800 -metadata Title="{TITLEHERE} wed (12.04.24 Wed. 19:20)" -metadata Album="{TITLEHERE} wed" -metadata Artist="{RADIONAME}" -metadata Track="1204" -metadata Album_Artist="{RADIONAME}" -metadata Year="2024" -metadata Genre="Radio" -metadata Comments="{TITLEHERE}_wed_(2024-12-04_19.20.12_Wednesday)" -c:a libmp3lame -ab 320k -y "/app/config/temp/{TILTEHERE}_wed_(2024-12-04_19.20.12_Wednesday).mp3".) -t 73800 is over 20Hrs of recording time. I strongly recommend not to do that, considering also thet your selected bitrate is 320kbps. This will result in extremely large file 3. 2024-12-04 11:05:10 [INFO] (Executing job 1-1) 2024-12-04 11:05:10 [INFO] (Job registered: True.) 2024-12-04 11:05:10 [INFO] (Aborting) The first attempt was aborted because the job with the same name & time was already executed. To prevent creating duplicate recordings, scheduler is configured to to run recurring job only once a day. 4. {RADIONAME} I'm confused about this naming. I think you edited the log output. If not than I would not use any parenthesis. These tags are written into a file. I'm not sure how ffmpeg is treating them 5. Recordings logs are empty. There is a bug in the software. It will be rectified in upcoming release Please tell me more about your setup. Are you running it on Unraid? Is appdata stored on cache drive? Please post a screenshot of the job you scheduled.

I never came across such a behavior. This is highly unusual. Please confirm what settings did you use for this particular job. Continuous option would create one single file for entire scheduled duration. It will not continue recording past the scheduled duration. Hourly will attempt to record scheduled job in segments. Example if you schedule 3 hours recording starting from 8 AM then this job will be triggered 3 times at 8AM., 9AM and 10AM. hence you will have 3 hourly mp3 files. To verify what parameters were sent to ffmpeg you can open container log. You will see details of the triggered job. If you think something is going on with currently recorded file, you can stop container. This will force ffmpeg to stop

1. I suggest you navigate to myipaddress:port/dashboard/recurring to see when is the next time this job will be triggered. You can also verify if job is set according to your time zone. 2. If I understand correctly you are trying stream live radio link through proxy/vpn wireguard. I have setup my radio container to be accessed using Nginx Proxy Manager and Cloudflare and I have no issues streaming it live on my phone. If the url that you are using has signal and can be recorded than there is nothing that would prevent it from being streamed. If I'm at work, I cannot stream or played recorded files at all. This is because of the security measure put in place by my employer. My guess is your issues are related to the proxy server. 3. I'm not familiar with wireguard. Most likely you have to do some port forwarding on your router 4. There is no additional settings that are required. Url is simply passed to a browser for playback

The way you have set it up is that appdata is using two locations. Primary location is cache drive and secondary location is an array. Most likely you have files residing in both cache/appdata and disk#/appadata What you really want is appdata to be exclusively on cache drive In addition docker image should be outside of an array too as Unraid constantly calculates parity

You can make this changes when you setup container template. Config folder can be set either to appdata on cache drive or in the array. You can edit location. From my own experience I can tell you that you will get better performance when appdata is outside of an array. Maybe create another share on cache called appdata1 and select it for config folder when installing cointainer

Do you have a cache drive installed? Your current setup goes through the array, which in the way slows down entire process. In addition, parity is calculated all the time. Proper way is to separate appdata from array on its own cache drive. I suggest you move appadata to cache drive and make changes in container templates to use new destination. It should be /mnt/cache/appdata Also appdata share should be set to use cache drive only. Error is bit cryptic, however it is most likely related to execution of FFMPEG

It looks like second recording was not executed. If you go to Dashboard/Recurring Jobs, how many job Id you can see in the same sequence? Hourly recordings have Id that starts with number 1 . For example for 3 hour recording there should be id 1-1, 1-2, 1-3 There is a column that shows last execution time. Out of curiosity. What system are you using? Is appdata folder on cache drive? Is it /mnt/cache/appdata or /mnt/user/appdata? This url usually works for me http://media-ice.musicradio.com/LBCUK

The reason it aborts recording is to prevent hangfire from triggering job multiple times within seconds. Triggered job is registered and any subsequent attempt on the same day will be aborted. The workaround for testing purposes is to create new job. Renaming job will not work and job will be aborted. You can trigger job manually by going to http:/youripaddress:port/dashboard The list of scheduled jobs is under Recurring Jobs I have some jobs scheduled to run for 2 or 4 hours. However in most cases I try to avoid it as stream can get dropped for no reason and file stays in temp folder. FFMPEG does not have a way to notify about stream being dropped. For LBC I suggest you try schedule recording using hourly mode instead of continuous. Set duration for 3 hours and select hourly mode. Unfortunately dropped streams do occur with LBC sometimes. There could be different reasons for it. I suggest you try to record from different sources and see if this problem repeats. Set different recording duration and check temp folder. If you want to include recordings in Plex you need to ensure that created radio library uses local metadata. However, even with this setting Plex will try to fetch unrelated metadata. Problem with Plex is that all recorded files are in one single folder but Plex prefers music to be stored in Artist/Album format. Hence, new recordings are not added to already scanned Albums. Therefore, you may have multiple James O'Brien folders in Plex after couple days of recordings.

To prevent creating duplicate recordings, rradio will record scheduled job only once a day. For testing, you can trigger job manually through dashboard under recurring jobs by selecting a job and clicking trigger now. Usually If I want to test something I create new job and trigger it using dashboard. Please refer to previous posts how to access dashboard http://ipaddress:port/dashboard I'm not entirely sure what is causing problem on your Unraid box. Please take a screenshot of rradio log. Do you run any other containers on this machine? Do you experience any problems with them like permissions? Are you using cache drive? Please take a screenshot of rradio template used for installation.

There shouldn't be any issues recording the stream in rradio but you cannot play them live right now.

I will look into a log issue. Thanks for letting me know about it. As for the URL you provided it's not exactly streaming URL. The format m3u8 is a playlist that is not compatible with any internet browser. Hence direct live streaming inside browser is not possible. This is due to the way it is actually done. Stream is segmented into small chunks. FFMPEG can handle it and it is possible to record it but in order to play it live it would have to go through FFMPEG first and then be send to a browser. Which means record and play at the same time. As you noticed VLC can do it. I'm hoping to tackle this problem at some point and implement some solution.

I think I know what the problem is. I remember I had a similar issue once and it was caused by incorrect version of ffmpeg. Basically, ffmpeg that is included in this rradio release is not compatible with Ubuntu. It's a bit strange because it is Linux version. You would have to look for what is called static release of ffmpeg and ffprobe for Ubuntu. I know there are installers for Ubuntu but I'm not sure if you would be able to copy installed file into "config/ffmpeg" folder. Note that you also need ffprobe file. They usually come in one release package. You need to replace existing ffmpeg & ffprobe files with versions compatible with Ubuntu. If you cannot find ffmpeg compatible with Ubuntu, you may compile ffmpeg yourself. Instructions should be available on ffmpeg.org site. I don't think there are any issues with folder permissions. Maybe you can run chmod on both files located in "config/ffmpeg" folder but my guess is it will be ineffective.

The values of PUID & PGID are Unraid specific. They may not even work on Ubuntu. I would try to remove them from the template when installing on your machine. I never really tried using Ubuntu, but would try to see if I can access "config\temp" and "media" folders. Actual recording is performed into temp folder and when it is finished file is moved to media folder. The fact that starting job throws permission error suggests that issue is with temp folder. Try to navigate to these folders using application similar to Windows Explorer and and see if you can copy some files into them. Either way, you should be able to run chmod command using Ubuntu's terminal. Setting up permissions through rradio terminal would not work. Before you run the command you need to make sure that rradio is not running. Alternatively, you may want to delete current rradio installation, remove config and media folders and create them manually. Set permission if it's necessary. Finally install rradio again

It is possible to trigger jobs manually. Depending on how many jobs you have created. If you want to test recording. The most recent job is added to the end of list of recurring jobs in the Hangfire Dashboard. Go to: http://TOWER_IP:8386/dashboard/recurring If you have more jobs. You will have to obtain job id number. For this you need to go to Jobs page in the application and click on Recording Log icon Now, go to the Dashboard and find the job Once selected, you can trigger it In the future I will add a button for triggering a job in the application. Restarting failed streams is much more complicated. I will look into it, but I cannot make any promises.

Happy New Year everyone! I decided to post an update and shed some light on things that will be coming. There is a second request for releasing application for ARM based devices and it is something I will definitely consider. Personally I do not know how well application will perform on Raspberry Pi. I had it running on very low powered AMD mini PC and it was not the best experience. UI responsiveness suffers visibly. We have to remember, that depending on how many recording jobs are performed FFMPEG has to do stream conversion in real time. Low powered device may have issues with that. Here are couple things that I would like implement in the next release. 1. To be able to set different Time Zones for different Radio Sources. This would be helpful when we have a station that operates for example in Europe or Asia and we have to calculate show's starting time. Hopefully it would also provide some solution to Daylight Saving Time changing time difference between time zones. 2. To have easier access to files that were already played and that we want to resume playback. 3. Separate Archive section for all files that we want to keep 4. Activity page showing currently recorded items. 5. Suspend/Resume recording jobs 6. File naming options. This would include selection of different date scheme like dd/MM/YYYY 7. To be able to set a recording job for specific date (date picker) These are couple things that require improvements. If you have any other suggestions or requests please let me know. There is a certain issue that everyone should be aware of. Application records the streams into appdata/rradio/temp folder. When recording is completed they are being moved to media folder. Occasionally some files are still in temp folder. This most likely happens when stream is interrupted or dropped. I strongly advise to check temp folder periodically and either delete or move files. We do not want these orphaned files to fill cache drive. I have very limited time right now for development and I do not want to make any promises regarding release date. I'm hoping that it will take couple months. For now please everyone enjoy it!