Problem playing music files on the MVP

[rtengvad]

Does anyone have problems playing music files on the mvp? Files and playlists works fine played with Sage on the computer but not on the mvp.

I can see that the server and the mvp are communicating like if the file is really sent to the mvp, and the mvps interface also indicate that music is being played. But no sound.

Any clues?

Rtengvad

[malbec]

Completely new to this, please keep that in mind.

I had the same problem...boiled down to trying to play wma files. Once I converted them to mp3 everything worked fine....

[rtengvad]

Hmmm strange. All my files are mp3.

Could be a problem with my system then... but no idea what to do since no audio settings on the Sage UI.

EDIT:
My log file: sagetv_0.txt

[rtengvad]

The new beta 4.1.7 has not solved my problem playing music files. I still get no sound when playing mp3 files on the mvp (pal-scart version).

I can see data is sent to the mvp but no sound. No problem when playing video.

I wonder if others with a pal-version mvp have the same problem.

Thanks

[Alfiegerner]

I have a pal mvp and am sorry to say I haven't had any problems playing mp3's. I haven't use this feature very much due to slowness of ui with large music set - when I have playback has been fine.

[rtengvad]

Thanks for that reply Alfiegerner.

Have you any idea what settings affects the mvp playback capability?

[Alfiegerner]

Sounds like an odd problem ...

So audio works fine on video / tv but not when playing straight mp3's?

I can't think of any settings that would cause that scenario ... (maybe someone with more know-how ...?) I know there are seeker/ settings that affect which files can be played but it sounds like that is not the issue as you can select the file with the mvp.

I wonder if it is some setting that has got screwed. If it is, try the following to force a reload of default MVP properties:

Unplug the MVP.

Move the MVP's .properties and .autobackup files elsewhere for now. In the clients directory of the sage parent directory move the 'MACADDRESS.properties' file to 'MACADDRESS.bak' and also move / rename the autobackup files.

After about 5 mins plug your MVP back in.

[rtengvad]

Ok here is what I have done

1) Stopped Sage service, unplugged the mvp and renamed the client folder to force Sage to create new mvp property files. Restarted Sage and after while I plugged the mvp back on. After boot up every time I tried to play a mp3 file the mvp crashed or rebooted it self.

2) I installed the original Hauppauge software to see if it was my mvp causing the problem. Everything worked fine.

3) Re-installed Sage from scratch building up the property files manually. Anxious I plugged in the mvp. Again it pretends to play the file but no sound.

So I’m back to start. No clues.

EDIT:

OK, I found out that after re-installation one of three possible scenarios happens when I try to stream mp3 audio files

1) The file seems to be played but no sound
2) The mvp flicks to boot up screen before the UI re-appear
3) Them mvp crash with black screen. Need to un-plug

I have attached a log file from when the mvp crash. The fun begins, I think, at time "on 2/22 0:30:41.590". If anyone can tell me what goes wrong I will be very happy.

Crash log file sagetv_0.txt

Thanks!

[rtengvad]

Found the problem!

It turns out that the media extender part of Sage doesn’t accept file paths or file names that contain special letters.

I had my music and pictures organized in a root folder names “Fælles” with the Danish special letter “æ”. Re-naming that and the problem went away for all music files that doesn’t contain other special letters.

The odd thing is that I’ve never had any problems on the server machine streaming music from that same path, but apparently the Sage extender part can’t handle the letters “æ” “ø” or “å”.

I have a few files where these letters are included the file name, so I hope for a fix soon.

Rtengvad

[Alfiegerner]

Hey that's great new! Glad you've discovered the problem. It looks like you should file a bug report with this.

[rtengvad]

Originally Posted by Alfiegerner

Hey that's great new! Glad you've discovered the problem. It looks like you should file a bug report with this.

I've done that. Thanks for your help.