next »

[Dotpitch]

Is it perhaps assuming the wrong bit-depth?

[Just For My Memory]

When the tag in MP3 file is too long (with Unicode characters)...




Tried with latest build of XMPlay (3.6.0.48)

[Pike84]

Do you have exclusive mode enabled in the WASAPI options page? If not, the output will be limited to the device's "Default Format", as set in the "Advanced" tab of the device's properties in the Sound control panel.

I didn't have exclusive mode enabled, and enabling it fixed the issue. Are there downsides to having the option ticked by default? I'd imagine many others will bump into the same problem; when their sound card defaults to something else than 44100Hz (the popular X-Fi seems to have 48000Hz as default).

Oh, and a little detail: the hertz symbol should be spelled Hz, with capital 'H' - it's spelled wrong in both main window while playing and the info window.

[Knurek]

Recently I've been getting all sorts of random hangs while using XMPlay.

Couldn't exactly reproduce it, nothing really seemed to matter - type of file used, activity being done to crash the player and so on, so I didn't want to pester Ian for fixes.

But recently, on a wild hunch, I've changed XMPlay's skin from Plastic to WAModern and lo and behold - no hangs for the past two weeks (and I was used to having to fire up task manager and kill XMPlay's process at least once a day).

Is this a known problem? If so, can anyone here explain what in the skin could have been causing this behavior?

[moriez]

Your question reminds me of a prob I had with the Lithe skin. Maybe this thread is of some help: http://www.un4seen.com/forum/?topic=12614.0

[Ian @ un4seen]

It happens with both CD-quality format and 88200 Hz (the latter resampled to 192000 Hz by XMPlay).  This is exclusive mode.  The receiver reports PCM. 

As Dotpitch suggests, perhaps the bitdepth/resolution is the problem. You could try disabling the "Use highest available resolution" option in the WASAPI options page and then play with the "Resolution" setting in the Output options page.

When the tag in MP3 file is too long (with Unicode characters)...

Please upload an example MP3 file (and confirm your title formatting string) to reproduce that problem with here...

   ftp.un4seen.com/incoming/

Recently I've been getting all sorts of random hangs while using XMPlay.

Couldn't exactly reproduce it, nothing really seemed to matter - type of file used, activity being done to crash the player and so on, so I didn't want to pester Ian for fixes.

But recently, on a wild hunch, I've changed XMPlay's skin from Plastic to WAModern and lo and behold - no hangs for the past two weeks (and I was used to having to fire up task manager and kill XMPlay's process at least once a day).

Is this a known problem? If so, can anyone here explain what in the skin could have been causing this behavior?

I can't think of any explanation for that. Are you using Windows Vista/7? If so, next time the problem happens, you could use the "Create Dump File" option in Task Manager to save a dump file for the hung XMPlay process and then upload that (after ZIPing) to have a look at here...

   ftp.un4seen.com/incoming/

Make sure you're using the latest stuff when doing that...

   www.un4seen.com/stuff/xmplay.exe

[Pike84]

Are there downsides to having the option ticked by default? I'd imagine many others will bump into the same problem; when their sound card defaults to something else than 44100Hz (the popular X-Fi seems to have 48000Hz as default).

Oh, and a little detail: the hertz symbol should be spelled Hz, with capital 'H' - it's spelled wrong in both main window while playing and the info window.

Uh, hello..?

[Ian @ un4seen]

I think you're right that the WASAPI plugin should have exclusive mode enabled by default. I'll make that change for the next update.

[Just For My Memory]

Download the test MP3 file here:
http://www.mediafire.com/download.php?9ar0nw0xwzz4xn1

Format string:
%?2{%2 - }%3 (%cut{%4|4|}) - %?1{%1|%0}

[Ian @ un4seen]

Here's an update to try...

   www.un4seen.com/stuff/xmplay.exe

Let me know if you still see the problem happen.

[Just For My Memory]

I thought it was fixed but it didn't

[Ian @ un4seen]

Are you referring to the title being cropped short, or are there still dodgy characters being shown?

[Just For My Memory]

Are you referring to the title being cropped short, or are there still dodgy characters being shown?

It is cropped short (Dodgy characters disappeared).

[saga]

IIRC there is a limit for the systray tooltip length in Windows which is about 64 characters, and your track title is about that length.

[Just For My Memory]

IIRC there is a limit for the systray tooltip length in Windows which is about 64 characters, and your track title is about that length.

See the first image I posted above and explain yours why... 

[wrkq]

Are you referring to the title being cropped short, or are there still dodgy characters being shown?

It is cropped short (Dodgy characters disappeared).

Actually, I think the "star" character (third from the right in tooltip on the screenshot) is still erroneous, too.
PS. What about the two-button-drag bug?

[saga]

See the first image I posted above and explain yours why...  

I would guess that previously 64 characters from the song title were copied (according to the documentation), but the terminating character was not set, so Windows simply read some garbage characters beyond the string length. In the MSDN you can read that my suspicion should be about right (see the szTip part of the struct). Windows doesn't limit itself in the displayed string length, but the data field that contains the string is simply not big enough to hold any strings longer than 63 characters (the 64th character musst be a string terminator).

[ridon]

fade-out setting doesn't work

[Ian @ un4seen]

IIRC there is a limit for the systray tooltip length in Windows which is about 64 characters, and your track title is about that length.

With modern Windows (since Win2K I think), the tray tooltip length limit can actually be raised to 128 characters (or 127+null), but XMPlay also has its own limit. A 139 byte buffer is used to build the tray title, but that is for the UTF-8 form of the title, in which there may be multiple bytes for each (non-ASCII) character that is displayed. In this case, 139 bytes coincidentally translates to around the old 64 character limit. Here's an update to try, which should allow more of exotic titles to be seen...

   www.un4seen.com/stuff/xmplay.exe

So I've made a huge jump from 3.6.0.1 to .47.
Because of that, I don't know if it was this way since the day it has been introduced, or broken by one of following updates, but the "press and hold left, then press and hold right, and do a 2-button drag" way of temporarily unlocking the "lock window position" feature works only in some places.
Concrete example: Miniwindow, track title. With position unlocked, I can leftclick+drag and move the window. With position locked, If I'll left-hold and click right, I get the context menu.
In comparison, clicking any "non-functional background" place in the skin lets me left-drag if unlocked, and do the 2-button drag if locked.

The update above should sort this.

fade-out setting doesn't work

What file format(s) are you playing? Note the fade-out option only applies to looped files (it fades-out the loop), but most file formats don't contain looping info. You could try enabling the "Auto-loop any track ending with sound" option for those formats.

[wrkq]

Ian, I know you've heard this already... but you rock.