Volume Keyframe on Cut-ted Metastrip #55668

Closed
opened 5 years ago by eaterjolly · 7 comments

System Information
Replicated on multiple platforms.

Blender Version
Broken: 2.79b
Worked: unknown

Short description of error
When frequently cutting and dragging elementary strips, that gives frequent opportunities to lose audio-video synchronization, often enough without noticing that has occurred until after a while of editing. Depending on how much editing takes place after losing synchronization simply spamming undo may not be a feasible means of reversal and manual re-alignment can require excessive effort that a amateur might barely find themselves capable of, so meta-ing synchronized audio-&-video strips seems best practice however seems to disable keying in all resultant cut strips thereafter.

Whether this expected function or a bug seems unknown, however has persisted for as long as I have been using blender and I'm sure implementing keyframing inside cut meta-strips (if the functionality doesn't already exist and this isn't a bug) should be much simpler than implementing automatic audio-video re-sychronization of separated strips.

Despite never having seen another bug report or stack-question about this, I'm confident this is a widely-affectent issue and one I'm sure any novice exclusively using blender for video-editing would prioritize as an issue they would most appreciate see-ing resolved.

Exact steps for others to reproduce the error
After a meta-strip has been cut, tab to enter 'the later' meta-strip (beginning after the selected frame), select audio strip, then attempt to set a keyframe.

Error:
Could not insert keyframe, as RNA path is invalid for the given ID (ID = SCScene, sequence_editor.sequences_all["{$source-file-name}".002].volume)

**System Information** Replicated on multiple platforms. **Blender Version** Broken: 2.79b Worked: unknown **Short description of error** When frequently cutting and dragging elementary strips, that gives frequent opportunities to lose audio-video synchronization, often enough without noticing that has occurred until after a while of editing. Depending on how much editing takes place after losing synchronization simply spamming undo may not be a feasible means of reversal and manual re-alignment can require excessive effort that a amateur might barely find themselves capable of, so meta-ing synchronized audio-&-video strips seems best practice however seems to disable keying in all resultant cut strips thereafter. Whether this expected function or a bug seems unknown, however has persisted for as long as I have been using blender and I'm sure implementing keyframing inside cut meta-strips (if the functionality doesn't already exist and this isn't a bug) should be much simpler than implementing automatic audio-video re-sychronization of separated strips. Despite never having seen another bug report or stack-question about this, I'm confident this is a widely-affectent issue and one I'm sure any novice exclusively using blender for video-editing would prioritize as an issue they would most appreciate see-ing resolved. **Exact steps for others to reproduce the error** After a meta-strip has been cut, `tab` to enter 'the later' meta-strip (beginning after the selected frame), select audio strip, then attempt to set a keyframe. Error: `Could not insert keyframe, as RNA path is invalid for the given ID (ID = SCScene, sequence_editor.sequences_all["{$source-file-name}".002].volume)`
Poster

Added subscriber: @eaterjolly

Added subscriber: @eaterjolly
mont29 commented 5 years ago
Owner

Added subscriber: @mont29

Added subscriber: @mont29
mont29 self-assigned this 5 years ago
mont29 commented 5 years ago
Owner

The problem comes from the naming of new strips inside the new meta strip - they are both (video and audio ones) named the same, this should never happen imho, and certainly will break unique RNA path any strip shall have. Will check.

The problem comes from the naming of new strips inside the new meta strip - they are both (video and audio ones) named the same, this should never happen imho, and certainly will break unique RNA path any strip shall have. Will check.
Collaborator

This issue was referenced by bb98e83b99

This issue was referenced by bb98e83b99e63348e0396a5ffe5bb2a20ff1607a
mont29 commented 5 years ago
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
mont29 closed this issue 5 years ago
Collaborator

This issue was referenced by c97794520f

This issue was referenced by c97794520f030b03a87c5c7b386aeb64571f46f6
Collaborator

This issue was referenced by 1ded3d2f7c

This issue was referenced by 1ded3d2f7c04100698afdee356e2ba8d4ae2d6bd
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Overrides
Interest/Performance
Interest/Pipeline, Assets & I/O
Interest/Translations
Interest/Undo
Interest/USD
Interest/Video Sequencer
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/Nodes & Physics
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Performance
legacy project/Physics
legacy project/Platforms, Builds, Tests & Devices
legacy project/Pose Library Basics
legacy project/Python API
legacy project/Render & Cycles
legacy project/Render Pipeline
legacy project/Retrospective
legacy project/Sculpt, Paint & Texture
legacy project/Text Editor
legacy project/Tracker Curfew
legacy project/Triaging
legacy project/User Interface
legacy project/UV Editing
legacy project/VFX & Video
legacy project/Virtual Reality
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#55668
Loading…
There is no content yet.