Topaz Video Ai Export

[Brook Mithani]

Ireally miss the ability to actually watch the video frame by frame as it encodes. Now you have to wait for it to finish before viewing the end result. I liked using it during the final export process. SMH!

A few days ago, there was a post here showing us how to download and use a Topaz model in cryosparc. The downloaded files included the micrographs (binned) and a few other files. So, along those lines, is it possible to export a Topaz training model using cryosparc? If not, can we get this feature please? Alternatively, I could also just compile a folder full of files that would constitute a full model if I knew what files exactly are needed.

Yes, the normal Cryosparc job exporting button works. After clicking the button and waiting for it to finish, you should fine a tar of that job, which includes the Topaz model, in the Topaz Train job directory in your Cryosparc directory.

Also, are you sending the JPEG or the ORF from LrC to Topaz, as you state Copy Original, I suspect the JPEG as the ORF should not present that option. And, is this JPEG an exported file from the ORF post LrC edits?

*A better suggestion might be to keep the original ORF and the Photoshop TIF. The TIF is viewable and editable in many Apps, and it contains all the work in full detail that you have done in the workflow, and you do not need to export JPGs (until you might need for a special purpose). The only downside of the TIF is more storage is needed.

Interesting idea. I'll probably end up only bringing a small number of images into Photoshop whereas all will go through Topaz. So other than deleting the .TIF and/or .DNG that were created is there no way LR can determine that the .ORF is the "true" original?

Confusion occurs when Lightroom-Classic refers only to the .ORF as the "Original" file. An exception is when you re-open a TIF from LrC to Ps- You see an option to open the "Original" ie. the Photoshop 'Original'.

So anytime you create a new derivative file by sending an .ORF to an external editor (Photoshop, Topaz, etc, etc) you are creating an RGB (not raw) file that is in a similar sense "original" to the external editor that was used to create it.

If your workflow is ORF (raw) > Topaz (DNG) > Photoshop (TIF), then the TIF has all edits preserved in a most useful (non-compressed, 16bit) file. It is already saved to disk and in the catalog. It can be re-opened in Photoshop, (or you can export a JPG [Compressed, 8bit] if you really must for a special purpose).

When replaying the model the only body in the part is changed to a construction body when an external copy geom feature is added to the model. This happens with no message on the command line or other notice. I found it by adding body display to the model tree and watching the icon change indicating the switch to a construction body. You can only observe this with the body icon expanded.

Weird. Is it a file created in Creo, or is it imported? Does it give you a mass when you do a mass properties? If it's an imported file, and you have Solidworks, import it into that, "fix" it there, and export it as a STEP. I'm guessing here because I'm stuck on Creo 4....until I switch to Creo 8 in the next couple weeks.

This includes several aspects ranging from appearances to body names and more, and it also includes an option to propagate the construction body attribute. It also depends on whether an external body/or bodies are added "as is" or being merged into the existing body in the part.

Is the setting Construction yes/no a logical toggle when redefining the ECG feature in the target part? I tried editing the definition of the ECG and unselecting the Construction yes/no. When I regenerate the body is still a construction body. I must be missing something and I cannot find details of this in the on line help files.

If you "uncheck" it, the "construction" body attribute/status will no longer be propagated to the target. That means an update of the ECG will no longer force an update of the construction attribute in the target body. In your case, I assume that means the target body will stay a construction body (simply because that is its current state and no update is forcing the body to change that status.) If you do a right-menu action on the body to "Unset construction body" status, then the body should become a regular solid body and should no longer change to construction during an ECG update.

I was able to activate the toggle option in the ECG and then manually unset as construction on the body to establish the design intent for the part as desired. Unless I missed something in the on line documentation, I think more detail should be provided for this in the help files. There are some nuances of multibody that most users will never figure out without some more explicit documentation.

Your on line multibody tips are useful and appreciated. I miss the old style user manuals which were much more comprehensive than the current on line docs in most cases. I still have a set of physical books from Pro/E release 17 on the shelf that I sometimes still refer to.

Nevertheless, I've found an indirect way to export it : copy and paste the body to create a new one. The 2 bodies are exported in the STEP. file The first remains empty while the second body is correct.

Video AI ($299) is a new and improved version of Topaz Labs' Video Enhance AI from late 2021 that upscales low-res video to higher resolutions, generates slow-motion footage from any source, stabilizes subjects, and generally improves detail, sharpness and clarity with any video. Topaz claims this new version of Video AI has been redesigned and engineered from the ground up, with notable improvements to usability, speed and performance.

The entire user interface of Video AI has been redesigned with improved visual aesthetics and usability. The colors, typography and controls all derive from the same design system used in its sibling enhancement app, Photo AI.

The biggest change to Video AI's interface is its ability to preview and export multiple videos simultaneously. The app is now fully usable while video is encoding, unlike the first version that locked users out until it was finished exporting. This new multithreaded architecture makes Video AI far more usable; especially when batch processing multiple videos.

Topaz also made considerable improvements to Video AI's user experience. The layout and labeling is clearer and easier for non-professional users to understand. Presets now play a more dominant role, with a number of helpful built-in options for common tasks, including:

Presets (and custom enhancements) are previewed by clicking the purple Preview button under the video. This encodes a few seconds of the source video, then displays the enhanced and original videos side by side for comparison.

When settings are adjusted and Preview is clicked again, a new preview is added to the Previews queue. Video AI allows multiple previews to be generated from the same video, or multiple imported videos.

Each preview saves the enhancement settings used to generate it. This allows you to queue up however many previews you want, pick whichever preview you like best, then click Export to export the enhanced video. Similar to the previews queue, multiple videos may be queued for export as well.

The preview and export queues are the most fundamental change in Video AI, for not only can the new app generate previews and exports simultaneously, but it also allows users to import more videos and work on them while the app is churning away in the background.

This new version of Video AI also makes file naming and exporting simpler by always exporting videos to same folder as the source file (by default, but you can change this in the app settings). Video AI also automatically names exported video files with hashed numbers and abbreviated acronyms for the enhancement settings used. This makes exported files easier to read and find compared to the first version of the app.

The aforementioned presets work by enabling and configuring encoding filters using saved values. Each filter may then be further customized to fine-tune (and in some cases improve) the results generated using the pre-built presets. The four main filters include:

Stabilization is a new feature in Video AI. This filter helps stabilize camera shake either by cropping-in ("Auto-Crop") or retaining field of view and intelligently filling-in gaps and empty spaces ("Full Frame"). The latter is basically the video version of "Content Aware Fill" in Photoshop.

The quality of stabilization is entirely dependent on how shaky a source video is. In my tests, handheld footage with light wobbles and bumps stabilized acceptably well using both options. Edges can however get a little wobbly and warpy, similar to what you see when using stabilizing effects in video editors (eg, Warp Stabilizer in Premiere Pro). I think the main benefit of this feature is baking stabilization into exported footage for faster timeline editing and processing later in post.

Frame Interpolation controls how additional frames are inserted into exported footage. Here you can select the speed of slow motion you want (eg, None, 2x, 4x, etc) and which AI model should be used (more on this a little later in this review).

Enhancement improves image quality using four AI model options: Proteus (fine-tune and enhance footage), Artemis (denoise and sharpen footage), Gaia (upscale footage), and Theia (improve details and clarity). If you can't decide which is best, generate previews using each to see which looks better. Here you can also delve deep into each model's settings to fine-tune output to your liking.

3a8082e126