Winamp 5.7 Beta 13, build 3444 (with Winamp Cloud Beta)

[lostinsound]

@lostinsound

Hmm, I can't seem to reproduce any problem there. The Cancel button for the ReplayGain results dialog is working ok for me.
It could be something to do with the "Save last position" implementation...?
(just noticed that last position is remembered for the Calculating RG dialog, but not for the Results dialog).

That's strange. I tried it in Safe Mode and it didn't work then either. I also ran the installer for the last build (3392), and the Cancel button worked fine in that one.

[MrSinatra]

Winamp > Prefs > Cloud Library > Options tab: Reset Cloud Library button

Confirm

Close Prefs

You then might need to logout & login again (via SignIn node in ML), and start again from scratch.

Your Cloud account should be automatically recognized (after logging in);
Your pc/local library should be automatically added
(you'll need to wait for the full scan to complete, and the "first pull completed" message to appear in Logging tab);
Winamp Storage view & Cloud web player will be empty - until you transfer songs again...

Egg,

I followed these directions precisely, and everything is the same, meaning I have the same problems, and the 3 items I previously had uploaded are STILL there. it feels as if nothing happened, but something seemed to be happening, as it took a while to finish.

so, i'm at a loss, what do you suggest?

[DrO]

@lostinsound

Hmm, I can't seem to reproduce any problem there. The Cancel button for the ReplayGain results dialog is working ok for me.
It could be something to do with the "Save last position" implementation...?
(just noticed that last position is remembered for the Calculating RG dialog, but not for the Results dialog).

there were a few quirks with this when the save position changes were made which slipped through. it should all be resolved as part of the next labs build including not all instances of the results dialog being remembered.

That's strange. I tried it in Safe Mode and it didn't work then either. I also ran the installer for the last build (3392), and the Cancel button worked fine in that one.

safe mode wouldn't have any effect on this as that only blocks 3rd party plug-ins (e.g. gen_jumpex.dll is not loaded in safe mode), not failings within the native plug-ins.

@lostinsound...i can reproduce it..i have to end task winamp from Task Manager

if you get the main right-click menu to appear, then 'exit' on that will work to close Winamp properly without blowing it out of the water as you're doing.

[DrO]

1\ Nice to see that Winamp Installer nags you to close the running version of Winamp. Any chance you can just pump a close message at Winamp via Windows Messaging for the truly stubborn idiot who refuses to close Winamp? Could have a button on that dialog to do it? (Or does the <ignore> implement a cattle prod to the delicates? That should work...)

force closing Winamp can cause other issues and so it's better to just not allow the install process until it's confirmed it has closed. but a fair point and something that will likely be looked at later the next time we need to make an noticeable changes to the installer.

2\ Nice to see the "Explore item(s) folder" on the playlist menu. Any chance of a "not found" reply? I have a playlist with three instances in it where I get zero response.
a\ An online stream (which is not available any more)
b\ Tracks that have been deleted from my hard disk.
c\ Tracks on my server but the server is not logged in.

Winamp didn't crash or hang on the above. It just did nothing... which would confuse some ID-10T users. A message box which pops up and says something like "I pity da fool who tried to look for something that ain't there..."

it had been there for years if you were using the Essentials Pack, was just worded differently when it was done via the FFOD plug-in instead of natively.

alas the OS API used for it doesn't indicate a difference without us having to do extra processing on what is being parsed to determine what may or may not open correctly in Explorer window(s).

First the Ts and Cs bit needs you to "Press next to accept"... but the button is labelled install.

i'm not seeing the next vs install thing you mention... a screenshot maybe?

And second... there really is a very naughtily confused set of ticks and hoops you have to jump through to NOT get this junk. You have to choose "Custom install" and then the only option in "custom" is to untick the option to install it.

on the components page, tap the up arrow to get the appropriate install type.

I know the Winamp Devs have little control over these extras... but there is a point that the people designing that page need to think about their average users who will get confused with this option page. Very weasily done.

no comment indeed

[DrO]

and umm i want to ask, will all equalizer preset will got an update bcause when i hear a lossless flac audio when i try all preset there no good preset i found except Flat preset

the presets will not be updated as there's no reason to do so. they're just there as something to base things from and if it's better for you when it's disabled, then that means you've got you audio setup properly - using the EQ is really for dealing with limitations in either specific audio formats or audio hardware issues e.g. headphones with limited range, etc.

[DrO]

Thanks for the new beta. Winamp did take a lot more time to install when loading the "emusic bundles" and the winamp toolbar options. I thought initially that it was my antivirus acting up.

--Running Windows 8 64 bit with 8gb ram--

as Egg also explained, the optimising changes don't have any effect on those pages which are server-side dependent.

the aim of the optimising stage is to improve loading times by preventing the OS having to move the plug-in dlls around more in memory than is needed when loading (which on older systems could be noticeable). however, it seems that there are cases where the OS API used for doing this can effectively corrupt the dlls causing Winamp to not load (along with it messing up most non-MSVC compiled dlls).

so until / if we can determine what is causing the OS API to mess up the native dlls, it's better to risk slightly slower loading times (potentially on older machines) vs Winamp just not loading at all. as there's been other changes to loading handling over the years since that was introduced which help as well. as from testing in a resource crippled virtual machine, there was no noticeable difference in loading time between the optimised and non-optimised installs (though that doesn't mean it may not be at complete odds for others).

[Batter Pudding]

force closing Winamp can cause other issues and so it's better to just not allow the install process until it's confirmed it has closed. but a fair point and something that will likely be looked at later the next time we need to make an noticeable changes to the installer.

I didn't mean a "forced" close. I just mean send the WM_CLOSE message into the message loop. (Rusty memory... is it WM_CLOSE or what ever the message is when you press the EXIT button in the application)

alas the OS API used for it doesn't indicate a difference without us having to do extra processing on what is being parsed to determine what may or may not open correctly in Explorer window(s).

Okay... if it causes extra work it isn't needed. Just idle thoughts from me. I make constant use of the version of this in the main Media Library, but never clicked it before on the Playlist as I didn't realise that is what "Jump To File" meant. ARF!! I assumed it was going to make my PC jump up and down in time with the music after installing one of those hydraulic suspension systems....

i'm not seeing the next vs install thing you mention... a screenshot maybe?

This only happens on the RELEASE version. Not the beta. I have attached an image of the message box. Notice the very small grey print which refers to the EULA mentions NEXT instead of INSTALL. Therefore it is techncially impossible to "agree" to the EULA and Privacy Policy.

on the components page, tap the up arrow to get the appropriate install type.

I am not talking about your Winamp installer options. I was talking about the weasel options on the crudware page. See screenshot for example. Only once you put that tick on the Custom Installation option do you realise that this thing is optional. A dialog box designed by a marketing person aimed at idiot lusers - but please don't comment on that as that is just my personal opinion. (You may notice I don't have much of an opinion of marketing people...)

I am not trying to set off a debate about crudware as I understand why it is there. But any crudware that kicks off a warning from McaFee will be loosing Winamp customers and damaging reputation. IMHO I think it also needs to at least be worded correctly to enable potential users to make correct decisions. At least treating users with some level of respect.

[DrO]

yeah it is a WM_CLOSE message, but as i found from the JTFE installer over the years, doing that causes some other plug-ins to baulk and then Winamp doesn't close properly (even if it can close ok when done via the user). hence it's easier to just nag to close but not do it - it also can get messy if say a podcast is downloading and the ok to quit prompt doesn't fire correctly as could happen on some older versions.

oh ok, is from the bundled stuff, thought it was something within our own pages, alas that's part of the OpenCandy 'fun' and is by design meant to be weasly to get people to install the stuff (which i don't like either, but sadly, installs via that do help pay the bills though i do agree at the cost of users either updating or continuing to use Winamp).

