VSE: Continuus Camstudio clip changes framerate after an image clip. #44760

Closed
opened 2015-05-19 09:47:05 +02:00 by Lino Thomas · 10 comments

System Information
Tested on Windows 7 (gtx970) and 8(no information of the gpu here).

Blender Version
Broken: 2.74 (000dfc0) [2015-03-31] Official blender build from website.

Short description of error
We have a camstudio video imported into the vse. We add now a image to the vse and put it somewhere above the video sequence. The image is displayed shorter than the video and doesnt interrupt the video clip.
When rendering the video the framerate changes after the imageclip was passed. Before the image clip it renders at normal speed, after passing the part with the image the framerate doubles. The video ends therefore way to early. The sound doesnt get played faster and ends at the expected time.
Upon deleting the image, blender renders the video as expected.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

Open the attached blend and just render the file.
Delete the image to see it rendering correctly.

blend test.zip

**System Information** Tested on Windows 7 (gtx970) and 8(no information of the gpu here). **Blender Version** Broken: 2.74 (000dfc0) [2015-03-31] Official blender build from website. **Short description of error** We have a camstudio video imported into the vse. We add now a image to the vse and put it somewhere above the video sequence. The image is displayed shorter than the video and doesnt interrupt the video clip. When rendering the video the framerate changes after the imageclip was passed. Before the image clip it renders at normal speed, after passing the part with the image the framerate doubles. The video ends therefore way to early. The sound doesnt get played faster and ends at the expected time. Upon deleting the image, blender renders the video as expected. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps Open the attached blend and just render the file. Delete the image to see it rendering correctly. [blend test.zip](https://archive.blender.org/developer/F177375/blend_test.zip)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @LinoThomas

Added subscriber: @LinoThomas

Added subscriber: @Psy-Fi

Added subscriber: @Psy-Fi

Confirmed, will take a look

Confirmed, will take a look
Antonis Ryakiotakis self-assigned this 2015-05-19 12:06:58 +02:00
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Any news?

Any news?

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Confirmed and looked into it.

Whats happening is the image causes the frames of the video not to be read. Then when the video shows again,
(as far as ffmpeg is concerned) this is read from a random location in the video stream.

This also happens if you remove the image shift the start of the video to where the image ended. The duration of the slowdown is the same too.

Ideally Blender would prefetch frames to avoid this (or handle the codec better).
However this is more an area to improve, rather than a bug.

For now, you can work around the problem by using codecs which better support random seeking. (lots of info about this online, you could try simpler codecs such as mjpeg, or you could enable proxies which use timecode to improve seeking).

Confirmed and looked into it. Whats happening is the image causes the frames of the video not to be read. Then when the video shows again, (as far as ffmpeg is concerned) this is read from a random location in the video stream. This also happens if you remove the image shift the start of the video to where the image ended. The duration of the slowdown is the same too. Ideally Blender would prefetch frames to avoid this (or handle the codec better). However this is more an area to improve, rather than a bug. For now, you can work around the problem by using codecs which better support random seeking. *(lots of info about this online, you could try simpler codecs such as mjpeg, or you could enable proxies which use timecode to improve seeking).*
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
5 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#44760
No description provided.