Skip to main content

Notice

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.
Recent Posts
21
Opus / Re: Opus and replay gain
Last post by Case -
Ergo, the header output gain is not "used by default", but is just used and there's nothing a user can do about it.
foobar2000 for example allows users to decide whether to use this info or not. It's tied to ReplayGain control.

In other words, this
And there is configuration option to even override the spec recommendation and force use of the tag over header value.
is only correct insofar as forcing any player to apply the album gain aligns with the spec recommendation, which is really not specified anywhere in the spec and is purely a developer judgment call.
The original specs made it clear that the header gain value is meant to be used for album gain: https://wiki.xiph.org/OggOpus#Comment_Header.
Quote
There is no comment field corresponding to Replaygain's ALBUM_GAIN; that information should instead be stored in the OpusHead 'output gain' field.
But as was mentioned, foobar2000 has had configuration for this since 2016. By default it retains the old behavior that Opus was born with and uses header gain field for album gain. But you can configure header to remain as null and then gain gets only stored in the two R128 gain tags.

I think your problem with foobar2000 is based on some huge misunderstanding. It fully follows the specs and allows user full control of the gain behavior. Both for encoding and decoding.
22
Opus / Re: Opus and replay gain
Last post by doccolinni -
We have been here from the beginning of Opus. In the discussions on the forum and IRC it was clear the authors don't want peaks included. So it should be respected.

That doesn't contradict literally anything I've said. From the standard itself it is clear that the authors "don't want peaks included", whence the use of "SHOULD NOT". But the fact of the matter is that the standard doesn't forbid the inclusion of peak values, it only discourages it.

I haven't said anything incorrect and you haven't disagreed with me, yet you phrased what you said in a manner that indicates disagreement. Kinda confusing.

The specs you quoted tells the reason "A muxer SHOULD place the gain it wants other tools to use by default into the 'output gain' field, and not the comment tag."
(...)
Could you please educate what the problem is?

Sure!

First of all, a specific loudness normalisation gain should not be something the muxer "wants other tools to use by default". Whether track- or album-based or even no (this one is important - see next paragraph) loudness normalisation should be used should be up to the decoder's/player's settings.

Furthermore, "use by default" out of context is misleading here, because it indirectly implies that the "other tools" can opt to not apply the header output gain. Whether that is true or not remains in a bit of a logical limbo, because the standard states:
Quote
       Players and media frameworks SHOULD apply it by default.  If a
       player chooses to apply any volume adjustment or gain
       modification, such as the R128_TRACK_GAIN (see Section 5.2), the
       adjustment MUST be applied in addition to this output gain in
       order to achieve playback at the normalized volume.
The very first sentence makes it seem like a player can indeed decide not to apply the header output gain ("SHOULD").
However, the very next sentence means that any player that does any volume control whatsoever (i.e., any player) can not decide not to apply the header output gain ("MUST").
In my experience, even a command-line tool like opusdec which actually does not do any volume control can not opt to not apply the header output gain.

Ergo, the header output gain is not "used by default", but is just used and there's nothing a user can do about it.

In other words, this
And there is configuration option to even override the spec recommendation and force use of the tag over header value.
is only correct insofar as forcing any player to apply the album gain aligns with the spec recommendation, which is really not specified anywhere in the spec and is purely a developer judgment call.
24
WavPack / Re: WavPack 5.5.0 Release Candidate
Last post by itisljar -
FLAC has also seen use to compress laserdisc rips. There are probably tons of other electrical signals with lots of spatial redundancy that can be compressed well, so I suspect that won't be the last of it.

It's first time I've heard of this, it's very interesting! I'd like to try it out, but I don't know if there is some sort of demo/free laserdisk image I can use for that.
25
3rd Party Plugins - (fb2k) / Re: Library Tree Discussion
Last post by WilB -
@yeyo

If possible I would like to keep an auto check of features.

So can we have one more go before I'll likely make it a manual setting in panel properties (which only Wine users etc. whose systems don't suport ShowHtmlDialog will have to set on a one time basis)?

1) In v1.3.2 beta would you mind replacing popupbox.js in ...foo_spider_monkey_panel\packages\{E85C9EF0-778B-46DD-AF20-F4BE831360DD}\scripts with the @regor  version above to see if that fixes the issue?

2) If it still fails to open options, can you insert the following return true on line 53, after isHtmlDialogSupported() {,  of the @regor popupbox.js to bypass the check & confirm that the options then opens correctly.
Code: [Select]
	isHtmlDialogSupported() {
return true;
26
WavPack / Re: WavPack 5.5.0 Release Candidate
Last post by Porcus -
There was such a discussion here some time too. @polemon, did you end up with WavPack or something else?   :)

MPEG-4 ALS supposedly supports 65536 channels. I have not tried to max it out.  (Also, I did at one stage manage to create .als files which would make the decoder consistently crash, so it's not production ready ... and will likely never be.)
29
General - (fb2k) / Re: Foobar won't remove the artwork
Last post by nothingness -
Hi, a simple solution is using a little program called AlbumArtDownloaderXUI to download better artwork for the albums. Foobar2000 as default always will prefer the images with more size and higher resolution. So, if your problem is that the images are embedded in the metadata of the audio files and you want to not see them, download a bigger image quality with that utility and problem solved.

A little tutorial of how you can integrate AlbumArtDownloaderXUI to Foobar2000 ;)
Thanks, but I already used it long times ago.
30
3rd Party Plugins - (fb2k) / Re: Library Tree Discussion
Last post by regor -
@The Chief  @yeyo or anybody else affected by the options dialog issue. I've uploaded a test version here. Click the download button. Please can you confirm that the options dialog always now opens correctly? I'm not able to reproduce the issue hence the test version, but then I don't have win11.

The features check is now done on the first use of the options dialog during a particular session, rather than during start-up as suggested by @regor . If it still isn't robust, then likely I'll remove the features checker & add a manual setting to panel properties for affected users, e.g. those using Wine.
Feedback from the test version: when two library trees are used in a topic interface, only one of them can be opened, and the other still cannot be opened.
PS:It is recommended to completely remove the function checker.

Testing exactly the same, works with no problems on win 10. Did you update both panels? Does the console warn about options not being available?
Spoiler (click to show/hide)

It makes no sense to have one working and another one not working due to the same function, and in any case if that's the problem then that's a SMP bug which should be fixed (not just remove it).

EDIT: have refactored the code (separated clipboard restoration from the check) and reused your parent doc html file. If it fails with that file, then options popup will simply not work properly in any case (unknown reason), so it will be SMP's/win 11 fault and should be fixed.
Code: [Select]
	isHtmlDialogSupported() {
if (this.soFeat.checked) return this.soFeat.gecko && this.soFeat.clipboard;
else this.soFeat.checked = true;

if (typeof doc === 'undefined' || !doc) {
this.soFeat.gecko = false;
}
if (this.soFeat.gecko) {
let cache = null;
let clText = 'test';
try {
cache = doc.parentWindow.clipboardData.getData('Text');
} catch (e) {}
try {
doc.parentWindow.clipboardData.setData('Text', clText);
clText = doc.parentWindow.clipboardData.getData('Text');
} catch (e) {
this.soFeat.clipboard = false;
}
if (cache) { // Just in case previous clipboard data is needed
try {
doc.parentWindow.clipboardData.setData('Text', cache);
} catch (e) {}
}
if (clText !== 'test') {
this.soFeat.clipboard = false;
}
} else {
this.soFeat.clipboard = false;
}
return this.soFeat.gecko && this.soFeat.clipboard;
}

Attached the file in case anyone wants to test it.