Author Topic: 3.4 reports, queries and bugs  (Read 358180 times)

Dotpitch

  • Posts: 2871
Re: 3.4 reports, queries and bugs
« Reply #200 on: 30 May '07 - 14:55 »
Removing that section indeed works. Looks like settings from xmp-scrobbler get misinterpreted as equalizer settings, because it re-appears after xmp-scrobbler (without any settings) is added and XMPlay is restarted. I haven't seen it before, but I hardly ever use the DSP-tab (haven't changed anything for weeks ;)), so it could have been there for some time. Uploaded the ini.

marcdesbiens

  • Posts: 8
Re: 3.4 reports, queries and bugs
« Reply #201 on: 30 May '07 - 15:32 »
Ok, it's almost funny cos' I was just minutes away from sending a message sayin' "Everything's alright !!!" and then it happened again, XMPlay shutting down by itself
(V. 3.4.1.9)  It happened after 2-3 hours of use, almost the same as with version 3.4.1.0.

I'll try a couple of different things though, 1st I switch back to the original skin, not sure if that could be the cause of the problem but I was using a different skin lately (Blue Tek,
when I switched versions the other day) 

Also I think you were suggestion possibly getting rid of the xmplay.ini file and starting completely fresh there ?  I was still using my personalized xmplay.ini file, I'll try that tarting with a brand new one later too. In the meantime, here's my xmplay.ini file below, if it can help you in some way :


[XMPlay]
FolderHistory=433A5C446F63756D656E747320616E642053657474696E67735C416E6472655C4275726561755C0000
CurTrack=1460
Track1=1457
External=4C414D45006C616D65202D2D616C742D707265736574207374616E64617264206C616D65202D2D616C742D707265736574207374616E64617264202D2D7474202531202D2D7461202532202D2D746C202533202D2D7479202534202D2D746E202535202D2D7467202536202D2D7463202537202D20256F006D703300064F4747454E43006F6767656E63202D74202531202D61202532202D6C202533202D64202534202D4E202535202D47202536202D63202537202D6F20256F202D006F6767000800
DSP=FF0002000C000000000055555541488334410001002800000000000000A040000040400000803F00000000000080BF0000C0BF000000C0000000BF0000803F
Shortcuts=50000080260348028000008027034D028100008025034B025100008028035002580000802D0352026001008058012D02090000800C034C0201020080220351020002008021034902
DeviceMode=0000000080BB000002000000020000008403000000000000
MixMode=48
AutoName=1
WriteSource=0
WriteSepInst=0
AutoAmp=0
RGain=0
Time=2
ShowTenths=1
Volume=49
Balance=50
Amplify=1091305472
AmpReset=0
PanSep=50
Loop=64
DecayEnd=5
LoopList=1
ListTotal=0
UnloadLast=0
AutoAdvance=1
FollowList=1
Trim=0
NoMute=0
Fade=0
NetBuffer=6
RestrictRate=0
AutoReconnect=0
Proxy=1
ProxyConfig=
Dither=0
MODmode=0
MODtimeinfo=1
MODxfx=1
MODloop=1
Mini=1
InTray=1
OnTop=259
MultiInstance=0
SaveClosePos=0
FadeBubbles=1
VisBubbles=1
InfoMove=1
WindowX=1314
WindowY=766
PanelPos=12189869
ListFilenames=0
ListQueue=0
Verify=1
NoDuplicates=1
ScanHTML=0
ArchiveLevel=1
SearchDrives=0
Random=0
DeadStop=0
Queue=1
QueueStop=0
QueuePlay=1
SubDir=0
TitleNoExt=0
TitleWA=1
TitleCUE=1
TitleScroll=1
TitleTray=1
Clipboard=0
AutoSet=0
InfoResize=0
InfoTextSize=2
InfoWidth=0
InfoList=43
InfoPaty=234
InfoPatmc=20
RestrictVis=0
RestrictVisW=290
RestrictVisH=218
SpectrumSpeed=1
VisSync=0
VisTextSize=3
HelpTextSize=3
PanelOpen=1
Info=1024
InfoPos=160200003C0000008F040000D4020000
VisSize=22010000DA000000
FindSize=7F010000DF000000C8000000F4010000
LibWidth=595
LibSort=2
LibMode=2
LibCols=0000000000000000010000006571264202000000E855164203000000000000000400000000000000050000000000000006000000000000000700000000000000080000000000000009000000000000000A000000E5CF2B410B000000E71221410C000000000000000D00000000000000
LibParseList=1
LibFilePath=0
LibAbrSize=1
LibInlineText=1
LibInfoTags=1
LibKeepOverridden=1
IgnoreTypes=avi mpg mpeg
FilePath=C:\Documents and Settings\Andre\Bureau\
WritePath=F:\Marc\AVG_Marc_Downloads\MP3_Vérifications\
TitleForm=%?2{%2 - }%?1{%1|%0}
Find=take it
FindPlay=0
FindIn=3
NetTimeout=10
UpdateCheck=0
UpdateTime=0




