2024-11-21, 06:25 PM
(2024-11-21, 01:05 PM)BotBlake Wrote: Hello thereThanks for the warm and positive welcome.
I thought I’d throw in my two cents as well.
It's awesome to have new testers/supporters on board! 😄
(2024-11-21, 01:05 PM)BotBlake Wrote: pyTAB should™ run automatically...It appears to be an error about something about the drm2 driver (pyTAB is obscuring the error as a generic ffmpeg error if I recall correctly). That may be because I'm using Fedora Silverblue + an Ubuntu 22.04 container (via distrobox). Either way, I'll try to reproduce either on a VM or direct ubuntu host OS.
We’re aware of a few issues, but none that would block the entire program flow.
However, even pyTAB’s JSON files can’t be uploaded directly via the Web UI – the Web UI doesn’t accept None. Upload via API – specifically the Swagger Web UI – works, though! (pyTAB doesn’t support upload via API yet – PRs welcome 🗿)
(2024-11-21, 01:05 PM)BotBlake Wrote: Feel free to share more details about your issues with us!I'm still having issues finding the #jellyfin-hwa-tool:matrix.org channel (maybe it's a private one?), Either way, I'm reachable via matrix.org too (@mrkzboo:matrix.org)
For discussions, the Matrix/Discord channels mentioned earlier are the best places to go.
(2024-11-21, 01:05 PM)BotBlake Wrote: Now about hwatest:I did notice some similarities when I was looking at the code (i.e: I had to force-print the ffmpeg_stderr to see why it was failing),plus I did some git archeology to understand which was born first, etc. Good to know!
Did you know that pyTAB started as a fork of hwatest?
https://github.com/joshuaboniface/hwates...est:master
hwatest is a standalone program that doesn’t work in combination with the Hardware Survey Server. It uses preconfigured test files and FFmpeg commands, whereas pyTAB pulls all that info directly from the hwa server.
(By the way, even the FFmpeg version to use! 😉)
I did like hwatest because by default looked at the ffmpeg installed version (whereas pyTAB gets a custom one from the Internet if I'm not mistaken). Doing so also helped me to notice that there's some input/output ffmpeg changes for 7.1 (I did notice pyTAB used ffmpeg 6.x) .
Plus, I'm not a big fan of full cloud/Internet dependency for running tools (e.g: downloading content / uploading results). I do understand that this the the whole propose of the tool, so I can't say much in that aspect for this scenario
(2024-11-21, 01:05 PM)BotBlake Wrote: So, it’s not possible to adjust hwatest’s output to make it compatible with the Server.Ah, that whitepaper it's gold. My first goal was to adapt JSON from hwatest to submit directly to the page. but if I'm to invest time, I'd rather do it on the proper tool, so I'm looking forward to keep the engagement on the helping!
If you're still curious about the output format, you can find a description in the hwa server’s GitHub repository
https://github.com/JPVenson/Jellyfin.Har...esult-data.
Oh and or course what jkboy and cody where saying 😁
If you have any more questions, feel free to ask.
Kind regards, Blake
PS: Great, I think this is my first ever post on the Forum 😆
PS: All this because a friend asked about my device's performance for jellyfin to compare and I wanted to have an apple-apple comparison between devices. Hopefully, when I get this running we'll be able to speak the same language (perf. data).