Closed LordDonkey closed 4 years ago
With the latest commits to master, the recording limit should be 1 minute. Were you running a build from master, or the 0.4.0 beta 5 release?
For the recording overlap issue ... which Decoder? Are you gettting good/solid decodes when you're seeing this issue?
I forgot to mention ... it will chop audio segments at 60 seconds. Recordings should be a maximumof 60 seconds. Playback of the audio will appear seamless because I link continuous audio segements together so that playback doesn't get interrupted.
It was the beta 5 build from yesterday's master. The issue exists with today's compile from the master as well. The system I'm on has a Phase I control channel and Phase II voice channels. The decodes are good, no errors, strong signal.
For that 67 second call, there was nothing written in the recordings folder for it, but I've found that other calls are intermittently not being recorded as well and barely any seem to be streaming. I've had numerous calls but only 8 have been streamed.
The latest master build fixed most if this issue. Recordings are being made and the stream appears to be working properly, minus the occasional TO:UKNOWN FROM:UNKNOWN in the metadata and the end of the recordings getting cut off.
@LordDonkey I merge another branch into master yesterday afternoon (2pm EST) with some Phase II changes. Did you happen to rebuild and run these latest changes?
There were some bugs in the code that may have contributed to the recordings being cutoff like you were seeing.
Yes sir, the audio cutoff issue is now fixed. Shoutcast V2 Stream metadata still occasionally shows as TO:UNKNOWN FROM:UNKNOWN. Here is a link to the stream history.
Others are reporting the same issue for Icecast as well. I suspect these are empty audio segments, but I'll have to do some testing to confirm and figure out a way to stop them from happening.
I'm asking because there was a 67 second transmission and it's not showing up in the recordings folder. Also, some transmissions aren't being recorded also or they are overlapped in other recordings.
Some of the metadata isn't making it over the stream, it's showing as TO:UNKNOWN FROM:UNKNOWN.