Messages

1456

Preview Build Discussion / Re: CD Ripping?

« on: March 07, 2020, 04:15:25 AM »

There are still those requesting ripping support (it's just playback sent to a file encoder instead of the speakers when you actually look at what's going on) & a lot of what's needed for that is there but just needs to be hooked up to get things working.

Burning support is better managed else where but there's nothing to say that things couldn't be done for those needing it to at least help prepare what could then be burnt. And WACUP doesn't include any of the Sonic Burning Engine or other aspects since those parts were replaced with WACUP versions & is why there's the features missing since they're not been re-coded.

Should I however do it, like I note above, ripping is something that makes sense, burning less so but who knows what will take my fancy to work on

-dro

1457

General Discussion / Re: What's happened with winamp58_3660_beta?

« on: March 07, 2020, 04:09:39 AM »

Work continued on Winamp after it was sold in January 2014 until it was officially halted in June 2014. Some stuff was attempted to be done after that but SHOUTcast took up too much time of my time & then I was let go in September 2015.

They tried to bring back some of the other ex-devs (but on a non-paid basis) & between what I'd been trying to do & what they did / reverted / whatever'd it then languished as an unreleased build until it was "conveniently" leaked in September 2018.

They then released the non-leaked version in October 2018 which barely had had anything done to it in over 2 years & to add insult to injury they put it pretty clear placement on the redesigned Winamp homepage that the 5.8 beta (most ignore that detail that it's a beta) is "not an on-going project".

So my take on that is that the original Winamp desktop client is no longer developed & is the main reason behind me doing WACUP (after being convinced to at least revive some of my plug-ins in January 2016) to provide a working & supported Winamp-compatible client since I'm working through replacing the need for using Winamp files with WACUP provided ones. That should also explain why I will not use their 5.8 beta nor re-base WACUP on top of it as my goals is to not have to use any Winamp provided plug-ins & dlls unless there's no alternative option.

2019 was supposedly going to be when they brought out the all new singing & dancing multi-platform but mobile focused Winamp v6. Nothing happened & instead 2019 saw the closure of the Radionomy broadcasting platform with SHOUTcast then being the one that people are pushed towards since they charge to use that. All that grouping of companies is now doing is running SHOUTcast's name into the ground & milking things for what they can as it seems like they've got a fair bit of debt around their necks after the mess of the Vivendi purchase & subsequent buy-back.

Is Winamp dead, as far as active development it seems so (not that it matters for WACUP) & what was meant to be v6 wouldn't have had any links back to Winamp proper. As far as the user base, people are still using it so on that count I don't call it dead but it's seen better days.

-dro

1458

Preview Build Discussion / Re: How To Make WACUP Default?

« on: March 07, 2020, 03:57:03 AM »

It won't do anything with WACUP unless you've manually associated it to be the default handler. Like the first quoted comment, this is by design whilst we're in a preview build state. The intention is to have support to do that get enabled in the next round of WACUP updates.

The preview build install requirements state Winamp 5.666 patched (will be installed if not already present) since by running the installer you're saying you're ok with it doing that step for you.

-dro

1459

Preview Build Discussion / Re: Window resize problem with dual-monitor setup

« on: March 05, 2020, 09:34:38 PM »

Ok, well hopefully I can replicate it & sort out something. Build 5144 is just being uploaded though I doubt it'll help with this issue.

-dro

1460

Preview Build Discussion / Re: Window resize problem with dual-monitor setup

« on: March 05, 2020, 09:19:16 PM »

I don't have the 5.666 code, I only have the pre-compiled gen_ff dll to work against that came from that installer (i.e. I can try replacing it's code via patching). So if anything things should work the same as 5.666 since I'm not directly doing anything to alter the modern skin engine behaviour.

Maybe a compatibility mode is being applied or there's some other weird interaction going on but I also don't know if it's something I can replicate. One other thing to do would be to remove the studio.xnf file within the WACUP settings folder whilst WACUP isn't running & see if that behaves or not (is the equivalent of an uninstall without loosing other settings).

-dro

1461

Preview Build Discussion / Re: Window resize problem with dual-monitor setup

« on: March 05, 2020, 07:50:11 PM »

That makes more sense of things especially the offset matching to the difference seen.

I'm sure I'd attempted to fix such things when I was working on the post 5.666 release before that went sour but had assumed that it had all been thrown away (note: I refuse on principal to run that beta).

I'll need to do some digging into what I can patch with the 5.666 compile of gen_ff being used to get it working correctly (was something to do with the wrong rectangle being used in an API response but I can't be sure since that's from 6 years back).

-dro

1462

Preview Build Discussion / Re: Window resize problem with dual-monitor setup

« on: March 05, 2020, 04:36:29 PM »

Ok, that rules out that possible idea. Another thought, are you running any software that might relate to the monitor that does zoning or any other related handling? Also are they aligned side-by-side in the monitor preferences or one above each other or any other type of alignment ?