Cheers !
Marc :-)

Cornet

  • Guest
Re: 3.4 reports, queries and bugs
« Reply #202 on: 31 May '07 - 12:18 »
Ian, did you find the samples I sent to your FTP folder?
There was no reply when I first asked you...

Ian @ un4seen

  • Administrator
  • Posts: 20401
Re: 3.4 reports, queries and bugs
« Reply #203 on: 31 May '07 - 15:47 »
Looks like settings from xmp-scrobbler get misinterpreted as equalizer settings, because it re-appears after xmp-scrobbler (without any settings) is added and XMPlay is restarted.

I wasn't able to reproduce it by just adding xmp-scrobbler to the DSP list, so I guess there must be a bit more to it. Can you reproduce it everytime? If so, I'll send you a debug version to find out what's happening.

Ok, it's almost funny cos' I was just minutes away from sending a message sayin' "Everything's alright !!!" and then it happened again, XMPlay shutting down by itself
(V. 3.4.1.9)  It happened after 2-3 hours of use, almost the same as with version 3.4.1.0.

Did it generate a drwtsn32.log entry? If so, please upload that to have a look at here...

   ftp.un4seen.com/incoming/

Also, is that 2-3 hours of gapless playback, or does it not matter whether it's playing at all? If it only happens when playing, is there a particular file or format that it happens with, and do you have any DSP active?

Ian, did you find the samples I sent to your FTP folder?
There was no reply when I first asked you...

Yep, I've got them. It was a bit puzzling at first, as your recordings didn't sound the same as playback here. Then I tried playing with the MOD options, and managed to reproduce the recording with the "Surround" option set to "mode 2". Note the Surround option will mean extra reverberations, and could produce some funky results. Have you tried disabling the Surround option?

Meanwhile, I have made a little tweak to the reverb, to reduce reverberation of the bass. It probably won't affect your issue, but it'll reduce/prevent bass drum rumbling...

   www.un4seen.com/stuff/xmplay.exe

Dotpitch

  • Posts: 2871
Re: 3.4 reports, queries and bugs
« Reply #204 on: 31 May '07 - 17:43 »
Looks like settings from xmp-scrobbler get misinterpreted as equalizer settings, because it re-appears after xmp-scrobbler (without any settings) is added and XMPlay is restarted.
I wasn't able to reproduce it by just adding xmp-scrobbler to the DSP list, so I guess there must be a bit more to it. Can you reproduce it everytime? If so, I'll send you a debug version to find out what's happening.
100% with 3.4.1.9. Apparently, it needs both xmp-scrobbler and xmp-msn, it won't happen if you only use one of them. I've attached the DSP= entry of various combinations, if you need more you can send me a debug version :).

Rich Nagel

  • Posts: 297
Re: 3.4 reports, queries and bugs
« Reply #205 on: 1 Jun '07 - 00:16 »
You can use Wintop on Win98, available here...

http://www.microsoft.com/windows95/downloads/contents/WUToys/W95KernelToy/Default.asp


Sorry for the extremely late reply, just got around to running WinTop. I only tried it on my 500 (but I have a hunch the results would be similar on my 233 - i.e. the percentage of difference). The numbers jump around quite a bit in WinTop, but here is an approximate average of what they were.

