Author Topic: Thanks for XMPlay 3.8.3!  (Read 1018 times)

sveakul

  • Posts: 40
Thanks for XMPlay 3.8.3!
« on: 23 Dec '17 - 03:59 »
Working fine here (not that THAT was a surprise!).  I removed the bass_aac and bass_alac plugins from 3.8.2.x and the new Media Foundation defaults seem to be good (Windows 7 here).  Just a couple of questions:

1.  Will there be a new xmp-wasapi plugin coming with the improvements contained in the recent basswasapi 2.4.2?

2.  When downloading an Opus radio stream, the track title only has the file name, like "192.opus" for the example http://199.189.87.9:10999/192.opus, even if the station is sending track title metadata for artist and title that show in the Message window.  Can this be changed so the behaviour corresponds to MP3 and AAC steams where the metadata is used in the download name and "write separate tracks" can be selected?

Thank you for your work!

caveman

  • Posts: 11
Re: Thanks for XMPlay 3.8.3!
« Reply #1 on: 23 Dec '17 - 12:46 »
Thanks for the great update Ian...you the man  :D

Ian @ un4seen

  • Administrator
  • Posts: 20845
Re: Thanks for XMPlay 3.8.3!
« Reply #2 on: 23 Dec '17 - 13:57 »
Working fine here (not that THAT was a surprise!).  I removed the bass_aac and bass_alac plugins from 3.8.2.x and the new Media Foundation defaults seem to be good (Windows 7 here).  Just a couple of questions:

The new "built-in" ALAC support requires Windows 10, so you should keep the ALAC plugin, but you can remove the AAC plugin on Windows 7. An updated ALAC plugin will be released soon to add support for the new HTTP seeking feature.

1.  Will there be a new xmp-wasapi plugin coming with the improvements contained in the recent basswasapi 2.4.2?

Yes, it won't make a massive difference, but there will probably be an updated WASAPI plugin release for the more precise latency/position reporting.

2.  When downloading an Opus radio stream, the track title only has the file name, like "192.opus" for the example http://199.189.87.9:10999/192.opus, even if the station is sending track title metadata for artist and title that show in the Message window.  Can this be changed so the behaviour corresponds to MP3 and AAC steams where the metadata is used in the download name and "write separate tracks" can be selected?

Unfortunately, the "write separate tracks" option isn't currently supported with plugins except for with Shoutcast metadata (eg. in the AAC case). Opus streams use the Ogg container format (same as Ogg Vorbis), and XMPlay does support separating Ogg Vorbis streams, so it might be possible to extend that to cover Opus streams without needing special support in the Opus plugin itself. I'll put that on the "look into it" list :)

sveakul

  • Posts: 40
Re: Thanks for XMPlay 3.8.3!
« Reply #3 on: 23 Dec '17 - 19:03 »
Thanks Ian for the info!  Whoops, returned the xmp-alac plugin, hadn't gotten to a non-"regular AAC" .m4a file yet.  Thanks for taking a look at the artist/title metadata for Opus stream downloads.  Have a good weekend!

piovrauz

  • Posts: 969
Re: Thanks for XMPlay 3.8.3!
« Reply #4 on: 25 Dec '17 - 15:55 »
Thanks for the updated XMPlay! Let's "install" it then... ;)

sveakul

  • Posts: 40
Re: Thanks for XMPlay 3.8.3!
« Reply #5 on: 30 May '18 - 03:37 »
1.  Will there be a new xmp-wasapi plugin coming with the improvements contained in the recent basswasapi 2.4.2?

Yes, it won't make a massive difference, but there will probably be an updated WASAPI plugin release for the more precise latency/position reporting.

2.  When downloading an Opus radio stream, the track title only has the file name, like "192.opus" for the example http://199.189.87.9:10999/192.opus, even if the station is sending track title metadata for artist and title that show in the Message window.  Can this be changed so the behaviour corresponds to MP3 and AAC steams where the metadata is used in the download name and "write separate tracks" can be selected?

Unfortunately, the "write separate tracks" option isn't currently supported with plugins except for with Shoutcast metadata (eg. in the AAC case). Opus streams use the Ogg container format (same as Ogg Vorbis), and XMPlay does support separating Ogg Vorbis streams, so it might be possible to extend that to cover Opus streams without needing special support in the Opus plugin itself. I'll put that on the "look into it" list :)

Hi Ian, was just wondering if you're closer to doing the updates mentioned above for xmp-wasapi.dll and the addition of track-specific Opus radio stream recording.  Thanks for your consideration.

Ian @ un4seen

  • Administrator
  • Posts: 20845
Re: Thanks for XMPlay 3.8.3!
« Reply #6 on: 31 May '18 - 15:17 »
Not yet, but I'll look into the WASAPI plugin update soon.

sveakul

  • Posts: 40
Re: Thanks for XMPlay 3.8.3!
« Reply #7 on: 1 Jun '18 - 03:18 »
Great, thanks Ian!

spacedrone808

  • Posts: 8
Re: Thanks for XMPlay 3.8.3!
« Reply #8 on: 1 Jun '18 - 09:42 »
I'd lite to thanks HUGE THANKS too!! Keep it up, this wonderful module player. Stay oldschool!