next »

[Brian]

Ian - many thanks and congratulations on the release of 3.4; a great step forward.

I have two queries, please:

(1) How do I get the library directory monitoring going? I've added several directories, each containing playlists, but they all show up in the list as having no entries.

(2) I wonder why the sample rates available don't correspond with all of the rates supported by my soundcard? For example, my soundcard supports 88200 kHz, but in XMPlay there's a jump from 48000 to 96000. I have `set hardware sample rate' checked.

Many thanks once again.

[Cris]

Another Bug: only Winamp DSP plug-ins work???
Other plug-ins (like MiniLyrics, xmp-scrobbler or Flanger, which worked in 3.3.0.6 as DSP plug-ins) are not visible anymore . How can these plug-ins be used in XMPlay 3.4?

[Dotpitch]

3.4 is here, and I really really like it!

The reworked Options and stuff windows looks better, and library monitoring with a blacklist for filetypes is perfect . The fullscreen visuals are nice, but you shouldn't use "boost" in xmplay.ini anymore, it will make the music stutter. I also noticed the sorting speed of the library increased a lot.

One note although. When running a fullscreen visual and the title pops up, the XMPlay icon still has a low resolution, it deserves a lot more .

[Cris]

3.4 is here, and I really really like it!

The reworked Options and stuff windows looks better, and library monitoring with a blacklist for filetypes is perfect . The fullscreen visuals are nice, but you shouldn't use "boost" in xmplay.ini anymore, it will make the music stutter. I also noticed the sorting speed of the library increased a lot.

Oops! I started my previous post without saying the good parts of the new version  Sorry about that. The best part of the new version is all of it
I especially like the new "extra-large" Equalizer, and I noticed (maybe it's a false impression) that the Reverb option sound a little different (better, of course). The bad part of the new Equalizer is that the skins have to be updated.

One note although. When running a fullscreen visual and the title pops up, the XMPlay icon still has a low resolution, it deserves a lot more .

Yup. And, also, it would be usefull a FPS display in fullscreen.

[amit]

Hello Ian ,

did you decide eventually to avoid the implementation of out plugins solution and instead convert from waveout to directsound?

[Ian @ un4seen]

(1) How do I get the library directory monitoring going? I've added several directories, each containing playlists, but they all show up in the list as having no entries.

Do the directories only contain playlists? The monitoring only actually looks for playable files and ignores playlists, so playlists will still need to be added manually. I wasn't really sure whether to process playlists in monitored directories, but in the end decided not to, as the playlists could contain files from other directories.

(2) I wonder why the sample rates available don't correspond with all of the rates supported by my soundcard? For example, my soundcard supports 88200 kHz, but in XMPlay there's a jump from 48000 to 96000. I have `set hardware sample rate' checked.

The sample rates in the Output options page are just defaults, and do not represent what the output/device/drivers support. To set another rate (eg. 88200), you can enter it instead of choosing one of the defaults.

Note that if the output does not support the chosen settings, then it can use its own settings (see "Output" text in the General info).

Other plug-ins (like MiniLyrics, xmp-scrobbler or Flanger, which worked in 3.3.0.6 as DSP plug-ins) are not visible anymore . How can these plug-ins be used in XMPlay 3.4?

I'm afraid old DSP plugins won't work with 3.4, and will need to be updated. An updated xmp-scrobbler plugin should be available later today/tomorrow, and I'll put an updated Flanger example (DSP plugin API) up on the XMPlay page shortly.

One note although. When running a fullscreen visual and the title pops up, the XMPlay icon still has a low resolution, it deserves a lot more .

Yeah, it uses the normal icon blown-up. It was either that or bloat the EXE with a high res icon... chunky icon won

the Reverb option sound a little different (better, of course). The bad part of the new Equalizer is that the skins have to be updated.

Yep, the reverb has been updated/improved

When using old 5-band EQ skins, XMPlay will automatically adjust the new/extra bands, so there shouldn't be too much of a problem. The extra bands can also be accessed using the EQ config dialog.

did you decide eventually to avoid the implementation of out plugins solution and instead convert from waveout to directsound?

Nope, XMPlay still uses Waveout by default. A DirectSound plugin is available on the XMPlay page.

[Brian]

Hello Ian ,

did you decide eventually to avoid the implementation of out plugins solution and instead convert from waveout to directsound?

You need to download the alternative output plugins (DirectSound and ASIO) separately; they don't come bundled with the main player download.  ASIO is working great here.

[Brian]

(1) How do I get the library directory monitoring going? I've added several directories, each containing playlists, but they all show up in the list as having no entries.

