Media format unsupported or otherwise unavilable/unsuitable for playing. · motioneye-project/motioneye#1824

(26 comments) (0 reactions) (0 assignees)Python (3,533 stars) (636 forks)batch import

bughelp wantedquestion

Description

Hello Im running motioneye 0.42.1 with motion 4.3.1 on Raspbian 10 buster on Raspberry Pi 3 model b. I record video on motion triggered in H264/OMX and since a few days I got the error « Media format unsupported or otherwise unavilable/unsuitable for playing. » ( Btw there is a misspelling on the word « unavailable ») when I read it through the web (192.168.1.x:8765)

I also upload my files on a Google Drive and videos on my drive are working correctly, same as read locally and when I download them

So where did the error come from ?

Thanks !

Contributor guide

Tech stack: pythonjavascripthtmlcss
Domain: frontendbackend
Issue type: bug
Difficulty: 3
Estimated time: half day
Activity status: stale
Clarity: needs investigation
Prerequisites: Basic understanding of video codecsmotioneye setup
Newbie friendliness: 30
Research direction: The issue reports a 'Media format unsupported' error when playing H264 video in the web interface. Investigate the web frontend's video serving mechanism, likely in the static files or templates. Check for any mime type configuration or browser compatibility issues. The error occurs only in the web interface but works locally and via Google Drive, suggesting a problem with how motioneye streams or serves the video file. Look into the relevant Python code that handles video playback in the UI. The misspelling 'unavilable' is also present in the error message, which could help locate the exact source.