Unfortunately I can not fix it until Adobe has told me how to do it.
Beiträge von Vouk
-
-
Das ist so nicht korrekt. Im Gegensatz zu anderen GUIs verwendet der Voukoder keine binaries (wie z.b. x264.exe sondern nutzt direkt die C API). x264 erkennt das dort anhand des übergebenen Pixelformats:
CodeOutput #0, mp4, to 'C:\Users\Daniel\Desktop\test\Sequenz 01_31.mp4': Metadata: encoding_tool : Voukoder R2 Stream #0:0, 0, 1/60: Video: h264 (libx264), 1 reference frame, yuv420p10le(tv, bt709, progressive), 1920x1080 (0x0) [SAR 1:1 DAR 16:9], 0/1, q=-1--1, 60 fps, 60 tbn Stream #0:1, 0, 1/60: Audio: aac (LC), 48000 Hz, stereo, fltp, delay 1024, 96 kb/s detected 8 logical cores w:1920 h:1080 pixfmt:yuva444p16le tb:1/60 fr:0/1 sar:1/1 sws_param: Setting 'pix_fmts' to value 'yuv420p10le'
Und MediaInfo zeigt mir im fertigen Video das auch korrekt an:
Code
Alles anzeigenVideo ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High 10@L4.2 Format settings, CABAC : Yes Format settings, RefFrames : 4 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 2 s 650 ms Bit rate : 5 908 kb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 60.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.047 Stream size : 1.87 MiB (98%) Writing library : x264 core 157 Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=23.0 / qcomp=0.60 / qpmin=0 / qpmax=81 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00 Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709
Es hat sicherlich eher mit der Kombination der Parameter zu tun. Kannst Du mir bitte mal Dein komplettes Log nach Reproduktion des Fehlers schicken? Dann sehe ich mir das an.
-
Did not find a solution yet. I close it until there is a way to do this with the ffmpeg / libav.
-
Will be back in the next version.
-
Will be available in the next release.
-
Everything is explained here: Voukoder Performance Analysis
Zitat- Voukoder does not necessarily do exports faster! It simply provides access to different encoders. These give you the possibilities to choose between the three encoding priorities. Encoding speed or video quality or filesize. You can't have all together!
- Voukoder does not speed up rendering! If the host application is slow with rendering / delivering frames Voukoder can't make it go faster and it is actually limited to that speed. No matter how fast any encoder / GPU is!
-
-
Please provide your full voukoder log. (Settings > Log) after exporting the project.
Technical information about the voukoder performance and how to real the log data: Voukoder Performance Analysis
-
Added bwdif, yadif, zscale and unsharp.
More to come ...
-
Firewall rules can be set per application.
And it is also common (but unusual for a desktop system) to DENY access from ALL. But ALLOW access from specific systems. This is called white listing.
But if the patron list does not work for you, maybe you also do not the the update notifications. Both are using the same server.
But it seems it is not a bug in voukoder.
-
It might also be related to the old windows component not supporting the advanced text formatting functionality I am using.
-
no it is not hardcoded. It is loading this data via the above link using the wxHTTP component. So if your internet is blocked by your firewall you would not see the patrons.
This is just like OBS is doing it.
-
Does anybody else have this issue?
Are you able to access http://version.voukoder.org/patreon/patrons.php ?
-
I'd recommend the same as here: Iphone 4K video MOV to h265
- Don't use levels when dealing with software decoders
- Don't use bitrate based encodings when not aiming for a specific filesize (i.e. for BD authoring)
-
Audio is not implemented yet. I was not sure how important that is to users.
-
Sure. I have added the "Ref" parameter to the x265 config!
-
Noticed it a couple of days ago and it is fixed already.
-
Not sure if I can do anything about it. I need to check the wxWidgets framework.
-
Yes, you are right. I check that with the documentation. I fixed that.
-
Please be a bit more patient. I was away during the weekend and I am currently sick at home. Maybe other people would have helped you, too.
But this depends alot on your project ... so there is not perfect setting for every situation. I'd would recommend "NVENC h.264" with simple settings like these. You might adapt the "quantizer" setting. A smaller "quantizer" has better quality, a larger "quantizer" produces a smaller file.