NOTE: New beta testers are not currently being added as I need to re-work the beta test program

If you've not already requested to be a beta tester & would like to then please send a PM to 'dro' to be added to the beta test group. Note: requests to be a beta tester are processed in batches when new beta builds are released so please by patient of this process.

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 ... 79
1
Wishlist / Feature Requests / Re: Tab Key to Toggle & Activate
« on: August 03, 2021, 01:46:29 AM »
That ended up being easier to fix than I thought - is nice to remove code for a change & things work better. Next beta build will have the fix for this.

-dro

2
Wishlist / Feature Requests / Re: Tab Key to Toggle & Activate
« on: August 02, 2021, 01:30:50 PM »
That is a media library window feature & is irrespective of the skin being used. However it's something I've still to get working with the replacement media library core which is what the 1.1.0+ builds now use (as per the changelogs) & it worked before because Winamp's gen_ml (no longer used) implemented the support for it. Have added this to my todo list.

-dro

3
Preview Build Discussion / Re: Cannot use ALT+Z hotkey
« on: July 31, 2021, 12:18:00 AM »
That's a bug that's already been fixed in the beta builds - was a side-effect from merging the next on stop plug-in into the WACUP core & the handling conflicting.

-dro

4
Have you looked at the diagnostics prefs tab I mentioned when you're doing that action to see how it's changing? A screenshot showing the dropped point or a small video might be helpful.

Also what skin & where exactly on WACUP are you dropping the files as I feel like I'm missing some small detail to be able to either replicate this & confirm whether it is expected or if I do have a bug.

-dro

5
What _exactly_ are you doing to the playlist ? i.e. what actions are you using, is the default to enqueue or play. As I can't currently replicate it clearing the shuffle table unless the current playlist has been cleared in some manner (e.g. double-click in the local library when the default is 'play' - in that scenario it is expected to clear the shuffle table).

However if you're expecting it to level out the playback of files then that is not what the feature is intended to do & that's something which will be looked into at a later time to factor in the number of plays (as stored in the local library / history) to try to make things seem less repetitive
Using the recorded playcount is still something I've got to implement later on as I said along with a number of other possible options to control shuffle.

-dro

6
There already is the means to see what the shuffle table is doing via the diagnostics preference tab for the shuffle list (look down to the bottom of the preferences tree) so getting access to a beta (which I'm not adding new people at the moment as the beta program isn't meeting my needs) isn't really going to help as nothing has been changed vs the current preview build.

The point of the option is to preserve the shuffle table between sessions but _only_ if the contents of the playlist haven't been changed i.e. starting WACUP with an external file / playlist that wipes the playlist is going to reset the shuffle table. Additionally the same can happen if using it & modifying the main playlist (as you've noted you're doing) depending on if it's a complete replacement of the playlist or if its adding to the existing playlist.

If it's the later then there is an attempt depending on how much of the playlist has been played to add the new files in a manner that won't mess with the existing shuffle table. However if you're expecting it to level out the playback of files then that is not what the feature is intended to do & that's something which will be looked into at a later time to factor in the number of plays (as stored in the local library / history) to try to make things seem less repetitive (even though shuffle is just a pre-generated random list so there's nothing to stop that duplicating things when it's regenerated).

-dro

7
General Discussion / Re: Sorry cannot write streams to disk
« on: July 20, 2021, 06:49:06 PM »
Unfortunately it's an issue with the in_mp3 plug-in & how it reacts to output plug-ins reporting low latency vs how it's trying to deal with streams.

I don't have a solution for now (as the in_mp3 plug-in will eventually be replaced with a WACUP built one instead of re-using Winamp 5.666's) other than possibly changing to use a different output plug-in.

-dro

8
General Discussion / Re: Updating openmpt input files into WACUP?
« on: July 19, 2021, 04:11:41 PM »
Well, I just wanted some improvements over the older version. I won't bother since it will lose some aspects. :)
I get the reasoning & you can give it a go as the core playback should work the same irrespective of the version but I don't know if you're going to need some of the WACUPification that's been done to it vs the generic version that's aimed at working in simpler Winamp compatible solutions.

