Big Clock Playlist Elaspsed and Remaining times are incorrect - build 1.99.53.24

[vikingt]

Hi, there was such topic before, but it's locked, so, again: I've discovered the playlist remaining just displays 0:00.00, while playlist elapsed shows just the current song elapsed time and not the aggregate of the entire playlist to that point as expected.
.. or any other way to see playlist remainig with option to encrease font - to be readeble from 4 metres

[dro]

I assume it's https://getwacup.com/community/index.php?topic=2059.0 that you're referring to as the prior thread which was locked which was done since it was reported as being resolved. I'll have to look into this as I'm not seeing it showing 0:00 but something doesn't look quite right with the time that's being reported in either of the playlist elapsed / remaining modes (the single playlist item seems to be ok). I've also moved this into a more appropriate part of the forum (not sure why visualisation was chosen).

[edit]
I see why it's not working though I'm also going to have to do something to try to reduce the time that it takes to calculate things as it's too slow for either of the playlist* display modes & is also potentially behind some of it showing just as the playing position.

[vikingt]

...in a perfect world, there will be option to have 3 big clock windows simultaneously - track time elapsed; track time remaining; playlist time remaining, or these 3 in one big clock window, with big enough font...

[dro]

What are you actually trying to achieve?

[vikingt]

my "player" laptop is about 4 m. from the place where I sit, listening music. All my music is in separate folder - band and band albums. now I can see track time elapsed on big clock window and track time remaining on main wacup window - in triple size. I'll be glad if I can see playlist /album/ time remaining, too.

[dro]

I've changed things for the next build so if you make a copy of the gen_bigclock.dll that comes with wacup & rename the copy to be gen_bigclock2.dll then it'll allow a second instance of it to be loaded which the installer will try to keep updated with following updates.

This is the 'quick' way to achieve dual windows which is why I'm not doing it for an unknown number of copies as that then has an impact on the way the core (especially with the x64 build) has to handle plug-in loading.

I might consider coming back to this & re-working the plug-in so it can be a single dll with everything contained to allow for multiple windows from it. As trying to have it show multiple things at the same time in a single window was my other thought but that's also a more involved change vs duplicate the dll & fix up how the config is read. Hopefully that'll suffice for you needs with dual windows.

[vikingt]

O, thank you very much. I'll try it when new build came.