Server Plugin: Transcoding Tests

[softworkz 3335]

7 hours ago, rb9999 said:

Stupid question I know, but how do I view the transcoding test reports?

The best way of viewing them is within the plugin.You see a list of test runs and for each, you can click on the "Results" button to view details:

 

But I think you are asking about those links at the top like:

and 

 

These links use the "localexplorer:" protocol and to open them, you need to install the browser extension that is mentioned at the bottom of the second post in this topic:

https://emby.media/community/index.php?/topic/112572-server-plugin-transcoding-tests/&do=findComment&comment=1185602

As the name says, this is for local access, which means that you need to have access to the exact same file path on the machine where the browser is running.
You could probably achieve this by creating the same mount inside proxmox and on the outer machine (pointing to the same data) and configure that path for the test output of the transcoding test plugin settings. Then it might work (haven't tried on Linux, though).

The reason why there's no implementatoin for remote downloading is that this would have taken several days of development, because allowing downloads from the file system is security critical and needs careful implementation - which is just out of scope for this plugin.
To make it still fairly easy when localexplorer: doesn't work, it is showing you the full paths for all the files, so you can just copy/paste them for accessing them with a tool of your choice (ssh, ftp, scp, etc.)

The top-level files for a test plan execution are always these two:

• .etrd - Emby Test Report Data
  This is a JSON file with data for all runs. It references other output files in the file system (in subfolder) by relative paths.
  It is meant to be used when accessing it directly in the file system where it has been written to
• .etra - Emby Test Report Archive
  This is simply a ZIP file. When you extract it, you get the full directory structure like in the output folder.
  There's also the .etrd JSON file and it's all the same as when accessing locally