Python API: sequencer_strip.frame_start inconsistancy #100688

New Issue

Vincent Girès · 2022-08-29T14:17:33+02:00

Vincent Girès commented

2022-08-29 14:17:33 +02:00

System Information
Operating system: Linux-3.10.0-1160.59.1.el7.x86_64-x86_64-with-glibc2.17 64 Bits
Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02

Blender Version
Broken: version: 3.3.0 Beta, branch: master, commit date: 2022-08-28 21:53, hash: 7b56c74881
Worked: 3.2

Short description of error
On 3.3.0 beta, the start_frame attribute of a strip is a float number. which make some inconsistency with
bpy.context.scene.sequence_editor.sequences.new_movie and frame_start argument that require integer only and fail with float.
I do not see such a change on the release log so I imagine this is not made on purpose?

Exact steps for others to reproduce the error
type(bpy.context.sequences- [x].frame_start)

**System Information** Operating system: Linux-3.10.0-1160.59.1.el7.x86_64-x86_64-with-glibc2.17 64 Bits Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02 **Blender Version** Broken: version: 3.3.0 Beta, branch: master, commit date: 2022-08-28 21:53, hash: `7b56c74881` Worked: 3.2 **Short description of error** On 3.3.0 beta, the start_frame attribute of a strip is a float number. which make some inconsistency with bpy.context.scene.sequence_editor.sequences.new_movie and frame_start argument that require integer only and fail with float. I do not see such a change on the release log so I imagine this is not made on purpose? **Exact steps for others to reproduce the error** type(bpy.context.sequences- [x].frame_start)

Vincent Girès commented

2022-08-29 14:17:33 +02:00

Added subscriber: @VincentGires

Omar Emara commented

2022-08-29 15:57:01 +02:00

Added subscribers: @iss, @OmarEmaraDev

Omar Emara commented

2022-08-29 15:57:01 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Omar Emara commented

2022-08-29 15:57:01 +02:00

The change looks intentional in 302b04a5a3.
But I guess it should be added to the release notes regardless.

The change looks intentional in 302b04a5a3. But I guess it should be added to the release notes regardless.

Vincent Girès commented

2022-08-29 16:07:25 +02:00

ah ok! sorry didn't check commits but only logs. i have to update my scripts then ;)

Richard Antalik commented

2022-08-29 20:14:21 +02:00

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Richard Antalik closed this issue

2022-08-29 20:14:21 +02:00

Richard Antalik self-assigned this 2022-08-29 20:14:21 +02:00

Richard Antalik commented

2022-08-29 20:14:21 +02:00

This was intentional change to allow retiming strips in a way, they can start and end at what would technically be subframe. Thanks for reminding, that this causes issues in existing scripts - added entry to release notes now.

Vincent Girès commented

2022-08-30 10:02:15 +02:00

yes indeed that would be nice to warn users since at least for me, there is at lot of places where i use this kind of script
scene.frame_start = strip.frame_start where it now fails on 3.3.0. easy to fix but better to know before the official release :)
thanks for your work!

yes indeed that would be nice to warn users since at least for me, there is at lot of places where i use this kind of script scene.frame_start = strip.frame_start where it now fails on 3.3.0. easy to fix but better to know before the official release :) thanks for your work!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Python API: sequencer_strip.frame_start inconsistancy #100688