Playing a MIDI file with the equalizer, regular reverb, and the MIDI plugin's reverb and chorus effects all disabled resulted in 20% CPU usage.

Enabling the regular reverb, the CPU usage was 30% (still acceptable, though).

Disabling the regular reverb (and leaving theh EQ disabled as well), and then enabling only the MIDI plugin's reverb and chorus, the CPU usage jumped to 85%-90% (really slows down my PC when trying to do anything else). The sound wasn't choppy like it was with the slightly older version of XMPlay with the MIDI plugin (like I mentioned previously), but there was a dramatic performance hit nontheless with the newer one(s).

Ian @ un4seen

  • Administrator
  • Posts: 20401
Re: 3.4 reports, queries and bugs
« Reply #206 on: 1 Jun '07 - 13:53 »
100% with 3.4.1.9. Apparently, it needs both xmp-scrobbler and xmp-msn, it won't happen if you only use one of them.

I still wasn't able to reproduce the problem here, but I did spot a little bug that could be the cause of it, with the wind in the right direction/etc :)

Here's an update to try...

   www.un4seen.com/stuff/xmplay.exe

Dotpitch

  • Posts: 2871
Re: 3.4 reports, queries and bugs
« Reply #207 on: 1 Jun '07 - 15:16 »
...but I did spot a little bug that could be the cause of it, with the wind in the right direction/etc :)
;D It's fixed.

Cornet

  • Guest
Re: 3.4 reports, queries and bugs
« Reply #208 on: 5 Jun '07 - 16:21 »
Yep, I've got them. It was a bit puzzling at first, as your recordings didn't sound the same as playback here. Then I tried playing with the MOD options, and managed to reproduce the recording with the "Surround" option set to "mode 2". Note the Surround option will mean extra reverberations, and could produce some funky results. Have you tried disabling the Surround option?

Meanwhile, I have made a little tweak to the reverb, to reduce reverberation of the bass. It probably won't affect your issue, but it'll reduce/prevent bass drum rumbling...
Disabling surround sound mode 2 removed the wierd bug. But using surround mode 1 moves the weird effect to a lower frequency. When surround sound is switched off, the effect dissappears.
The bass effect seems to get very overwhelming with your tweak.

marcdesbiens

  • Posts: 8
Re: 3.4 reports, queries and bugs
« Reply #209 on: 5 Jun '07 - 22:36 »
Sorry, I was away temporarely ... regarding the shutdown problem I was having the other day, I tested XMPlay more ...  recently and it hasn't occured again, so I am pleased.  Not sure if it was due to the skin I was using, but I switched to the original one since then and so far so good, no issues @ the moment.  Cheers, mate. 
Marc ;-)

Auren

  • Posts: 144
Re: 3.4 reports, queries and bugs
« Reply #210 on: 25 Oct '07 - 20:49 »
There's a small interface bug. The problem is in the parsing of "\n" symbols in tags.
« Last Edit: 15 Feb '10 - 05:34 by Auren »

Ian @ un4seen

  • Administrator
  • Posts: 20401
Re: 3.4 reports, queries and bugs
« Reply #211 on: 26 Oct '07 - 15:07 »
I tried to reproduce that (by adding a multi-line ID3v2 comment tag to an MP3), but couldn't, so please upload an example file that it happens with...

   ftp.un4seen.com/incoming/

Auren

  • Posts: 144
Re: 3.4 reports, queries and bugs
« Reply #212 on: 26 Oct '07 - 17:16 »
No problem. I've uploaded the file.
It's called David Guetta - Baby When The Light (Dirty South Remix).mp3

Tsorovan

  • Posts: 1247
Re: 3.4 reports, queries and bugs
« Reply #213 on: 26 Oct '07 - 17:45 »
The MP3 was probably created on a *nix platform, hence no \r

Ian @ un4seen

  • Administrator
  • Posts: 20401
Re: 3.4 reports, queries and bugs
« Reply #214 on: 29 Oct '07 - 17:15 »
Yep, that does seem to be it. Windows multi-line controls require "\r\n", so the "\n" will have to be expanded by XMPlay first, which is a nuisance :P

