Video gets cut in half after adding it to the VSE in 2.77 or 2.77a - need ffmpeg update #48686

Closed
opened 2016-06-20 08:50:53 +02:00 by John Moran · 16 comments
Model Name:	iMac V 10.6.8
Model Identifier:	iMac11,2
Processor Name:	Intel Core i3
Processor Speed:	3.2 GHz
Memory: 4 GB

64-bit Operating System

ATI Radeon HD 5670
VRAM (Total):	512 MB

Windows 7 Professional
Dell XPS L502X Laptop
Intel i7 2630QM CPU @ 2.00 GHz
Memory: 6.00 GB
NVIDIA GeForce GT 525M
64-bit Operating System

Blender Version
Broken: 2.77 and 2.77a
Worked: 2.76b

I add a video (1080 or 4k .mp4) to the VSE by adding it or drag and dropping it to the sequencer with all the correct frame rate and frame length (also without the correct frame rate and frame length) but it gets cut close to half in 2.77 and 2.77a (should be 3912 frames but only 1953 frames show up. Except the audio is correct or shows up full). Added the same video without making sure the frame or length was correct in 2.67b and the whole video was there. This happens on a Mac and Windows using any 1080 or 4k .mp4 video.
Thank you for all you hard work and a great program
John Moran
jmoran@san.rr.com

``` Model Name: iMac V 10.6.8 Model Identifier: iMac11,2 Processor Name: Intel Core i3 Processor Speed: 3.2 GHz Memory: 4 GB ``` 64-bit Operating System ``` ATI Radeon HD 5670 VRAM (Total): 512 MB ``` Windows 7 Professional Dell XPS L502X Laptop Intel i7 2630QM CPU @ 2.00 GHz Memory: 6.00 GB NVIDIA GeForce GT 525M 64-bit Operating System **Blender Version** Broken: 2.77 and 2.77a Worked: 2.76b I add a video (1080 or 4k .mp4) to the VSE by adding it or drag and dropping it to the sequencer with all the correct frame rate and frame length (also without the correct frame rate and frame length) but it gets cut close to half in 2.77 and 2.77a (should be 3912 frames but only 1953 frames show up. Except the audio is correct or shows up full). Added the same video without making sure the frame or length was correct in 2.67b and the whole video was there. This happens on a Mac and Windows using any 1080 or 4k .mp4 video. Thank you for all you hard work and a great program John Moran jmoran@san.rr.com
Author

Changed status to: 'Open'

Changed status to: 'Open'
John Moran self-assigned this 2016-06-20 08:50:53 +02:00
Author

Added subscriber: @Jmoran

Added subscriber: @Jmoran

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Please link to a sample video that has this problem.

Please link to a sample video that has this problem.
Author

Here is a link to the video (Test Video.mp4) and the .blend file (test video.blend) with the video packed into the file.
https://www.dropbox.com/sh/yoy7dhj9bsxt5xv/AABHa1uLMFChs-BOYY4VCqk2a?dl=0

The video was shot with a LG G3 phone. VLC player says the frame rate is 29.451966 codec is H264 MPEG-4 AVC (part 10) (avc1).

The other bug I did not mention if you look at the Test Video.blend file the Auto Frame Rate put the video at Custom (10.0 fps) FPS:120 /: 12.000.
I didn't want to add it as it was not so important as the VSE cutting video.
Thank you so much
You are awesome for getting back to me so soon specially for an open source program. Another reason Blender is so great!

Here is a link to the video (Test Video.mp4) and the .blend file (test video.blend) with the video packed into the file. https://www.dropbox.com/sh/yoy7dhj9bsxt5xv/AABHa1uLMFChs-BOYY4VCqk2a?dl=0 The video was shot with a LG G3 phone. VLC player says the frame rate is 29.451966 codec is H264 MPEG-4 AVC (part 10) (avc1). The other bug I did not mention if you look at the Test Video.blend file the Auto Frame Rate put the video at Custom (10.0 fps) FPS:120 /: 12.000. I didn't want to add it as it was not so important as the VSE cutting video. Thank you so much You are awesome for getting back to me so soon specially for an open source program. Another reason Blender is so great!
John Moran was unassigned by Bastien Montagne 2016-06-21 16:25:56 +02:00

Added subscriber: @mont29

Added subscriber: @mont29

Please try the latest build from our buildbot. Here everything looks OK (1953 frames at 29fps makes it 1min6sec, as expected). 2.77a however indeed detects/sets bad framerate, but this seems to be fixed in current master.

