Yes I will investigate here. I will probably need a chinese contact person who explains the whole situation in china to me. Preferably with good english skills and also knowing how to work together internationally. Can you use this website without VPN?
是的，我将在这里进行调查。我可能需要一位中国联络人向我解释整个中国的情况。最好具有良好的英语水平，并且知道如何在国际上合作。您可以在沒有VPN的情況下使用此網站嗎？
Edit: Does this link work in china? https://d.voukoder.org/voukoder-8rc1.msi
Did you try using a comma as separator?
i.e. "-3,-3"?
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.
Thanks to my all supporters by either PayPal or Patreon.
Gronkh, Schauerland, Michael Wooldridge, Kai_307 (Kai C. Ternes), Chris Woods
Es scheint ein Duplikat von 7.2.121 video filters still applied despite removing them in options zu sein was in dem nächsten Release behoben sein wird.
This issue is getting reported again and again, but I was never able to reproduce it myself. Thanks for providing the neccessary steps so i was finally able to reproduce this behaviour on my dev machine. So, yes I can confirm it and looking into it right now.
This issue is fixed in the next release.
No, but this might have to do with the MKV implementation in FFmpeg. Maybe there were changes in its codebase. But normally a container (esp. MKV) is not that much interested what color format is withing its frames/packets. So i can't really tell.
MKV is nice because you can put almost anything into it but it does have its flaws.
[15:57:12] Opening codec: libmp3lame with options: abr=0|b=128000
[15:57:12] FFmpeg: Specified sample rate 96000 is not supported
[15:57:12] Failed opening codec: libmp3lame
Set the audio sample rate in premiere to less than 96000.
[12:30:44] Timebase: 265046161/-1303869184 (-4.92 fps)
The frame rate auto detection did not work. Select a proper frame in premieres video tab.
Can you please post a log file for that issue?
Please enable low-level debugging in the Voukoder settings and share the logfile with that. Let's see if we'll find a hint there.
I don't see anything suspicious so far.
Can you reproduce this or did this just happen just once?
Is there enough space on drive T: left?
Du hast einfach Glück gehabt das es eine relativ leichte Anpassung war. 
Wird im nächsten Release enthalten sein. Benötigt dann zusätzlich den angepassten Premiere Connector 1.7.0.
Die Daten in rgb48le und bgra64le sind identisch. bgra64le hat nur eine andere Kanalsortierung und zusätzlich einen Alpha Kanal für Transparenz.
Ich habe mal diverse Tests durchgeführt. Das sieht soweit ganz gut aus. Der Adobe 16 bit Modus enthält allerdings nur 15 bit Farbinformation und muss in FFmpeg kompatible 16 bit skaliert werden. (SIMD SSE2).
[09:56:46] FFmpeg: Stream #0:0
[09:56:46] FFmpeg: , 0, 1001/60000
[09:56:46] FFmpeg: : Video: ffv1, 1 reference frame, bgra(progressive), 3840x2160 (0x0) [SAR 1:1 DAR 16:9], 0/1, q=2-31, 200 kb/s
[09:56:46] FFmpeg: ,
[09:56:46] FFmpeg: 59.94 fps,
[09:56:46] FFmpeg: 59.94 tbn
[09:56:46] FFmpeg: Video
ID : 1
Format : FFV1
Format version : Version 3.4
Codec ID : V_MS/VFW/FOURCC / FFV1
Duration : 3 s 270 ms
Bit rate mode : Variable
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 FPS
Color space : RGBA
Bit depth : 8 bits
Scan type : Progressive
Compression mode : Lossless
Default : Yes
Forced : No
coder_type : Golomb Rice
MaxSlicesCount : 4
ErrorDetectionType : Per slice[10:10:43] FFmpeg: Stream #0:0
[10:10:43] FFmpeg: , 0, 1001/60000
[10:10:43] FFmpeg: : Video: ffv1, 1 reference frame, rgba64le(progressive), 3840x2160 (0x0) [SAR 1:1 DAR 16:9], 0/1, q=2-31, 200 kb/s
[10:10:43] FFmpeg: ,
[10:10:43] FFmpeg: 59.94 fps,
[10:10:43] FFmpeg: 59.94 tbnVideo
ID : 1
Format : FFV1
Format version : Version 3.4
Codec ID : V_MS/VFW/FOURCC / FFV1
Duration : 3 s 270 ms
Bit rate mode : Variable
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 FPS
Color space : RGBA
Bit depth : 16 bits
Scan type : Progressive
Compression mode : Lossless
Default : Yes
Forced : No
coder_type : Range Coder
MaxSlicesCount : 6
ErrorDetectionType : Per sliceEin "copy" geht an der Stelle nicht. Premiere dekodiert jedes Frame und gibt den Framebuffer unkomprimiert an Plugins (=Voukoder) weiter. Voukoder muss das dann mit FFmpeg / libav abgleichen. In diesem Falle wäre es wohl:
Ist ein bisschen Arbeit, sollte aber gehen.
I enabled the timecode information in mov/mp4:
Tagged date : UTC 2021-02-11 19:31:35
TIM : 00:00:41:50
TSC : 60000
TSZ : 1001... and 00:00:41:50 is exactly the position where I rendered my short clip from the original footage from.
Available in the next release.
Following up the bt2020/HDR topic here: HDR Encoding Guide for Premiere Pro
Okay, premiere now supports this formats:
PrPixelFormat_RGB_444_12u_PQ_709 = MAKE_PIXEL_FORMAT_FOURCC('@', 'P', 'Q', '7'), // 12 bit integer (in 16 bit words) per component RGB with PQ curve, Rec.709 primaries
PrPixelFormat_RGB_444_12u_PQ_P3 = MAKE_PIXEL_FORMAT_FOURCC('@', 'P', 'Q', 'P'), // 12 bit integer (in 16 bit words) per component RGB with PQ curve, P3 primaries
PrPixelFormat_RGB_444_12u_PQ_2020 = MAKE_PIXEL_FORMAT_FOURCC('@', 'P', 'Q', '2'), // 12 bit integer (in 16 bit words) per component RGB with PQ curve, Rec.2020 primaries
PrPixelFormat_RGB_444_10u_HLG = MAKE_PIXEL_FORMAT_FOURCC('@', 'H', 'L', '1'), // 10 bit integer per component RGB with HLG curve, Rec.2020 primaries
PrPixelFormat_RGB_444_12u_HLG = MAKE_PIXEL_FORMAT_FOURCC('@', 'H', 'L', '2'), // 12 bit integer (in 16 bit words) per component RGB with HLG curve, Rec.2020 primariesI'm just wondering they're all RGB. When dealing with bt2020/HDR it's not YUV anymore?