Re: [MP3 ENCODER] Persistent JS problem, --nspsytune or not
Roel> addendum: nonetheless JS influence or not, "--nspsytune" only has Roel> negative implications on the -V1 (-q1) I use. Perfectly possible 128k Roel> sounds better, just wanted to express that imo -V1 does not. Roel> Roel> I don't know what the cause is, but the improvements on lower bitrates Roel> are at cost of sound quality degradation on higher ones. I can't hear the joint stereo noise you mentioned. Maybe this is because there is differences among individuals on perception of sound. So, I can't fix it directly. Since there is no problem currently in regular stereo mode, I believe the problem is caused by (default) psymodel of joint stereo. BTW, why do you stick to joint stereo? I think people who pays serious attention to sound quality should not use joint stereo at high bitrate, at least with current version of lame. Even FhG doesn't use joint stereo at high bitrate. -- Naoki Shibata e-mail: [EMAIL PROTECTED] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] Persistent JS problem, --nspsytune or not
Hello, On Sun, 08 Oct 2000 11:24:19 Naoki Shibata wrote: > > Perhaps you are hoping joint stereo to be improved, but --nspsytune >doesn't improve anything with joint stereo. > --nspsytune is intended to improve result of vbrtest.wav and square >wave with VBR. You can obtain vbrtest.wav from website of lame. And, >--nspsytune improves CBR quality at bitrate like 128kbps. Perhaps you >can easily notice difference with result of appluad.wav. > Does this mean that --nspsytune as not as useful at higher bitrates and higher quality vbr settings (ie. -V1 -h)? At these higher quality settings and bitrates, can --nspsytune possibly do more damage than good? Basically I'm just wondering what the risks are when using this setting in different settings. I have used it in many different cases and sometimes it seems to help but others it seems to either make little differences, or actually hurt more than help. It seems the affect this switch has on the bitrate is somewhat erratic. I have seen it increase the file size quite significantly, but also decrease the file size as well. Dibrom 10% cash back on all your calls through 2000 at Lycos Communications at http://comm.lycos.com -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Re: [MP3 ENCODER] Persistent JS problem, --nspsytune or not
Roel> I just tried on the version without extensions. I don't understand Roel> the extra benefit of the nspsytune. Please explain to me what flaw needed Roel> fixing in the older lame's and how you did it? I still find the sound Roel> not good, and the file only gets needlessly bigger. Perhaps you are hoping joint stereo to be improved, but --nspsytune doesn't improve anything with joint stereo. --nspsytune is intended to improve result of vbrtest.wav and square wave with VBR. You can obtain vbrtest.wav from website of lame. And, --nspsytune improves CBR quality at bitrate like 128kbps. Perhaps you can easily notice difference with result of appluad.wav. Roel> Maybe my standards are too high, but there is (and has been always) a Roel> serious JS problem on the velvet track (http://r3mix.50g.com): I'm also aware that there is some problem with joint stereo of lame. -- Naoki Shibata e-mail: [EMAIL PROTECTED] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
