Error and strange behavior with partitions and subme

1. offizieller Beitrag

    Case 1 - OK

    Voukoder: bframes=0 / partitions=p8x8,b8x8,i8x8,i4x4 (default) / subme=9

    MediaInfo: bframes=0 / analyse=0x3:0x113 / subme=9

    Case 2 - Remove b8x8. By some reason, subme 9 was forced to 7. FFMpeg CLI (4.0, 4.1.1) do not change subme from 9 to 7 with the same settings.

    Voukoder: bframes=0 / partitions=p8x8,i8x8,i4x4 (without b8x8) / subme=9

    MediaInfo: bframes=0 / analyse=0x3:0x10 / subme=7

    Case 3 - Remove b8x8 and leave Subme at default (7). Leads to AME Error: A low-level exception occurred in: Voukoder 1.1.3 (Exporter:9)

    Voukoder: bframes=0 / partitions=p8x8,i8x8,i4x4 (without b8x8) / subme=7 (default)

  • Digeridoo 19. März 2019 um 17:03

    Hat den Titel des Themas von „Error and strange behavoir with partitions and subme“ zu „Error and strange behavior with partitions and subme“ geändert.
    • Offizieller Beitrag

    Case 2: For some reason x264 does not take the subme=9 setting. There is also no clue in the log-file. Maybe it is related to the issue described in case 3.

    Case 3 - Thats an actual issue:

    Code
    [2019-03-19 22:28:32,266265][INFO] Unable to parse encoder configuration: crf=17,tune=film,x264-params=keyint=50:min-keyint=1:scenecut=0:bframes=0:partitions=p8x8,i8x8,i4x4

    It can't parse the configuration right. The commas in the partitions value are mistaken as the comma for separating the man key/value pairs. This is part of ffmpeg / libav.

    Using in FFMpeg CLI -x264-params "...:partitions=p8x8,i8x8,i4x4:..." works fine, delimiter of parameters here is a colon.

    What about Voukoder? Should commas in partitions replaced using other delimiter? Or it is not possible / does not help?

  • Vouk 25. Juni 2019 um 07:41

    Hat das Label Behoben hinzugefügt.