Topaz Video Ai Preset

[Jennifer Kovachick]

suraj @nipun.nath @yazi.saradest

Hello everyone, here is my first topic on the creation of my presets under TVEAI v3.x

I worked on creating two presets in Proteus, the first for 4K Ultra HD output and the second 8K Ultra HD. Feel free to give your opinions here. I will work soon on preset for DVD to 1080p, VHS to 1080p

on the one clip I tested it (VHS v1), A lot of details were lost compared to to Blury4k preset (tested both Theia & Proteus) .

but i only tested one clip, 2sec preview. I upscale to 1080p with all presets i tested, on the same 2 sec preview clip.

Actually, I had several problems, but I have corrected everything and tested them out tonight. Everything seems to be working now. I will make some formatting changes tomorrow to make the links easier to copy and will post some presets Jorge (who else?) made for deNoise.

ages ago(permalink)

Hi Pete

It's not on the ATN site - you copy the link from the site of the preset you want to use.

Then open Photoshop and your Topaz product (say Adjust)

Click on the preset button in the bottom left corner of the Topaz adjust window.

Then click on 'import from internet' and a small window opens, paste in the link to the preset you want and press OK.

Originally posted ages ago. (permalink)

reflective fang edited this topic ages ago.

Is there a way to delete some of the built in presets from Adjust, if you know you will never use them? They don't show in the presets folder with the imported presets. Just delete them out of the default tpp-file, not sure anymore, but my default file probably was renamed to 00mine.tpp:

Open it in notepad or another Text-editor (not Word) and erase the line (resp. when line wrapping was enabled in your editor like in the image above, the whole block)

You can also open the preset file and set all values for mod="0" to mod="1" and delete it later in the GUI. By this they are not physicall deleted, but not visible in the GUI anymore. But better make a backup-copy of the file before doing so. Rename the extension to something else than tpp so Adjust won't read the backupfile.

If you need further help on the structur of presets or if you want to keep downloaded presets in a single file (maybe sorted by subject) you might remember my tut about how to sort presets

Originally posted ages ago. (permalink)

Ablichter edited this topic ages ago.

I was able to install the presets; however, they all did not appear in the toolbar (list) on the left side of the Filter menu. When I tried re-loading, it said it already existed. I tried shutting down CS4 and re-opening, that didn't work. HELP

ages ago(permalink)

Jorge, I understand that. My wife and I both have MACS and CS4. I was able to load all the Adjust presets on mine with no problem. On hers she loaded all as well, but 2 of them do not show-up in the toolbar. However, if you try to re-load the 2 presets it says they already exist. She has tried shutting down CS4, also re-booting her MAC.

ages ago(permalink)

What about the file settings? I'm not a Mac user, but I know if you "right-click " to check the properties of the files they shall show as read and write.

The next solution I can think of, is to rename the files to see it that solves the problem. Chek an let us know.

ages ago(permalink)

Move them to another path, import them from there again and let us know what happend. And please tell us the name of the presets.

ps

Another possibility would be they are corrupt. Check the filesizes with yours or just copy yours over to her MAC.

Originally posted ages ago. (permalink)

Ablichter edited this topic ages ago.

Hi. I have a Mac as well and I can't get the DeNoise presets to load. I d/l'd them from atncentral and tried to import the .tpp files into the plugin with no luck. Changed the permissions of the folder and the files, still no go. Thanks for all of these anyway, I'll keep trying to figure it out as well as try some of the Adjust presets.

ages ago(permalink)

There is a parse error with all Denoise preset I tested so far, when you apply the URL in Firefox (not with IE). If I load those preset from my site they work well.

MAC users: please check and give in the URL in Safari and let us know what it say. You should see it as plain text in any browser.

Don't know whats wrong yet (might be again a MIME error), but it seems Firefox and MACs a bit picky by sticking more to the rules. I will investigate the website soon.

Originally posted ages ago. (permalink)

Ablichter edited this topic ages ago.

Well, not wrong - but maybe not within the XML specifications.

Not sure yet Jorge, as said when the XML is parsed as it (and not just displayed / parsed as plain text only) Opera, Firefox and some website checkers I've got are complaining about the numbers in the start-tag at line five.

