In T63607#661898, @hudson barkley (snuq) wrote:

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?

Cache visualization is now displayed in similar way to timeline cache visualization.

Can not reproduce this.

Video file is a source of audio strip in some cases. Movie strips doesn't support packing, so technically it's doing what it is supposed to do.

@Sebastian Parborg (zeddb) I guess you can use https://wiki.blender.org/wiki/Process/Module_Owners/List if unsure.

In T63372#656531, @David Brennan (davidbrennan) wrote:

Wait: Then how do you edit animations in sync with audio and images in the VSE?

Step 1: Move marker area to the top

Agree, would fix T57976: VSE, marker area is invisibly blocking the strips

I was thinking of a different problem than prefetch and cache disk solve. What I think could be faster is tweaking strip parameters and effect parameters within a single frame. Right now it seems to load raw images and re-render scene strips for that all the time. Using a variation of rna_Sequence_update for certain properties that don't need to clear raw images in the cache would be relatively simple to add I expect. And as I understand it the raw images for the current frame are always in the cache regardless of the cache settings.

In D4443#104236, @Brecht Van Lommel (brecht) wrote:

Works well in my tests, still some comments which are hopefully easy to address

• I expected the options to show the cache to be in the View menu, similar to how it is in the timeline.
• Cache visualization should be more similar to the timeline (just add e.g. a softbody modifier to see it). Thinner, orange and semi-transparent and maybe at the bottom? It's a bit too eye-catching now I think, and drawing similar to the timeline helps users recognize what it is.

• change type of BKE_sequencer_cache_put_if_possible to bool
• implement ghash iterator utilizing callback

Thanks, I was busy this week haven't got even to respond to you.

In T62604#642812, @Brecht Van Lommel (brecht) wrote:

@Richard Antalik (ISS), you actually have commit rights to the documentation repository (username and password and are the same as for logging into this site).

@Olly Funkster (Funkster) this is problem with 3D scenes..

Task is more or less invalid, but docs should be fixed so I guess..
I can not make those changes (I think)

I am dividing by scene->r.*sch - should I check for zero?

Thanks for pointing this out. Adding scene to itself is not supported for quite a while.

@hudson barkley (snuq) Brecht probably meant that VSE code does not have setup of new viewport in place to allow fast rendering.

Can confirm this (also can not open file).

Thanks, I wasn't looking hard enough :)

Added default values for RNA properties
SeqCache is "self contained" - no reference to IMB_moviecache

I was thinking about this IMB_moviecache issue we have here - in D3934: VSE cache with frame prefetching (WIP) I pointed to a direction I want to go with cache

renamed free_after_render -> is_temp_cache
removed some prefetch specific code
Added this text to seqcache.c:

Cleanup diff
fix crash when changing resolution

Given no exact steps, I simply used Blender's file browser to look if I can see downloaded image

Will fix.

In rB005626b8c6b4e9af92ffc07d0b3f2b0a1c8dc4b8#220119, @Campbell Barton (campbellbarton) wrote:

Oops, "Video Editing" not "VFX". The main preview with the factory settings.

In rB005626b8c6b4e9af92ffc07d0b3f2b0a1c8dc4b8#220068, @Campbell Barton (campbellbarton) wrote:

Wire outline is no longer draws correctly w/ default VFX startup.

Is P917 patch on top of this diff?

Well practical thing to do here is to give up :)
Personally I don't care, I would remove all poll functions from all operators ;)
What I am saying is, that clicking that button will cause a visible action, that can do nothing...

In T61923#627800, @Jon Seigel (jseigelis) wrote:

Oh, my bad, I didn't mean to step on your toes.

Naah.

Fix private function name.

I also rewrote this operator in patch D4290: VSE new python operators

I can not confirm this.

In T60743#623877, @ThinkingPolygons (ThinkingPolygons) wrote:

Turning off region overlap fixes it, yeah.

When rendering scene, cache is cleared. Currently the cache is global, so it prevents caching.

I asked in IRC, I was suggested to revert commit and commit again, so I did that.

@Brecht Van Lommel (brecht), Sorry I accidentally committed D4396: Fix VSE color picker with this.

Thanks for correcting me.

Thanks for clarification.

I would like to use this patch. Can not update, so uploaded new version.
Removed comments, functionality is clear enough, task will be referenced in commit message.

Is this the same issue? T54438: Sequencer Scene preivew Color Management is broken

I will "fix" this for most sane cases.

Indeed, this is much better. Thanks.

In T60460#625623, @Andrew Sprok (sprad001) wrote:

the only problem with that is, every time you download a new build you need to add the --factory-startup