My understanding of backward and forward compatibility was kinda reversed - from application point of view, to support newer files.
So if this is not the case, I will consider different approach here

I tested it in your custom build and it's a much welcome improvement! How about updating the scale when volume != 1.0? I use .wav audio samples and soundtracks that are normalized by default, and I lower their volume in the VSE. But the waveform still doesn't reflect that. Would that improvement be possible? It'd be much welcome for me 😄

Fix issue with not deleting original proxy file
Add dirty mutex, so it is very unlikely to crash building proxies by human interaction, but I have to look deeper, how it is usualy done in blender.
For multithreading I am using my wm_jobs "hack" but I think, that it may be useful for this kind of job manager to be able to run more than one jobs.

Fix HUGE memory leak (still some bytes left, but not gigs of them at least :)
Add PNG / MJPEG codec selection to UI
Render smaller imbufs instead of post-scaling
Render everything to fixed size - so 25% proxy no longer means 25% of source resolution, but it is 25% of "project" resolution (scene->r.xsch)

Well, ideally you would use the offsets as they were used before. But if not, you don't have to convert before storing, since we're not forward compatible, but we have to be backward compatible, that's what do_versions() is for.

I can "convert" old files, by adjusting offsets when loading.
When I load files blend file saved by blender compiled with this diff, it's much worse - there can be sequences with 0 length
I can "convert" offsets back when saving.

fix minor issues, that slipped

I tried the patch. Animated strips work now, but I still have trouble with strips loaded from a file that was created with vanilla blender.

Great, thanks! invite sent.

Hi, it's richardantalik at google mail

Hi @Richard Antalik (ISS) I would like you to join a small slack workspace with myself and a few others who are interested in upgrading the VSE.
If you can share with me an email address I would be happy to send an invite to you.

@Richard Antalik (ISS) I would create a new differential as this one has messed up permissions. Unless an admin like @Campbell Barton (campbellbarton) can fix it.

In T54259#526451, @Richard Antalik (ISS) wrote:

I can provide windows build

Just a notice to anyone interested:
I started working on this and will need a week or 2 to polish it

rebase on top of latest master

Looks like a mismatch between premultiplied and straight alpha… bytes are always straight iirc, while float are usually premultiplied in sequencer…

Looks like there's a problem with the 32-bit float image.

Hey, sorry for the slow responses, I'm quite busy at work at the moment. Can you please update the patch? Currently it doesn't apply.

I couldn't reproduce this issue, but I think I know what may cause it (I still don't know how exactly it gets triggered though).

I think this is for you @Joshua Leung (aligorith) ?

I can't get it to constantly crash in both Windows and Linux under the same circumstances.
Sometimes it crashes in all editors and sometimes not...

Committed rBc8b6e3d77717a6efdc0dc68c18aa07a291385e3a

Fixed audio glitching when pitch is animated, also sequence position / length is stable now. I was not able to reproduce these 1 frame offsets that I remember seeing last time.

I was sad to see this functionality lost as well, I used it to preview scenes with a compositor performing image manipulation. It was (almost?) the only way to buffer the compositor for a play-blast.

Looking into it…

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.

Indeed… :/

As stated earlier, we are currently only accepting crash reports for 2.8. Furthermore, in this case, the behaviour here is the same as it was in master, and is the same as what happens for Text objects.

Oh my bad then... Sry.

https://code.blender.org/2018/06/beyond-the-code-quest/ you lost this. just under a first photo. it is published on Jun 29th

@dark999 (dark999) What do you mean?
Am I only suppose to submit bugs that crash blender?
Did I miss a line somewhere?
'Cause I think I read everything how to commit bugs.

I'm just curious, Blender 2.8 crash ?? Or 'crash report only' is said only to make noise?