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
1
General Audio / Re: Where did these (obsolete!) sampling rates come from?
Last post by Porcus -
Quote from: Porcus on
5.6, 7.4, 11.1 and 22.2 kHz?
[...]
Those sampling rates were used in Apple SoundCap ("HCOM" fourcc) files - anyone even seen one?
Both FFmpeg and SoX got some support. The SoX documentation refers to them as:
Code: [Select]
Format: hcom
Description: Mac FSSD files with Huffman compression
Channels restricted to: mono
Sample-rate restricted to: 22050 11025 7350 5512.5
Reads: yes
Writes:
   8-bit HCOM (8-bit precision)
Those sample rates do make sense, but who am I to tell whether a mid-eighties Macintosh would use 22050 or something so close that 22050 is a practical approximation. Anyway 1/2, 1/3 and 1/4 is also sensible - remember this was before .wav, so its restriction to integer was not a concern.

Also interesting is that this could be the first lossless audio format, although it might be a stretch to call it an audio compressor if it merely let a general-purpose compressor (PackIt?) loose on files that happen to contain audio.
2
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by regor -
Quote
For my part, I'll make a quickie tool to clean up/uninstall my components (and others, given a list of GUIDs) from the configuration database.
That would be wonderful.

Anyway I don't think the discussion per se is bad, to me it's clear some people have problems with the current design and there are some legit use cases where V2 has been a downgrade instead of an improvement.

I think it's useful to develop that discussion -obviously not in this thread, sorry- to hopefully reach to some solutions for the problems mentioned. Or at least give them an answer if it's a design decision which will not change.
3
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Defender -
Quote from: oops on
Quote from: Defender on
Play from ELP - VU 2024 fullscreen - Exit - Crash
Video of the gaudiest setup I could squeeze in to torture test.
Video is sped up 50% to squeeze it under the imgur limits (since it's MP4 cannot embed either).

Cannot reproduce the crash. I mistakenly hit the X button for the VU meter instance in the Jsplitter panel; it didn't crash. And you can see the 0 exit code at the end. Don't know what how your set up is knocking the VU meter off kilter.
In your video I do not see an active ELP. The issue is ELP and ELP only. And only when at least once a play command was issued from ELP AND VU has been put in fullscreen.

Also ELP is running fine and keeps running fine going fullscreen with VU and back again a 100x.

The ONLY (but big) issue is fooBar crashes on exit, when the above situation is met.

BTW. I am going to respond to your earlier message to me.
4
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by oops -
To all. Mea culpa. I didn't mean to spark a discussion on the design decisions of the player. I missed some detail that led to a crash. We found the problem and fixed it. Let's move past it.

Just tried to get someone going again until I roll out a fixed release. It's what I wish someone did for me if I ever was stuck with a showstopper.

For my part, I'll make a quickie tool to clean up/uninstall my components (and others, given a list of GUIDs) from the configuration database.
7
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by oops -
Quote from: Defender on
Play from ELP - VU 2024 fullscreen - Exit - Crash
Video of the gaudiest setup I could squeeze in to torture test.
Video is sped up 50% to squeeze it under the imgur limits (since it's MP4 cannot embed either).

Cannot reproduce the crash. I mistakenly hit the X button for the VU meter instance in the Jsplitter panel; it didn't crash. And you can see the 0 exit code at the end. Don't know what how your set up is knocking the VU meter off kilter.
8
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by regor -
Quote from: Case on
Exactly when before have you seen someone ask to delete configuration to try to troubleshoot a crash? I can not remember that ever happening before.

I'm not familiar with config file sharing scene, but if that is a thing, then separate files make that easier. Or are you referring to people sharing "skins", entire foobar configurations with custom themes? Not sure the used config system is a factor with these, people seem to be happy to take whatever packages they are shared with.

I doubt your complaining about Peter's design decisions is going to make him happy to listen to your suggestions, if there are suggestions somewhere. All I see is complaining about self inflicted issues.
Well if Peter doesn't want to listen, it's their decision not mine. That doesn't change there may be flaws in the design, and ignoring them doesn't do any good. It's also not "good" to just tell users it's their problem when a flaw is shown. It is not only me who has complained about this since more than a year.

A quick search:

Spoiler (click to show/hide)

There are several threads pointing to problems (no deletion, abs paths, full tag caching, infinite grow) with the actual database handling. Whether it is components or tracks.

Obviously you may ask users to create another thread with suggestions all in a proper way without under-appreciating peter's work, I get it. But you also have to understand people has life, and the same Peter may not like to read a random user bashing the current system on a Monday, that random user may not want to post the same problem in a super-polite way for the 10th time when 9 times before it has also been ignored. (not that I think I have been aggressive, but if that's the case, sorry)

About your questions:
Quote
Exactly when before have you seen someone ask to delete configuration to try to troubleshoot a crash? I can not remember that ever happening before.
For sure I have read multiple times in v1 to just delete the cfg file if it was corrupted to reset the component and only that.

Quote
I'm not familiar with config file sharing scene, but if that is a thing, then separate files make that easier. Or are you referring to people sharing "skins", entire foobar configurations with custom themes? Not sure the used config system is a factor with these, people seem to be happy to take whatever packages they are shared with.
There are other skins where this is or may be required. But also it's useful for regular users. If I want to create another portable install and just copy some of my component settings and layout I have to either copy all or nothing in V2.

Example:
Spoiler (click to show/hide)

There is also no way to selectively backup some components/settings or restore the backups. Current design is just a blackbox, and we just hope it works until it doesn't (like this case).

An user doesn't care who is the responsible of the bug (devs may like to engage in that discussion), the user just wants a simple way to fix it. A single global config file removes the last resort fix of deleting the file.