Use MKVToolNix or if you are more command/coding inclined FFmpeg. Both of these tools allow you to create a new file, combing the upscaled video file with the audio from the original file.
Doing this you can mostly ignore the VEAI audio issues.
Use MKVToolNix or if you are more command/coding inclined FFmpeg. Both of these tools allow you to create a new file, combing the upscaled video file with the audio from the original file.
Doing this you can mostly ignore the VEAI audio issues.
Copyright issues aside, itâs way too early to be testing anything with the leaked Windows 11 build.
When Microsoft is ready to share a product with developers, they will open up early Windows 11 betas for developers on MSDN. If Microsoft follows their own precedent, they will later open up a Windows 11 beta build for the masses.
Any âleakedâ version of Windows 11 right now will likely be a mix-mash of Windows 10 and early Windows 11 code. Any builds at this point are likely nothing more than early alpha builds and sections of the code base could be completely rewritten before a Windows 11 RTM is released.
True⊠but maybe the devs might be a little curious still ?
And to think that the solution for this is just for the VEAI to do two operations: demuxing audios, subtitles and subtitles before processing the Upscale and then changing it at the end of the process, because thatâs exactly what everyone here does, they use an app like MKVCleaver to demux audios, subtitles and subtitles and then modify the final product of VEAI Upscale the audios, subtitles and subtitles, with for example the MKVTOOLNIX app. This would be very simple and easy for developers to implement, anywayâŠ
Att.
DruidÂź.
They already have to solve many problems before with the VEAI, because they would create new ones as a product that, as mentioned above, doesnât even exist yet, anywayâŠ
Att.
DruidÂź.
Yeah, youâd think so. I feel like Iâm taking crazy pills when updates continuously release without this simple solution FINALLY implemented. Oh well.
I learned early on to never use VEAI audio pass through, because it sucks. Iâve been using MKVToolNix since day one to put the original audio track and subtitles back into the upscaled video. Only on a few occasions have I had synchronization problem, because VEAI was dropping frames, but not very often.
The reason im asking is because the audio would still intact when im using 1.8.1 version.
After upgrading to 2.2.0, every output i made loses its sounds eventho i turned on the âkeep audioâ option.
So in summary, theres nothing wrong with my setup but in 2.2.0 they purposely removed the audio in the output video?
If yes, why would they still keep the âkeep audioâ option in the UI eventho the result will always have no audio?
No, they did not. It has always been broken and remains broken. Sometimes, in some situations, it works, but it has always been better to use an external program to handle the audio.
What⊠so why the earlier version im using has no problem with the audio output?
With this version, everything i made have no sound. I tried like 10 different video with different format and specs but still no sound. I thought theres something wrong with my setting.
Im thinking downgrading to earlier version if this only happened in recent newer version.
I canât speak for version 1.8.1, but 1.6 and 1.6.1 had all sorts of audio issues.
1.6.1 VEAI would convert mono-channel audio to dual-channel and convert 5.1-channel to dual-channel when it did not crash before finishing the upscaling. If the video had any sort of issue in the tracking, it would throw off the audio tracking when remerged with the original audio.
What I finally did to get 1.6.1 to work the way I wanted was to use FFmpeg to create a new CRF 0 libx264 mp4 video with no audio and feed that into VEAI to upscale. That would work around all of the tracking issues and prevent VEAI from crashing when modifying the audio.
Finally, once I had a video upscaled with VEAI, I used an FFmpeg bash script to merge the upscaled video back with the original audio and any subtitles to make a finished mkv.
No idea how downgrading would help, if 1.8.1 is anything remotely like 1.6.1 when dealing with audio issues. My $0.02, if you are not comfortable with FFmpeg, use MKVToolNix to merge back the original audio into your upscaled video. It should only take a few minutes at most to merge the original audio with the new video into a new file.
The bottom line is, you donât want the audio output from VEAI. Ever. Not until they fix it.
I use 2.1.1 (rtx3090 i710700). âKeep audioâ works fine (in stereo mode, without subtitle) with all the models, except the interlaced Dione, where there is no sync ⊠and it is useless.
I suppose thatâs fine, if you are upscaling family home videos with basic LR stereo, but forget it if you want to keep the original 7.1 Dolby Atmos in the upscale by using the âkeep audioâ option.
Why output model usually wrong from what I picked???
Thereâs an annoying bug now where if you change from Low/Medium/High, it will show the recommended model, but it wonât actually change your active model. You need to click the dropdown menu to select it again. If you import a vid, and the default is GHQ, if you swap to for example Medium preset, it will show AQ at the top, but the applied model is still GHQ, you you need to manually select AQ again. Your active model is displayed on the bottom right.
This really needs to be fixed.
For people using Nvidia cards (mine 1080Ti) , I was getting random lock-ups and after looking into it for some time, I found the Nvidia HD Audio device driver was the problem - iâm not the first to have this issue.
I disabled it in device manager (because uninstalling it just comes back after reboot) and PC has been on for 6 days! Couldnât get more than a few hours out of it before that. I re-enabled it and lock-ups just come back.
I now need to see if I can use optical for the sound now!
Send a message with Taylor Bishop tagged in it. Thereâs only a day or so before the next release.
Perhaps the developers or the Topaz Team responsible for VEAI could consider an idea that came to me yesterday (yes, it is insane, but I thought it couldnât hurt to ask):
How about (if that were possible) adding a sort of âGenre Templatesâ that users could add to existing models to adjust them more specifically? What I mean by that: The already existing models have been trained on a variety of âbasicsâ (like people, faces, objects and such) and on different source quality levels (low res, high res, with artefacts and such), but what about creating templates according to genres, that will âtellâ each of the models to more specifically address issues that are source dependant, no matter what model has been chosen - a couple of examples that I thought of yesterday:
These could be done as a sort of âbuy-inâ option, so people could choose which templates they want; you could do a trial period for people to decide, offer discounts on template packs with templates from similar areas of interest (like SciFi & Fantasy) and so on.
Just a thought, that way to could financially compensate the work involved.
Now that an official Windows 11 build is released to insiders, I would be able to test VEAI as a beta tester.