Author Topic: 3.7 reports, queries and bugs  (Read 71990 times)

Dotpitch

  • Posts: 2871
3.7 reports, queries and bugs
« on: 22 Dec '12 - 10:25 »
3.7 is here, just before Christmas :). Thanks Ian! Please gather all questions and problems in this thread.

Btw:
  • 3.0: February 24th, 2004
  • 3.1: August 1st, 2004
  • 3.2: February 13th, 2005
  • 3.3: December 22nd, 2005
  • 3.4: April 3rd, 2007
  • 3.5: December 22nd, 2009
  • 3.6: December 22nd, 2010
  • 3.7: December 21nd, 2012

[edit]Corrected release date for 3.7.[/edit]
« Last Edit: 22 Dec '12 - 17:23 by Dotpitch »

saga

  • Posts: 2179
Re: 3.7 reports, queries and bugs
« Reply #1 on: 22 Dec '12 - 12:17 »
That was supposed to be December 22nd, 2011! Damn! Anyway, great job, Ian. ;)

tongub

  • Posts: 91
Re: 3.7 reports, queries and bugs
« Reply #2 on: 22 Dec '12 - 12:35 »
With Shuffle on

-At the end of the track it will play random track on the playlist
-But if you hit next it will play the exact next song on the playlist

saga

  • Posts: 2179
Re: 3.7 reports, queries and bugs
« Reply #3 on: 22 Dec '12 - 12:52 »
That is intended. Be sure that both checkboxes are checked in the "Playlist" config page:
[x] Random order ... apply to play/next/previous controls [x]

Y@nekŪ

  • Posts: 273
Re: 3.7 reports, queries and bugs
« Reply #4 on: 22 Dec '12 - 21:29 »
Testing, testing...  ;)

tongub

  • Posts: 91
Re: 3.7 reports, queries and bugs
« Reply #5 on: 23 Dec '12 - 01:09 »
That is intended. Be sure that both checkboxes are checked in the "Playlist" config page:
[x] Random order ... apply to play/next/previous controls [x]

Oh yeah, didn't realize that I had this option checked in 3.6. Thanks.

Jace

  • Posts: 825
Re: 3.7 reports, queries and bugs
« Reply #6 on: 23 Dec '12 - 11:17 »
Sort of bug, but not in the player itself. The website menu on left seems to say 3.6 still. :P
(Or is it just me?)

Edit: Sorted now, it seems!
« Last Edit: 23 Dec '12 - 15:39 by Jace »

Bob_McCarty

  • Guest
Re: 3.7 reports, queries and bugs
« Reply #7 on: 23 Dec '12 - 15:00 »
Six antivirus scanner on VirusTotal are detecting 3.7 as an infected file.

Ian @ un4seen

  • Administrator
  • Posts: 20400
Re: 3.7 reports, queries and bugs
« Reply #8 on: 23 Dec '12 - 15:46 »
Sort of bug, but not in the player itself. The website menu on left seems to say 3.6 still. :P

Oops, that's updated now.

Six antivirus scanner on VirusTotal are detecting 3.7 as an infected file.

I guess that will be corrected shortly, in updates of those scanner databases.

Anyway, have a good Christmas, people! See you all again next December, or perhaps the one after :D

Alt

  • Posts: 69
Re: 3.7 reports, queries and bugs
« Reply #9 on: 23 Dec '12 - 17:16 »
Merry Christmas to you too, Ian & thank you for your's great support!

Version 3.7 seems fine, the only thing I don't understand why xmplay's process runs with 'normal' priority instead of 'real-time' as before. Using "Boost" for 'high' priority atm.

Dotpitch

  • Posts: 2871
Re: 3.7 reports, queries and bugs
« Reply #10 on: 23 Dec '12 - 22:05 »
Version 3.7 seems fine, the only thing I don't understand why xmplay's process runs with 'normal' priority instead of 'real-time' as before. Using "Boost" for 'high' priority atm.
Only the audio processing thread runs at real-time priority, all the rest is at normal priority. What do you need the higher priority for?

garson

  • Posts: 138
