Latest WACUP public preview for x86 & x64 is build #23960 (March 1st 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #23960 (March 1st 2026) (x86 & x64 changelogs)

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dro

Pages: 1 ... 93 94 [95] 96 97 ... 135
1411
Wishlist / Feature Requests / Re: Chromecast Support
« on: January 07, 2020, 03:43:39 PM »
The last time I looked, there's no formal way for a standard Windows program to do it as you either need to be within Chrome or a Android/iOS app.

I know VLC apparently added an unofficial mode but I've not tried it nor does it seem to be done in a manner that would allow it to be used as a library by other programs (unless anything has changed since I last looked).

Maybe I've missed something as really we'd just need to get the WACUP streaming server output accessed from the chromecast device but it's how to get that working which if there is a sensible way of doing it then I would be willing to support it.

-dro

1412
I've just finished the initial steps for merging the playback excluder plug-in into the wacup core as well as fixing the reported issue.

That should improve how things work compared to the existing plug-in as the file is now blocked from attempted playback before the input plug-ins are normally passed the file to play.

-dro

1413
Resolved Issues / Re: Now Playing - leading spaces not saved
« on: January 06, 2020, 08:02:11 PM »
Changes made for the next build so there'll be a $padout() & $lpadout() which will add the padding onto the string passed instead of only padding if it's below the size provided along with the existing $pad() not needing an input string but still being able to pad with a custom character (e.g. $pad(5, #) will output #####). I think that should cover the possible usage needed without breaking any older behaviour.

-dro

1414
Resolved Issues / Re: Now Playing - leading spaces not saved
« on: January 06, 2020, 04:12:46 PM »
The stripping of whitespace is down to how the setting are saved & something I let happen as trailing whitespace niggles me no end.

What you can do is put a $pad(,5) at the front for 5 spaces & I'll change it to also be able to do $pad(5) without needing to have an input string to start with.

The thing with the pad & lpad methods is it's handling is related to the length of the input string so you have to know the length of that to then get the desired padding which isn't the most obvious of solutions & I think I might consider another method that probably works in a more expected manner & leaving the existing pad/lpad methods alone (apart from working if there's no input string as that's reasonable imho).

-dro

1415
General Discussion / Re: plugin development ressources
« on: January 06, 2020, 04:00:07 PM »
I've not used Code::Blocks in over a decade & only briefly so at the time so it might have to be Visual Studio (really depends on what's needed for the NAS side unless you're just focusing on the plug-in side of things). Though that would allow you to make use of the VS2017 runtime that's shipped with WACUP to help keep the size of the dll & related distributables to a minimum (which is always nice).
I am wondering if there's something I can do from my side that might help you out as it wouldn't be too hard for me to add a command-line option to export the library playlists to a folder (as long as it can be accessed via normal path handling methods) & likewise copying them back but it's more about the files that the playlists relate to that can be the issue depending upon the direction of file transfer.

-dro

1416
#1 is a bug as it's meant to do that but doesn't do it correctly as part of the transitionry work.

#2 is already meant to be checked for & prevented against but will look into what's going on.

-dro

1417
Wishlist / Feature Requests / Re: New Milkdrop defaults
« on: January 06, 2020, 03:37:49 PM »
However, I would like see some improvments in MilkDrop in the future, if that falls in the scope of WACUP.
What sort of improvements?

-dro

1418
Preview Build Discussion / Re: CD Ripping?
« on: January 06, 2020, 03:36:32 PM »
The plug-in that handled it was replaced under WACUP but is only capable of doing CD playback at the moment.

Ripping will get re-implemented (since it's just playback with file conversion) however burning support is something I'm not sure about trying to re-implement.

For burning I have wondered about doing enough to create the file(s) needed to then be passed onto a dedicated burning program.

-dro

1419
General Discussion / Re: plugin development ressources
« on: January 06, 2020, 03:23:48 PM »
Apologies for the delay in replying.

I never found that aspect of the wiki all that helpful. Depending on the type of plug-in you're looking to make it's often much better to have a look at an existing plug-in to get a better idea otherwise some of the older Winamp SDK's included a selection of simpler examples that might also help.

You can ask on here or drop me an email or get on the discord & that might be quicker to help with programming related questions.

-dro

1420
Resolved Issues / Re: Playlist does not show queued items
« on: December 22, 2019, 12:06:36 AM »
Alas it's a known issue with the current build (it goes back 2 builds from what I remember) where it fails to work in some installs.

It's already fixed for the next build, just it hasn't been released yet - is likely the next preview build will be available early January.

-dro

1421
Wishlist / Feature Requests / Re: Podcast art cache
« on: December 17, 2019, 04:51:08 AM »
Well I thought I'd do my Sunday night R&D session today & have a quick look into this & that's all I've spent the day doing *shrugs*

The next beta build will have an initial implementation that will create & use folder.<image_type> for the feed artwork - there will be no options, no handling for feed items doing their own thing & it's purely to see if all of the changes that have been needed to get it working do actually work. If they do then it can be refined later on but I've spent more time on this then I should have done so something will be better than nothing for the time being.

-dro

1422
Skins / Re: Classic Skin Color Variants
« on: December 16, 2019, 09:56:01 PM »
It is possible if the author of the classic skin has gone to the effort of providing colour variants & you've got them available. A few would include the additional versions within the skin zip & you then have to manually extract / install them as needed to be able to make use of them.

However there's nothing in place that will do it like the modern skin colour themes support.

-dro

1423
Wishlist / Feature Requests / Re: Podcast art cache
« on: December 12, 2019, 11:04:19 PM »
The podcast view is not like the local library views - I just pass a simple HTML blob to the IE based browser & it's left to get & render things as needed & this is one more reason why I really would prefer not having any browser aspect as part of WACUP as I can't cleanly display things but am at the mercy of how whatever engine being used wants to work. There are means to pass the image data (if present via the existing artwork service) in as part of the HTML blob but it wasn't implemented from the start as the artwork handling support coming from Winamp's core & associated input plug-in had issues (and still does for MP3 based files until that's completely replaced).

My suggestion to disable the display is purely there as a temporary workaround to alleviate the issue being seen until a solution is implemented as unless it's part of the downloaded episode file (as the local library view uses) then it's a web request without any knowledge of the local file info.

That is why I was saying about doing things akin to local files & how artwork is managed for that but due to the dynamic nature of feeds, it needs to account for external changes as that is what will happen & people will get annoyed if it then shows the wrong artwork. But like I also noted, I don't know without actually looking into it what sort of cache life information I'm going to get back from the feed to help manage keeping things current which is for the overall image & not the per-episode aspect since that would have to be tagged (which is another issue as that doesn't work correctly).



tl;dr - temporarily disable artwork, something will be sorted that tries to use local copies depending on how the embedded IE wants to work & embedded browsers are an evil I really could do without (or people formatting information for feeds consistently which ain't going to happen...).

-dro

1424
General Discussion / Re: Portables, Syncing, Metadata
« on: December 12, 2019, 10:51:02 PM »
I don't really have much to suggest as I've not directly touched the portables support so the only thing I can assume is that there's something else indirectly changed which is causing the issue.

Portables support is something that needs to be planned out as to how to best replace it but in all honesty, it's not something this high up on my priority list & I'll have to allocate some time now over the first few months of next year to see if there's anything obvious I can try to fix with the information the handful of plug-ins involved might be trying to use (this is one of those cases where source code would be helpful but is also why a replacement plug-in of some form is needed).

-dro

1425
General Discussion / Re: Bluetooth Headset & Auto Pause
« on: December 12, 2019, 10:45:50 PM »
What output plug-in are you using under WACUP? As it's not something I'm aware of being directly coded into WACUP (especially if out_ds is the plug-in being used which hasn't been altered from what 5.666 uses) & it might be more down to the output plug-in &/or how the interaction with the OS/audio driver works.

Alternatively it might require selecting the specific device in the output plug-in config but I'm not sure what else is going on as I've no bluetooth devices to even try to replicate the issue.

-dro

Pages: 1 ... 93 94 [95] 96 97 ... 135