Latest restricted WACUP beta release is build #18980 (April 24th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #18980 (April 24th 2024) (x86 only)

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 - scr1m3

Pages: [1]
1
General Discussion / Virtual auxillary input
« on: June 26, 2020, 10:21:32 AM »
I want input audio from my browser (Google Play Music, YouTube, etc) into WACUP. This is so I can use plugins such as AVS. I was thinking perhaps I could do this with a virtual AUX driver. But I'm not sure if this is possible or how I would do it. I'm currently using HDMI out to an amp for audio (this may change to optical out in the future), so there isn't a way to do this with my current audio driver.

Has anyone done this before?

2
Skins / Re: Big Bento Modern - final release v1.13
« on: May 25, 2019, 08:03:24 AM »
Had a quick look online, it seems that your laptops has 32GB of eMMC storage. It has 1 SODIMM slot that takes up to 4GB DDR3L.

I would strongly recommend upgrading the RAM to the 4GB.

You could also look into ways of disabling unnecessary Windows features. You can look here for some tips. https://www.youtube.com/watch?v=nVy4GAtkh7Q

The issue as other have mentioned is that Windows will be swapping memory to disk, which will hurt performance. It doesn't have sufficient memory to store the OS as well as the applications you might want to run such as WACUP or a web browser.

3
Skins / Re: Vortex 1.04 release candidate
« on: January 13, 2019, 07:15:45 AM »
Awesome skin!

4
Wishlist / Feature Requests / Re: Support for alphabetical characters in the disk number metadata field
« on: June 30, 2018, 08:21:18 PM »
Tested ogg as well, same result. Not sure what other formats would be worth testing. I tried wma, which it seems isn't supported (I doubt anyone uses it anymore anyway)

5
Wishlist / Feature Requests / Re: Support for alphabetical characters in the disk number metadata field
« on: June 27, 2018, 12:47:46 PM »
I mostly use FLAC and MP3. I'll check some other formats later when I get home.

6
Skins / Re: Big Bento Modern - final release v1.02
« on: June 23, 2018, 10:25:39 PM »
Thank you victhor, I'm really loving this new skin. Makes Winamp feel like it was released in 2018 :)

Was wondering, is there anyway for the end user to change the browser in Web Reader to something like Chrome for example?

I tried adding Google Play Music as an experiment, but it's not playing audio. So I'm not sure what the web browser included is, is there any possible configuration options to enable for instance javascript?
<sourceitem name="Audio > Google Play Music" comment="Play the Google Play Music of the file playing" url="https://play.google.com/music/listen#/sr/%ARTIST%-%TITLE%" icon="icon.google"/>

7
Wishlist / Feature Requests / Support for alphabetical characters in the disk number metadata field
« on: June 23, 2018, 09:41:57 PM »
I have several albums that are multi-side and/or multi-disk vinyl's. WACUP allows you to save a disk number but doesn't support alphabetical characters. For instance, A or B would show as a blank disk number and 1A would just show as 1.

Just a nice to have.

Pages: [1]