Which is in this case the "40", "30", "5" - or in other words: the naming of a preset (not the naming of the file).

But for now I can't tell for sure, unless MAC users are checking this by downloading the presets from my site or unless Jim alters a preset and provide it for downloading from his site.

Or do you have a FTP-Upload to Jim's site? If so we would be able to check that out.

As said some platforms and browsers are not that "tolerant" as MS & IE is, which is quite good so.

Originally posted ages ago. (permalink)

Ablichter edited this topic ages ago.

Okay - I have bad news for you. Since I'm not a coder I wasn't sure about that, but all XML validators I tried tells the same and my developer affirmed that too:

Numbers are not allowed as first characters in a NameStart-Tag.

That it works on PC is - as said - because they are more tolerant. And the tests with my website are "working", because the presets are not parsed as XML, but shown as plain text :-(

Which means:

1. Some have to change all presets and put the name of the cam f.e. to the end of the tag or apply a "C" (for Canon) in front of it.

2. Topaz Labs should be informed - they need to validate the presets when they are saved (and loaded). Users should not be able to name presets with leading numbers - at least the plugin should provide a hint that numbers are not allowed. Something like this.

ages ago(permalink)

Why are you opening the presets with something besides the Topaz product?

Any XML stream you open with a web browser will not be useful to the browser or to the user.

The presets are specific to the Topaz software, are they not?

ages ago(permalink)

Scott is right. Isn't he? Why does this affect it if you're using Topaz as the "retriver" an not a browser?

So, Do you think that only changing the file name OR the descrition name withing the file?

ages ago(permalink)

Why are you opening the presets with something besides the Topaz product?

Because its no problem to do so and to edit them in a text-editor like you also can do with html-files (since XML and HTML are both markup languages) as long you are aware of the structure (header, etc) and tags and follow some rules.

They were saved within the plug-in to a filename which got a number in front - unfortunately this string also is used to reflect the name of the preset within the plug-in, instead of using the description field for that.

Any XML stream you open with a web browser will not be useful to the browser or to the user. Doing so is / was for testing purpose only.

F.e you can check if the file is present in the webserver directory and if it will be downloaded without an error. F.e. the webserver might throw the error "404 File not found" or "403 - forbidden" - you will never find out about that when you just do it in the plug-in, since usually those errors are not catched by the app or plug-in.

Assuming the file was there, "readable" and opend by a browser it will either be displayed as plain text or when the web-server provides information about it via the MIME type it might be parsed as XML. Which happens here when I open such a file with Firefox and it complained about being "not being wellformed".

As said those Denoise files didn't stick to the specifications; in general not the users which would save preset in this way are to blame (because they can't know about the XML-specs), but the plug-in which allows user to write almost anything they like (*) to the filename and by this to the so called NameStart-Tag in the file.

(* - edit) which is even worse doing so on a MAC and when you exchange files between MAC and PC, since on MACs you can write special characters like \ / * ? in a filename, which is not allowed on PCs.

The presets are specific to the Topaz software, are they not? Well, they are just text-files named by a specific extension. This tpp-extension makes them visible to Topaz software - rename the extension to xml doubleclick them and they will open with IE or with a XML-Editor if there is any on the system.

As a markup language they just describe something like: "I myself are best read as Version XML 1.0, UTF8 encoded, the following values are for or written by Topaz Adjust 3.0.1, at the third position in the next row you can expect the name of the author and at the 4th position the value for the brightness" etc. pp.

Pretty simple.

Originally posted ages ago. (permalink)

Ablichter edited this topic ages ago.

Hi ablichter,

I'm not here to argue - I am just curious. As a software engineer I understand XML and XML validation. Additionally, I understand why Topaz would use XML.

My point is- why run XML files that are intended solely for use by Topaz software through a validation tool? There are many XML formats that are meant to extend XML beyond its current use. One might say that Topaz is extending the XML they are using. So - as long as Topaz software understands how to read it, why should they worry if a tool from the W3C or somewhere else can validate it?

I can certainly see the value of hand editing a preset file, but I don't see any onus on Topaz to support such editing. The interface they have provided is the plug-in itself.

On the other hand, you could certainly edit using notepad.exe and produce files that are valid to the Topaz software.

Happy editing!

Scott

ages ago(permalink)

3a8082e126