Hello.
I am in the process of encoding a number of files that were captured from minidv to avi. I am enconding to mp4 using the QSVEnc codec. (I have an Intel A380 graphics card).
I have a custom setup for deinterlacing and then apply a number of other filters including resizing.
Unfortunately, the encoding is failing. The majority of the avis that I try to encode are stopping between 50 and 60% of the way. I notice that the progress bar moves along normally until this point then goes right to 100% in an instant and the file shows as complete with no errors logged. When I playback the resulting file, the audio is fine, but as you might guess, the video simply freezes at, give or take, the same percentage that is stopped encoding.
any ideas?
Thanks
Ready sticky, provide proper details.
Wild guess is that there is something wrong with your files,...
Is there a utility in the software that allows me to provide you with all the details simply?
Sometimes, when I retry the file 3 or 4 times, it works, so I don't suspect there is a file problem. Further, before I had the A380, I used hybrid to encode the very same files to both prores and x264 without this problem.
Perhaps it is the a380, I'm not sure.
As much detail as I can gleen:
Base tab: video = QSVEnc, audio = auto add (all), default container = mp4
QSVEnc tab: encoding mode = icq (strength 22), format = AV1, quality = balance, bit depth = 10-bit, sampoing = YUV420, input buffer = 3, all other tabs under QSV untouched
Crop/Resize: resize method = bicubic spline (I override this in vapoursynth), auto adjust width, height set to 1440, Convert output to PAR = Square Pixel (1:1)
Delinterlace/Telecine: Auto deinterlace = QTGMC (Vapoursynth), Preset = slower, Bob = checked, OpenCL = checked (I tried it unchecked and same problem), Neo = checked
Vapoursynth: DeHalo/FineDeHalo = checked (strength adjusted to 1.50, Frame/Resize/Resizer = NNEDI3, neighbourhood = 32x6, neurons=64, network=2, GPU = checked, Color/Matrix/ColorMatrix = checked, From = Rec.601/470bg/470m, transfer = BT.709, Adjust by resolution = checked (resulting in To: = Rec.2020ncl)
This is all I have changed from the defaults.
thank you
a. create a debug output (sticky stated how)
b. check the Vapoursynth Preview: Can you access the whole file here? It might a problem with the used source filter. Try for example enabling AviSource support, this way Hybrid will look if there's a 64bit vfw decoder for your DV content and use that in case it is available. (using BestSource might also work)
c. if you use a virus scanner aside from Windows Defender or MalwareBytes, try if it help adding excemptions for the temp-, output- and Hybrid-folders.
Cu Selur
Ps.: could also be a driver (update drivers) or QSVEncC issue (etracting the latest release from
https://github.com/rigaya/QSVEnc/releases and renaming QSVEncC64.exe to QSVEncC.exe and replacing the existing files might help).
Unfortunately, I do not see a sticky on any of the messages.
Yes, I can access the whole file in preview
In Vapoursynth -- Source I have checked both Prefer avisynth for avi files and Prefer BestSource
I only use Windows Defender
Should I download the 7z file, extract all the files then simply cut and paste the QSVEncC64.exe to where I have Hybrid installed, changing the name to QSVEnc.exe, or do I need to replace all of the files from the extracted download?
Thank you.
Sticky =>
https://forum.selur.net/thread-3.html
Quote:Should I download the 7z file, extract all the files then simply cut and paste the QSVEncC64.exe to where I have Hybrid installed, changing the name to QSVEnc.exe, or do I need to replace all of the files from the extracted download?
you should extract all the file into the Hybrid/64bit-folder. Then delete the exiting QSVEnC.exe and rename the QSVEncC64.exe to QSVEncC.exe .
Quote:In Vapoursynth -- Source I have checked both Prefer avisynth for avi files and Prefer BestSource
Did you try it separately and check in the Vapoursynth Script View, whether it influenced the created script?
Quote:Yes, I can access the whole file in preview
Vapoursynth Preview? (I hope)
Assuming the file is fine, the script can be previewed and got analysed correctly, the most likely causes seem to be:
a. either some driver problem
b. some heat problem
c. some access problem to the file (especially likely when the file lies on an usv drive or is accessed via an instable network connection)
Cu Selur
Hello.
Thanks for all your help. My intel software that checks for component driver updates found one this morning and installed it. I haven't had any problems since.
Thanks again
