Re: [FFmpeg-user] Question about file size changes
Carl; MediaInfo may not be good for some things but it does appear to identify the details of the closed captioning streams/content? better than ffmpeg or ffprobe have with the options I have found to date. In this case it also appears to have identified (for me at least) a conversion from BDAV to mpegts because of a file suffix (mts) suggesting the prefix to be invalid triggered a web search by me that suggested a means to prevent that conversion (by changing the file type to m2ts). MediaINFO appears to have confirmed for me that the m2ts suffix prevented the change from BDAV to mpegts. This statement "When you remux, you cannot change the quality of the media in the file, this is simply not possible." confuses me because this statement "While there is indeed some BDAV writing support in the mpegts muxer, I don't think it is complete." Seems to indicate a remux operation that changes from BDAV to mpegts may use incomplete BDAV interpretation code that may not be as good as a remux that maintains BDAV on both sides. If I understand "While there is indeed some BDAV writing support in the mpegts muxer, I don't think it is complete." as noted above you appear to indicate that the conversion of the file suffix to m2ts should deliver either equivalent or better results by eliminating the change from BDAV to mpegts caused by the mts file suffix. Thanks this appears to be the answer I was seeking. Do I understand what you wrote? On Wednesday, June 19, 2019, 10:27:08 AM EDT, Carl Eugen Hoyos wrote: Am Mi., 19. Juni 2019 um 02:54 Uhr schrieb David Shuman : > In terms of which conversion is more valid which play quality would be > closer to the original -- does the m2ts change less of the content when > remixing than the mts as BDAV does not change to mpeg-ts our would > one consider the additional headers from m2ts to more of a quality > change so mts provides a file more like the original again in terms of > play quality? There are several misunderstandings in this thread, I will try to explain some of them (and repeat other explanations): When you remux, you cannot change the quality of the media in the file, this is simply not possible. FFmpeg is not a file editor, so contrary to what some comments here imply, you simply cannot remux and expect that the resulting file is very similar to the original file, with only the changes you wanted. On the contrary, the output file is always a new file with new properties, some of them will be identical to the original file, others won't. You already know that MediaInfo is not an ideal tool to find issues in FFmpeg. While there is indeed some BDAV writing support in the mpegts muxer, I don't think it is complete. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Question about file size changes
Am Mi., 19. Juni 2019 um 02:54 Uhr schrieb David Shuman : > In terms of which conversion is more valid which play quality would be > closer to the original -- does the m2ts change less of the content when > remixing than the mts as BDAV does not change to mpeg-ts our would > one consider the additional headers from m2ts to more of a quality > change so mts provides a file more like the original again in terms of > play quality? There are several misunderstandings in this thread, I will try to explain some of them (and repeat other explanations): When you remux, you cannot change the quality of the media in the file, this is simply not possible. FFmpeg is not a file editor, so contrary to what some comments here imply, you simply cannot remux and expect that the resulting file is very similar to the original file, with only the changes you wanted. On the contrary, the output file is always a new file with new properties, some of them will be identical to the original file, others won't. You already know that MediaInfo is not an ideal tool to find issues in FFmpeg. While there is indeed some BDAV writing support in the mpegts muxer, I don't think it is complete. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Question about file size changes
In terms of which conversion is more valid which play quality would be closer to the original -- does the m2ts change less of the content when remixing than the mts as BDAV does not change to mpeg-ts our would one consider the additional headers from m2ts to more of a quality change so mts provides a file more like the original again in terms of play quality? On Tuesday, June 18, 2019, 1:11:21 PM EDT, Moritz Barsnick wrote: On Tue, Jun 18, 2019 at 16:31:45 +0200, Jerome Martinez wrote: > On 18/06/2019 15:01, Moritz Barsnick wrote: > > I don't know why mediainfo determines different video bit rates (1817 vs. > > As it is not possible to compute the bitrate per stream in MTS/M2TS > without parsing the whole file, MediaInfo does an estimation, and in > this case the estimation is unfortunately different depending on the > container used. That's what I thought. I believe it's no different for ffmpeg, which does warn regarding duration estimation for some codecs (notably MP3), but otherwise does not indicate whether a displayed bitrate is from metadata or from knowledge or from estimation. (I may be wrong here, too lazy to check.) > (I plan to add "estimated" later when relevant so more explicit that > it could be different for the same stream, but more complex in the > code), As to not confuse people, that's probably better. But multimedia coding is so complex anyway, it tends to confuse people. ;-) > (the question about the overall bitrate and file size change will > stay though, due to the good reasons you provided). Yes, it wasn't 100 % clear from the original posting what the complaint was. > Jérôme, developer of MediaInfo. Thanks for pitching in, Moritz ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Question about file size changes
On Tue, Jun 18, 2019 at 16:31:45 +0200, Jerome Martinez wrote: > On 18/06/2019 15:01, Moritz Barsnick wrote: > > I don't know why mediainfo determines different video bit rates (1817 vs. > > As it is not possible to compute the bitrate per stream in MTS/M2TS > without parsing the whole file, MediaInfo does an estimation, and in > this case the estimation is unfortunately different depending on the > container used. That's what I thought. I believe it's no different for ffmpeg, which does warn regarding duration estimation for some codecs (notably MP3), but otherwise does not indicate whether a displayed bitrate is from metadata or from knowledge or from estimation. (I may be wrong here, too lazy to check.) > (I plan to add "estimated" later when relevant so more explicit that > it could be different for the same stream, but more complex in the > code), As to not confuse people, that's probably better. But multimedia coding is so complex anyway, it tends to confuse people. ;-) > (the question about the overall bitrate and file size change will > stay though, due to the good reasons you provided). Yes, it wasn't 100 % clear from the original posting what the complaint was. > Jérôme, developer of MediaInfo. Thanks for pitching in, Moritz ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Question about file size changes
On 18/06/2019 15:01, Moritz Barsnick wrote: I don't know why mediainfo determines different video bit rates (1817 vs. 1870), ffmpeg claims to have copied exactly the same amount of video into the target containers. I don't trust mediainfo on this. As it is not possible to compute the bitrate per stream in MTS/M2TS without parsing the whole file, MediaInfo does an estimation, and in this case the estimation is unfortunately different depending on the container used. I'll fix that in MediaInfo for at least having the same video bitrate output when one changes from MTS to M2TS (I plan to add "estimated" later when relevant so more explicit that it could be different for the same stream, but more complex in the code), so you would avoid such kind of question about the video bitrate (the question about the overall bitrate and file size change will stay though, due to the good reasons you provided). Jérôme, developer of MediaInfo. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Question about file size changes
From what I understand, I am doing a copy that should not alter the original content except to add dropped frames as necessary to sync the video and audio due to transmission errors. Why is the KB/S changing and by two different values depending solely on the suffix for the files. Which conversion is more valid in this case? MTS or M2TS? On Sunday, June 16, 2019, 06:36:01 PM EDT, Dennis Mungai wrote: On Sun, 16 Jun 2019 at 22:26, David Shuman wrote: > I have a video recorder that outputs files with an .mts suffix. mediainfo > identifies these files as BDAV more commonly .m2ts files I attempt to copy > these files with the following commands > > ffmpeg -i > "D:\Dave\Videos\010-raw\mts\Charge-05082019-2255.mts" -c > copy > "D:\Dave\Videos\020-fix\mts\Charge-05082019-2255.mts" 2>&1 > | wtee "D:\Dave\Videos\log\mts\ffFIX-Charge-05082019-2255.txt" > I renamed the file to have a .m2ts suffix and tried again > ffmpeg -i > "D:\Dave\Videos\010-raw\m2ts\Charge-05082019-2255.m2ts" -c > copy > "D:\Dave\Videos\020-fix\m2ts\Charge-05082019-2255.m2ts" > 2>&1 | wtee "D:\Dave\Videos\log\m2ts\ffFIX-Charge-05082019-2255.txt" > The resulting output files according to mediainfo have had their video bit > rates increased The original is 1778 kb/s regardless of file suffix, > the .mts copy is 1817 kb/s and the .m2ts copy is 1870 kb/s. > > Why do the copies have higher video bit rates? Nothing else significant > appears to have changed the .mts claims format is mpeg-ts on the output, > all other formats both input and the .m2ts output claim to be BDAV. > Is there a way I can keep the bit rate the same so the copy matches the > original except for corrections made during the copy for missing franes, > etc? > > > Most likely you're seeing the effects of muxer overheads. From your console: muxing overhead: 9.707805% ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Question about file size changes
On Sun, 16 Jun 2019 at 22:26, David Shuman wrote: > I have a video recorder that outputs files with an .mts suffix. mediainfo > identifies these files as BDAV more commonly .m2ts files I attempt to copy > these files with the following commands > > ffmpeg -i > "D:\Dave\Videos\010-raw\mts\Charge-05082019-2255.mts" -c > copy > "D:\Dave\Videos\020-fix\mts\Charge-05082019-2255.mts"2>&1 > | wtee"D:\Dave\Videos\log\mts\ffFIX-Charge-05082019-2255.txt" > I renamed the file to have a .m2ts suffix and tried again > ffmpeg -i > "D:\Dave\Videos\010-raw\m2ts\Charge-05082019-2255.m2ts" -c > copy > "D:\Dave\Videos\020-fix\m2ts\Charge-05082019-2255.m2ts" > 2>&1 | wtee"D:\Dave\Videos\log\m2ts\ffFIX-Charge-05082019-2255.txt" > The resulting output files according to mediainfo have had their video bit > rates increased The original is 1778 kb/s regardless of file suffix, > the .mts copy is 1817 kb/s and the .m2ts copy is 1870 kb/s. > > Why do the copies have higher video bit rates? Nothing else significant > appears to have changed the .mts claims format is mpeg-ts on the output, > all other formats both input and the .m2ts output claim to be BDAV. > Is there a way I can keep the bit rate the same so the copy matches the > original except for corrections made during the copy for missing franes, > etc? > > > Most likely you're seeing the effects of muxer overheads. From your console: muxing overhead: 9.707805% ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Question about file size changes
I have a video recorder that outputs files with an .mts suffix. mediainfo identifies these files as BDAV more commonly .m2ts files I attempt to copy these files with the following commands ffmpeg -i "D:\Dave\Videos\010-raw\mts\Charge-05082019-2255.mts" -c copy "D:\Dave\Videos\020-fix\mts\Charge-05082019-2255.mts" 2>&1 | wtee "D:\Dave\Videos\log\mts\ffFIX-Charge-05082019-2255.txt" I renamed the file to have a .m2ts suffix and tried again ffmpeg -i "D:\Dave\Videos\010-raw\m2ts\Charge-05082019-2255.m2ts" -c copy "D:\Dave\Videos\020-fix\m2ts\Charge-05082019-2255.m2ts" 2>&1 | wtee "D:\Dave\Videos\log\m2ts\ffFIX-Charge-05082019-2255.txt" The resulting output files according to mediainfo have had their video bit rates increased The original is 1778 kb/s regardless of file suffix, the .mts copy is 1817 kb/s and the .m2ts copy is 1870 kb/s. Why do the copies have higher video bit rates? Nothing else significant appears to have changed the .mts claims format is mpeg-ts on the output, all other formats both input and the .m2ts output claim to be BDAV. Is there a way I can keep the bit rate the same so the copy matches the original except for corrections made during the copy for missing franes, etc? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
