Skip to content

JSON report on windows not escaping file path #817

@henryborchers

Description

@henryborchers

The json report generated by mediaconch does not escape the file path backslashes for Windows file paths in MediaConch.media.ref field which results in malformed formatted json on Windows.

MediaConch.exe dummy\bars.mp4 --Output-Json=dummy.json will generate the following json


{
  "MediaConch": {
    "version": "0.2",
    "verbosity": 5,
    "creatingApplication": {
      "name": "MediaConch",
      "version": "25.04",
      "url": "https://mediaarea.net/MediaConch"
    },
    "media": [
      {
        "ref": "dummy\bars.mp4",
        "implementationChecks": [
          {
            "pass_count": 0,
            "info_count": 0,
            "warn_count": 0,
            "fail_count": 0,
            "checks_run": 0,
            "name": "MediaConch Implementation Checker does not support AVC as found in Video track"
          }
        ]
      }
    ]
  }
}


"ref": "dummy\bars.mp4", does not escape the backslash. JSON reads \b in the filename as an escape character instead of a backslash.
Since Windows uses backslashes for paths, this is only a problem on Windows machines. This should either escape the backslash character with a second backslash or the ref field should use the unix style paths aka forward slash.

I have tested this on both 25.04 and on latest commit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions