Bug Report The broken picture in case of record, why?

santer

Member

Attachments

  • 2017-05-22 00-02-05.flv_snapshot_00.00_[2017.05.22_00.10.35].jpg
    2017-05-22 00-02-05.flv_snapshot_00.00_[2017.05.22_00.10.35].jpg
    418.7 KB · Views: 19
  • 2017-05-22 00-02-05.flv_snapshot_00.00_[2017.05.22_00.11.03].jpg
    2017-05-22 00-02-05.flv_snapshot_00.00_[2017.05.22_00.11.03].jpg
    431 KB · Views: 15
  • 2017-05-22 00-02-05.flv_snapshot_00.00_[2017.05.22_00.11.10].jpg
    2017-05-22 00-02-05.flv_snapshot_00.00_[2017.05.22_00.11.10].jpg
    422.4 KB · Views: 15
  • log.txt
    10.7 KB · Views: 5

santer

Member
@R1CH
@OG See OH Zee

No overloading, but broken frames...
┃ ┣download_frame: min=0 ms, median=0.001 ms, max=12.182 ms, 99th percentile=0.003 ms

What do you think about it?
 

Attachments

  • LA ICQ 1 look-ahead 50.txt
    17.9 KB · Views: 12

koala

Active Member
You are overtuning the Quicksync encoder. LA_ICQ is tricky and not the most stable, and quality 1 is very unusual. Use ICQ rate control instead and use quality of 15..20. Smaller values than 15 only produce enormously huge files but not visibly better footage, and they strain the encoder very much.

As alternative, try NVENC as encoder. If you require it, NVENC has an explicitly lossless mode. At least with Pascal GPUs, I don't know if your slightly older GPU supports this.
 

santer

Member
@koala
NVENC lossless log, and No overloading, but broken frames...
And ┃ ┣download_frame: .... - best in quick sync
 

Attachments

  • 2017-05-24 21-44-24.txt
    18.1 KB · Views: 7
Top