Latest WACUP public preview for x86 & x64 is build #20202 (September 28th 2024) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #20686 (December 23rd 2024) (x86 & x64 changelogs)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

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 [2] 3 4 ... 113
16
General Discussion / Re: Winamp ML import
« on: January 06, 2025, 12:06:24 PM »
I'd really need to know what version of winamp you were trying to import from. As the import action I offer (accessed via the empty local library window or by going through media library window -> library button -> import -> import legacy (external) db) just needs to be pointed at an existing winamp settings folder (usually %appdata%\winamp) & as long as it's in the appropriate format then it should work.

I've only really tested the import action with copies of the local library from 5.63 to 5.666 specifically though I was given a set of main.dat/main.idx files last year from newer revision & my local library plug-in was able to import them without issue. If it's from a much older local library instance then it's most likely the layout of the columns might not be in the order that I'm expecting which would then prevent the import from seeing all of the data.

If needed you can message me a copy of the existing main.dat/main.idx from the winamp install you're trying to import so I can then check them out & if needed fix my importer &/or generate an appropriate copy of the library.dat/.idx files wacup uses for you to use with it.

17
General Discussion / Re: album art overview
« on: January 06, 2025, 11:54:49 AM »
That is what I'd expect the details view mode in my local library plug-in to currently look like as I didn't want to do a like for like replication of winamp's look for those items.

When items are selected in that mode the background colour of the text should change (as long as the skin being used defines things in a manner which makes it visually obvious) but I'm currently using a simpler way to achieve the details mode which I will need to come back to trying to expand upon but I was aiming more at just getting something that was working vs eye candy & which also worked ok under WINE based setups.

18
Preview Build Discussion / Re: Issues opening multiple files?
« on: January 02, 2025, 08:15:11 AM »
This is why I shouldn't reply at 3am in the morning when I can't sleep. Will have a proper re-read later today when I'm hopeful more with it.

19
Preview Build Discussion / Re: Issues opening multiple files?
« on: January 02, 2025, 02:55:29 AM »
What version of Windows are you using?

20
Preview Build Discussion / Re: APE Tags causing crash
« on: December 29, 2024, 03:04:23 PM »
There's now a change in place for the next build which hopefully will allow in_mp3 to behave whilst not causing a live patch that was in place to resolve another issue from occurring which appears to have been conflicting with what the input plug-in is doing with APEv2 tags.

21
Preview Build Discussion / Re: APE Tags causing crash
« on: December 29, 2024, 01:38:21 PM »
I've just had a quick look & it's crashing within the re-used in_mp3 plug-in from the 5.666 installer for which I'd been wondering what was going on. My testing is against the current beta build so really it's not WACUP build specific but is the in_mp3 plug-in at fault & is probably more luck than anything with it not having caused problems with whatever the older build was it was working for you.

The x64 build of WACUP doesn't use that plug-in though it's still to get its own proper in_mp3 replacement but it doesn't crash with that file so if you're not needing to use any of the modern style skins nor any 3rd party plug-ins then that's an option to consider using.

Will see if there's anything obvious I can do to work around whatever in_mp3 is doing as like you I'd like to see far fewer crash reports too :)

22
General Discussion / Re: Update library?
« on: December 21, 2024, 12:32:33 PM »
Preferences -> Media Library -> Folder Monitor or Media Library window -> Library button -> Local Library -> folder monitor section at the bottom of that (if applicable)

Right-click any of the local library nodes (root or specific will control which items are checked) or from the right-click menu within the local library views or by using the view action / settings button in the top right of the active local library view gives refresh / remove actions.

So equivalents are all there & imho there's more places to access them compared to what winamp's ml_local plug-in offered vs wacup's ml_ll.

23
Skins / Re: none of the bento skins are available?
« on: December 18, 2024, 02:33:39 PM »
It's intended for now as there's no x64 equivalent of the gen_ff plug-in that I can use & I've still to actively start working on making my own modern skin engine plug-in.

Doing that would eventually remove one of the remaining reasons for the x86 build to have to keep relying on the 5.666 installer & reusing some of it's dlls for features.

The x86 build is not a downgrade to the x64 build as it has more features & more potential support compared to the x64 build which is just the pure wacup experience for now & with more time will improve in comparison to x86.

24
However I'm still seeing it intermittently prevent WACUP from closing normally when the plug-in is running so I've got to look into that.
I've possibly found something that'll better allow the process to close irrespective of plug-in / external dll weirdness messing up things from what I could see with this plug-in so hopefully the next build will be better behaved on all counts.

25
I'd not seen the edits & luckily hadn't purged the legacy crash reports from the older builds that I do periodically though the crash didn't seem to show me much other than morphyre was trying to call something no longer there when process close was happening.

With the crash on loading, I made a change for the x64 build just before 19516 was created with how the embedded window frames are able to be created by plug-in as Morphyre uses & it messed up an expectation of how that works for the x86 plug-ins. I've now changed that back & its loading ok again. I've also fixed it to use the correctly scaled window frame so it'll match the look of the classic skin scaling.

However I'm still seeing it intermittently prevent WACUP from closing normally when the plug-in is running so I've got to look into that.

26
That's good to know & saves me testing things tomorrow if it's working ok for you with the in_mp3 suggestion.

When in_mp3 is finally dropped I should have gotten my handling to be equivalent for local AAC & you shouldn't notice a difference 🤞 Though I still think it's better if possible to get them into a container format like MP4.

27
The changelog pages don't link to the builds as those are mostly the beta to beta build changelogs & I don't openly provide them (even though the preview builds are just public beta builds).

The preview download page has links back to prior preview builds & those for now still have old build links.

Also you've referenced the x64 preview build & that can't do my in_mp3 suggestion as it's pure wacup & cannot load any winamp plug-ins since it can't use x86 / 32-bit dlls.

28
As part of me moving WACUP away from re-using the handful of the remaining plug-ins from 5.666 to do playback, etc there's been an overall swapping over to WACUP native versions & raw AAC playback was one of those which happened earlier this year.

Seeking in raw AAC is something I've still to implement (which'll have to be a crude brute forcing since such files aren't really designed for nice seeking like AAC in an MP4 container) though pausing should be working. You could try setting AAC back into the in_mp3 config but I can't guarantee that'll work due to other things in my core that control which input plug-in is going to be used for various file formats.

29
Simple option is change the active output plug-in to wasapi & see if that makes a difference. As either the output is clipping silence or the MP3 decoder is doing it but that's a bit more involved to change around (unless you make a test portable install using the x64 build so the existing installation isn't altered & the x64 build uses a different decoder plug-in compared to the x86 build which would rule out decoder vs the files being played).

30
Do you remember what file type(s) those affected files might be?

Pages: 1 [2] 3 4 ... 113