Paulguk 3 Posted April 26, 2025 Posted April 26, 2025 I have a couple of videos that I acquired and they don't show the media info when added to my libraries. I have worked out for myself that it is due to them having variable bitrate audio rather than constant bitrate audio. I worked this out by removing the audio track as a test using MKVToolnix and then re indexing the videos without the audio. The files play ok but it means that if I want to use filters in Emby to find videos these are excluded. Is this a know issue?
Abobader 3464 Posted April 26, 2025 Posted April 26, 2025 Hello Paulguk, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team
Luke 42078 Posted April 26, 2025 Posted April 26, 2025 Hi, please try refreshing the metadata on it. If there's still no media info after that, then please attach the emby server log: How to Report a Problem Thanks.
Paulguk 3 Posted April 27, 2025 Author Posted April 27, 2025 So I have attached some screen shots along with a before and after log. These are the actions I have carried out to aid you. 1. Placed problem file onto my NAS in the appropriate folder and ran a 'scan library files' of the season folder. 2. No media info shown giving duration of the episode or video and audio details (screenshots attached) 3. Downloaded first emby log (attached) 4. Loaded file into MediaInfo app and took a screenshot of the audio details to assist. 5. Stripped audio from the file using MKVToolNix. 6. Placed file without audio in the appropriate folder (overwriting the problem file) and ran a 'scan library files' of the season folder. 7. Details for the video now show. 8. Downloaded second emby log. embyserver (after audio stripped off and reindexed).txt embyserver (With issue).txt
Solution Luke 42078 Posted April 27, 2025 Solution Posted April 27, 2025 OK see this: [aac @ 0x18653a0] Audio object type 42 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. In the near future we will be updating the ffmpeg build within Emby.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now