Latest WACUP public preview for x86 & x64 is build #24784 (August 3rd 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24784 (August 3rd 2026) (x86 & x64 changelogs)

Author Topic: Play Tracking Preference Not Saving  (Read 86 times)

umihimeyokai

  • Newbie
  • *
  • Posts: 4
    • View Profile
Play Tracking Preference Not Saving
« on: Today at 12:35:46 AM »
In v1.99.52.24626

Under preferences>Playback>Play Tracking

The Now Playing Tab

The Last field where it says "The following field can be used to specify output when playback stops. If left empty nothing will be output when playback stops. If left empty nothing will be output when playback stops."

Two minor bugs.
1. If box left empty, behavior of text box is left as default when playback stops instead of being empty. Which is probably preferable behavior, but just doesn't match instructions for field.

2. Field doesn't save preference when populated in at least some cases between sessions of WACUP. In my use case, I type a space in the field so that it displays no visible characters when sourced in OBS. Workaround has been to simply retype the space in this field every time I open up a session. Not a big deal, in fact I keep forgetting to mention it. But I finally remembered to give a heads up lol ;D


« Last Edit: Today at 12:37:07 AM by umihimeyokai »

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5832
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Play Tracking Preference Not Saving
« Reply #1 on: Today at 10:02:10 AM »
The preview box showing text is wrong so that's now fixed for the next build. Otherwise the action is working correctly against what I'd tried to do vs the original behaviour so it'll leave what's in the file as was last set when playback stops instead of clearing it (maybe that needs to be a dedicated mode possibly via another options from the dropdown assuming it actually makes sense to implement that).

A space character not being maintained is due to the handling stripping off whitespace characters when the formatting strings are processed. The simplest way to ensure you will have a space / effectively empty output no matter is to use $char(32) as the formatting string. You could also use $crlf() which just outputs a linebreak & should still do the same as the $char mode.

Also I've only checked this against the current (as of this reply) 1.99.53.24784 build.
« Last Edit: Today at 10:03:16 AM by dro »