Recording Error

[conorjesu34]

The message is: "stream recording: encoder exited with an error. Please check stream archive settings.

Then it records after 2-3 tries.

Now the problem is, the recording isn't going to the desktop like I have it set to go...

 

[djsoft]

What RadioBOSS version do you use and what encoder settings? Try the standard like MP3 128kbps 44100 Hz stereo. Also ensure that recording path is correct. If it can't save the recorded files, it will show an error.

 

[Chris Deacon]

We are having recording failures exactly the same as above every once in a while (latest version). We use Streamarchive command to record a program for later replay. Sometimes the write process fails and the file becomes locked and cannot be deleted without a complete reboot of RB. Streamarchive fails to overwrite the same file in the same location sometimes, so we asked it to delete the file after it had been played, so next time the folder was empty, but the problem occurred again last week but only on one day. Every other day of the week it works perfectly. It does not occur on the same day every week, but appears to be random. Its a 360kbps MP3 file. The log shows 3 attempts to write the file but then fails with the message "stream recording: encoder exited with an error. Please check stream archive settings." The settings are normal and work on the following days with the same encoder settings and recording path. Is this a bug?

 

[djsoft]

RadioBOSS uses external mp3 encoder (lame.exe) to do the actual encoding, and it's possible, while RadioBOSS made a request to stop the encoding, it will keep running for some reason and holding a lock to the file.
Please try using a different file format e.g. OGG or FLAC to see if it makes things better.

 

[Chris Deacon]

I'm sorry to say it did not solve the problem. We are now using FLAC as suggested but today had exactly the same problem. Here's the log error:
Stream Recording: encoder exited with an error. Please check stream archive settings. Attempting to restart.
There seems to be a serious bug here because the function is currently unreliable. We have lost several live broadcast repeats because of this issue and the locked file (see above) cannot be deleted without restarting RB between midnight and dawn. It is a random error that writes the file but leaves the file with zero content. We use it in a multiple schedule command to record a program following the news. We would be pleased if you could look into this for us please as I note several other reports of the same problem.

 

[djsoft]

If you use any 3rd party antivirus, please try removing it (disabling may not be enough). Also, please try the latest beta 6.1.0.4 to see if the problem is still there.

 

[Chris Deacon]

The problem with streamarchive recording continues in the most recent version of RB. We need to protect our server with Avast and have added all RB related directories and files as exceptions, but we still get locked files on a regular basis. The lockups do not coincide with any logged windows event or other RB command. The streamarchive command is used in a multiple command however. Streamarchive on, then play program a second later (streamarchive recording from a line input). Then streamarchive off.

 

[Chris Deacon]

Update: Today I recorded two one hour programs in flac and the result as observed in tracklist was two one hour long files of ZERO bytes that could no longer be deleted without a reboot. You state elsewhere that the files write progressively. This is not happening. It’s an ongoing source of frustration in an otherwise brilliant program... what else can be causing this error? (Same for mp3 files). Do I need to insert a pause for a sec or two before the recording starts?

 

[djsoft]

You state elsewhere that the files write progressively.

Yes, this is correct. This is true regardless of the format you use, it will be written as it goes, in small chunks (several kilobytes). You can try removing Avast to see if it fixes the problem, we've seen it in the past that overly paranoid antivirus software could cause weird bugs.