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
3
Development - (fb2k) / Re: New filesystem redirector service for relative paths in portable install
Last post by Peter -
Quote from: Montchenot on
"Could not open folder: The parameter is incorrect. (0x80070057)"
Still present in public 2.25 preview, from Playlist View and ReFacets
Files appear to get properly updated but the folder cannot be open by right clicking
Sorry, works for me now.
More details please: filesystem path of your portable install, filesystem path of your media folders and problem files that it refuses to show in Explorer, so I can recreate same exact scenario.
4
Other Lossy Codecs / Re: SBR usage of xHE-AAC at 72kbps, 80kbps, and 96kbps
Last post by Klymins -
Quote from: celona on
Write to Poikosoft (see https://www.poikosoft.com/contact ), it is a mistake, SBR should be used up to 36 kbps in mono VBR (56 kbps in CBR), up to 40 kbps in stereo VBR with PS, up to 64 kbps in stereo without PS, both in CBR and VBR.

In my opinion the maximum limit is in CBR with SBR for bitrates lower than 64 kbps in mono or 72 kbps in stereo, in VBR for bitrates lower than 48 kbps in mono or lower than 64 kbps in stereo with PS, lower than 96 kbps without PS. But it would be an exaggeration to keep at bay the requests of other users more demanding on numbers than on the sound obtained.

Thank you though I think this answer is rather mazy and probably containing some mistakes, but in this page poiko said "All formats supported by the xHE-AAC encoder are listed in xHE-AAC configuration." which was unrealistic from the beginning and now I also remembered this reply of yours - what the heck?
5
3rd Party Plugins - (fb2k) / Re: Biography Discussion
Last post by regor -
As you may expect... your report is vague at minimum. If you expect more updates or help, provide more details.

There have been zero changes related to the usage you described and again zero changes on mod 2 (except the auto-cycling bugfix, also present on original bio).  If there is something wrong, it was also on previous updates.
Correlation does not imply causation

Your skin and particular usage is also clearly beyond the scope of most packages. And different foobar versions also behave differently, have been multiple reports about streaming TF being broken on latest updates for example.
6
3rd Party Plugins - (fb2k) / Re: Biography Discussion
Last post by Defender -
Quote from: regor on
Bio and Library Tree updates have unrelated fixes/improvements.
I had a lot of issues with Bio MOD 1 (I am running 3 instances in various places in the skin at once) especially when streaming.
When I downgraded your Bio Mod 1 a month ago to the original script I had a *lot* less problems.

I now installed BIO MOD 2 and have been streaming and switching between streams like crazy. No issues so far.
I'll keep you posted.

Thx.
7
General Audio / Re: The "business model" of hybrid codecs with correction files
Last post by Brand -
Quote from: skamp on
  • Correction files are supposed to live in the same directory as the lossy files, which makes it very inconvenient to copy an entire lossy collection to a DAP (say, my iPhone). I could write a BASH script (and I just might) to move lossy files and correction files to twin directory structures. That way I could just drag and drop the lossy directory structure to my iPhone. But I also would need to run that script in reverse to join lossy and correction files back together.
No need to do that (bold part).
You can just copy the whole hybrid music collection with all of its folder structure to another device with a filter that excludes *.wvc files, for example. There are file managers, file copying apps and scripts that let you do that easily. That is assuming the target device doesn't have some restrictions in terms of what software can access it.

And that's the nice thing about the hybrid approach. Having only one set of files to maintain and not needing any additional conversions, you just copy the lossy part over to any space-constrained device.

But, as you mentioned, the downside is that the lossy part of the hybrid codec (using WV here as an example) is just not very efficient. I didn't do much testing myself, but from what I've read, AAC achieves the same quality at half the bitrate. And it also decodes faster, for what it's worth.
8
3rd Party Plugins - (fb2k) / Re: Biography Discussion
Last post by regor -
As far as I know, scripts affected by new protocols for relative portable libraries are mine (in particular Playlist-Manager-SMP), which have all been updated to work on foobar 2.25+ yesterday (check nightly).

I can confirm Find & Play may also be broken on 2.25; no idea how m-tags works, but there is a '$info(@REFERENCED_FILE)' reference which I presume may output file-relative too (*). Neither I have the interest, nor setup to test it (portable + foobar 2.25 + relative tracked library + m-tags + some kind of tracks referencing m-tags being used by the script). The feature would probably affect how external items, like youtube videos, save and reference their tags.
The culprit would be: .\scripts\medialibrary.js, lines 69 to 75

Bio and Library Tree (**) updates have unrelated fixes/improvements, and should work fine on any foobar version.

(*) If that's not the case, then script is 100% working. I don't have access to m-tags source code neither the knowledge required about foobar SDK to know if the new protocols would also apply to third party components in this case (but I think it does, since m-tags work like tracks).
(**) I initially suspected about Library Tree, somehow I did a wrong search or mixed files on my first take... but when I looked at it yesterday again there was zero usage of RawPath references, so it's safe.
9
General Audio / Re: Can higher bitrates sometimes sound worse than lower ones
Last post by shadowking -
Quote from: fred-hy on
because of poor optimisation?

For example, let's say an encoder is optimised to give the best quality between 128 kbps and 256 kbps. Could using 320 kbps with this encoder sound worse than 256 kbps due to that?

Do any encoders have this problem, especially FDK and opus-tools?

Normally no the higher bitrate has less error , But it may be possible in this way :

There is an artifact audiable with lower bitrate, You encode with higher bitrate but artifact is still there and:
The error gets shifted in way that makes the higher bitrate sound different (more objectionable) even though the objective quality is overall higher.
10
Other Lossy Codecs / Re: SBR usage of xHE-AAC at 72kbps, 80kbps, and 96kbps
Last post by celona -
Write to Poikosoft (see https://www.poikosoft.com/contact ), it is a mistake, SBR should be used up to 36 kbps in mono VBR (56 kbps in CBR), up to 40 kbps in stereo VBR with PS, up to 64 kbps in stereo without PS, both in CBR and VBR.

In my opinion the maximum limit is in CBR with SBR for bitrates lower than 64 kbps in mono or 72 kbps in stereo, in VBR for bitrates lower than 48 kbps in mono or lower than 64 kbps in stereo with PS, lower than 96 kbps without PS. But it would be an exaggeration to keep at bay the requests of other users more demanding on numbers than on the sound obtained.