Gapless Winamp output without the use of a plugin.


Recommended Posts

I am a very big Pink Floyd fan. I pretty much listen to them everyday of the week.

They are also the only band that has more than 1 album that I love every song on.

The only problem is that most audio players have a small gap between songs, and when you're listening to Pink Floyd it can ger really annoying.

I tried many plugins but all of them didn't work too well and they didn't allow me to use my other DSP plugins.

I then started messing around with Winamp and found the trick to doing this without a plugin.

I only did this in Winamp 5 but it should work on just plain old 2.

Lets get on with the guide now.

1)Open Winamp and right click "Options>Prefrences" or just press ctrl+p

2)In the treeview on the side look for the group titled Plug-Ins. In that group there should be an Output selection. Click it.

3)You should now see a box in the area next to the treeview. In that box there should be things that say "Nullsoft Disk Writer plug-in" and "waveOut output". Look for one that says "Direct Sound output". Click it and then press the configure button at the bottom of the window.

4)A new window should've popped up. Look on the top of it and click the tab "Buffering". This is the final part. all you need to do is Adjust the Buffer-Ahead on Track change to a high number.

There are 3 slider bars that allow you to adjust the Buffer settings.

Buffer Length

This adjusts the length of the buffer. This also limits the Prebuffer and Buffer-ahead.

Example: If I had a Buffer Length of 2400 ms then my Prebuffer and Buffer-Ahead could only go from a range of 0 ms - 2400 ms.

Prebuffer on start/seek/underrun

This tell Winamp how much data to eat before it outputs sound. I don't really understand what that means, so I can't inform you on this.

The suggested amount for this is 500 ms - 1000 ms.

Buffer-Ahead on track change

This is what we want to change. This tells Winamp when to start reading the next song to get a gapless transition. For me, I just set it to 5000 ms (5 seconds) but that is a bit to high for some people. I'd say anywhere from 1000 ms to 5000 ms is a good range. If you have low memory, a slow computer, or and outdated one, then set it lower, but not to low, or else it'll still have gaps.

The way this works is like this.

Example: If I set the Buffer-Ahead to 5000 ms, then Winamp will start reading the next song where the current song had 5 seconds left until it ends. This make it so winamp can trnasition them smoothly.

After that is all done, click the apply button on the window and then close the propterites window. Try it out! open two songs and set it near the end. If it worked then there should be no gap.

Waluha!

You know, I was wondering the same thing as you were and I too decided to fiddle around with those settings, because I have alot of Game soundtracks that loop. When I did it though I didnt think it was the best way to it though. Seems I was wrong.

Good stuff.

Oh, Ill also point out, It should be fairly obvious, but you cannot set the Buffer-Ahead any higher than the max amount winamp is allowed to buffer tracks. :D

which is what Dazza said.

OK folks, let's get this right:

When you get to the buffering tab, Whatever the value for "Buffer length" is is going to be the *MAX* you can make the "Buffer-ahead on track change" setting. So, if you leave "Buffer length" at 2000 you can't set "Buff-ahead ..." to any higher than 2000.

That is what Kenta meant when writing

  "Kenta" said:
Buffer Length

This adjusts the length of the buffer. This also limits the Prebuffer and Buffer-ahead.

Example: If I had a Buffer Length of 2400 ms then my Prebuffer and Buffer-Ahead could only go from a range of 0 ms - 2400 ms.

HTH

Hmmmm - RIO Karma - =costs money = I have to spend money

WinAmp = free = I can listen to it through my 210 Watt Receiver in my AV system which I have my computer routed through and add effects, set EQ, etc.... - And I don't have to pay for it.

Guess which one *I* am going for.

What's funny is that you're still using a plugin.

It's just that they plugin you're using *comes* with Winamp. =)

What you mean to say is that you're not downloading *another* plugin.

Just about *everything* in Winamp is plugin based. Input plugins, output plugins, DSP plugins, visualization plugins...

If you didn't have any plugins, Winamp wouldn't do very much...

Dazza: I daid it, but it wasn't in a very good position to read it from.

Superkicky: I could send you the updated Direct Sound output plugin to see if that works.

If you want it just PM me.

semifamous: Yes your right, but it's the way out language developed.

Think of it this way. If you had hot coffie and let it set on the counter for a few hours and then drank it, you'd say it's cold.

Then you do the same thing, but with an ice cold soda. When you go to drink it, you say it's warm, even though the soda and coffie are about the same tempature.

The same can be said with the included plugins and the 3rd Party plugins. But if we got technical, yes, they are just plugins.

I still notice one "little" gap in live recordings, to fix it, choose "remove silence at the beginning / end of track" in "other" tab.....

Use this trick, plus Kenta Guide, and you will no hear gaps between songs.