I'll do that for the next update.

Auren

  • Posts: 144
Re: 3.4 reports, queries and bugs
« Reply #215 on: 8 Nov '07 - 10:42 »
There's one more problem.

When I set the volume to "0" and raise it up, sound doesn't come immediately. There's a delay that equals the buffer length (for example, if I set the buffer length to 3 seconds there will be no sound during 3 seconds when I raise up the volume from "0" value).
This doesn't happen when I use DirectSound for output.

raina

  • Posts: 1163
Re: 3.4 reports, queries and bugs
« Reply #216 on: 8 Nov '07 - 11:48 »
@Auren, that's why DirectSound was introduced to XMPlay in the first place. Just use the DS plugin if that bugs you.

Ian @ un4seen

  • Administrator
  • Posts: 20401
Re: 3.4 reports, queries and bugs
« Reply #217 on: 8 Nov '07 - 15:21 »
When using the default (waveOut) or ASIO output, XMPlay applies the volume to the sample data. When the volume is increased, the buffered data is amplified, but if the buffer contains silence (eg. the volume was 0), it's still gonna be silence :)

Auren

  • Posts: 144
Re: 3.4 reports, queries and bugs
« Reply #218 on: 8 Nov '07 - 16:27 »
Oh, I see now. Thanks for the explanation.

kragg

  • Posts: 45
Re: 3.4 reports, queries and bugs
« Reply #219 on: 19 Jan '08 - 11:45 »
Hi
Some little annoyances to report :

- sometimes (not all the time, but around 1 out of 3 ???), when I drag the playhead and drag it forward (to go ahead on the song), the sound gets muted. I can see the vumeters display sound, but i hear nothing anymore. To get sound again, i have to go a bit backward, and then it works again. Isis a known bug ?

- Is there any way to give more priority to playback over updating library ? I have quite a lot of mp3 on my HD, and when i click on a file (if XmPLay isn't already opened), I'd expect the playback starts right now since the application is started. But this is not the case : it takes at least around 10-15 seconds before playing a simple file ! First i didn't understand why sometimes the playback was immediate, and why sometimes it could take so long, then i understood that there had such "hang" when i had added some mp3 i my "music" folder, and i suppose XmPlay takes all this time to update the library (that's it, isn't it ?).  It is quite annoying since this "refresh lag" makes XMplay very slow as a simple player...

CHeers

saga

  • Posts: 2180
Re: 3.4 reports, queries and bugs
« Reply #220 on: 19 Jan '08 - 11:52 »
concerning your second issue, i can only confirm this for heavy cpu load and it also happened all the time when i didn't have the library activated. please check your system load in the taskman, maybe an evil program is stealing your resources ;D

<Unknown>

  • Guest
Re: 3.4 reports, queries and bugs
« Reply #221 on: 20 Jan '08 - 17:03 »
Can XMPlay play Videos??? ??? ???  ?
:o :o :o :o :o


Dotpitch

  • Posts: 2871
Re: 3.4 reports, queries and bugs
« Reply #222 on: 20 Jan '08 - 17:03 »

tniemi

  • Posts: 42
Re: 3.4 reports, queries and bugs
« Reply #223 on: 20 Jan '08 - 23:26 »
Yep, that does seem to be it. Windows multi-line controls require "\r\n", so the "\n" will have to be expanded by XMPlay first, which is a nuisance :P

I'll do that for the next update.

Please also note that old Apple OS used "\r" for newline:
http://en.wikipedia.org/wiki/Newline#Representations
You may want to fix that too. I know few people that are unable (and unwilling) to upgrade to OS X.

Zarggg

  • Posts: 1242
Re: 3.4 reports, queries and bugs
« Reply #224 on: 21 Jan '08 - 17:25 »
Please also note that old Apple OS used "\r" for newline:
http://en.wikipedia.org/wiki/Newline#Representations
Actually, I think you have that backwards. In fact, the article itself states that Unix uses LF and MacOS-pre9.0 uses CR. (which are not \n or \r, but that's a different discussion entirely :P)