Author Topic: Suggestions for 3.9  (Read 176875 times)

Ian @ un4seen

  • Administrator
  • Posts: 23470
Re: Suggestions for 3.9
« Reply #425 on: 2 Dec '20 - 16:38 »
I started to look into that, but then it occurred to me that it may not be the quickest way to do what you want. If you enable monitoring of the folder(s) in XMPlay then it should automatically add the new FLAC files and remove the missing old ones. Even without monitoring, it may be quicker/simpler to manually remove the dead old entries and add the new FLAC files (eg. drag'n'drop the containing folder), rather than using a looser dead track recovery option. Such a new option would probably require some checking of the search results before applying them to make sure it didn't find something unexpected with the looser matching.

saga

  • Posts: 2483
Re: Suggestions for 3.9
« Reply #426 on: 2 Dec '20 - 16:49 »
Quote
Even without monitoring, it may be quicker/simpler to manually remove the dead old entries and add the new FLAC files (eg. drag'n'drop the containing folder), rather than using a looser dead track recovery option.
I try to avoid that as it will lose play counts and custom tags.

Marto

  • Guest
Re: Suggestions for 3.9
« Reply #427 on: 6 Dec '20 - 20:33 »
Linux Version would be GREAT!!!
Nowdays, almost all you want to do, can be achieved within a linux distribution.
With AppImage implementation, most of the software out there could be used in any Linux distro, without package requirements.
Since almost two years ago, I switched to Linux totally. but I dont have XMPlay!!!! Most light, fast, adn configurable software out there.

Maybe I'm just dreamer, but a Linux version (AppImage, snap,, flatpak... you choose) would be awsome

Ian @ un4seen

  • Administrator
  • Posts: 23470
Re: Suggestions for 3.9
« Reply #428 on: 7 Dec '20 - 16:12 »
Quote
Even without monitoring, it may be quicker/simpler to manually remove the dead old entries and add the new FLAC files (eg. drag'n'drop the containing folder), rather than using a looser dead track recovery option.
I try to avoid that as it will lose play counts and custom tags.

Are you doing the FLAC conversion with XMPlay? If not, you could try that, as it will use the source's overridden tags when writing the FLAC file, so you won't need to be concerned about losing those tags when replacing the old track :)

Linux Version would be GREAT!!!
Nowdays, almost all you want to do, can be achieved within a linux distribution.
With AppImage implementation, most of the software out there could be used in any Linux distro, without package requirements.
Since almost two years ago, I switched to Linux totally. but I dont have XMPlay!!!! Most light, fast, adn configurable software out there.

Maybe I'm just dreamer, but a Linux version (AppImage, snap,, flatpak... you choose) would be awsome

While not as nice as having a native Linux version, XMPlay does work on Linux with Wine. When I last tried it there were some visual glitches with the z-order of the panels but that was many years ago, so things may have improved since then, or perhaps you could use a skin that doesn't have sliding/overlapping panels.

saga

  • Posts: 2483
Re: Suggestions for 3.9
« Reply #429 on: 7 Dec '20 - 16:15 »
Are you doing the FLAC conversion with XMPlay? If not, you could try that, as it will use the source's overridden tags when writing the FLAC file, so you won't need to be concerned about losing those tags when replacing the old track :)

To be clear, I'm replacing some OGG and MP3 files with FLAC replacements; so converting them with XMPlay wouldn't make much sense. :)


While not as nice as having a native Linux version, XMPlay does work on Linux with Wine. When I last tried it there were some visual glitches with the z-order of the panels but that was many years ago, so things may have improved since then, or perhaps you could use a skin that doesn't have sliding/overlapping panels.
Unfortunately I can confirm that those issues still exist. In particular some invisible panels (e.g. the EQ panel) become visible just by clicking on the main window, which makes some skins difficult to use.

Ian @ un4seen

  • Administrator
  • Posts: 23470
Re: Suggestions for 3.9
« Reply #430 on: 8 Dec '20 - 18:05 »
Are you doing the FLAC conversion with XMPlay? If not, you could try that, as it will use the source's overridden tags when writing the FLAC file, so you won't need to be concerned about losing those tags when replacing the old track :)

To be clear, I'm replacing some OGG and MP3 files with FLAC replacements; so converting them with XMPlay wouldn't make much sense. :)

Oh, were the OGG/MP3 files generated from MOD files and you now want FLAC versions, but the custom/overridden tags are set on the OGG/MP3 files rather than the original MOD files?

saga

  • Posts: 2483
Re: Suggestions for 3.9
« Reply #431 on: 8 Dec '20 - 19:01 »
No, MOD files aren't involved this time... :) They are downloads from Bandcamp. Sometimes I use custom tags for them to not edit the original files.

saga

  • Posts: 2483
Re: Suggestions for 3.9
« Reply #432 on: 6 Jan '21 - 17:00 »
Would it be possible to set the BIF_EDITBOX style on the BROWSEINFO struct passed to SHBrowseForFolder? This would allow the user to manually enter (or copy&paste) a path in the folder browser dialogs, making them a lot more useful.

Ian @ un4seen

  • Administrator
  • Posts: 23470
Re: Suggestions for 3.9
« Reply #433 on: 7 Jan '21 - 17:28 »
Yep, here's an update with that flag set:

   www.un4seen.com/stuff/xmplay.exe

It seems to behave a bit strangely, in that only the final subdirectory is initially shown in the box but you need to enter a full path for it to work. I don't know if that's normal?

saga

  • Posts: 2483
Re: Suggestions for 3.9
« Reply #434 on: 7 Jan '21 - 18:44 »
Thanks for the quick update! Indeed it behaves as intended - the dialog itself will not put a full absolute path there but it is still possible by the user to supply one. So for example if you are browsing your music library with Explorer, you can quickly copy the current path and paste it in the dialog to add that folder.