If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I recently updated my install of Mezzmo to version 5.2.0.0 from 5.1.1.0. After the update, m4a audio files are treated as video files by the BubbleUPnP Android app which I use as the audio renderer. Other audio files such as mp3's play in the BubbleUPnP Android app as expected. I sent a log to the BubbleUPnP developer thinking the issue was with their android app. They replied with the following:

....the media server set a mime-type of video/mp4 for m4a audio files. That is not correct and it should be audio/mp4 or audio/m4a or audio/x-m4a....

I took a look at the device profile I was using and the .prf file, BubbleToMxPlayer.prf, does not appear to have changed from the DeviceProfiles folder to the DeviceProfiles.bak folder. The device profile is set to BubbleToMxPlayer & the delivery options seem fine.

Let me know if you would like me to email a full set of logs. The section below appears to confirm the mime type being incorrect for these. taz1l0z1l3z4l28552l622zal6501xdc05.m4a is the uid of the m4a file which is being requested. This is an audio file but it appears be identified as video/mp4.

Looking at the profile it appears that the container id of the audio mp4 section is wrong and will not match the file, it is mp4 but should be mov,mp4,m4a,3gp,3g2,mj2. It is matching the video mp4 container id so this is why video/mp4 is used as the mimetype. We have fixed this so you can send an email to support [at] conceiva [dot] com and we will send you the updated profile.

Looking at the profile it appears that the container id of the audio mp4 section is wrong and will not match the file, it is mp4 but should be mov,mp4,m4a,3gp,3g2,mj2. It is matching the video mp4 container id so this is why video/mp4 is used as the mimetype. We have fixed this so you can send an email to support [at] conceiva [dot] com and we will send you the updated profile.

Thank you for the reply. I have replaced the device profile with the new one provided, stopping the media server, closing the GUI, replacing the file, then reopening the GUI & starting the server. Unfortunately I'm seeing the same behavior as originally reported.

Can you please enable diagnostic logging then after restarting your Mezzmo media server try playing the file in the app then add the logs to a zip and send the logs to support [at] conceiva [dot] com so we can investigate what is happening?

Can you please enable diagnostic logging then after restarting your Mezzmo media server try playing the file in the app then add the logs to a zip and send the logs to support [at] conceiva [dot] com so we can investigate what is happening?

The 2nd device profile you sent along has resolve the issue. Thanks as always for the great support!