First impressions are very good so far. The progress bar works again, although I feel exporting takes a lot longer on this 3.0 version that the older version, a sec/frame option would be appreciated.
used the GUI and did not touched any kind of command.
Probably caused by missing color primaries, transfer function or color matrix, when Iām using the CLI I have to set it manually, not sure with GUI
Can the devs just add -c:a copy to the command line to temporarily solve the audio re-encoding problem? Writing an audio option on the UI takes time but I think copying the stream is better than what it does right now.
2 Likes
Isnāt that something we can do ourselves in the options?
Yes for CLI, but I didnāt find the option in GUI.
I didnāt installed yet, there is an option to pause the procces?
Not yet.
Toby - for the pixelation/blocky issue, would it fix it if you change the Output Encoder to something else? From example, change H264 to H265 High Quality.
If you could also share the video and your logs, please. Submit File to Dropbox.
Please let me know if youāve sent the video and logs. Thanks!
Andres - can you please share the logs, video, and a screenshot of the strip? If you could also confirm if youāre using GUI or command line. Thanks!
Please leave me a note here if youāve attached something. Thanks!
@verbiate Are you referring to the disk space filling up when using Stabilization or any model/settings?
1 Like
Lee - I want to try to locally reproduce this. Can you confirm for me if this happens when using Auto or Estimation in Proteus or if it also happens when you manually tune the settings? If you can also confirm what your machine system is and send me the clip shown in the screenshot, a screenshot of any settings/models/presets used when this happens, and your logs/
Submit File to Dropbox.
Please be sure to send me a note to let me know if youāve sent me something. Thank you.
Can you share some more context about what happens when using Auto in Proteus? Please feel free to share with me a sample if possible. Submit File to Dropbox..
Weāve added some fixes to it in this build and there are some other things pending fixing. We would like to know if thereās something weāre still not aware of. Thank you.
Could you confirm if the ghosting with auto settings in Proteus happens with any image and what your OS is? If you could also share with me the original clip and a video/screenshot showing the ghosting, that would be great. Submit File to Dropbox.
If you can also do the same and share with me the original clip and a video of the color shift when using 10-bit material, Iād appreciate it.
Please leave me a note here if you sent something. Thank you!
Program is stripping hdr info and no Options for hdr(Main10,Main12 and Rec 2020,rec 2100,St2084pq (nits 100-4000 Gama).
Confirming this only happens on auto, not on manual.
I sent you a snippet of the film, the same scene I was using.
I also sent three screenshots, two in auto (100%, and upscaled), one in manual.
I only use the GUI, no CLI.
1 Like
Has anybody written a tutorial or made a video on how to use the ver 3 alpha. I am absolutely struggling with this new GUI. I do real basic work with ver 2. Proteus using auto and than tweaking the sliders. Set my output to 200% or there abouts and MP4 with a constant rate of 5. Thatās all and I love the results for my uses.
I really donāt understand the new preview as the old one was so simple and worked. At this point I just get too frustrated with Ver 3.
I am a mouse person as disabilities dictate as little keyboard use as possible. I really like that Topaz has improved VEAI so much in a short time but if I have to stick with 2.6.4 and Proteus V3 than thatās fine also. I realize that this is an Alpha release but the work flow of the program took such sharp change that Iām lost.
Thanks
Hey Mike iām sure all the issue you report will be improved., it has been many time reported. i was disapointed this time to still see the crop button not working with mouse (as iām hand disabled like you too), but iām sure all this is on their to do list at some point. as said itās a early alpha to be tested. I suggest you to stay on the 2.6.4 until a Gui will be usable for you (and me lol).
You can post what you donāt understand, iām sure lot of people here and myself too for the few i know would be ok to help you understsand it. some of the stuff not working (like the preview), pretty sure itās not finished and will be a lot improved.
for example, there is no way to set actually the quality of the output, except by editing the command line (the gui allow this, an access to the ffmpeg command line, in the parameters). it really mustnāt be used for doing usual work, but just to test, see whatās wrong and report it, for now. I saw alpha software before much worst that this (and final release much worst than some alpha version lol).
1 Like
The new preview actually works fine, just not the way it used to. Set up your model and parameters and click preview. The box at the bottom of the screen will split in half, and on the right, the name of your preview will be there, along with (hopefully) a % completed number. It might stick at 1%, but it IS running. After a few seconds (or longer), the % will change to a checkmark. Once it does, just click on that line once, and the preview will start playing above alongside the original. Click the āXā above the preview text to stop it from playing and remove it, then you can run another, OR you can just run more previews and they will appear in a list, so you can refer back to them. Iām attaching a screenshot with red arrow on some of the spots Iām referring to. Hope it helps!
1 Like
Hi,
Iāve sent you a zipped file with the original file, the output from v 2.6.4, and three from the Alpha. There are no log files where they should be though!!
1 Like
