Finalization of flv file failed #11
Comments
|
We're not sure why this happens on some flvs, but there is a workaround here: https://github.com/Red5/red5-server/wiki/Repairing-Recordings |
|
That's a bummer ... The workaround (I knew about it) is not really feasible for us because it happens for every single recording. |
|
Here's an interesting observation: the setup where the issue occurred was a VirtualBox VM and the streams were written to a shared folder. Then I was testing something else in a different VM. This time the streams folder was not shared and it worked. Isn't that mysterious? |
|
Thanks letting everyone know dAnjou! Exactly the same problem here with Red5 not finalizing the FLV's when it was running in a vagrant shared folder. Moved the folder elsewhere and it worked perfectly. I am running Red5 1.0.4. |
|
I would assume this has something to do with shared folders then; if anyone has a fix or a suggestion to work around this then please create a pull request. |
|
We have stumbled over the same warning several times: From my experience it only happens with big files of 100-150 MB. Red5 is running on a DigitalOcean VPS with CentOS 6.5. The vs1450087575474_918.flv in particular had 300MB. For future reference here's the file/code with the Line 876: |
|
I can consistently trigger the issue by recording 10 minutes of HD (1280x720) video. I just recorded a 10:21 video which resulted in a .flv.ser file of 146,5 MB (I used a recent MacBook Air's webcam and the bitrate is 1.88Mbits/s). These are the 3 files created by Red5 including the .flv.ser: Using the above mentioned |
|
What codecs and publishing (to red5) are you using for the test? |
|
We're using H.264 for video and Nellymoser for audio. Just to be clear the above image is taken with a .flv created with: |
|
The flv and ser aren't meant to be combined; the finalizer uses .info and .ser to construct the flv and it also does some processing if memory serves. |
|
Oh yeah I know, I just brought it up because others reading this thread might consider the |
|
The issue also has something to do with either the length of the video (more likely) or with the size (less likely). From 12 videos I just recorded, most were under 40 seconds long, but 3 of them were between 7 and 8 minutes. All 3 of them failed with the same error:
creating a tiny .flv file, .flv.info and big .flv.ser files. In terms of size they occupied 42MB, 71MB and 80MB respectively. In the past we recorded 120MB files without any issues that's why I'm saying it's not necessarily size related.. I managed to recover the videos using https://github.com/Red5/red5-server/wiki/Repairing-Recordings . Here's the command I used in Windows' Command Prompt with Red5 1.0.6 (videos were recorded with 1.0.3).
The command basically triggers the
|
|
The actual line in org.red5.io.flv.impl.FLVWriter where the exception happens is: |
|
Our stack trace is a bit different than the one posted at the top. Maybe because we're running Red5 1.0.3 ? In our case the exception seems to be thrown by the |
|
Looking at another batch. From 2701 videos recorded over 4 months with Red5 1.0.3, 21 of them had this issue. 20 of them are between 12.8MB and 81.2MB while the 21st is 149.1MB in size. From the top 20 biggest files recorded, they occupy 14 positions including the 1st 6: |
Hi,
our Red5 1.0.5 has trouble finalizing the FLVs. We were using 0.9RC before where it worked. We upgraded to 1.0.5 for native RTMPS support (which works). We're pretty much using the default Red5 settings. The client is a self-made Flash application, I'd rather not post the code, it's kinda messy but as I said, it worked with 0.9RC before.
Oh, it happens every single time, not just once in a while, So, this doesn't really help us: https://github.com/Red5/red5-server/wiki/Repairing-Recordings
I'd appreciate any pointers on how to debug this! Thanks.
This is what is received:
The following commands produce perfectly fine audio/video streams:
And here's the
error.log(Das Argument ist ungültig means Invalid argument):The text was updated successfully, but these errors were encountered: