Wow it's been so long (: I will try recent build sometime this week and see if I can isolate

Wonder if this might be related to https://developer.blender.org/T90855 ?

Figured this would have been reported already... until it is fixed, the function should probably come with a warning about the way in which it is broken, instead of just leaving users to puzzle over why an (already known) problem is occurring :/

In T90633#1224063, @Andrea Beconcini (beco) wrote:

Hi, I would love to work on this if nobody else has started yet!

In T91386#1219578, @Peter Fog (tintwotin) wrote:

The fade functions are implemented as a temporary solution till time permits a proper implementation, maybe modifier based, so it will not interfere with f-curves. The functions are actually coded in python and can be updated without building Blender. Search for a file called sequencer.py in your Blender installation if you want to tinker with it, save it and restart Blender to see the changes.

@Peter Fog (tintwotin) Okay seems you've got pretty full functionality going already, nice :)

In D12441#324316, @Richard Antalik (ISS) wrote:

I will repeat comment from T91191 for calrity. Best to continue technical discussion here.

This change would introduce various issues like:

• What happens when you select multiple strips?
• What happens when selection is randomly distributed?
• What happens when you select all strips?
• What if some script relied on this functionality?

I would propose logic like "Swap active strip, or selected if only one strip is selected". On uncovered cases we can cancel operator with error.

Thanks for initiating this @Peter Fog (tintwotin) ... these legacy problems do creep in over time and can be hard to pinpoint and notice - nice to finally have fingers on it!

In T91284#1218042, @Pratik Borhade (PratikPB2123) wrote:

Hi, thanks for the report. This is actually duplicate of T70246: Tooltips doesn't display when play animation

Will merge this report into T70246 :)

In T91191#1217805, @Peter Fog (tintwotin) wrote:

Imo, all of them should be moved into the strip sidebar which works on the active strip no matter if it is selected or not.
(The Change Path/Files functionality seems to be already exposed in the Source sidebar)

Note: Menu description would be have to be changed from "active strip" to "selected strip" if this is corrected.

In T91191#1217597, @Aditya Y Jeppu (quantimoney) wrote:

Box select doesn't make the strip the active one (although selected) and therefore the function "fails" here. Consistency wise, the box select should have the same functionality (not making anything active but just selected). So mostly this should just be left as it is, other areas in blender too have functionality which is applied to only the active one, even when other entities might be selected.

In T91004#1213693, @Richard Antalik (ISS) wrote:

I have changed report a bit, because this issue is causing unwanted behavior.

@David Salvo (slinkeepie) Please always write steps if you want to present some. GIFs can't be followed well because you can't pause or rewind and you don't know where they even start. Alternatively upload video, but especially steps to reproduce should be in text form.

In T90960#1212252, @Richard Antalik (ISS) wrote:

I haven't closed this due to old GPU, because I think this is duplicate. If above reports can't be reproduced by @David Salvo (slinkeepie), I will merge this report anyway, so he can re-check after probable duplicate is resolved.

In T90960#1211952, @Peter Fog (tintwotin) wrote:

As I understand it, is the Metadata function made for BF inhouse use, if you want to check how it is supposed to be used, then export an image sequence in exr, adding the various metadata https://docs.blender.org/manual/en/dev/render/output/properties/metadata.html Then add this image sequence as a strip and switch on the metadata in the preview https://vse-docs.readthedocs.io/video_sequencer/preview/sidebar.html?highlight=metadata#sidebar

In D12308#319349, @Peter Fog (tintwotin) wrote:

If @David Salvo (slinkeepie) or anyone else want to test how working with drawing handles and outlines this way, you can download a build called D12308 the next few days here: https://builder.blender.org/download/patch/
Direct link to win: https://builder.blender.org/download/patch/blender-3.0.0-alpha+master-D12308.022521ad3922-windows.amd64-release.zip

Thanks Philipp, and yeah sorry, this is probably the first report of mine that I consider obviously not a bug - guess I got a bit carried away 😅 Having said that, I think it's a great idea, so if it doesn't go ahead here I will put on right-click select (unless you can suggest a better place?).