Do the directories only contain playlists? The monitoring only actually looks for playable files and ignores playlists, so playlists will still need to be added manually. I wasn't really sure whether to process playlists in monitored directories, but in the end decided not to, as the playlists could contain files from other directories.

Yes, they contain only playlists. So I take it this means I can't get the benefit of directory monitoring? That's disappointing - I'd been looking forward to it.

[Cris]

Other plug-ins (like MiniLyrics, xmp-scrobbler or Flanger, which worked in 3.3.0.6 as DSP plug-ins) are not visible anymore . How can these plug-ins be used in XMPlay 3.4?

I'm afraid old DSP plugins won't work with 3.4, and will need to be updated. An updated xmp-scrobbler plugin should be available later today/tomorrow, and I'll put an updated Flanger example (DSP plugin API) up on the XMPlay page shortly.

I don't use xmp_scrobbler and Flanger, I just had them there. But about MiniLyrics I'm sad it doesn't work anymore... can't you make it so it will work? Please It's not a DSP, it just needs to know details about the song I'm listening to...

[Knurek]

I did manage to wreak some havoc on the playlist by playing with overwriting module data, and then deleting the files from the library. Will see if I can reproduce it 100%

[Dotpitch]

The shortcuts box in options and stuff is doing a little weird... Purely aesthetic, but the topmost action will often remain selected. Could you add some sort of sorting on action someday? And perhaps rename "Info - Fullscreen visuals" to "Info - Toggle fullscreen visuals", it confused me a bit.

I did manage to wreak some havoc on the playlist by playing with overwriting module data, and then deleting the files from the library. Will see if I can reproduce it 100%

XMPlay crashed when I mass-tagged some modules, without deleting them from the library. Worked fine the second time .

[urlwolf]

Thanks for the release! Changelog looks yummy.

bug report: When adding dspOzone.dll through the DSP winamp wrapper, it crashes here.

[yagood]

Updated version of xmp-scrobbler is ready.

[urlwolf]

thanks for the scrobbler plugin.

When adding a large library it crashes too.
I did so in 3.3., I had to add small parts e.g., A-B, then C-D... Y-Z.
But now that the library will be 'live',  connected to my music dir, I'd need to do it propperly, that is, no draggon-dropping small chunks but assigning the dir in the library options pannel.

Any workarounds?

[amit]

I didn't think ASIO output would be available at first stage. This exceeds my expectations

Thanks ,Ian .

[raina]

Scandinavian characters in .XMs stopped displaying properly.

Oh and everything seems to be XMPlay-able now when opening files with the Open file(s) button. XMPlay-able gives me the same listing as All files.

[yagood]

Probably a bug - when I use "Add directory" in the Playlist window and select certain directory, files from that directory are being added two times to the playlist, so it looks like this (instead of display names I paste paths below):

001 E:\Mp3\!soundtrack\Batman Begins [2005-06-14]\01. Vespertilio.flac
002 ...
.
.
.
012 ... (last file from this directory) ...
013 E:\Mp3\!soundtrack\Batman Begins [2005-06-14]\01 Vespertilio.flac
.
. (files from that directory, but without "." after track number in the path - marked as dead)
.

For some reason it only happens in this particular directory, I can't reproduce it with other directories so far. It worked fine with 3.3, not sure about 3.4 betas.

[Maserati]

digg 
http://www.digg.com/software/XMPlay_3_4_released

[raina]

* MOD signature shown in "General" info

Why not identify the tracker for other modules as well? Of course some evil trackers pretend to be something they aren't but breaking module standards can expose them.

[Torkell]

Current observations and bug-like effects:


The built-in Spectrun and Spectrum 3D visulisations now appear at the same size as the other visulisations (previously they defualted to about half the height of other visulisations).

The horizontal 'scroll' in Spectrum 3D is a lot (about 2x by eyeball) faster than 3.3.0.6.

Full-screen visulisations are painfully slow with and without restrict size, and the resizing appears to be nearest-neighbour (WinXP SP2, Athlon 1.3GHz, GeForce4 Ti4600).

The library file is *not* backwards-compatible. 3.3.0.6 will delete the 3.4.0.0 library file.

MOD pattern display now scrolls the pattern as opposed to the bar. I can't find a way to change this - middle-clicking in the display toggles the channel instead of the scrolling behaviour.

MOD auto-looping defaults to 'never' - this is counter-intuitive if you had auto-loop and MOD only selected in 3.3.0.6.

It's not clear that the 'Save' button in the preset section saves all the presets, rather than updating the selected one (and so doesn't affect the same things as 'Load' and 'Remove'). This is probably a case of RTFM, but it's still unclear HCI.