Re: 3.7 reports, queries and bugs
« Reply #11 on: 23 Dec '12 - 23:20 »
I was hoping for expanding cue sheets to virtual tracks, as big new feature (one that I mostly miss). :(

ll

  • Posts: 1
Re: 3.7 reports, queries and bugs
« Reply #12 on: 24 Dec '12 - 02:49 »
My library will scroll responsively in 3.6.  After upgrading to 3.7, updating the library list while scrolling takes ~ 1.5 sec.
  • ~ 60 songs in my library window displayed at a time
  • Win 7 x64
  • ~ 4k total library items
For now I'm back to 3.6, no issues scrolling.  The library window updates almost instantly when scrolling.
Thanks for the great software!

Deb

  • Guest
Re: 3.7 reports, queries and bugs
« Reply #13 on: 25 Dec '12 - 06:26 »
Merry Christmas! And thank you for this marvelous present!

I was wondering if one of my pet peeves, that is, the inability to remove dead links from the url drop-down menu in a straightforward manner (without having to edit the xmplay.ini file) has been addressed.

Thank you.

Dotpitch

  • Posts: 2871
Re: 3.7 reports, queries and bugs
« Reply #14 on: 25 Dec '12 - 10:36 »
I was wondering if one of my pet peeves, that is, the inability to remove dead links from the url drop-down menu in a straightforward manner (without having to edit the xmplay.ini file) has been addressed.
No, it is not. If it had, you would've read it in the changelog (xmplay.txt or Support Site).

tongub

  • Posts: 91
Re: 3.7 reports, queries and bugs
« Reply #15 on: 26 Dec '12 - 19:15 »
Edit: Ignore me, another silly mistake of my part.

Chinese Sausage

  • Posts: 424
Re: 3.7 reports, queries and bugs
« Reply #16 on: 27 Dec '12 - 05:55 »
Merry Christmas! And thank you for this marvelous present!

+1  :D

Thank you very much Ian!

saga

  • Posts: 2179
Re: 3.7 reports, queries and bugs
« Reply #17 on: 15 Jan '13 - 17:36 »
While auto-amp is active and the amp display is updated in the settings dialog, it seems like the amp type drop-down list is also updated everytime. This makes it particularly hard to change the auto-amp type while a song is playing.

Ian @ un4seen

  • Administrator
  • Posts: 20400
Re: 3.7 reports, queries and bugs
« Reply #18 on: 15 Jan '13 - 18:04 »
Yep, I've noticed that too. Here's an update that should sort it...

   www.un4seen.com/stuff/xmplay.exe

saga

  • Posts: 2179
Re: 3.7 reports, queries and bugs
« Reply #19 on: 16 Jan '13 - 21:09 »
I'm not sure if something broke here recently, but this used to work better, IIRC. I'm playing an OGG file in XMPlay and change the Vorbis tags using MP3Tag at the same time. The changes are definitely written to the file as a peek in the hex editor confirms. However, no matter how often I choose "Refresh info from file" in XMPlay, the new tags aren't updated, neither in the info panel nor in the track info. Using "Refresh info from file" after the track has finished playing works as expected.

Dotpitch

  • Posts: 2871
Re: 3.7 reports, queries and bugs
« Reply #20 on: 17 Jan '13 - 06:19 »
Are you using the ReadAhead setting?

saga

  • Posts: 2179
Re: 3.7 reports, queries and bugs
« Reply #21 on: 17 Jan '13 - 11:52 »
Nope. And I don't see how/why it should affect the re-scanning of tags.

Ian @ un4seen

  • Administrator
  • Posts: 20400
Re: 3.7 reports, queries and bugs
« Reply #22 on: 17 Jan '13 - 15:34 »
I'm not sure if something broke here recently, but this used to work better, IIRC. I'm playing an OGG file in XMPlay and change the Vorbis tags using MP3Tag at the same time. The changes are definitely written to the file as a peek in the hex editor confirms. However, no matter how often I choose "Refresh info from file" in XMPlay, the new tags aren't updated, neither in the info panel nor in the track info. Using "Refresh info from file" after the track has finished playing works as expected.

I tried updating an OGG file's tags while it was being played by XMPlay just now, and the tag editor was unable to write the tags to the file because XMPlay had it open. I was using the Winamp in_vorbis plugin rather than MP3Tag, but I would expect it to be the same with that. Are you sure the file is being updated successfully during playback in your case, eg. if you open it in a 2nd XMPlay instance (while the 1st is still playing it) you see the updated tags?

saga

  • Posts: 2179
Re: 3.7 reports, queries and bugs
« Reply #23 on: 17 Jan '13 - 17:05 »
I see it in a hex editor while XMPlay is still playing the file. Isn't that enough of a proof? :)

Ian @ un4seen

  • Administrator
  • Posts: 20400
Re: 3.7 reports, queries and bugs
« Reply #24 on: 17 Jan '13 - 17:40 »
I'm just puzzled how the file managed to get updated while XMPlay was playing it. I gave MP3Tag a try just now, and it also was unable to update a file's tags while XMPlay was playing it, so I'm still puzzled :) ... Are you definitely updating the tags of the same file (in the same path) that XMPlay is playing? If so, is XMPlay playing the file itself, not a plugin?