Closed m0vse closed 1 year ago
After further investigation and running ffprobe on both working and non-working files, it appears that the files that are being identified as AUDIO, have the audio (AAC) stream first whereas the ones correctly identified as VIDEO have the video stream (H264) first.
Having examined the code in scanner.js, it only looks at the first stream, maybe it should iterate through all streams until it finds valid video?
I reproduce the same issue with video .MOV recorded with iPad. stream audio is #0 and stream video is #1. So media scanner tells that it's an AUDIO type.
This pull request might resolve it, did for me. https://github.com/CasparCG/media-scanner/pull/41
It's now nearly 4 years since this issue was opened and @m0vse provided a PR to resolve it, and I'm still getting a huge number of mis-detected media files using the vanilla release of the media scanner. What needs to happen to get some movement here?
This should be fixed in https://github.com/CasparCG/media-scanner/releases/tag/v1.2.0
I had a show yesterday and copied some .mpg files (1920x1080 25fps) into the media directory. I then couldn't find them in the CasparCG client under the video section. Eventually I noticed that they had appeared in the audio section so had been wrongly identified (this happened to 3 out of 10 files).
When I loaded them into the client, the videos played fine.