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.

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
General Discussion / Metadata Required for WACUP to function as intended
« Last post by Aminifu on July 25, 2021, 10:19:16 PM »
I started this thread as a place for Winamp/WACUP users to share what they have learned related to the title subject. Due to the age of Winamp, and since WACUP is based on Winamp and still uses pieces of Winamp code, some metadata is needed for certain features to perform as intended.

Some music formats can store metadata within the file and some do not, so some metadata can be provided by the various input plug-ins. Some metadata is provided by Winamp/WACUP itself (i.e. %filename%, %folder%, %playcount%, etc.). Some music formats can support a greater variety of metadata than others. With the introduction of the media library, it became possible for metadata to be associated with music files that do not (or did not) store metadata within the file.

Winamp/WACUP is able to compensate for some missing metadata (e.g. using %artist% as %albumartist%, even when they are not the same thing) and/or by guessing from the information provided in a file's filename. I'm looking to learn more about the minimum default metadata needed and not what is needed for individual needs such as that required to support custom media library views and/or custom ATF strings.

The information provided by ATF Help (html page) is a great resource. Even with that, it took me awhile to learn that providing the correct %artist% and %albumartist% and the %album% for each file is a good idea (even if it meant making up an album name for files that were released individually).

So, please share what you know.  :)
12
General Discussion / Re: Sorry cannot write streams to disk
« Last post by dro 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
13
General Discussion / Sorry cannot write streams to disk
« Last post by imac on July 20, 2021, 11:12:29 AM »
On some internet radio stations I get "Sorry cannot write streams to disk", I use ASIO output to sound card and WACUP 1.0.21.7236.

This one I get the "Sorry cannot write streams to disk" http://113fm-edge2.cdnstream.com:80/1741_128
14
General Discussion / Re: Updating openmpt input files into WACUP?
« Last post by dro 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
15
General Discussion / Re: Updating openmpt input files into WACUP?
« Last post by Aminifu on July 16, 2021, 04:57:35 AM »
Well from one old timer to another, I'm sure you know that sometimes things advertised as an improvement aren't. Also you know the saying "If it ain't broke, don't fix it".  ;) 
16
General Discussion / Re: Updating openmpt input files into WACUP?
« Last post by ant on July 16, 2021, 02:43:45 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
Well, I just wanted some improvements over the older version. I won't bother since it will lose some aspects. :)
17
General Discussion / Re: Updating openmpt input files into WACUP?
« Last post by dro 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
18
General Discussion / Re: Updating openmpt input files into WACUP?
« Last post by ant on July 16, 2021, 02:21:29 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
Darn it. :(
19
General Discussion / Re: Updating openmpt input files into WACUP?
« Last post by ant on July 16, 2021, 02:20:16 AM »
Open the WACUP Preferences and scroll down to the Advanced section (bottom on the left) and select the Diagnostics group. Then select the File Associations tab in the Diagnostics group. This tab should list most of the file types associated with the active (checked) input plug-ins. Some input plug-ins do not directly report the file types they handle. However the ones you're interested in should be listed.
OpenMPT Module Decoder v0.5.5.4 [in_mod.dll] show them.
20
General Discussion / Re: Updating openmpt input files into WACUP?
« Last post by dro 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
Pages: 1 [2] 3 4 ... 10