In theory QuickSync for h265 is built in already, just the same way as h264 is implemented. But for some mysterious reason it is not finding the hardware encoder profile. I don't know why.
Beiträge von Vouk
-
-
Code
[19:27:39] FFmpeg: [ GPU #0 - < NVIDIA GeForce GTX 760 > has Compute SM 3.0 ] [19:27:39] FFmpeg: Multiple reference frames are not supported by the deviceIt looks like your GPU does not support this settings.
-
The Voukoder log file: Where do I find the log file?
-
Can you post a logfile with low level debugging enabled?
-
Do you have a sample RED file I can reproduce this with?
-
Well, of course FFmpeg as standalone is faster than DVR + Voukoder, because DVR is rendering the frames before Voukoder can encode them. You'd have to compare:
- DVR export time + FFmpeg encoding time
- DVR with Voukoder export
-
Can you tell me about what was special in that project? Maybe some audio settings?
-
I'm not able to render anything with the latest beta 0.4.1. I get the message: "Render Job X failed as the current clip could not be processed. Cannot add audio clip."
Can you attach the voukoder logfile? Where do I find the log file?
-
this is not my picture but it made by a top-professional colorist. This is a result of ProRes rendering of solid color. Also, he reported some problem with levels (sorry, he did not provide details).
Has that 444 16 bit mode being used for this export session?
-
Well, it depends on the complexity of your DVR project and on your laptop of course. You might want to add your voukoder logfile of that export session to this thread.
-
The "prores_ks" encoder can only be fed with 10 bit data. So even when it outputs 8 bit data. Yes, confusing.
-
I will most likely rename these types so it is more clear what to choose.
For higher bit depths than 8 bit always use 4:4:4 16 bit. That means: For all ProRes codecs always use this one.
-
I've tried setting it to both 16 and 32 (and 24) bit in the audio page in DVR as well as many different combinations between those and the audio settings in the Voukoder audio page. Still the same error. What am I doing wrong? I had no such problem in version 0.3.0.
Please try to reset the plugin. Remove everything from the renderqueue and add it new to it. Maybe even start with a fresh new project.
4.1 has the reported bug with color rendering, so, I did not install it, sorry
What kind of color rendering bug? I am not aware of any.
-
The free version unfortunately does not support exporter plugins.
-
I was about to write it's a bug in the connectors' pixel format conversion code. But then I rendered a 1920x960 HEVC 4:4:4 12 Bit video successfully with the latest version of Premiere.
Can you confirm?
-
Yes, I have issues with VEGAS 18 from time to time. I didn't find the reason for it yet. Still investigating.
-
I can confirm both.
I didn't find a way to get the aspect ration information in IOOutSuite4. So it's hardcoded to 1:1 currently.
As AE works in RGBA only I guess it would be:
- Range: full
- Matrix: rgb
- Primaries: (Unset ?)
- Transfer: (Unset ?)
-
Thanks, that's nice to hear. Yes, the existing connector might still be working with CS6 for some time, I just don't have any possibility to test it with CS6 anymore.
And yes, it is not easy to develop these plugins/connectors. I almost get no support from that NLE companies (Magix is a positive exception). But most of my questions to Adobe and BlackMagic are still unanswered and I don't get a free license from them. Adobe doesn't even want to increase the limitation of 2 registrations per account for testing purposes.
-
This should be possible. Changing the framerate is always a bit tricky, but I'm doing this for the deinterlacing filters already.
-
Voukoder is using what's selected here:
