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.
Last post by marc2k3 -
A script included with JScript Panel 3 already does this...
The obvious downside is that adding your own buttons is not easy.
FWIW, it works by drawing single font symbols so the colour/size can be anything. I use the Segoe Fluent Icons font for my own scripts but anyone writing their own can use whatever font they want.
Last post by Just_Addict -
I've been fruitlessly trying to suppress a long gap between the listed last track and a hidden track in a multi-track flac file. I only found one old thread asking the same question, but the given solution is not what I want. It works but the track before the hidden one is still reported too long and the waveseekbar still shows a lot of wasted space, resulting in loss of resolution detail.
Foobar2000 complains if I use POSTGAP that it is not supported, even though valid in cuesheets, and PREGAP is just ignored. This should not be this difficult. Like why is foobar2000 saying postgap is 't valid even though as far as I could find, it is a valid entry? And why is pregap just ignored when it comes to reporting tracklength?
To test unrelated issue, I've been checking the console log of foobar 2.2 preview (2023-05-23) x64 and found 2 strange things about ASIO output (foo_out_asio 2.2.2) :
1) when I start any 24-bit (or even 32bit just for testing) track this is what I see in the log: Opening track for playback: "D:\track_name_here.flac" new service_impl_t<autoproxy_output_v5>(device = "ASIO : Combo384 ASIO 1.03", buffer_length = 0.050s, dither = false, bitdepth = 16)
it shows bitdepth as 16... Is this actually the bitdepth that output is going to use or just a default init value that's logged and it switches to a correct value afterwards (but not shown in the logs)?
DAC uses Amanero Combo384 USB interface with the latest drivers installed and tested with other apps to support 16-32bit with 44.1-384kHz, No DSPs were active during testing and bit depth is set to auto (the only option for ASIO) in the output device settings in Foobar.
from the looks of it, it's opening stream with insane sample rate of 3072000 and then switches to a correct one, with everything lower than 174/192khz I get only one entry for the input stream with correct sample rate. Is it supposed to be like this?
Let me know if you need any other logs or configured settings.
Last post by Terence -
Come to think of it, there are other ways, but it's no longer the icons themselves: - with CUI, you can save layouts. So having one layout for the light theme and another for the dark theme (with the corresponding icons). You can then change the layout using the View > Layout menu, or a button or a keyboard shortcut. This doesn't change the main toolbar at the top, but it does change the other toolbars, so an additional toolbar is required. - with DUI, you can save themes in a .fth file (in Preferences > Display > DUI > Import / Export Theme ). The theme used is the theme.fth file in the configuration folder (Roaming folder). When I double-click on a .fth file, it imports the theme into foobar. But it also brings up a “Choose Theme Sections to Import” window every time. And it depends on your layout, but I find it slower than with CUI. - I use Auto Dark Mode to automatically change the system theme in the morning and evening. It can be used to automatically trigger scripts. I use AutoHotkey to trigger keyboard shortcuts (e.g. change layout in CUI). It also lets you do lots of other things, like open a theme.fth file (for DUI), modify a registry key, change a setting in a file, replace a file, click wherever you want... I use this for a few programs that don't have automatic theme changes (it's a bit complicated to do). I'm glad dark mode has been added to foobar2000 and CUI. - Maybe with a toolbar made with a javascript panel? JScript Panel or Spider Monkey Panel. It should be possible to make a toolbar that changes theme automatically (I've already made a volume button that follows the dark or light mode, from SMP's sample scripts, so it should be possible). But I have no idea if it's possible to redo all the buttons in javascript. I don't know much about it, so I can't say. I'm saying some things from memory, so I hope I'm not talking too much nonsense.
Last post by john33 -
Where does "exhale channel remap" come from? It's not required and I've never seen it before. And, the previous version would encode multichannel audio but the channels were not necessarily in the correct order.
Last post by Porcus -
Question and possible wishlist item: Since %last_modified% doesn't work now, how can it "Find tracks edited after External Tagging" - does it simply compare tags and report the different ones?
Because if not, that is a thing to ask for. (Rather than committing the whole thing.)
replaygain_scanner_entry_v2::ptr rg_api; if (replaygain_scanner_entry_v2::tryGet(rg_api)) { rg_scanner = rg_api->instantiate(replaygain_scanner_entry_v2::flagScanGain); } if (!rg_scanner.is_valid()) // Failed to instantiate ReplayGain scanner.
The code doesn't care about anything else. Core is just asked to give the component a ReplayGain scanner instance and for reasons unknown it fails for you. In my previous post I mentioned the only two reasons I knew of why RG scanner instantiation could fail. foobar2000 version was not a factor, the method has been supported for ages and works on all versions where the component works.
But now I did some more testing as I remembered an old troublemaker. Turns out https://www.foobar2000.org/components/view/foo_arg component breaks RG scanner instantiation. If you have had that component installed all your RG scan results are invalid.
PS: post editing not working after an hour is not about forum software being archaic. It's intentionally limited as editing old posts doesn't help with conversation. No one who follows the discussion would see edits done to old posts as they have already read the original posts and moved on. If you have some meaningful new information make a new post.
Last post by darkflame23 -
Thanks, ah yes, think I posted in the wrong thread! Very confusing having two components with very similar functions and names!
Last post by Peter -
Update: I'm actively working on restoring it and upgrading to latest mediawiki. No worries about the content, it's been thoroughly backed up.
