[GH-ISSUE #73] [e302a3b] Rate change doesn't affect quality using CBR #67

Closed
opened 2026-05-05 15:04:53 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @LordHDL on GitHub (Feb 28, 2015).
Original GitHub issue: https://github.com/zakk4223/CocoaSplit/issues/73

Example video: https://www.dropbox.com/s/lq7tcbeljn8riw3/CS%20Rate%20Change.mp4.gz?dl=0

I started with 5000 bit rate and dropped it to around 300 or so. The video quality remains as if it were 5000, and there is some visual flickering after the change.

This was when using CBR. The rate change worked correctly using CRF.

Originally created by @LordHDL on GitHub (Feb 28, 2015). Original GitHub issue: https://github.com/zakk4223/CocoaSplit/issues/73 Example video: https://www.dropbox.com/s/lq7tcbeljn8riw3/CS%20Rate%20Change.mp4.gz?dl=0 I started with 5000 bit rate and dropped it to around 300 or so. The video quality remains as if it were 5000, and there is some visual flickering after the change. This was when using CBR. The rate change worked correctly using CRF.
Author
Owner

@zakk4223 commented on GitHub (Feb 28, 2015):

What’s the compressor config look like? Also make sure you are compiling against a new ffmpeg AND x264. The CBR mode uses an x264 parameter that didn’t show up until around x264 build 139 I think. (current build is 146)

On Feb 28, 2015, at 10:36 AM, LordHDL notifications@github.com wrote:

Example video: https://www.dropbox.com/s/lq7tcbeljn8riw3/CS%20Rate%20Change.mp4.gz?dl=0 https://www.dropbox.com/s/lq7tcbeljn8riw3/CS%20Rate%20Change.mp4.gz?dl=0
I started with 5000 bit rate and dropped it to around 300 or so. The video quality remains as if it were 5000, and there is some visual flickering after the change.


Reply to this email directly or view it on GitHub https://github.com/zakk4223/CocoaSplit/issues/73.

<!-- gh-comment-id:76549414 --> @zakk4223 commented on GitHub (Feb 28, 2015): What’s the compressor config look like? Also make sure you are compiling against a new ffmpeg AND x264. The CBR mode uses an x264 parameter that didn’t show up until around x264 build 139 I think. (current build is 146) > On Feb 28, 2015, at 10:36 AM, LordHDL notifications@github.com wrote: > > Example video: https://www.dropbox.com/s/lq7tcbeljn8riw3/CS%20Rate%20Change.mp4.gz?dl=0 https://www.dropbox.com/s/lq7tcbeljn8riw3/CS%20Rate%20Change.mp4.gz?dl=0 > I started with 5000 bit rate and dropped it to around 300 or so. The video quality remains as if it were 5000, and there is some visual flickering after the change. > > — > Reply to this email directly or view it on GitHub https://github.com/zakk4223/CocoaSplit/issues/73.
Author
Owner

@LordHDL commented on GitHub (Mar 1, 2015):

My x264 library and ffmpeg are current git. Compressor config:

screen shot 2015-02-28 at 8 00 24 pm

<!-- gh-comment-id:76561996 --> @LordHDL commented on GitHub (Mar 1, 2015): My x264 library and ffmpeg are current git. Compressor config: ![screen shot 2015-02-28 at 8 00 24 pm](https://cloud.githubusercontent.com/assets/5182602/6428968/a4fa485c-bf84-11e4-8022-93a0576a2383.png)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/CocoaSplit#67
No description provided.