With the eula thing, it's likely a simple mis-match between the default wording in NSIS installers and what we do. have made a note to check it out when we do a final build (but has likely been like it for years and years and years ).

[Batter Pudding]

yeah it is a WM_CLOSE message, but as i found from the JTFE installer over the years, doing that causes some other plug-ins to baulk and then Winamp doesn't close properly (even if it can close ok when done via the user). hence it's easier to just nag to close but not do it - it also can get messy if say a podcast is downloading and the ok to quit prompt doesn't fire correctly as could happen on some older versions.

AH... it's always them pesky plugins. You have the sensible option - pass the buck to the user. (And I promise not to now go and be a stubborn little tester and press ignore... as no doubt chaos will ensue...)

oh ok, is from the bundled stuff.....

Anything that pays the bills is good. Us seasoned users are used to the tick boxes in products. Just someone may need to shout at McaFee to stop them issuing bogus malware alerts on the embedded AVG installer. (See the other thread about this)

I only picked up on the wording of the "click NEXT" thing as my eyes are in full-on pedantic testing\proof reading mode.

I did have a bit of a chuckle as the description of TuneUp Utilities and how it will "help make sure your computer is running to full capacity". Which is, at least honest. The way I read that is it fills the PC up with crud to the top instead of making it more efficient.

