PeteL

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!

Despite some the errors in the log, your installed application is running and should be able to continue run correctly. The Antiforgery and keyring notifications are minor issues. In addition, the port you selected doesn't really affect the application. What you see when start the application is blank page because your need to setup radio sources first. I was able to replicate the view you previously attached in your post If you expand the window it should look like this Go to this address in your app to create new source. Note they you will have different IP address of your server http://192.168.1.100:8383/create To test application you can use this URL http://media-ice.musicradio.com/LBCUK To schedule new recording go to this page. Since this is most likely your first station source, the URL will end with number 1 http://192.168.1.100:8386/schedule/create/1 Confirm that you can access dashboard http://192.168.1.100:8383/dashboard Again, your application is running and pages are empty on desktop and your phone till you setup station sources. You can also see in your browser if there are any errors when loading the application. Press FY12 on your keyboard and go to Console. It will display errors Can you please take a screenshot of the rradio template you installed. Please let me know how it goes.

It looks like you did not setup any Sources (Stations). The view from your picture is designed for tablets. Use your PC and open the page in a browser. Next to Stations label should be a plus sign. Click on it. It will take you to the page where you can add URL. In the beginning of this thread I described how to go about setting up recordings. Sometimes you need to reload page in the browser. On Windows PC press Ctrl button + F5. On Mac, hold Shift button + reload icon on the top of page You may also try to use different web browser. You can also test application by dropping some mp3 files into Media (recording destination) folder on your server. As long they are tagged with Artist and Album id3 tags they will be recognized and imported (close application and reopen it). The picture you posted is most likely due to that nothing was setup and recorded. Please let me know if you were successful in setting up application.

This is unintended feature that I tested myself. Application was not developed for that purpose, however it is possible to import other media files like audiobooks or podcasts as long they are in mp3 format and have Artist and Album id3 tags. Application will create rrs podcasting feeds. The only downside is that files are not in order.

Interesting idea. I did not try triggering a job using command line. To tell the truth I don't think it's possible. Job Dispatcher needs to receive two pieces of information, job number and processing type. I think API would be more suitable for such a scenario. As for second suggestion. It sounds more like Record button (on/off). I will have to take a closer look at HomeBridge.

It looks like not everything was loaded properly. On windows, hold Ctrl and press F5 and on Mac hold Shift and click on Reload icon. This should solve the problem.

Great.

I tested URL and it works correctly. Try to schedule new recording using different show name & time. Do short test recording for 1-2 minutes using continuous method. If you can please post container log including info when job is registered, arguments and post processing. Also, please check recording log. You will find it on Jobs page. Each individual job name has it's own log. Click on the note icon left to the clock icon. It should have a start date & time, end date & time and ffmpeg exit code There could be different reasons for this issue. What options are you trying to use for scheduled job? Please ensure that both config & media folders are set correctly in the container template. Also, check the appdata/rradio/temp folder and see are there any incomplete recorded files. It is possible that ffnpeg stops recording because of incorrect folder permissions.

I'm happy that you are enjoying this app. Any suggestions on new features and improvements are welcomed. Thanks.