http://www.saunalahti.fi/~cse/in_mpc_0.92k.zip
[list]

Note that above plugin has some problems with tag type selection. Please use my version before Frank fixes the problem. And don't save APE 2.0 tags that require UTF-8 coding, it's not implemented yet.
http://www.saunalahti.fi/~cse/in_mpc_0.92k.zip

Finally... the headroom setting seems to work.

Seems that when the default replaygain with MPC/Vorbisgain/mp3gain is used (89dB), headroom value K-15 gives the closest results to MP3gain/Vorbisgain.

Case:
Is APE 2.0 going to be used with SV7? I'll add that to my list as well...

Interesting. After a few quick listening tests, K-14 now seems to be what previously was the disabled "0 dB headroom". K-16 in this 0.92k version sounds like "2 dB headroom" in 0.92h to me. (All tested with ReplayGain off, ClipProtect title based.)

Now the pics about the K-levels on http://www.uni-jena.de/~pfk/mpp/howtobecom...theageof14.html make perfect sense to me: K-14 really is needed now. I think i will use K-16 with this new plugin. K-20 sounds acceptable too, really not overly quiet like it used to.

Yeah.. suddenly all makes sense..

Well, this is great. I'll probably use K-14 or K-15, both are close depending on the case. But both are close enough to Mp3gain/Vorbisgain.

Thanks...

There definitely is a difference-I thought the k slider had previously only offered degrees of attenuation, but was afraid I was doing something wrong. I knew it was odd that I was using as much power with my external amplifier, and the suggested settings...What I experience using the K-scale slider and the pictures on the website you referred me to in the other thread jibe now-they didn't last night when I was reading it. It makes sense now since the lower k values actually boost the output by some dBs, which is what seemed to be happening in the examples...

As far as taggning goes, I've had no problems using Case's program (and Speek's frontend, of course)...

Thankyou Frank for the fix. Sanity has returned to my music listening levels, and the reality now matches the theory.

hmmm... anyone notice that the Bitrate in the 0.92k plugin Info section reads incorrectly now? I have a file that is VBR 183.6kbps for example but it says under Bitrate: CBR 186329 kbps !
Only seems to appear when I first start Winamp and before playing anything, if I start playing a song and then look at the info again it reads correctly.

So you have 12...13 dB into the direction "hit my brain directly" (louder + more/only distortions) and 11...12 dB into direction
"never clip or clip-prevent at all".

Frank-thank you for everything. I am trying not to be the dumba$$ here, but I have no idea what you meant by this above quote. Any clarification would be much appreciated. Thanks.

He just meant that if K-2 is the "hit my brain directly" and K-26 is the "never clip or clip-prevent at all", K-14/15 is there in between.

Thanks for reporting the bug, it was caused by my modifications. Please download the version from my site again, it's fixed now.

Yep, it will work even with SV4.

Fast work Case!
The tag type options is much improved now with 0.92k too. :-)

If Ape tags are used or auto selected in the plugin does it default to Ape v2.0?

Jeff

If you select APE 1.0, APE 2.0 or Force ID3 v1.1 your selected type is used.
Empty selection, ID3v1.1 and Auto check if tag information can be stored in ID3v1.0 / ID3v1.1 tag, if the information fits ID3 tag is used. Otherwise it uses APE 2.0.

Another K-related question.

Does anybody know what the follwoing code should do?

------------------------------------------------------------------
void
setvolume ( int volume )
{
mod.outMod->SetVolume (volume);
}

void
setpan ( int pan )
{
mod.outMod->SetPan (pan);
}
------------------------------------------------------------------

Have this something to do with the system audio level control?
(WAV output level, volume output level) ???

Both system calls do not change anything here. Moved via
the slider above the playtime slider.

They probably call Winamp's output plugin volume and balance control. They do have effect here, maybe you have disabled volume control from your output plugin.

If I remember correctly, those change the internal Winamp volume and leave the system volume untouched. Basically adding another volume control to the three that already exist....

EDIT: Just checked, I think those are for when the user has the "alternate volume control" setting enabled within the WaveOut plugin.

In Windows 2k/XP default plugins change system volume, at least on Creative labs cards. It can be disabled by activating Alternate volume control method.

Weird... neither settings change the system volume on my machine (XP Pro, Stereo-Link). The alternate volume control setting causes a delay when changing the volume on my machine though.

I made similar tests, when I comment the functions away I can't adjust volume at all, not with Alternative mode or without it. When the functions are active volume control works always.

I'm not familiar with your sound card, but can other programs control it's mixer settings? The alternate control manipulates PCM data directly so there is delay caused by buffer.

Yes... Media Jukebox can modify the system volume correctly. I never remember Winamp changing the system volume when I had my SB-Live... I was using Windows 2000 and the drivers supplied from Creative though.

Seems like Winamp's volume control is quite strange then. On my old Live! system volume was changed and now with Audigy it also changes. Different drivers don't seem to change the behavior. Only way to disable system volume changing is using waveout with alternate volume or directsound output.
Anyway, Frank should leave the functions in. Without them volume control does not work at all.

As long as I can remember (on NT/2000 systems) WinAmp changes the volume of the Wave device, at least when using the WaveOutput Pluging (except with Alt. mode).
--
Ge Someone.

In Winamp 2.79 at least waveOut it linked to WAVE Volume (by default), DirectSound is independent.