Skip to content
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

First just sound, video follows after a few seconds #26

Closed
Haringkoning opened this issue Feb 16, 2017 · 9 comments
Closed

First just sound, video follows after a few seconds #26

Haringkoning opened this issue Feb 16, 2017 · 9 comments
Labels
bug keyframe cut Problem is related to accurately cutting on frames or keyframes

Comments

@Haringkoning
Copy link

Haringkoning commented Feb 16, 2017

Hi, when I use LosslesCut on a Mac (macOS Sierra 10.12.23 (16D32) some edited videos have the following problem: video starts, I can hear sound but no video yet, only after a few seconds the video can be seen. From that moment the video plays correct (in sync). Publishing such clips on YouTube is not possible. The file can be uploaded, but can't be processed.
I have included a sample of such video.
uhlvjd.mp4-00.32.16.547-00.33.04.956.mp4.zip

@Haringkoning
Copy link
Author

Some info provided by MediaInfo:
General
Complete name : /Users/.../Downloads/uhlvjd.mp4-00.32.16.547-00.33.04.956.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 5.65 MiB
Duration : 48 s 406 ms
Overall bit rate : 979 kb/s
Encoded date : UTC 1904-01-01 00:00:00
Tagged date : UTC 1904-01-01 00:00:00
Writing application : Lavf57.56.100

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 39 s 0 ms
Bit rate : 1 010 kb/s
Width : 720 pixels
Height : 436 pixels
Display aspect ratio : 16:9
Original display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.129
Stream size : 4.70 MiB (83%)
Encoded date : UTC 1904-01-01 00:00:00
Tagged date : UTC 1904-01-01 00:00:00
Color range : Limited
Color primaries : BT.601 PAL
Transfer characteristics : BT.709
Matrix coefficients : BT.601

Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 48 s 406 ms
Bit rate mode : Constant
Bit rate : 160 kb/s
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 spf)
Compression mode : Lossy
Stream size : 946 KiB (16%)
Language : English
Default : Yes
Alternate group : 1
Encoded date : UTC 1904-01-01 00:00:00
Tagged date : UTC 1904-01-01 00:00:00

@mifi
Copy link
Owner

mifi commented Feb 17, 2017

Does it matter where you do the cut? (start-end points)

@Haringkoning
Copy link
Author

Nope, some are fine from 00:00:00 till an any point are fine, some not. The same goes for videos edited at any other point.

@mifi
Copy link
Owner

mifi commented Feb 17, 2017

If you do the same cut many times on the same video, sometimes it works on youtube and other times it does not? You're saying it's not deterministic?

@Haringkoning
Copy link
Author

That's correct; some are fine, some aren't. In general the videos downloaded from YouTube can be edited without problems.

@codyolsen
Copy link

@mifi This sounds like the same issue in #13

@mifi mifi added the bug label Mar 19, 2017
@mifi mifi added the keyframe cut Problem is related to accurately cutting on frames or keyframes label Mar 26, 2017
@TechManiacHD
Copy link

It seems like the same bug to me. I noticed it on many of the cutted videos. I learnt to cut with adding few extra seconds to the clip on both ends.
Although, I am cutting videos in order to save disk space and then I am doing everything else in PowerDirector 16. With Losseless-cut I am only cutting off that footage that I would not use for sure and that way i can safe up to 1/3 space on each project.

@bnku
Copy link

bnku commented Feb 2, 2018

I confirm the presence of this problem.

@mifi
Copy link
Owner

mifi commented Feb 11, 2018

Yes, unfortunately this is the long standing issue with ffmpeg not being able to consistently cut on the keyframe borders. Long discussion here: #13

@TechManiacHD that's a very good tip, i'm using the same technique. I'll add it to readme.

@mifi mifi closed this as completed Feb 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug keyframe cut Problem is related to accurately cutting on frames or keyframes
Projects
None yet
Development

No branches or pull requests

5 participants