-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For filesize 2GB+, dvr mp4 stream.mp4 moov atom not found srs 3.0 #1694
Comments
Have the same issue. I've found that it happens on recordings of ~ 2hrs or more. Would love to see a solution for this. Perhaps it's an issue with mp4 and not flv? |
@franzwarning not exactly about record duration, its error when file size larger than 2GB. I think it error when unpublish stream, because mp4 format need to re write moov header when finish |
Did you have the same issue? And you have any solution for this issue? I'm considering to use dvr segment plan to separate to small MP4 file and join them together after stream unpublish |
Does this mean that flv doesn't need to? Might consider switching to flv in that case. Or using the segment plan, just makes my life a little more difficult. |
@franzwarning yes, you can change dvr format to flv, if you choose dvr plan is segment make surre dvr file size not larger than 2GB (I used it). Then just wait contributor fix this bug |
mdat->nb_data = uint32_t(mdat_bytes);nb_data overflow int->uint32 |
It seems the overflow of mdat size, which use uint32_t. |
定义的这个字节是int,所以只有2GB大小,需要改成uint64_t。 |
注意,前32字节就是ftyp,跟着后面16字节是mdat的头,其中Size就是 解析如下:
使用mp4box查看:
|
(Description)
Hi all, I use SRS for my livestream system. Everything OK but sometime, when have long livestream, the mp4 dvr file after livestream is break. I used ffmpeg to check the file, and the error like that:
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x41e55c0] moov atom not found
5e8ab3d7b3b1a2001b5e9b93.1586148554308.mp4: Invalid data found when processing input
Anyone have the same issue and how to fix this?
SRS(Version):
3.0release
SRS(Config):
The text was updated successfully, but these errors were encountered: