3.4 reports, queries and bugs

Started by Brian,

Tsorovan

Effect tails are what time-domain effects like delay and reverb have.

amit

I read in the xmplay history :
Quote* Support for embedded CUE sheets
Does this refer to tracks having the cue as part of their tags?
I am asking this because I tried playing such a track but xmplay  didn't recognize the cue.

Jace

Quote from: urlwolfSmall bug.

I have assigned F12 to minimize/restore from tray.
It minimizes ok, but doesn't restore.
It does if I assign other shortcut (I have tried ctrl + .)

Thanks

Have you removed the already existing hotkey for F12? (Reload skin).. Perhaps that's thorwing it off a bit?

And Ian, concerning the playlist stuffups, either you've already fixed it in the latest stuff or something very very odd is going on. Unable to reproduce it now, tried several times. No files removed, no reboots, nothing. =\

So yeah, good job! :D

Cris

There would be a problem when using fullscreen visuals. I don't know how or why, but sometimes, when in fullscreen, XMPlay just closes. No errors, no crashes, no nothing. It just closes. Has anyone else had this problem?

raina

Cris, some visualizations apparently will do that. I didn't have many visses installed but when the fullscreen feature came to town, I went to the support site to download some of my old favorites. I ran all of them in fullscreen for a while and just said goodbye to any which did that. Most of CoR's stuff seems to work fine and fortunately, the Rabbit Hole does too. The 1.1 TEST that is, not the 1.0.

Dotpitch

Quote from: amitI read in the xmplay history :
Quote* Support for embedded CUE sheets
Does this refer to tracks having the cue as part of their tags?
I am asking this because I tried playing such a track but xmplay  didn't recognize the cue.
Yes, CUE-sheets embedded in tags should be recognized. What filetype was it, and did the tag show up on the info/message tab?

Ian @ un4seen

Quote from: MaseratiIan is there a way to clear the 'Find Track' without the windows critical stop sound?

Here's an update with a "NoBeeps" secret INI setting to disable all beeping...

   www.un4seen.com/stuff/xmplay.exe

Btw, from now on, I've decided to increase the version number even in "stuff" versions (at least in the Options'n'stuff window). Release versions will be "3.4.x.0", while stuff versions will be "3.4.x.y".

Quote from: KnurekThe MOD year detect function needs some tweaking.
Bad year detection on ftp://ftp.modland.com/pub/modules/Fasttracker/Maxym/liver landou 2.ft. Not sure if there's a way to automate that though. :|

I've tweaked it a bit (updated EXE above), so that it doesn't misdetect the year of that file.

Quote from: Auren1. There's a bug with output device naming in cyrillic:
2. There is a cosmetic bug with string's place in "Options and stuff":
3. There is a cosmetic bug with an end of time string in "Track info" dialog.

Please try the update above, and let me know if you still have these problems.

Quote from: urlwolfI have assigned F12 to minimize/restore from tray.
It minimizes ok, but doesn't restore.
It does if I assign other shortcut (I have tried ctrl + .)

Is that a global shortcut? It'll work when XMPlay is in focus, but it appears that Windows doesn't allow global hotkeys to use F12 - I guess it's already taken/reserved.

Quote from: amitI read in the xmplay history :
Quote* Support for embedded CUE sheets
Does this refer to tracks having the cue as part of their tags?
I am asking this because I tried playing such a track but xmplay  didn't recognize the cue.

Yep, it'll check APEv2 tags (and FLAC via the plugin) for a "Cuesheet" tag, as used by Wavpack (and FLAC) and maybe others. What format is your file? Please upload it to have a look at...

   ftp.un4seen.com/incoming/

Quote from: CrisThere would be a problem when using fullscreen visuals. I don't know how or why, but sometimes, when in fullscreen, XMPlay just closes. No errors, no crashes, no nothing. It just closes. Has anyone else had this problem?

Yep, some vis are a bit picky about the res they run at, particularly changing the res. If you have a plugin like that, you could try going fullscreen with another vis, and then switch to the picky one.

XMPlay should actually catch the vis crashing, but it'll then continue to run the vis, in the hope that it was a one-off :) ... Instead of doing that, it'll now unload the vis in the update above, which should avoid further problems (like XMPlay closing).

Cris

#67
Quote from: Ian @ un4seenYep, some vis are a bit picky about the res they run at, particularly changing the res. If you have a plugin like that, you could try going fullscreen with another vis, and then switch to the picky one.

XMPlay should actually catch the vis crashing, but it'll then continue to run the vis, in the hope that it was a one-off :) ... Instead of doing that, it'll now unload the vis in the update above, which should avoid further problems (like XMPlay closing).

OK, but the problem is I don't use only ONE visual, I use ALL visuals (In fact I'm using only one, Rappa, which uses the other ones). So it's kinda hard to see which visual behaves weird when I have about 100 of them ;D

Sometime before (I think sometime last year) I checked all of the visuals to see which one crashes, and I deleted some of them (about 10 or so...). The ones which I currently use worked fine then.
I don't know if this helps, but this problem usually appears when the song changes and that's why I assumed it's related to XMPlay (some kind of buffer error, because the fullscreen visuals use lots of CPU, especially Rappa which has some more effects and can run multiple visuals in the same time). Anyway, I'll try to test (again) the visuals, to see if any of them crashes.

My PC config: AMD Sempron 2600+, ~1,8GHz, 512 DDR, ATI Radeon 9250 (128 MB, 128 bits)

EDIT: Oh, and one more thing: Rappa also has the ability to catch the vis crashing, and many times it "saves the day". This is one more reason why I assumed that this problem is XMPlay related more, then visual related.

amit

Quote from: Ian @ un4seen
Quote from: amitI read in the xmplay history :
Quote* Support for embedded CUE sheets
Does this refer to tracks having the cue as part of their tags?
I am asking this because I tried playing such a track but xmplay  didn't recognize the cue.

Yep, it'll check APEv2 tags (and FLAC via the plugin) for a "Cuesheet" tag, as used by Wavpack (and FLAC) and maybe others. What format is your file? Please upload it to have a look at...

   ftp.un4seen.com/incoming/


I have just finished uploading the file :"Covenant - United States of Mind" . I hope it helps.

PVTele

As urwolf says, the library is not quite crashproof. If I enable directory monitoring for my +/- 3,000 track My Music directory, it will crash. Add chunks manually, little by little, and it's fine. Annoying, because directory monitoring is a very useful tool, especially for someone as forgetful as me ;-)

Zarggg

Cris.. that is exactly the reason I stopped using Rappa three years ago. It consistently crashes XMPlay.

Also, Ian... Any chance of slowing down the Spectrum (3D) to 3.3-and-earlier levels? ;D

Pike84

Going fullscreen with Rabbithole still closes XMPlay here ::).

Maserati

going to options>plugins crashes when loading 64th Note v1.2 beta 3. 
This does not happen with beta 1 of that plugin.
http://www.hcs64.com/usf/

Airon16

I'm mixing a couple of tracks here from artists I cherish (like Purple Motion or old tracking buddy Mick Rippon) and came upon something strange.

The sensitive ramping does not seem to be on when I'm using the WAV writer and seperating by instrument. I get a load of clicks that are not heard in the WAV writer output when I'm simply outputting the whole tune.

The tracks I tested this on are the S3M "Star Shine" by Purple Motion, Tamas Kingdom.mod and Mr House by Mick Rippon.

Notably most of these clicks occur when the instrument ends, not begins. Perhaps sensitive ramping needs to be active for the samples at the end if used in the WAV writers "Seperate Instrument" mode.

Knurek

XMPlay doesn't report MilkyTracker made XMs as such (even though they have MilkyTracker in the tracker field).

Rich Nagel

The new version of XMPlay is EXCELLLENT, thanks for all your hard work, Ian! -:)

One small (well, maybe not small <G>) buglet with the new version of the MIDI plugin: when clicking on the "Add" button (or clicking on any of the existing patches to replace them), the open SoundFont dialog box doesn't appear at all (?).

I doubt that the folowing is a bug (but rather my slloooooowww PCs <G>), but enabling the MIDI plugin's reverb and chorus options makes the MIDI files (that have those controllers embedded in them) almost unplayable. Sound is extremely choppy, even with XMPlay's main reverb disabled.

XMPlay's main reverb doesn't do this... sound is fine when using it (verses the MIDI plugin's reverb and chorus effects). BTW, thanks for the big increase in the regular XMPlay reverb... I can really get that "deep hall" effect now <G> -:)

deus-ex

Quote from: KnurekXMPlay doesn't report MilkyTracker made XMs as such (even though they have MilkyTracker in the tracker field).
Because Peter didn't pay the support fee. ;D

raina

Quote from: KnurekXMPlay doesn't report MilkyTracker made XMs as such (even though they have MilkyTracker in the tracker field).

This is what I was after here: :)

Quote from: raina
Quote from: XMPlay Version History* 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.

Knurek

How about an option for auto-switching the VIS to patternviewer when applicable, and back to another selected VIS for other formats...
It's seriously not fun now, having to switch between them, and with certain new version of certain plugin by certain person for certain module format that's gonna be released certainly soon it won't get better I tells ya.

deus-ex

Quote from: KnurekHow about an option for auto-switching the VIS to patternviewer when applicable, and back to another selected VIS for other formats...
It's seriously not fun now, having to switch between them, and with certain new version of certain plugin by certain person for certain module format that's gonna be released certainly soon it won't get better I tells ya.

I'd support that, certainly. :)