[Pierre Jasmin]

I am looking at OPENCL GRAPHICS TEST
on that page (with imac config lowest on chart with card included)

and noting they use a more contemporary card in the mac 2010 chassis which someone might not notice just looking at the chart (i.e. using a card faster than a single D300).

– since that only tests GPU it’s a bit misleading

The other issue in such comparisons is often drivers make a substantial difference – i.e. if the iMac does not run the same OS version, it’s not a fair comparison either

[Pierre Jasmin]

Actually not clear at first glance the test compares against a single Radeon 7970 on the 2010 Mac Pro(not an original card).
RE:LuxMark here across different cards outside that machine.

https://www.tomshardware.com/reviews/radeon-r9-290x-hawaii-review,3650-34.html

Notice how this compute benchmark almost linearly grows as the GPU number increases (e.g. 7990 vs 7970, 2 vs 1 GPU test, it does not really double here as they clock down the second GPU on the card for electrical reasons)- and this means that the D300 is roughly a FirePro 7000 on that test.

This is a compute only test, does not stress IO from RAM to VRAM and back etc…

Pierre

[Pierre Jasmin]

Yes Premiere does not work for effects that use time with transitions, it’s an old problem
You need an extra level of nesting (i.e. make Twixtor in a nested clip than drop that in main timeline where you do the transition)

Sorry for that, it’s outside our control
Feel free to file a feature request at Adobe

Pierre

[Pierre Jasmin]

Yes Premiere does not work for effects that use time with transitions, it’s an old problem
You need an extra level of nesting (i.e. make Twixtor in a nested clip than drop that in main timeline where you do the transition)

Sorry for that, it’s outside our control
Feel free to file a feature request at Adobe

Pierre

[Pierre Jasmin]

Yes Twixtor 5 is compatible with CS6 AE
(Actually 5.1.1 for CS6 is minimum and 5.1.5b for AE CC — and 5.2 for Premiere CC)

Pierre

[Pierre Jasmin]

Yes Twixtor 5 is compatible with CS6 AE
(Actually 5.1.1 for CS6 is minimum and 5.1.5b for AE CC — and 5.2 for Premiere CC)

Pierre

[Pierre Jasmin]

If you advance frame by frame and you see you have a regular pattern like:
1-2-3-3-4-5-6-6-7-8-9-9
What you can do is set Twixtor Interp Mode to Nearest, and Motion Vecors to No Motion Vectors, and speed to 133.3333% (4/3).
This will remove one of every 4 frames.
make it 1-2-3-4-5-6-7-8-9

So, because you might be off by one frame (to arrive at the duplicated frame) you can create a nested sequence of the clip, and apply Twixtor to the main (parent) sequence. Then if you are off you can just slide the clip a frame at a time until you hit the right beat.

The net result will be a movie 1/4 less duration. From there it’s normal Twixtor slowmo (75% speed). This will require double nesting or a first pass render that you reload.

Pierre

[Pierre Jasmin]

If you advance frame by frame and you see you have a regular pattern like:
1-2-3-3-4-5-6-6-7-8-9-9
What you can do is set Twixtor Interp Mode to Nearest, and Motion Vecors to No Motion Vectors, and speed to 133.3333% (4/3).
This will remove one of every 4 frames.
make it 1-2-3-4-5-6-7-8-9

So, because you might be off by one frame (to arrive at the duplicated frame) you can create a nested sequence of the clip, and apply Twixtor to the main (parent) sequence. Then if you are off you can just slide the clip a frame at a time until you hit the right beat.

The net result will be a movie 1/4 less duration. From there it’s normal Twixtor slowmo (75% speed). This will require double nesting or a first pass render that you reload.

Pierre

[Pierre Jasmin]

Twixtor in what application?
This is a symptom of frame rate mismatch somewhere

Pierre

[Pierre Jasmin]

Twixtor in what application?
This is a symptom of frame rate mismatch somewhere

Pierre