Okay I think I've had a small epiphany in my head as to what's actually happening when you drag any SELECTED/HIGHLIGHTED region of a strip: It's literally just a shortcut for [g]rab, using mouse release instead of click to confirm. I mean it's obvious I guess, but I've never really thought about it too closely.

In T90843#1210251, @Peter Fog (tintwotin) wrote:

I think part of the problem here is that the user do not notice having handles selected, since the strip is both outlined and have handles selected.

If it was either handles or outline showing what is selected, I think it would be avoided. Actually having both selected is inconsistent with how selection works in the 3d view where you do not have both the object and a vertex selected at the same time.

In T90826#1210280, @Philipp Oeser (lichtwerk) wrote:

Not sure I understand correctly.

In your example the strips are positioned so that snapping the right end to the end of the strip below will have exactly the same outcome as snapping the left end to the start of the strip above.
It is true, in this case you dont get the "dual-snapping-lines".
If I move the meta above slightly by one frame on do it again, I can see it snap to both ends.

strips-do-not-snap-at-both-ends-simultaneously-and-right-side-is-preferred-repro.blend603 KBDownload

So I dont see the advantage of displaying both snapping borders if they are exactly lined up? The result of the snapping is correct, no?
Could you elaborate?

In T90843#1210215, @Peter Fog (tintwotin) wrote:

If you mean grab and drag, I think it's a bit difficult, because I know it is annoying to grab and drag the center of the strip, and you intent to move the entire strip and only the handle moves, however there are situations where you would want to grab and drag the center of the strip with the purpose of moving the handles:

In T90843#1210075, @Philipp Oeser (lichtwerk) wrote:

Can confirm the behavior, but this does not look like a bug (it might be an improvement of current behavior though).

@Richard Antalik (ISS), @Peter Fog (tintwotin) : opinions?

Is nowhere safe from spam? :O

In T90855#1209798, @Peter Fog (tintwotin) wrote:

If you add this to the gif {Image_name,size=full} it'll show in full size.

In T90812#1209643, @Peter Fog (tintwotin) wrote:

If you haven't already, you could join the VSE chat: https://blender.chat/channel/vse/ Here we discuss any VSE related question, ex. if you find something odd and you're unsure if it's a bug, it would be a good place to discuss it first.
There are many ways to contribute without being able to code ex. testing new patches or experimental builds can also be a great help.

Having a setup to build Blender is mainly about downloading and installing the right stuff https://wiki.blender.org/wiki/Building_Blender/Linux And ask for help if you get stuck. Applying diffs(patches) is quite simple too. You do not have to code to do any of that stuff, but that would allow you to quickly try out a new patch and report bugs in it if you find any.

In T90812#1209639, @Peter Fog (tintwotin) wrote:

If you build Blender yourself you could try to change the value here #define MAXSEQ 32 https://developer.blender.org/diffusion/B/browse/master/source/blender/makesdna/DNA_sequence_types.h$490 to something else and do the testing needed to check if a change will cause unforseen problems(I guess this might be the major hold back).

Here's a quick test with 64 channels:

Legend!! Thanks so much, super quick :)

Thanks Philipp, appreciate the effort! Hopefully there's not a big technical bottleneck...
Though I didn't show it in the attached example (I should have), when you have more than one showing in the graph editor it does get very confusing (and there are situations where you want multiple selections). Those particular keyframes become very difficult to work with in that case.

In T90407#1201425, @Peter Fog (tintwotin) wrote:

@Richard Antalik (ISS) Additional unused transition improvements: D10207

In T90407#1201288, @Richard Antalik (ISS) wrote:

Technically this never worked properly, but arguably rBd373b43f07f5 made it a bit worse. Got some initial fix ready, will continue tomorrow to cover more edge cases.

Hi all, can confirm this with v3 alpha ede1ce6e9a5b .
Not sure if it helps, but switching sound from Pulseaudio to Open AL fixed it for me...
David