BogProg X-Fade 2.0 (Input Crossfading)

[Tom_Bosleys]

Hey, no problem. Take your time. If you want, I can reinstall 5666, wait for it to crash and paste that log, but I'm not sure how helpful it will be.

[thinktink]

BogProg X-Fade 2.5.8.24 is now available.

Download

Changes:

• Improved compatibility for slightly older versions of Winamp.

[Tom_Bosleys]

Awesome job! I will try this with my current setup, and with versions 5551-5622 throughout the next week and get back to ya.

[thinktink]

!?

[Tom_Bosleys]

The older version do not have a error log plugin like the new ones do, so the crashes that I've received (just had one today) are vague at best. Just ntdll.dll errors on a random access memory code, forcing me to restart winamp. That after about a day of it running fine. The queue file function of winamp stops working with your plugin, I also might add.
Right now I'm up to version 5571, and so far it's running fine (a few hours). So far they've all acted the same as 5541--which has been the most stable version for the server.

[thinktink]

The older version do not have a error log plugin like the new ones do, so the crashes that I've received (just had one today) are vague at best. Just ntdll.dll errors on a random access memory code, forcing me to restart winamp. That after about a day of it running fine.

The only thing I can think of to get more detailed information is to run Winamp under WinDbg32, which comes with the Microsoft SDKs. The useful thing to look at would be the stack trace if you can figure out how. Other than that it's just a guessing game.

The queue file function of winamp stops working with your plugin, I also might add.

Is that like when queuing a file from Windows file Explorer (right click then Enque in Winamp) or is that something you do from within Winamp itself? Is this something to do with the old JTFE plugin?

[EDIT/] What steps do I need to do to replicate the issue?

Right now I'm up to version 5571, and so far it's running fine (a few hours). So far they've all acted the same as 5541--which has been the most stable version for the server.

Good to know it's working.

[thinktink]

BogProg X-Fade 2.5.9.25 is now available.

Download

Changes:

• Fixed crash on certain input plugins that provided empty string through which an alternate method for retrieving metadata from the original plugin was required (winampGetExtendedFileInfo called through winampGetExtendedFileInfoW, and vice versa.)

Found this crash when I tried to load a WAV file with X-Fade installed on older version of Winamp.

[Tom_Bosleys]

Unfortunately, that is very much over my head

All I have is the standard error log at the moment, but I don't recall the .log of 5666+ being anymore useful other than saying a memory read error.

Here is one I had for v5571:

--5571 -- ran 6 hours + queue is broken

Problem signature:
Problem Event Name: APPCRASH
Application Name: winamp.exe
Application Version: 5.5.7.2810
Application Timestamp: 4b2f0bcd
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7ba58
Exception Code: c0000005
Exception Offset: 0002e39e
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

I'm up to 5601 b3091, and so far 5541 has been the most stable for who knows what reason, but it runs for days and no problems at all, where as the rest of these only go a few hours without the same crash out. Same load/plugins, etc.

[Aminifu]

I have been successfully using thinktink's input plug-in (BogProg X-Fade (in_bpxfade.dll)) for several years to provide crossfading. I'm happy to report version 2.5.9.25 works equally well with Winamp v5.9.0.9999 under Windows 11.

Winamp's native crossfading feature is part of the Nullsoft DirectSound Output (ds.dll) plug-in. So this output plug-in must be used in order to use the native crossfading feature. Nullsoft DirectSound Output will also work with BogProg X-Fade when it's crossfading feature is disabled.

BogProg X-Fade hooks into the audio processing chain (on the input side) after the file type input decoder plug-in (that supports fully functional transcoder functions). So it can work with any Winamp output plug-in. It also provides an optional resampling feature for the source file's native sample rate and bits per sample. The volume levels of the next track and the ending track during the overlap period are unaffected, unless the optional logarithmic transitions feature is used. This feature slowly increases the volume level of the next track to it's normal level and slowly decreases the volume level of the ending track to zero during the overlap period. The overlap period is adjustable in millisecond increments. I don't know what the maximum overlap period is. The most I've ever used is 15 seconds.

BogProg X-Fade comes with an optional output plug-in called BogProg NoFlush (out_bpnoflush.dll). This plug-in will be stacked with the final output plug-in you choose to use. BogProg NoFlush insures that the playback timing will not be interrupted and you won't get any pops or clicks or other audio artifacts when BogProg X-Fade crossfades the next audio track.

BogProg X-Fade (and it's companion BogProg NoFlush) was developed for SHOUTcast users, but it works for non-SHOUTcast playback also.

Seeking is very laggy depending on which final output plug-in you use and if the output plug-in has large buffering. Expect lag and weirdness when seeking.

BogProg X-Fade works best with source files that have little to no periods of silence at the beginning and end of each file. The overlap period should be selected to account for such silence, if needed