I do however appreciate that my delay in offering a newer preview build doesn't help things though with what I've seen in the changelogs, most of the things fixed (am somewhat dubious over some of the stated security issues in terms of actually being able to use them maliciously since you still need to have gotten a bad file onto the machine somehow) is unlikely to make a marked difference with a bit more of a wait.

-dro

9
General Discussion / Re: Updating openmpt input files into WACUP?
« on: July 16, 2021, 02:41:41 AM »
If you really need to use the newer openmpt build, disable the in_mod plug-in by un-checking it via the input plug-in preferences page & accept that some aspects are not going to work like they did. The onus is then on you to either to remember to change it back when a newer WACUP build is provided or to keep manually updating the openmpt build of the plug-in.

-dro

10
General Discussion / Re: Updating openmpt input files into WACUP?
« on: July 16, 2021, 01:15:05 AM »
You can't easily see what input plug-in is going to be used when there's multiple plug-ins trying to claim a file type (what aminifu has noted whilst I'd started to reply sort of helps but there's no conflict reporting nor does it show the actual query order of the plug-ins).

The way that things currently work means the first plug-in queried that reports it wants a file type will be the one that gets to handle & that's biased towards the WACUP plug-ins since they're loaded before any 3rd party plug-ins get loaded i.e. WACUP's in_mod will be loaded before the openmpt provided in_openmpt.

The preview build hasn't been updated since March which is why it's on an older revision of libopenmpt - it's been thrown about maybe allowing for inter-build updates for some of the plug-ins but that's not been thought about for a while. It's now going to be at some point in August at the earliest that a newer preview build is going to be offered which will have the latest libopenmpt update included when that occurs (the current beta is already using 0.5.9 with the next one to use 0.5.10 as I'd not seen they released the newer version until just after I'd done a new beta build on the same day).

-dro

11
General Discussion / Re: Updating openmpt input files into WACUP?
« on: July 15, 2021, 11:36:09 PM »
It's as safe as installing any plug-in but with how the input plug-ins are checked for what to use to play things then it's unlikely it'd actually be used over the WACUP provided plug-in without disabling that one first.

-dro

12
I couldn't determine what it was that has changed with stereotool 9.70 compared to 9.63 causing it to not like the way that WACUP was working when it was first reported about a month ago. Manually killing the wacup.exe loader process but leaving the winamp.original process (need to look at the details view in task manager or an equivalent in a 3rd party process tool) will then allow loading to complete.

However there's been changes made & have been confirmed as working with the 81xx beta builds that allow either version of the plug-in to work :)

-dro

13
General Discussion / Re: WMA ?
« on: July 13, 2021, 12:46:34 PM »
The only change was a while back & is that in_wm.dll eventually got added to the blocked list of plug-ins. Trying to re-use the Winamp 5.666 plug-in is just not worth the hassle & it should be being handled via the directshow input plug-in (if configured to do so & if there's an appropriate filter available).

-dro

14
General Discussion / Re: Newest Beta Release Download link???
« on: July 12, 2021, 12:01:35 AM »
I've been somewhat busy with focusing on coding so I'm a bit behind on the pm's & emails.

I'm not actively adding new beta testers at the moment as I've some house cleaning to do with the existing inactive ones (maybe 1 in 7 with access are even using the new builds) also there is the "Note: requests to be a beta tester are processed in batches when new beta builds are released so please by patient of this process." with the 2 places I list about what to do to be considered.

Also at the moment beta testing is just not doing what I want to get back from it & I've yet to decide how I want to proceed with it. It's nothing elitist (as has been claimed before by some) but I need people to actually test things rather than get access & I never hear anything from them (or even worse spread beta versions around which aren't fit for wider consumption - if they are then they get released as a preview build for just that).

@Aminifu: That is not available for those who aren't beta testers.

-dro

15
Skins / Re: Big Bento Modern v1.2
« on: July 07, 2021, 10:14:42 PM »
v1.2 is now available & remember if you want to / can do it to give victhor a thank you maybe even as a donation (see the first post).

-dro

Pages: [1] 2 3 ... 79