[Matthias Noe]

Hey, Pierre,

Thanks for the offer, but I mjust found out two things:
a) that this effect is also not reserved to twixtor but at least to PPs new Morph Cut feature, aswell.
b) there is a rather easy work around: The phenomenon vanishes as soon as I do not output directly to h.264 (be it as *mp4 or *mov). I realized when I wanted to output 2 jpeg stills to showcase the problem here in the forum and there was no brightness difference left at all in these stills :). But maybe this information is already helpful to you.

Greets,
Matt

MY SYSTEM:
OS: Windows 7 | 64Bit | Ultimate
Motherboard: Asus | P8P67 DELUXE
Processor: Intel | Core i7-2600K 3400 1155
GPU: ASUS | GeForce GTX760 | 2 GB
RAM: G.Skill | Ripjaws 16GB 1333-999 | 4x4GB
System-Drive: ADATA | Internal SSD, 128GB | ASP900S3-128GM-C | Sata
Monitor: Eizo | 23 L FS2331-BK

[Matthias Noe]

Hey, Pierre,

Thanks for the offer, but I mjust found out two things:
a) that this effect is also not reserved to twixtor but at least to PPs new Morph Cut feature, aswell.
b) there is a rather easy work around: The phenomenon vanishes as soon as I do not output directly to h.264 (be it as *mp4 or *mov). I realized when I wanted to output 2 jpeg stills to showcase the problem here in the forum and there was no brightness difference left at all in these stills :). But maybe this information is already helpful to you.

Greets,
Matt

MY SYSTEM:
OS: Windows 7 | 64Bit | Ultimate
Motherboard: Asus | P8P67 DELUXE
Processor: Intel | Core i7-2600K 3400 1155
GPU: ASUS | GeForce GTX760 | 2 GB
RAM: G.Skill | Ripjaws 16GB 1333-999 | 4x4GB
System-Drive: ADATA | Internal SSD, 128GB | ASP900S3-128GM-C | Sata
Monitor: Eizo | 23 L FS2331-BK

[Matthias Noe]

It’s been this way since a couple of versions and Adobe doesn’t seem to bother. And there are a couple of instances that can occur where the editor is not really to blame: e.g. when he is relatively new to the job and so caught up in the tunnel that 1 hour passes like 5 minutes, or when even the work of 5 minutes is hard to rebuild sometimes. It’s just a frustrating experience and it’s totally avoidable if the software did what it promises to do. Period.
I just had the case that I had two sequences named the same in my project(I had re-imported another cut that I had saved seperately) and all of a sudden, the one I was working on just turned into the older one with the same name. So abruptly I had two identical sequences with the status from 2 days ago and no undo could bring back my work. And OF COURSE the most recent Autosave (every 10 minutes is my setup) is an hour old. A freaking hour! And there was nothing I could do. Yes, I could force the habbit to save every 5 minutes but isn’t that something that Adobe clearly can and simply should automate for us editors? They even claim to do so but from version CS3 or so on this bug is like a huge middle finger to everyone who foolishly thinks that the promised auto save works. It just should work. Period.

MY SYSTEM:
OS: Windows 7 | 64Bit | Ultimate
Motherboard: Asus | P8P67 DELUXE
Processor: Intel | Core i7-2600K 3400 1155
GPU: ASUS | GeForce GTX760 | 2 GB
RAM: G.Skill | Ripjaws 16GB 1333-999 | 4x4GB
System-Drive: ADATA | Internal SSD, 128GB | ASP900S3-128GM-C | Sata
Monitor: Eizo | 23 L FS2331-BK

[Matthias Noe]

To specify a bit more, I did an all hand-animated mood shot if you will of how the fireflies should move along said path.

https://www.youtube.com/watch?v=EAxuB1hgEQY&

This was done crudely by handanimating a couple of lens flares’ adjustment layers (hence the bit unrealistic motion blur), wiggling their brightness with an expression, whilst due to keyframing of course not having the slightest bit of universal control over them as a ‘swarm’. I COULD do it that way, but I’d loose the great looks of powerful, swarmy look that particles create plus not learn something new while doing it. Maybe somebody in here knows how to pull a shot like that off with particles in AfterFX. I feel like a 400$ PlugIn like Particular should do a trick like that easily…