My LG has something like that & it was causing some weirdness when I tried it out briefly (it caused WACUP & other software to take a lot longer to load & just felt sluggish so I dropped it but the window splitting thing was otherwise potentially useful).

Otherwise I'm going to have to see what I can replicate by trying out the specific resolutions as I'm not seeing it myself at the moment with 4K (main) & 1080p (secondary).

-dro

1463

Resolved Issues / Re: Bugs in latest release - v1.0.9.5118

« on: March 05, 2020, 04:30:55 PM »

Correct that's not yet been started on though I've done some preliminary work on how to try to quickly fill the tree view part of it (which would then drive a sub-query purely related to the selected folder) but that's as far as it's gotten. You should also have beta access now

-dro

1464

General Discussion / Re: Queuing with JTFE from media library

« on: March 05, 2020, 04:26:01 PM »

There was an explorer menu option with the older version of the plug-in under 5.666 but it also didn't work too reliably but is on the list of things for the native support for additional explorer menu actions. The majority of it comes down to needing a known api in place that can deal with things so plug-ins can react accordingly without basically the hackish way that I'd tried to get things like the external queuing to work.

Unless I'm mis-reading things, it seems you're saying that queuing up items from elsewhere in the JTFE queue isn't also adding them into the main playlist editor - is that so or am I just mis-reading things?

-dro

1465

Skins / Re: Migrating from DeviantArt to WinCustomize

« on: March 05, 2020, 04:20:17 PM »

I get why they're culling things but it also seems such a shame but a lot of the internet doesn't care too much & probably $$$ is the driving reason.

-dro

1466

Wishlist / Feature Requests / Re: my bug & wishlist

« on: March 05, 2020, 04:18:52 PM »

As a quick reply, a number of the issue noted above are already fixed as part of the 4994/50xx/51xx beta builds.

However some like merging the URL dialog as part of 4.1 don't make sense to do as the input mechanisms (one a custom solution & the other from the OS) aren't compatible with taking URLs.

5.1 is an opt-in & enabling that when its needed does most of what you're asking for however it's not enabled by default since it can cause performance issues (as found during the early betas which led to it being an opt-in than a default on).

I'll go through the rest once the new build is released though it'd be helpful if you can also go through & see what has or hasn't been fixed / implemented on the issues when you can

-dro

1467

Wishlist / Feature Requests / Re: Favicon

« on: March 05, 2020, 04:13:05 PM »

The icons that are present at the moment are those that come from what Winamp 5.666 & earlier provided & yes they're mostly not all that great but  I don't see much point in removing them as it will break compatibility in that area.

Hence the support to manually set an icon is there but it probably needs to be made more obvious.

Depending on what it looks like then I might consider including it. Victhor might have SVG of the icon otherwise the large 512px version is at https://getwacup.com/WACUP_logo_512.png or even better (now that I've remembered) there's https://getwacup.com/community/index.php/topic,487.0.html though depending on the styling I've found it has issues being scaled down to a small size (32x32px is normal for the notification area though high-dpi scaling might get it to use a 64x64px icon but that needs to be at 200% scaling from how it looked when I last played around with such things).

-dro

1468

Preview Build Discussion / Re: Window resize problem with dual-monitor setup

« on: March 04, 2020, 01:06:58 AM »

Have you by any chance been experiencing crashes on closing?

-dro

1469

Resolved Issues / Re: Bugs in latest release - v1.0.9.5118

« on: March 04, 2020, 01:05:40 AM »

That's expected as the replacement is lacking a lot of features including normal importing (it should have attempted to auto-import the existing legacy library) & is only included as a means for testing out its stability in earlier builds. Importing, etc is to be worked on in the coming months so that the legacy plug-in can then be finally dropped.

-dro

1470

Resolved Issues / Re: Bugs in latest release - v1.0.9.5118

« on: March 01, 2020, 11:03:32 PM »

Crash reports are auto-uploaded but it is also attempted to send it via email (bugs @ getwacup . com) so any additional information can be provided. Due to what's collected, it's put into a zip which can be found via Preferences -> Advanced -> Error Feedback (or the Crash_Reports folder within the WACUP settings folder if you know where you're looking). The emailing behaviour can also be disabled via that preferences page though I'd recommend against disabling it completely as its better for me to get any crash report than none

With the crash mentioned, I've just been looking through them & saw a number which seemed to be related to such an interaction & I've got that already fixed for the next build. If you want to send it over via email then I'll double-check it.

For the autoplaying feature, Preferences -> General -> Autoplay is where you can change the playback behaviour. 5.666 doesn't have any of that feature set which is why it's acting differently

The preset could be failing depending on the GPU being used as some don't like AMD setups & others don't like nVidia setups. It could also be causing a crash when DirectX is trying to process it which some do & it's done the better option of a blank render vs taking the whole process down (as older WACUP & Winamp builds would suffer). I don't know what's the specific cause until directly checking out the preset.

-dro