Re[3]: [MP3 ENCODER] Persistent JS problem, --nspsytune or not
NS Perhaps you are hoping joint stereo to be improved, but --nspsytune NS doesn't improve anything with joint stereo. NS --nspsytune is intended to improve result of vbrtest.wav and square NS wave with VBR. You can obtain vbrtest.wav from website of lame. And, NS --nspsytune improves CBR quality at bitrate like 128kbps. Perhaps you NS can easily notice difference with result of appluad.wav. RV thanks for the clarification. now I understand what nspsytune tries RV to achieve. RV I just asumed that it had something to do with JS because you told RV that it wouldn't work with the RH extensions. RV I guess the JS problem will be tackled at another time :) addendum: nonetheless JS influence or not, "--nspsytune" only has negative implications on the -V1 (-q1) I use. Perfectly possible 128k sounds better, just wanted to express that imo -V1 does not. I don't know what the cause is, but the improvements on lower bitrates are at cost of sound quality degradation on higher ones. -- Best regards, Roelmailto:[EMAIL PROTECTED] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
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[2]: [MP3 ENCODER] Persistent JS problem, --nspsytune or not
Hello Naoki, Sunday, October 08, 2000, 4:55:50 PM, you wrote: 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. NS I can't hear the joint stereo noise you mentioned. Maybe this is because NS there is differences among individuals on perception of sound. So, I NS can't fix it directly. NS Since there is no problem currently in regular stereo mode, I believe the NS problem is caused by (default) psymodel of joint stereo. NS BTW, why do you stick to joint stereo? I think people who pays serious NS attention to sound quality should not use joint stereo at high bitrate, NS at least with current version of lame. Even FhG doesn't use joint stereo NS at high bitrate. using VBR the advantages of JS far outweigh the disadvantages of JS. Velvet is for the moment the only track where JS consistently messes up. The noise is clearly audible and not in the 16kHz spectrum. Thing is I advice to use a headphone. Sennheiser HD-490 ($37)+SB128PCI ($25) makes it very audible. I am not the only person that hears this. I had quite a bit conversation about velvet with David McIntyre of QDesign trying to tweak their mp2/mp3 encoders on this track. All findings were confirmed. They only occur in the R channel. The distortions I talk about now are of the nature that anyone with the right equipment can detect them. It is not to put down all the hard work you put in -nspsytune, but I just wanted to signal that on -V1 this is a quite noticable quality degradation and size increase generally speaking. -- Best regards, Roelmailto:[EMAIL PROTECTED] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
[MP3 ENCODER] Persistent JS problem, --nspsytune or not
Hello Naoki, Saturday, October 07, 2000, 1:00:29 PM, you wrote: NS --nspsytune doesn't work correctly if RH extensions are enabled. I just tried on the version without extensions. I don't understand the extra benefit of the nspsytune. Please explain to me what flaw needed fixing in the older lame's and how you did it? I still find the sound not good, and the file only gets needlessly bigger. Maybe my standards are too high, but there is (and has been always) a serious JS problem on the velvet track (http://r3mix.50g.com): "lame -V1 -b128 -h -ms -q1": Sounds perfect to my ears. Average bitrate: 225,8 "lame -V1 -b128 -h -mj": rhytmic metallic 'static' noise over the complete length in the R channel. Average bitrate: 229,4 "lame -V1 -b128 -h -mj -q1": same rhytmic metallic 'static' noise over the complete length in the R channel. file is a bit smaller: Average bitrate: 223,6 "lame -V1 -b128 -h -mj --nspsytune": a much more disturbing kind of noise: it's alternating and sounds like some glitches. over the whole length of the piece and distributed in a set of 'bursts' of considerable volume. more sad news: Average bitrate: 245,4 On this track, the nspsytune does only have negative influence (imo). Not to be destructive or judgemental, but telling my findings is all I can do. Hopefully Naoki or someone has use for these. Respect and best regards, Roelmailto:[EMAIL PROTECTED] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
