I need to look into and fix this.
Beiträge von Vouk
-
-
It might help to install the Intel GPU driver.
But on my i7 7700K system I was never able to install a working QSV support. I don't know why. Is there some information in the log file?
-
- Go to the videos filter tab
- Select bwdif or yadif
- Done.
You will lose 50% temporal resolution (as explained by Capt. Disillusion) as deinterlacing interpolates the other half of the frame.
-
Nice to hear.
-
Please use the latest version. The frame rate is problematic ...
Zitat[14:18:18] Timebase: -59673179/612929536 (-10.27 fps)
Please click "Match source" in the video tab or select a proper frame rate (i.e. 60 fps)
-
You need to deinterlace the video. Either you do this in VEGAS. Or you use one of the deinterlacing filters in Voukoder (i.e. bwdif or yadif).
-
Sure! Check out this topic:
-
Turing processors are supported, but they don't support encoding interlaced video.
-
Main log file
The main log file contains all log data for one single day:
- Voukoder initialization
- All exported files
These log files are located here and will remain for 7 days:
The files are named by the ISO date (yyyy-mm-dd).log:
Export specific log file
If you have "Create log next to the export file" enabled you can also find it - well ... - next to the exported file. This log file contains only the export relevant information.
Low level debugging
Sometimes its neccessary to also log information FFmpeg provides during encoding. This can be done by ticking "Enable low-level logging" (see screenshot above)
-
Please provide a Voukoder logfile.
-
Zitat
[15:23:05] Display #0 on: NVIDIA GeForce RTX 2070 SUPER
[15:23:05] Interlaced: Top first
Turing GPUs do not support interlaced encoding anymore.
-
I tried various ways: Twitter, Email, Helpdesk ... no response anymore.
-
-
Release Candidate 1
Fixes
- Closing the separate logfile properly
- Fixed atrim selection by sample count
- Fixed bwdif filter options matching their labels
- Fixed deinterlacing filters (Bobbing)
- Fixed audio stream bug
- Clearing options on encoder change
Changes
- (h264_amf, hevc_amf) Added "GOP size" option
- (x264,x265) Added more options (@Kleinrotti )
- Added wavpack encoder (@Kleinrotti)
- Added SVT-AV1 encoder (experimental)
Notes
This is not the final version 5 release. Use it on your own risk.
For using NVENC encoders driver version 436.15 or newer is required.
Download
-
Note:
Default:
major_brand : mp42
minor_version : 0
compatible_brands: mp42mp41
PSP:
major_brand : MSNV
minor_version : 19474624
compatible_brands: MSNVmp42isom
iPod:
major_brand : M4V
minor_version : 1
compatible_brands: M4V mp42isom
-
As far as i remember the width has always to be a multiple of 16 and the height a multiple of 8. So with an uneven number it will most likely never work.
-
Interlacing
https://www.youtube.com/watch?v=5eu_KjKsnpM
Solution:
- You could deinterlace (convert it to non-interlaced) it first. Either by premiere oder using a voukoder filter..
- You could use the x265 encoder instead
- Buy a second cheap older GPU and use it for encoding
-
Here is an other try with 1920x800 frame size, and it doesn't work.
Zitat[10:48:50] Frame size: 1920x801
Maybe you can try with exactly 1920x1080?
-
You can try to ZIP the logfile, but I guess I found the reason:
Zitat[10:35:52] FFmpeg: VCEEncoderTrace: 2020-04-15 10:35:52.964 41B0 [VCEEncoderTrace] Info: SetProperty(-1) FrameSize:4096,1708
[10:35:52] FFmpeg: VCEEncoderTrace: 2020-04-15 10:35:52.964 41B0 [VCEEncoderTrace] Warning: SetProperty FrameSize failed in AMFPropertyStorageExImpl with return code:0x5
Seems the AMD VCE encoder can't handle that frame size.
-
For the english users: It seems the HD8000M series does not support GPU video encoding.