Roger Singh Could it be the source clips have a different framerate other than the timeline?
Beiträge von Vouk
-
-
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
-
-
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.
-
-
Yes, I can add this. Not too much complicated. Both yuv444 for 8 and 10 bit. For h264 and h265. But this depends on if your GPU supports this formats. Otherwise you'll get an error when the export starts.
-
Do you know if there is a public export SDK for AVID available?
-
The intention was to create a new premiere connector with a later SDK that is not CS6 compatible anymore. So we can still differentiate both - even if both connectors are installed.
-
I was able to reproduce this. To me it seems the frame buffer does not have the final video stream resolution. But I am not able to get some information (stride) about the image in the frame buffer. I always get "noParam(-6)" ... More hassle with undocumented code ...
-
That's nice to hear, but still strange.
I've just added support for additional framerates in 1.8.0 ...
-
The sampling frequency is just a display issue.
So the logfile is looking okay so far, besides that it just stops at some point. This is the time where it crashes?
-
Can you post a logfile, please? (See the sticky topic about where to find it)