[Bernhard G.]

Hello,

Motion Compensation aka Optical Flow aka Pixel Motion
for De-Interlacing would make most sense if there also was an additional Effects Category in the Effect Controls Window, e.g. labeled Standards Conform and containing everything about the Clip’s conforming behavior in the sequence (Fit to Sequence, De-Interlacing, Frame-Blending, Color Space, etc.).

Motion-Adaptive De-Interlacing analyzes, which parts of the image have moving objects at all and discard+interpolate to fill up only those parts of a line that contains motion.
Motion Compensated De-Interlacing tracks detail information to intelligently fill up the discarded parts of the lines.

The analysis for Motion Compensation could also be used for speed changes
and for Super Resolution (upscaling by collecting detail information of neighboring frames).
I’d guess, Adobe could use the analysis currently done for Warp Stabilizer to perform an excellent De-Interlacing, and Super Resolution processing 😉

In detail I would expect a more automate and logical behavior of fields handling, e.g.:

if I place a 1080i/25 clip in a 1080p/25 sequence, PP should automatically assign
Motion-Compensated De-Interlacing to the clip.

If I place a 1080i/25 clip in a 1080p/50 sequence, PP should automatically distribute
the 50 fields to the 50 frames and interpolate the missing lines via Motion-Compensation.

If I place a 1080p/25 clip in a 1080p/50 sequence, PP should automatically interpolate the missing frames not by frame-blending, but by motion analysis.

Thank You for listening!

Best regards,
Bernhard

[Bernhard G.]

Hello Dennis,

Thank You for Your reply!

[Dennis Radeke] “We’d rather you be mad at us for having to change the text file than not offer GPU support at all.”

I’m not mad at Adobe 🙂
I appreciate that Adobe enabled this to get other GPUs running.
Also, Thank You for the detailed explanation!

My point is: BMD Resolve shows, there is also an alternate (and very elegant) model to handle this issue: Self-responsibility of the users by warning and informing them.

[Dennis Radeke] “We’ve done a lot of the ‘boring’ stuff already”

I see that and CS6 was a huge step – no doubts.
But for me, the feature Motion-Compensated De-Interlacing has become an indicator on how far I can rely on PP in a workflow.

[Dennis Radeke] “Most of our effects and process pipeline are 32 bit float already (just check out those icons to the right of many of the effects).”

But on the long run those icons should disappear so I don’t need to filter for filters at all.
The less I need to take care of those things, the more creative I could be 🙂

[Dennis Radeke] “Spine-masks – YES! I’m with you 100% on that one and I’ve asked for it for ages.”

Very glad to hear!

[Dennis Radeke] “we are working on better integration with Speedgrade for the future”

Recently I read an interview with Adobe’s Patrick J. Palmer (Speedgrade) and I do very appreciate what he said; that Adobe also takes care of the ‘One-Man-Bands’ who don’t have the time for being specialists. At least I do see the necessity being a ‘One-Man-Band’ more and more emerging.

Thank You for listening!

Best regards,
Bernhard

[Bernhard G.]

[David Lawrence] “3) WYSI not WYG if you use maximum render quality and don’t have the right hardware. Lots of confusing variables.
“

Very glad, I’,m not the only one complaining this!

To actually get 32bit float processing in PP is nearly rocket science!

I’d expect 100% 32bit float, 100% MRQ, pixel-for-pixel 100% the same value regardles if GPU or CPU.

In FCP-X I don’t need to think of it. ALL is processed 32bit float RGB.

Don’t forget to write Feature Request to Adobe.

Best regards,
Bernhard

[Bernhard G.]

[Gary Huff] “if you happen to get a render error, you very well can’t get pissed at Adobe”
I do not get ‘pissed’ at Adobe. No app is perfect. No company is. And I understand well Adobe can’t test all configurations out there, especially on Win-PC side.
With DaVinci Resolve, BMD follows a model of self-responsibility of the user.
When enabling Mercury GPU, PP could warn and inform the user that the GPU isn’t officially supported and force to confirm this.

[Gary Huff] “Premiere will ask if I want it to automatically set the timeline for it “
Yet I have to activate 32bit float and MRQ manually.

[Gary Huff] “You don’t have to create a sequence as soon as you start a new project if you’d rather do this.”
Good point. Then why does the dialogue appear at all?

[Gary Huff] “You do realize that everything you’re using in FCPX to apparently do 90% of the work you need is actually a plugin too, right?”
How do You know what I need for 90% of my work 🙂

[Gary Huff] “that’s easy enough with AE dynamic linking”
Agreed. Dynamic linking is great! But tools directly inside PP would be more streamlined.

[Gary Huff] “doesn’t that require Motion to pull off anyway?”
Again: no app is perfect. Spline Masks and Motion Tracking would be VERY useful
inside PP as they would be inside FCP-X.

Best regards,
Bernhard

[Bernhard G.]

Hello,

recently we finished the first real projects with FCP-X.
Within FCP-X we had 90% of the features we needed for 90% of our work.
Additionally, FCP-X has high-end image processing algorithms under the hood.
No doubts regarding quality. A very streamlined process.

PP CS6 has some great special features and it benefits from the whole CS suite.
It’s consequent native format support it great! Because of this it is confusing, PP needs ‘render files’ at all. Mercury runs very well! Also confusing is the sequence setting by codec instead per video standard. I also get headache when I need to do rocket science to get full quality out of it (GPU yes/no, 32bit float yes/no, etc…) or hack my app for GPU support at all… WHY???

Too much of thinking…
Too many plugins and other CS-apps needed…

To convince me, Adobe needs to implement all those boring features, no evangelist on this planet could convincingly praise as ‘awesome’, but that are extreme important for real professional workflows (100% 32bit float, motion-compensated de-interlacing, spline-masks, color-grading, etc…) so that 90% of work in 90% of the projects could be done within PP.

Currently I have a clear bias towards FCP-X !

Best regards,
Bernhard

[Bernhard G.]

Hello,

my tip would be to copy everything from Your sequence
into a 1920×1080/p sequence with double frame rate.

You’ll need to activate frame blending for every 1080p clip to interpolate
the missing frames!

Let AME convert back to 1080i.

At the moment, PremierePro‘s de-interlacing and motion change processing can’t be assumed as ‘professional’
(CS6 the same as CS5.5).

So PLEASE don’t forget to write Adobe a feature request for
motion-compensated de-interlacing and motion analysis for speed changes!
They are listening.

Best regards,
Bernhard

[Bernhard G.]

…forgot something…

the cloud unit should look like the logo from iFFmpeg
https://osx.wdfiles.com/local–files/icon:iffmpeg/iFFmpeg.png

and be branded Apple Satellite

😉

[Bernhard G.]

Hello,

this is a nice concept. But I would expect something more cloud-like.

I imagine:
– a well designed device that fits well onto a desktop as under it,
and also well into a 19” server-rack (e.g. by coupling two of them?)

– 1-2 PCI-E slots / BTO-option for Nvidia Tesla

– 2 Thunderbolt and 2 Gb Ethernet ports

– in a server-rack, several units are interconnected via Thunderbolt;
making Thunderbolt the backend

– Promise-RAIDs as other HW-vendors supporting Apple’s proprietary Thunderbolt-backend-protocol

– on/under the desktop, the local unit is connected via Gb Ethernet;
being the frontend

– standard-interface is the iPad 🙂

– display device is the 4K iTV :-))

– making us edit with PROCUTX on the iPad while GUI/Monitoring in 4K on the iTV :-)))

– doing hardcore-processing on our private cloud :-))))

Best regards,
Bernhard

[Bernhard G.]

Hello,

why is there a need for native support or for a workaround to hack the app at all?

I absolutely understand, Adobe can’t test ALL possible hw-combinations,
especially with the huge range of products on Windows PC side,
and hw-recommendations are always welcome.

But wasn’t it sufficient, if Adobe informs and warns the user,
e.g. when turning on Mercury GPU Playback, that performance might not be the best?

DaVinci Resolve’s model of self-responsibility of the user could also work for Adobe!

Thank You and best regards,
Bernhard

P.S.: Already wrote this as a Feature Request.

[Bernhard G.]

Hello,

a speculation:

– The Event-Project structure is aimed at collaborative workflows yet to be released.0
– Multiple users accessing one Event via rudimentary rights management while working
on their private Project.
– User could share a Project as a Compound Clip into an Event.

Best regards,
Bernhard