next »

[Sebastian Andersson]

I have finished a MusePack input plugin for XMPlay which is available from the XMPlay webpage.

[Knurek]

I hear some static at the begining of some of my encodes. Should I upload the buggy files somewhere?

[Roj]

I hear some static at the begining of some of my encodes. Should I upload the buggy files somewhere?

It might not be the files, especially if they play properly on other players.  If the files are OK, static results when the audio stream is somehow interrupted.  This can be caused by buggy sound card drivers or an application that somehow has playback priority screwed up (it's not getting enough cycles).

I'd check the files with another player first.

[Knurek]

It might not be the files, especially if they play properly on other players.  If the files are OK, static results when the audio stream is somehow interrupted.  This can be caused by buggy sound card drivers or an application that somehow has playback priority screwed up (it's not getting enough cycles).
I'd check the files with another player first.

Work fine with Winamp plugin. Work fine with Foobar. Shouldn't be the problem of the files then.
I've noticed that the files that have static have some silence at the begining - the silence is decoded as static by the XMPlay plugin. Maybe that helps somehow.

[Roj]

Work fine with Winamp plugin. Work fine with Foobar. Shouldn't be the problem of the files then.
I've noticed that the files that have static have some silence at the begining - the silence is decoded as static by the XMPlay plugin. Maybe that helps somehow.

There ya go - structured problem solving.  You've just eliminated the soundcard drivers (two instances where the files play correctly), XMPlay (the Winamp plugin with XMPlay) and the files themselves (via foobar).  You've also noted special common characteristics of the files (the silence at the beginning of each).  That leaves only the XMPlay mpc plugin.

[Sebastian Andersson]

I hear some static at the begining of some of my encodes. Should I upload the buggy files somewhere?

You can send some of your files to my e-mail.

[Sebastian Andersson]

An update is available for xmp-mpc. It includes a ReplayGain fix and some minor improvements.

[Sebastian_Mares]

Download also available from http://support.xmplay.com/Plugins_native.html.

[Knurek]

An update is available for xmp-mpc. It includes a ReplayGain fix and some minor improvements.

That seems to have fixed whatever was wrong - no static here now. Thank you.

[Tsorovan]

Seeking is really slow. I'm beginning to suspect this is inherent in the MPC format? In a 27-minute track, it takes almost 3-4 seconds to jump to the end of the track on a 3 GHz P4C w/ 1 GHz FSB. Seems to work really nicely otherwise!

[Sebastian Andersson]

xmp-mpc uses libmusepack 1.1. There is no seek table included when seeking, it simply decodes to the frame wanted. That could be the reason why the seeking is so slow.

Edit 1: Here's the link to the HA post.

As Lefungus says, the seek table was broken and could produce artifacts.

[Sebastian_Mares]

Seeking is really slow. I'm beginning to suspect this is inherent in the MPC format? In a 27-minute track, it takes almost 3-4 seconds to jump to the end of the track on a 3 GHz P4C w/ 1 GHz FSB. Seems to work nicely otherwise!

Seeking is done by traversing all frames - there is no table of contents whatsoever. Peter or whoever is maintaining libmusepack removed that seektable feature due to some troubles. I cannot find the HA post where that was stated, though.

[Tsorovan]

Okie! Hoping SV8 gets nice, fast seeking. Or maybe even SV7.5. It's not slower seeking that in_mpc.dll (naturally), so... *shrug shrug*.

Again, nice work!

[raina]

Sounds nice, indeed. But what about tag editing? Since the native plugin doesn't have it, what would be the priorization if I was to use both the WA and native plugins? XMPlay only uses the features from WA plugins it doesn't have in itself. Would this work for native plugins as well? Playback with the native, tag adjustment with the WA plug.

[Ian @ un4seen]

Yep. Native plugins will always supersede WA plugins for playback, but you can still use the WA plugins for tag editting purposes if you wish.

[Tsorovan]

I just have to say this plugin works great so far. How about adding dynamic bitrate display (VBR yadda yadda) like in_mpc.dll?

[Sebastian Andersson]

An update is available for xmp-mpc. It now reports the encoder which was used to produce the stream, the profile name and the number of frames (in the main panel).

Regarding your VBR stuff Tsorovan; I will have a look at what I can do about it.

[Tsorovan]

I have this MPC file that seems to be corrupt. Thing is, whilst in_mpc.dll just hops onto the next file when it detects the corrupt frame or wherever at 6:47, this plugin produces loud distorsion for a split second, then crashes XMPlay.

Let me know if you need the file (it's 10 MB or so).

[Sebastian Andersson]

I am not sure why xmp-mpc produces distortion sound and crashes XMPlay, but it could be due to a difference between in_mpc and xmp-mpc. in-mpc uses an old (buggy) version of the MusePack decoder library, while xmp-mpc uses the latest one (libmusepack 1.1). The MusePack development team might have introduced a new feature, bug fix or any thing, which caused this problem.

While I am at it, I could mention that I have added a VBR display in xmp-mpc and reduced the DLL size a bit (no compression).

Link: http://www.un4seen.com/filez/2/xmp-mpc.dll

[Tsorovan]

Ah I see. Also: cool, thanks!