Bitrate mismatch between source and result video, when not specifying bitrate per parameter about superview HOT 7 CLOSED

Thanks for the report. Any chance that you can post (part of) the source file so I can investigate?

from superview.

Sure. Here you go: https://www.dropbox.com/s/8jwdszf2ns4vphc/source_clip.mp4?dl=0

from superview.

Nice flying :)

I checked, ffprobe lists the video as having 36MB/s average bitrate. You should also see this number in the output when running the superview command. The output file has a similar bitrate for me.

Can you run ffprobe on both the input on output file on your system and post the results?

$ ffprobe -i source_clip.mp4 -v error -show_entries stream=codec_name,bit_rate
[STREAM]
codec_name=h264
bit_rate=38678952
[/STREAM]
[STREAM]
codec_name=aac
bit_rate=128000
[/STREAM]
$ ffprobe -i output.mp4 -v error -show_entries stream=codec_name,bit_rate
[STREAM]
codec_name=h264
bit_rate=38531794
[/STREAM]
[STREAM]
codec_name=aac
bit_rate=128049
[/STREAM]

from superview.

I already see one difference. You ran superview either on mac or linux. I ran it on Windows with ffmpeg 4.1.3. Also when i ran it superview reported on the cli the following:
Filter files generated, re-encoding video at bitrate 0 MB/s
Could this be windows specific?

from superview.

I tested with 4.1.3 (latest version), but it could be that ffprobe outputs the bitrate info differently in other (older?) versions. It would be great if you can put the ffprobe output of the input and output file as above.

from superview.

Can you check with release v0.2? https://github.com/Niek/superview/releases/tag/v0.2

I changed the way the input specs (among which bitrate) are parsed, it should work better across different ffmpeg/ffprobe versions.

from superview.

Closing this, I assume it's fixed in 0.2.

from superview.