Please try the latest build from [our buildbot](https://builder.blender.org/download). Here everything looks OK (1953 frames at 29fps makes it 1min6sec, as expected). 2.77a however indeed detects/sets bad framerate, but this seems to be fixed in current master.
Author

I am sorry but the problem is still happening in that new build (blender-2.77-994dd5c-OSX-10.6-x86_64.zip) except now the auto frame rate is Custom (58.92fps) FPS: 707 /: 12.000. (In 2.76b the frame length comes out 3912 which is at 1min 6sec and that is the whole clip). When I add the video to the new build as was the problem in 2.77a the video comes out at 1953 frames at 33sec and should be 3912 frames at 1min 6sec. The cut clip shows the dog sniffing near a yellow patch of grass at the end. The whole clip has the dog walking away from camera at the end (just for your reference). Here is the link to the .blend file of the new build you ask me to use with the same video cut problem called (Test Video 1.blend). The .blend file has the video pack into the file. https://www.dropbox.com/sh/yoy7dhj9bsxt5xv/AABHa1uLMFChs-BOYY4VCqk2a?dl=0
Thank you so much for all you work!!

I am sorry but the problem is still happening in that new build (blender-2.77-994dd5c-OSX-10.6-x86_64.zip) except now the auto frame rate is Custom (58.92fps) FPS: 707 /: 12.000. (In 2.76b the frame length comes out 3912 which is at 1min 6sec and that is the whole clip). When I add the video to the new build as was the problem in 2.77a the video comes out at 1953 frames at 33sec and should be 3912 frames at 1min 6sec. The cut clip shows the dog sniffing near a yellow patch of grass at the end. The whole clip has the dog walking away from camera at the end (just for your reference). Here is the link to the .blend file of the new build you ask me to use with the same video cut problem called (Test Video 1.blend). The .blend file has the video pack into the file. https://www.dropbox.com/sh/yoy7dhj9bsxt5xv/AABHa1uLMFChs-BOYY4VCqk2a?dl=0 Thank you so much for all you work!!
Author

Okay I am not very fast at math and I should have known that 1953 frames equals 1min 6 sec at 29.451966. But everything I said in my last comment is true. So thinking about it 2.76b was giving me the wrong frame rate at 3912 frames but showing me the whole clip and 2.77a and the new build is giving me the correct frame rate but only showing me half the clip as you will see in my (Test Video 1.blend) file it shows 1953 frames at 33 sec and if you look at the original clip the 33sec mark shows the dog sniffing near the yellow spot of grass and 33sec later the dog is walking away from camera at 1min 6sec.
Sorry for not realizing I was getting the correct frame rate just not the whole clip.

Okay I am not very fast at math and I should have known that 1953 frames equals 1min 6 sec at 29.451966. But everything I said in my last comment is true. So thinking about it 2.76b was giving me the wrong frame rate at 3912 frames but showing me the whole clip and 2.77a and the new build is giving me the correct frame rate but only showing me half the clip as you will see in my (Test Video 1.blend) file it shows 1953 frames at 33 sec and if you look at the original clip the 33sec mark shows the dog sniffing near the yellow spot of grass and 33sec later the dog is walking away from camera at 1min 6sec. Sorry for not realizing I was getting the correct frame rate just not the whole clip.

Added subscriber: @Sergey

Added subscriber: @Sergey

I still cannot reproduce the issue, here on my linux build of current master it loads the video correctly (1953 frames over 1min06sec). However, indeed loading it with testbuild of linux64 of today am getting odd things.

So my bet is, your file is too recent for ffmpeg used in official builds (own debian testing version is newer than the one used on testbuilds), i.e. you'll have to wait for an update there (@Sergey shall know better about that), until then you'll have to adjust framerate manually…

I still cannot reproduce the issue, here on my linux build of current master it loads the video correctly (1953 frames over 1min06sec). However, indeed loading it with testbuild of linux64 of today am getting odd things. So my bet is, your file is too recent for ffmpeg used in official builds (own debian testing version is newer than the one used on testbuilds), i.e. you'll have to wait for an update there (@Sergey shall know better about that), until then you'll have to adjust framerate manually…
Bastien Montagne changed title from Video gets cut in half after adding it to the VSE in 2.77 or 2.77a to Video gets cut in half after adding it to the VSE in 2.77 or 2.77a - need ffmpeg update 2016-07-15 16:39:50 +02:00
Author

It must be the Phones way of doing the frame rate in combo with Windows and Mac OS build if you are not getting my results. I cant get blender to give me back the last half of any video no matter what I try on Blender. I can of course use another Editing program like Premiere and it works just fine. I just want to use Blender to do all my video and animation work. Just so you know and if it might help. I did run the video through HandBrake and trans-coded the video to 29.97 FPS instead of how it came straight out of the phone at 29.451966 FPS and it worked on blender perfect in all respects on both Windows and MAC OS. I don't know enough if that is an ffmpeg problem or not, I hope it is and you wont have to work on the build too hard to fix it.
Thank you so much for all your work!!

It must be the Phones way of doing the frame rate in combo with Windows and Mac OS build if you are not getting my results. I cant get blender to give me back the last half of any video no matter what I try on Blender. I can of course use another Editing program like Premiere and it works just fine. I just want to use Blender to do all my video and animation work. Just so you know and if it might help. I did run the video through HandBrake and trans-coded the video to 29.97 FPS instead of how it came straight out of the phone at 29.451966 FPS and it worked on blender perfect in all respects on both Windows and MAC OS. I don't know enough if that is an ffmpeg problem or not, I hope it is and you wont have to work on the build too hard to fix it. Thank you so much for all your work!!
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

After updating FFmpeg can we close this? @Jmoran try using a daily build https://builder.blender.org/download/

After updating FFmpeg can we close this? @Jmoran try using a daily build https://builder.blender.org/download/

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Bastien Montagne self-assigned this 2017-01-06 14:39:01 +01:00

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided. For now assuming this has been fixed.

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided. For now assuming this has been fixed.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
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: blender/blender#48686
No description provided.