Announcement

Collapse
No announcement yet.

Winamp 5.9.2 Released

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NJK
    replied
    Originally Posted by -Px- View Post

    Sorry, was that announced somewhere?
    Hello Admins, In the not too distant past, the WINAMP Windows desktop version download address was: https:\\download.nullsoft.com/winamp/client/[WINAMP-FILE-NAME.exe] When removing the file name, this directory would show a listing of WINAMP installers (with full names) available for downloading. https:\\download.nullsoft

    post #9 by rlerouxWinamp

    "Winamp employee here. While there hasn't been any formal communication, the desktop player development is effectively on hold
    since the departure of DJ Egg and the remaining of the desktop team after the release of version 5.9.2.
    You can check https://www.llama-group.com for the latest company info.
    TLDR : We are currently under Judicial Reorganization.
    Winamp's parent group sold Shoutcast to be able to repay old debts.
    There have been layoffs affecting the development of the desktop player.
    We're focused on building a modern web and mobile platform.​"

    Leave a comment:


  • -Px-
    replied
    Originally Posted by NJK View Post

    As you might not know, there is no development team anymore working on the desktopplayer.
    DJ Egg isn't around anymore so changes are your error report is landing on a pile that isn't going to be touched any day soon.
    Sorry, was that announced somewhere?

    Leave a comment:


  • NJK
    replied
    Originally Posted by M.D-78 Odysséus View Post
    Greetings.
    I'm trying to configure the Error Send Reporter in Gmail, following these steps, but I'm not successful. ​
    As you might not know, there is no development team anymore working on the desktopplayer.
    DJ Egg isn't around anymore so changes are your error report is landing on a pile that isn't going to be touched any day soon.

    Leave a comment:


  • M.D-78 Odysséus
    replied
    Greetings.
    I'm trying to configure the Error Send Reporter in Gmail, following these steps, but I'm not successful. @
    Can you help?
    I'm using my gmail login and App Password works on Hard Disk Sentinel but in Winamp there is no option to select SSL and TLS (STARTTLS), how do I get around this problem?​

    Leave a comment:


  • ViRGE
    replied
    Originally Posted by Pawel View Post
    I see there are many people who really don't know what is happening here...

    It is not a secret, that Egg is not working for Winamp anymore. He was a person who really cared about Winamp development. But not anymore. They decided to put it all on New Winamp Media Player (https://www.winamp.com) and access from mobile apps (Andorid and iOS), currently in beta tests.
    As a long-time lurker, I appreciate someone explicitly noting this. I had no idea that Egg was gone; I just figured he went incognito again.

    Not that this is in any way [i]good[.i] news. But thanks for the heads up.

    We live, we die, we live again, and then we die again!

    Leave a comment:


  • Pawel
    replied
    Originally Posted by NJK View Post

    if it's the same as the one that Dr0 is working with in his wacup project than it's going to be a problem with codex that were leased and that lease has ended.

    As far as I know, DrO is not working with any Winamp sources. WACUP was based on latest AOL/Nullsoft release (and it is gonna change and be fully independent media player).


    Originally Posted by rlerouxWinamp View Post

    Indeed. Our source repo contains (often very old) licensed library code that we most probably can't publish as open source. The last desktop team did a good job refactoring most of those away (using vcpkg a lot), but until we've audited everything, we cant be 100% we won't get in trouble if we release the source-code as-is.

    I've proposed to release what we can (meaning all files we 100% identify as ours) to the community so there's at least something out there you guys can legally use (even if only as reference, since it probably won't build).

    Management is open to the idea, but we haven't had time in our roadmap to fit this just yet​.


    Making Winamp Open Source is a great idea. Maybe tthe best what you can do for Winamp. Modern listeners rely on streaming services and mobile devices. We all know it. But, there are still plenty of people who listen to their own collections, from their own discs. They don't need the Internet to listen to media - all they need is a fast, powerful and reliable player like Winamp.
    Yes, licensed code is a problem (I thought most of licensed code was removed in 5.9x line)... Certainly, trying to make the source codes public makes a lot of sense.

    However, Is the Winamp community ready for such a gift? Are there people who want and are able to use it for the benefit of everyone? I hope so...

    -Pawel

    Leave a comment:


  • rlerouxWinamp
    replied
    For the time being.

    Leave a comment:


  • NJK
    replied
    Originally Posted by rlerouxWinamp View Post



    Management is open to the idea, but we haven't had time in our roadmap to fit this just yet.
    Does this roadmap abandon the desktop Winamp and are all bets placed on the online version??

    Leave a comment:


  • Mikey7
    replied
    Originally Posted by rlerouxWinamp View Post
    Management is open to the idea, but we haven't had time in our roadmap to fit this just yet.
    It might lend legitimacy to particular rogue build that I won't mention here. In any event, it would be the boon needed to keep the 5.x desktop Winamp going into the future.

    Leave a comment:


  • thinktink
    replied
    Originally Posted by rlerouxWinamp View Post

    Indeed. Our source repo contains (often very old) licensed library code that we most probably can't publish as open source. The last desktop team did a good job refactoring most of those away (using vcpkg a lot), but until we've audited everything, we cant be 100% we won't get in trouble if we release the source-code as-is.

    I've proposed to release what we can (meaning all files we 100% identify as ours) to the community so there's at least something out there you guys can legally use (even if only as reference, since it probably won't build).

    Management is open to the idea, but we haven't had time in our roadmap to fit this just yet.
    Ok, that's exciting but weird to hear.

    Leave a comment:


  • zumer
    replied
    It would be a very big gift to the community. The Winamp desktop must not die. We are ready to respect your copyrights.​

    Leave a comment:


  • rlerouxWinamp
    replied
    Originally Posted by NJK View Post

    if it's the same as the one that Dr0 is working with in his wacup project than it's going to be a problem with codex that were leased and that lease has ended.
    in a perfect world it should be open source and one could build with the lastest release but it's not a perfect world as we all know
    Indeed. Our source repo contains (often very old) licensed library code that we most probably can't publish as open source. The last desktop team did a good job refactoring most of those away (using vcpkg a lot), but until we've audited everything, we cant be 100% we won't get in trouble if we release the source-code as-is.

    I've proposed to release what we can (meaning all files we 100% identify as ours) to the community so there's at least something out there you guys can legally use (even if only as reference, since it probably won't build).

    Management is open to the idea, but we haven't had time in our roadmap to fit this just yet.

    Leave a comment:


  • Myhrddin
    replied
    I don't know if this could help anyone who's having trouble with crashing etc but, if you had a tool that would scrub the registry after uninstalling winamp and then reinstall it maybe that would solve the issue. I've used RevoPro Uninstaller for years and it makes a backup of the registry and does a system restore point when I go to uninstall something in case I want to undo the uninstall I'm about to do. In the past, having it remove residual registry entries as well as files that didn't get removed has cured issues with other programs.

    I'm not sure this would be the solution for every problem but, it's possible that an actually clean install would do the trick.
    The other thing I have done with each new Winamp iteration is to install it into a new location that I usually differentiate by tacking on the version number to the end of the winamp folder it's goin' into.

    Just a thought. Hope this might help someone with their issues.

    *fingers crossed that development on the Windows client/app/program of Winamp continues unabated and that whatever friction may be happening behind the scenes also gets resolved in a positive fashion that lets things continue moving forward.

    ~Myr

    Leave a comment:


  • Mikey7
    replied
    Well...i guess all good things come to an end. Pity.

    Leave a comment:


  • NJK
    replied
    Originally Posted by Ingvar View Post
    thinktink​, as far as I know, the Winamp sources have already been leaked in 2021, but I don't know what version of Winamp it is.​
    if it's the same as the one that Dr0 is working with in his wacup project than it's going to be a problem with codex that were leased and that lease has ended.
    in a perfect world it should be open source and one could build with the lastest release but it's not a perfect world as we all know

    Leave a comment:

Working...
X
😀
🥰
🤢
😎
😡
👍
👎