Skip to main content


Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: --nsmsfix tuning with DM\'s (Read 4455 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

--nsmsfix tuning with DM\'s

Dibber, and others

There hasn't been much talk about the effect or possibilities of --nsmsfix switch.

Dib, I suppose you might have been working with it while finetuning your new presets?

I've been using --dm-preset standard with --nsmsfix 1.15 to slightly cut down the bitrate.

--nsmsfix tuning with DM\'s

Reply #1
yes, I am working on this.

--nsmsfix tuning with DM\'s

Reply #2
This thread is going slightly OT.

What I would be interested in is that COULD the optimal --nsmsfix value be higher than 1 (default of nssafejoint)?

--nsmsfix tuning with DM\'s

Reply #3
I already answered this question.  Yes, it can be used IMO without creating more problems, but only if other issues are addressed first.  This means that you have to work on fixing tonality issues and pre-echo more fundamentally if you are going to use a higher nssafejoint value.  This is part of what I've been working on.

Thread moved to technical section and OT content split off to this thread:


--nsmsfix tuning with DM\'s

Reply #4
I would really suggest that in a HQ setting safejoint is used as until now, value = 1.

The bitrate savings are marginal using values between 1.0 and value for joint stereo.