Winamp News

[DrO]

MarkRH: i've made a change which will allow for it to be present and install without it causing a crash which was happening due to setup trying to load the gen_*.dll plug-ins, see if it adds a custom option during install and then unload it afterwards.

it's that last bit which for some reason is causing the gen_Wake_up_call.dll plug-in to freak out so i've changed it so we leave the 3rd party plug-ins loaded all the way through setup (which increases the memory usage a bit but makes things more stable).

so that should solve that issue at least with your specific usage (and make updating easier ).

[wojtek1986]

One more question: Are you going to release new Winamp also as portable app (without installer)?

[DrO]

probably not. maybe a bit more will be looked at to making it easier for others to create portable installs at some point, but with everything else that needs to be done (once i've gotten SHOUTcast duties out of the way), i'm not going to do anything towards portableapps support, etc any time soon.

[wojtek1986]

Thanks for quick answer.

[justin7674]

Hi, I am a developer looking for some projects to help in. I am interested in audio fingerprinting technologies and I was wondering if you guys ever found a replacement to Gracenote services. If not I would be interested in working with you guys on a solution.l

[M3wThr33]

we still get requests from people who bought the pre-AOL purchase shareware licenses expecting to get a pro key because they'd paid for the shareware version (was one only last week) so i'm expecting the negativity when things are released and more people find out.

it was never clear what would happen with a v6.x release when it came to licensing, though i suspect it would have been an option to upgrade for a small cost like a few $ for existing 5.x pro users.

one thing that will be interesting is seeing what happens to all of the "Winamp + crack" torrents and downloads floating about as there won't be a need for such things anymore (but i suspect they'll still be floating around as there's been 6.x version ones for well over a decade that i remember seeing).

At one of my older companies, the game was only released on Direc2Drive. It had literally zero DRM. Once installed, it ran. (It was merely released to fulfill a contract)

Sure enough, it ended up on torrent sites with all these complicated cracks that it never needed.

[musicf8]

At one of my older companies, the game was only released on Direc2Drive. It had literally zero DRM. Once installed, it ran. (It was merely released to fulfill a contract)

Sure enough, it ended up on torrent sites with all these complicated cracks that it never needed.

I remember seeing a lot of keygens for nagfree shareware (inc winamp 1.x) back in the day on AOL server chatrooms. Seemed kind of odd to get a keygen for a program where you don't gain anything by registering except to help out the developer.

[duke2010]

Please please include built in support for Asio audio output on the new Winamp.

Before it was only available via plugin and it wasn't great. Winamp will never challenge the audiophile players without Asio support.

Im looking forward to the new Winamp, I think it was overdue a refresh. Good luck!

[DrO]

there are no plans to natively include asio support. including a native wasapi output plug-in would be more appropriate and that's not on the current plans either.

if the 3rd party plug-in isn't good, then that's something which the author needs to be resolve though what you mean by "it wasn't great" is somewhat subjective.

[duke2010]

there are no plans to natively include asio support.

Oh, that's a real shame. Is it really that hard to implement?

There are an army of people using Foobar and paying for players such as Jriver just to get Asio support. They will never use Winamp without Asio support (including me!). You could even charge for it as a premium feature.

but anyway thanks for the quick reply!

what you mean by "it wasn't great" is somewhat subjective.

It was a long time ago I tried it but from what I remember it was struggling with different sample rates etc. It was a very beta plug in. Would have been much better if it was built in so when you setup the software you can just switch on Asio
.
Think of all the audiophiles out there with their fancy DACs. They wont use this software without Asio support to bypass the Windows and driver mixers.

Im not being difficult here, its just how it is! But anyway thanks for the replies, I will still give the new Winamp a look when it comes out.

[DrO]

i have no idea how difficult it is to implement but with everything else that needs to be re-built / added to a new Winamp client, implementing additional output plug-ins when it's not an area i'm that knowledgeable in makes it an unknown (and anything like it would probably take a while to get to being useful - just as i've seen be the case with any of the Winamp wasapi plug-ins or even those for foobar2000, etc).

as you cannot just magically implement something and just because it's 'official' be super wonderful and work perfectly - it took years for the DirectSound plug-in to become stable.

and as has been mentioned only a few posts prior to yours, there will not be a pro / premium / paid version of Winamp so we wouldn't be charging for something like it anyway.


as for the 3rd party plug-in, that's down to the author of it. and it's not like someone else who has an interest in such things could look to make a different plug-in, but as 3rd party plug-in development is effectively dead, and with everything else we've got to do, Winamp is probably not the right solution for those sorts of people as you describe them.

and trying to have Winamp be a tool for everyone in such a manner for what is effectively a niche feature is not something that i'd expect to see happen (as it's a lot of work for a very small number of people). so i know you're not trying to be difficult, but a bit of reality needs to be maintained and just because Winamp development will continue, it doesn't mean everything from dead / unsupported 3rd party plug-ins including the kitchen sink will be natively implemented.


whereas things like playlist searching (as per attachment) is something that is often requested and benefits a lot more people. it's painful juggling act at times and not everyone will be happy but that's just how things have to be to achieve something rather than nothing.

[duke2010]

That all sounds fair enough, I hope it all comes good!

(Maybe keep it in mind for later versions )

[Juanus]

whereas things like playlist searching (as per attachment) is something that is often requested and benefits a lot more people. it's painful juggling act at times and not everyone will be happy but that's just how things have to be to achieve something rather than nothing.

That's a cool new feature. Will you be able to search through every playlist if you have the playlist node highlighted or just the currently active playlist?

[Victhor]

[DrO]

That's a cool new feature. Will you be able to search through every playlist if you have the playlist node highlighted or just the currently active playlist?

i still need to get per-playlist searching working. as it was something i quickly looked into on sunday night to see what would be needed and got it to the point where it can do what's shown on the right of the attachment.

as for doing inside of all playlists, i was thinking about that as well and it can be done, is just how best to provide the search results. as my 3 initial thoughts are:

• just indicate the playlists which match (setting to bold or something like that) and / or a number / column to indicate the number of matches
• provide a sub-pane which shows the matches and the parent playlist (so much like the library searches for the tracks pane, but with the playlist name in the first column)
• provide the matches as child items of the playlist i.e. like a tree (which could get very messy with expanded states, etc but it makes it clear what relates to what)

of those 3, i think the second one is the one i prefer (as it better matches other aspects of the library and is a bit simpler to implement), though i quite like what the third one (using a tree) could look like.