Edited by retri
  • 1 year later...
  • 1 month later...
  • 2 years later...
  • 2 months later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Ea and Ubisoft's already have a 3rd party client mode where it removes the store features from the client and only uses 60mb of ram rather than 700.... I use playnite for gog and epic games because the the third party legendary client etc Combined in playnite epic and gog only use 200mb/ram while also showing my entire library from every other platform...
    • Also, this domain thing only works with Pro version of Windows, not the home version
    • More useless bloat to kill your pc by accident
    • Windows 11 gets more customization, a Recall home page, and more in new builds by Taras Buria Microsoft kicks off this Monday with a duo of nearly identical builds for Windows Insiders in the Dev and Beta Channels. Build 26200.5661 (Dev) and 26120.4452 (Beta) are now available for download with two big changes: a new home page for Recall and the recently spotted ability to customize where system indicators appear on the screen. The new Recall home page features more personalized content to help you get back to recent activities. It displays your latest snapshots and a curated view of the top three applications and websites you have spent the most time on in the past 24 hours. Here is what it looks like: In addition, Recall received a new nav bar on the left side of the screen with quick links to Home, Timeline, Feedback, and Settings. The next big addition is the ability to change where system indicators (brightness, volume, and more) appear on the screen. Now, you can set these at the top-left corner or top-center. To adjust this, go to Settings > System > Notifications > Position of the onscreen pop-up. Here are other changes included in today's builds: [Start menu] We are adding a Boolean to the Configure Start Pins policy to allow admins to apply Start menu pins once. This means that a user will receive admin pins on day 0 but can then make any changes to their Start pinned layout and have those safeguarded. These changes can be optionally applied through the existing configuration service provider (CSP). [File Explorer] We are restarting the roll out of AI actions in File Explorer that began rolling out with Build 26120.4151. Some Insiders may have seen the feature disappear. [Settings] In the most recently flights, we have added the country or region selected during device setup under Settings > Time & language > Language & region. Here is what was fixed: [General] Fixed the issue causing the Windows Vista boot sound to play instead of the Windows 11 boot sound. Fixed an issue where the option to reset your PC under Settings > System > Recovery wasn’t working on the previous build. Fixed an underlying issue leading to certain KVM virtual machines unexpectedly failing to boot, showing “UNSUPPORTED_PROCESSOR”. The Dev build has an extra fix: Fixed the issue causing a small number of Insiders to experience repeated bugchecks with KERNEL_SECURITY_CHECK_FAILURE after upgrading to most current Dev Channel builds. Known issues include the following: [General] [IMPORTANT NOTE] When joining the Beta Channel on Windows 11, version 24H2 – you will be offered Build 26120.4250 After installing Build 26120.4250, you will be offered the most recent update available. This 2-hop experience to get onto the latest flight in the Beta Channel is just temporary. After you do a PC reset under Settings > System > Recovery, your build version may incorrectly show as Build 26100 instead of Build 26120. This will not prevent you from getting future Beta Channel updates, which will resolve this issue. Some Windows Insiders may experience a rollback trying to install this update with a 0x80070005 in Windows Update. We’re working on a fix for Windows Insiders impacted. [Start menu] The following are known issues for Windows Insiders with the new Start menu: Using touch to navigate the new Start menu may not work reliably. For example, it currently does not support the swipe-up gesture. Drag and drop capabilities are limited from “All” to “Pinned.” In some cases, duplicate entries may appear in folders on the Start menu. [Xbox Controllers] Some Insiders are experiencing an issue where using their Xbox Controller via Bluetooth is causing their PC to bugcheck. Here is how to resolve the issue. Open Device Manager by searching for it via the search box on your taskbar. Once Device Manager is open, click on “View” and then “Devices by Driver”. Find the driver named “oemXXX.inf (XboxGameControllerDriver.inf)” where the “XXX” will be a specific number on your PC. Right-click on that driver and click “Uninstall”. [Click to Do (Preview)] The following known issues will be fixed in future updates to Windows Insiders: Windows Insiders on AMD or Intel™-powered Copilot+ PCs may experience long wait times on the first attempt to perform intelligent text actions in Click to Do after a new build or model update. [File Explorer] The following are known issues for AI actions in File Explorer: Narrator scan mode may not work properly in the action result canvas window for the Summarize AI action for Microsoft 365 files when reading bulleted lists. As a workaround, you can use Caps + Right key to navigate. [Widgets] Until we complete support for pinning in the new widgets board experience, pinning reverts you back to the previous experience You can find the announcement for the Dev build here and for the Beta build here.
  • Recent Achievements

    • One Month Later
      adnan.hebibovic earned a badge
      One Month Later
    • Week One Done
      adnan.hebibovic earned a badge
      Week One Done
    • Dedicated
      tesla maxwell earned a badge
      Dedicated
    • Dedicated
      Camlann earned a badge
      Dedicated
    • Week One Done
      fredss earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      629
    2. 2
      Michael Scrip
      224
    3. 3
      ATLien_0
      220
    4. 4
      +FloatingFatMan
      145
    5. 5
      Xenon
      135
  • Tell a friend

    Love Neowin? Tell a friend!