[DrO]

now I get a new crash, when I click on the "add" button inside the playlist to add new files/folders. This time a string operation (CharUpperBuff) fails:

should be fixed as well for the next labs build.

[Juanus]

I am not sure how I made this happen. But all of a sudden my phone showed up twice. (see screen shot)
I can remove each of them individually and then close Winamp and when I open it again just one phone shows up. (Still haven't installed my VPN)

[ryerman]

Hi Batter Pudding

...I make constant use of the version of this in the main Media Library, but never clicked it before on the Playlist as I didn't realise that is what "Jump To File" meant.....

Maybe you're confusing "Jump to file" with "Find file(s) on disk" (FFOD)
"Jump to file" works on Playlist entries within Winamp. It became a native plug-in.

I believe that FFOD was only available for the Playlist if the 3rd party (DrO) plugin was installed.
Apparently, it has now become native and reworded to "Explore item(s) folder" on the menu.

[DrO]

FFOD had only been adding the menu item for a few years as the core of the plug-in had already been rolled into Winamp natively since 5.58 (though the plug-in provided the core on older 5.5x installs).

when i killed my plug-ins, changing the wording of the FFOD menu item to be the same as other parts of the library, etc made sense to do, hence how it is now.

and JTFE i still treat like a 3rd party plug-in (despite it having been included in Winamp longer than a lot of the other plug-ins and sits on the fence of being 1st party) since it's still under my sole ownership and so i decided not to make it be loaded under 5.7's safe mode (which is only for 100% Nullsoft plug-ins).

[Batter Pudding]

Ah... now I get it. So "Jump to disk file found on explorer" is nothing to do with NASA's shuttles or bad car suspension. And I have been confusing two different features over the years.

I have only been using Winamp for 15 years so don't know all the features yet. It's a media player with so may different user's requests added. I just play albums... but am looking for the "Make me a cuppa" add-on.

I'll play with Jumping Files when I next get five mins. I can see it is for making temporary "play these tracks next" playlists from the main playlist. Clever. And insanely customisable!

I can tell how old it must be as a plugin as now I start it the dialog box is tiny - designed for tiny old screens of the past. Have you considered making it a little bit bigger so the text fits on the buttons?

(Quickly ducks and runs before crockery is thrown at me by DrO....)

[Koopa]

I have found 2 problems using Beta 7:

1) Graphic Bug (see Attachment): The grey area between the playlist in the library and the active playlist hasn't been there in Beta 5/6. Thus i can't see the number of songs and the playtime of a saved playlist anymore.

As DrO already said, I had fixed the issue already in one of the Winamp-de-de.wlz updates.