- User Since
- Apr 19 2011, 9:09 AM (439 w, 14 h)
This is still an insta-crash in 2.81... and its a rather serious issue for anyone using the vse along with scene strips... im not sure why this is still considered low priority.
i realize that fixing the above/below behavior is a bit of a big thing, but could we at least fix the issue referenced in https://developer.blender.org/T64964 with a single strip?
It shouldnt be much to fix that, just add an 'if audio imported also, add one to the video channel'... also, adding a check to prevent adding to channel 0 is probably a good idea.
Fri, Sep 6
Wed, Aug 21
side note: The frequency of the interpolation can be controlled with the 'accuracy' setting when exporting as audio only, but there appears to be now way to control this when exporting to video.
My suggestion: This accuracy setting should be changed to a render setting, and always displayed in the render panel under the other audio settings.
ok, this is weird... today im not getting the same issue with the 'bump' when exporting only audio, even compressed.... but I still see the issue every time when exporting to video/audio combined... but I now see it with ANY audio codec in video, not just lossy formats.
Tue, Aug 20
Aug 10 2019
sorry, i guess this isnt really a bug, more of a misunderstanding on my part.
Jul 19 2019
Ah yeah, ctrl-alt-space works. I guess the menu in the console area should be changed to reflect this? right now it lists ctrl-space as the shortcut.
Jul 12 2019
Jun 10 2019
Jun 5 2019
Ah, ok, that explains the lamp thats shining through the object, thanks.
But, what about the reflected one on the side that is visible in the render, but not in viewport?
May 29 2019
in addition, as i stated, if you set everything to 'filmic log' and strips to 'filmic log' or 'raw', it all behaves correctly, EXCEPT for color strips, which cannot have their color space set.
...also having to set every imported vse strip to a different color transform is not ideal...
Filmic is useful for video editing for the same reason filmic is useful in compositing.
Displaying hdr values over 1 is not the only way filmic works, the way colors are mixed and the way they clip is also greatly affected (this is why filmic in the vse is useful).
But, the sequencer does not need to have values over 1 displayed, and the real bug is there is currently is NO WAY to get those values TO display (at least for color strips).
alright, figured id make this easier to test, here's a .blend with the script already loaded and ready to run, just make sure you change the filepath variable or make sure you have a 'video.mpg' file on the root of your D drive
May 24 2019
May 22 2019
May 21 2019
May 20 2019
This is also demonstrating a 'light leaking' behavior (the specular shine on that edge that shouldnt be there either) that has been reported as: https://developer.blender.org/T64787
Maybe its related?
May 11 2019
Is there any hope of having the video auto-packing removed again so it behaves like 2.79? Or will this only be made into a warning popup? I really miss being able to actually use the auto-pack feature...
I understand the desire for blender to behave uniformly across all file types, but sometimes it just doesn't make sense to do so.
May 10 2019
May 5 2019
May 2 2019
Upon further comparisons with blender 2.79, i have noticed similar speeds, with 2.8 only being a couple fps slower with the same setup (the 'material' mode in 2.79 playback being 27fps while the 'lookdev' mode in 2.8 being about 23fps). Similarly, the 'solid' mode is a bit slower in 2.8 as well.
If this smallish slowdown is a bug, or simply new features slowing blender down a bit, I don't know enough to say, I figured I could give some hard numbers just in case.
Apr 30 2019
This seems to not be resolved yet, at least not completely (maybe remove the 'excessively' from the title now? heh).
The latest build is MUCH faster, and actually use-able now, but it is still a lot slower than the viewport.
Even with a very basic camera and cube only scene, lookdev (and solid) mode never gets above 20fps in the vse, and rendered mode about 2fps. viewport for both modes is over 30fps.
Apr 27 2019
Apr 18 2019
Apr 16 2019
what about the fact that there is no way to unpack a video track once it is packed? and no way to manually pack a video-only track?
or how it doesn't auto-pack video-only tracks or image sequences?
or that it doesn't auto-pack a video that is a texture in the 3d view? or the movie clip editor?
if this isn't a bug, then certainly those things are.
Apr 15 2019
What do you mean? Thats the whole issue with this report, it IS packing movie strips.
Apr 14 2019
Mar 14 2019
Mar 13 2019
Dec 18 2018
Nov 15 2018
Note, this bug is still in existence, and still makes the horizontal scrollbar impossible to use in the vse. And, as of 2.8, it seems the region overlap is now enabled by default, meaning that the vse is broken in the default setup...
Sep 22 2018
I was working with him on this script, we did end up getting it to work, and yes, the context was the problem... but regardless, shouldn't blender give an error rather than just crashing? Seems like it is still a bug.
Aug 23 2018
I want to throw in my 2 cents about the scene_update handler too, right now my script needs to check for renamed vse strips, and added strips.
As far as i know, the only way to do this is to use a continuously running function that checks for changes (using scene_update_post right now).
Yes, this is not good behavior, and its not ideal, but give us another option if you are going to remove it...
Without that function, it will severely cripple my script on 2.8.
Jul 8 2018
Image proxies can be useful tho, what about transparent images/sequences? It would be nice if these were proxied in a way to preserve that transparency.
As a side note, I have seen this happen before from some other cause, but it was one of those unreproducable 'what the heck just happened??' moments...
So, it is entirely possible that other combinations of commands may cause this, but Blender was most definitely set to av-sync mode in that situation.
Jul 7 2018
I am also interested in a resolution to this bug.
Jun 22 2018
Mar 8 2017
ok, in the file you provided, the 'transparent' checkbox in the render properties of the 'Text' scene is not checked, that does need to be enabled for proper transparency in the scene strip, and it fixed it on my computer at least (on 2.78c). You should probably change that in the example file.
Mar 7 2017
Your 'Text' scene needs to have transparency enabled in its render settings, enable that and transparency in the vse should work fine.
Jan 8 2017
Just ran into this bug when trying to write an addon that copies a strip to another scene... not possible to use duplicate for such a task, and there seems to be no way of linking the strips, so it seems I might be stuck until this is fixed...
Would it be possible to give bpy.ops.sequencer.duplicate() the ability to duplicate into another scene maybe?
Oct 19 2016
Thank you for looking into this, Olly! Interpolation between frames sounds great, and I doubt anyone would notice unless they are dealing with ridiculously low framerates for some reason.
Oct 17 2016
I noticed that when setting the buffer very high, the volume is not changed mid-buffer (it adjusts the entire buffer's volume to the keyframe value at the beginning of the buffer). My guess is the lack of interpolation between buffers is causing a sudden volume change that is causing the pops.
Apr 30 2016
Mar 2 2016
Seems that the latest version of blender from buildbot does indeed fix this! Fantastic!
Mar 1 2016
ok, managed to reencode the test file and it seems to make blender crash every time.
Ive been away a bit, didnt have any time to test.
Hopefully you will still get notified of the posts when this is closed?
Anyway, those test files do not cause the crash for me either. I think it is related to the resolution or size of the video, or maybe the container, or maybe due to some encoding settings... the files it crashed with were 1080i 8000kbps h264 and ac3 in an mp4 container.
Doing some tests today but reencoding the files takes a while, ill post results when I can narrow it down a bit.
Feb 19 2016
Feb 2 2016
This started happening on my computer, my script using sqlite3 would not work, and typing 'import sqlite3' in the python console would not work.
This was happening in any .blend file (even when I loaded the factory defaults), running blender from various locations, and in several different versions of blender.
Jan 27 2016
May 1 2015
Ah, it is fixed! Awesome, thanks!
Mar 31 2015
Aug 19 2014
If it's an api limitation, why did it work in 2.70? Also if that same operator is called from the console, it behaves as expected, it's only doing this when called from a panel