I know, I could get much better results if I used different settings for each scene… but I don’t care that much. Proteus and VEAI can do wonders but it can’t do miracles. Depending on the monitor or TV/Streaming device I’m using to view the video it makes a big difference which is why I say Auto is mostly ok but I cannot stress enough Auto can be all over the place if the input video is poor and varies in quality during the video. Currently I find Auto mostly OK but still slightly soft for my use case but not objectionable. As far as VEAI settings the better the input video the better Proteus auto works. That’s my standard pre and post VEAI-Proteus workflow. Lastly I then do post-processing to rate I require and any other touchup that might help. This gives me the best output file for me. In that case I will clean up the video in preprocessing and then run VEAI at 100 percent scaling.įor my VEAI I use the encoder.json mod that came up with. The exception is if the video is already 1920x1080. Those will go to 1280 and I’m fine with that. I’ve not had enough success with anything lower then 640 going to up to FHD so I don’t try. So if a input video is 1280x that gets reduced to 854 or say the video is 640 then up it goes to 854. I also downscale or upscale my input videos to 854x480 for better time management if the quality is not great to begin with. I personally use a CF or 0 or whatever equates to lossless. And the encoding should be done at the highest rate you can do. Anti-aliasing, deblocking, mild noise reduction maybe smoothing. If your video to be upscaled is of lesser quality then preprocessing is probably going to help. I like to first inspect the video based on input resolution as compared to a know high quality video of the same resolution. That doesn’t mean you can’t take a poor quality video and use VEAI and Proteus but recognize what your working with first. I only use Proteus and have found first the old garbage in garbage out is never more real than when you are trying to upscale even with something like VEAI. If you have made some discoveries and formed your own approach to good results that you share them here, as well. I’m going to submit it separately, in another post to this topic. I am composing an outline of a method I’ve more or less ‘tripped over’ in the last week or two, that is helping me get much better results than I did previously. I’m hoping everyone will contribute their comments here and maybe we can collaborate to find an approach that will get the best enhancement out of Proteus 3. What I am hoping to do is start a discussion of what VEAI user’s methodologies are when it comes to setting Proteus 3 to do its best on your video. Even though it isn’t perfect (yet) you can get a lot more out of it by perfecting your technique. And, I actually hate golf.)Īs I’ve been discovering, Proteus 3 is a tool. It’s not the tool’s fault if the techniques aren’t good… - (That’s a simile I’m using here to illustrate my point. One of the things that struck me was simply having Proteus 3 and some lousy footage to work with wasn’t enough it’s kind of like having a set of expensive “pro” golf clubs and still playing lousy golf. This is with a piece of terrible video I roll out whenever I want to see if VEAI’s enhancement capabilities have evolved enough to make a silk purse out of a sow’s ear. I have just finished a session with the VEAI 3.0.0.6 beta where I was taking some really bad, old fil-based source material and converting it to FHD leveraging Proteus 3 to do the heavy lifting. (There is only one thing better than being right that is being absolutely right.) At the popular request, (of one person,) this Topic has been moved from suggested feature discussions to this location.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |