Looking at it now ...
What frame rate did you select?
Code
[17:21:09] Timebase: 65536/3931327 (59.99 fps)That looks a bit suspicious ...
Beiträge von Vouk
-
-
Can you please post a voukoder logfile and tell me how to reproduce this? (See sticky topic in this forum)
-
Release Notes
Make sure you are using the latest connector for your application(s). For using NVENC (SDK 9.1) encoders driver version 436.15 or later is required.
Fixes / Changes
- Revived the SVT AV1 encoder (still - but a bit less - experimental)
- Added "temporal mix" + "change fps" video filters
- Updated libx264 encoder to the latest version
- Added "prores_aw" encoder
- Added YUV 4:4:4 (8 bit and 10 bit) support for nvenc_h264 and nvenc_hevc (If the GPU supports it)
- Added support for timecode tracks (the connector has to provide a timecode)
Credits
Thanks to my all supporters by either PayPal, Patreon or BTC. Also thanks alot to the translators.
Top Patrons
Gronkh, Schauerland, Terry Mundy, Andreas Martin Aanerud, Michael wooldridge and Chris Woods
-
Just bought a copy of Premiere CS6. Thanks to PWC .
-
I already tried to render and export the clip. I didn't experience any sound issues in the resulting file. I was not able to reproduce this issue.
-
Currently Voukoder only supports Mono, Stereo and 5.1. These are basically hardcoded options in there. In the Voukoder successor I plan to also allow completely custom channel configurations.
Yes, thats nasty. I already asked BM how to request floating point audio data always and then Voukoder creates the requried sampleformat by itself. No reply so far.
-
Can you please post a logfile?
-
Roger Singh Could it be the source clips have a different framerate other than the timeline?
-
Can you tell me how to reproduce this? The logfile looks okay.
-
This is how i tested it:
3600/3600 = 1 hour
0/60 = 0 min
6/1 = 6 s(0.4 * 60) / 1 = 24 // timebase is 1/60 ~ 60 fps
results in 01:00:06:24 (So this is the timeline timecode, i guess)
How can I reproduce the issues you have found?
P.S.: I have sent this issue to BM. (Along with the other questions I have). Let's see what their reply is.
-
Alright. Version 9rc2 and resolve connector 0.7.0 should support timecodes! Maybe someone could test it.
-
Voukoder 9 - RC2
RELEASE CANDIDATE - NOT FOR PRODUCTION USE!
Make sure you are using the latest connector for your application(s). For using NVENC (SDK 9.1) encoders driver version 436.15 or later is required.
Fixes / Changes
- Revived the SVT AV1 encoder (still - but a bit less - experimental)
- Added "temporal mix" + "change fps" video filters
- Updated libx264 encoder to the latest version
- Added "prores_aw" encoder
- Added YUV 4:4:4 (8 bit and 10 bit) support for nvenc_h264 and nvenc_hevc (If the GPU supports it)
- Added support for timecode tracks (the connector has to provide a timecode)
Credits
Thanks to my all supporters by either PayPal, Patreon or BTC. Also thanks alot to the translators.
Top Patrons
Gronkh, Schauerland, Terry Mundy, Andreas Martin Aanerud, Michael wooldridge and Chris Woods
Download
-
Working on getting the timecode from resolve right now and already got something like this:
Hope this is what you'll need.
-
Voukoder 9 - RC1
RELEASE CANDIDATE - NOT FOR PRODUCTION USE!
Make sure you are using the latest connector for your application(s). For using NVENC (SDK 9.1) encoders driver version 436.15 or later is required.
Fixes / Changes
- Revived the SVT AV1 encoder (still - but a bit less - experimental)
- Added "temporal mix" + "change fps" video filters
- Updated libx264 encoder to the latest version
- Added "prores_aw" encoder
- Added YUV 4:4:4 (8 bit and 10 bit) support for nvenc_h264 and nvenc_hevc (If the GPU supports it)
Credits
Thanks to my all supporters by either PayPal, Patreon or BTC. Also thanks alot to the translators.
Top Patrons
Gronkh, Schauerland, Terry Mundy, Andreas Martin Aanerud, Michael wooldridge and Chris Woods
Download
-
Sorry, I don't have any AMD Pro GPUs at hand. Last time I checked AMD did not react to my question if they can support me with hardware.
-
Sorry, I don't have time to get involved with another project. (And I also don't have NV12 capture devices).
-
VP9 / QSV is acually built in already. But the initialization fails always and thus it is not displayed in the UI. Last time i checked (many months ago) the FFmpeg / libav implementation was not even working properly.
It is a bit painful to work with the QSV encoders.
-
It will be included with Voukoder 9.
When using such hw-features one has to know what the GPU capabilities are of course
But many people don't know. There are many "bug reports" like this already.
-
Unfortunately I can not work full time on Voukoder. I will check this when I find some time.
-
It should look like this:
Then it appears like this in Resolve:
