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
Off-Topic / Re: AudioSurf
Last post by coveyinvest -
Really interesting to see how AudioSurf analyzes tracks using FFT and normalization instead of RMS. Your test tone approach was clever, and the format compatibility tips are super helpful.
2
3rd Party Plugins - (fb2k) / Re: JSplitter (splitter + SMP x64 alternative)
Last post by regor -
Quote
Yep. But it's a pure coincidence) I hasten to inform you that there is a bug in the foo_listenbrainz2 plugin, due to which the plugin can report literally anything about the state of the unchecked menu, in other words, we can simply get numeric garbage. Therefore, in 32 and 64 bit versions it turned out differently, just was unlucky with 32 bits) But when menu is checked it is always correct, that's a fact.

Thanks for taking a look at it. I was expecting that after seeing your gif, so that's why I tried both architectures. I opened an issue about this on October for that particular component, but it was considered a SMP problem at that point and not a bug. Don't really care about who got it wrong first, although people using flags in different ways smells like problems...

If following marc's approach works for checking entries from any component, whether they do it right or not, that's probably the best approach (in addition to filling issues when found).
https://github.com/marc2k3/foo_spider_monkey_panel/commit/3c1704bf8271d8d95829177d76734e24b628bd43

There are so many components that is not feasible to check them one by one to find who is doing it right, and many will probably never receive updates.
3
Audio Hardware / Re: Question in-ears magnetic driver
Last post by fooball -
The main risk is to the CRT.  Playing around with magnets to distort the picture can result in the shadow mask becoming magnetised and a semi-permanent distortion in the path of the electron beam.  De-gaussing was not an uncommon servicing job when CRT TV was mainstream, and IIRC some TVs had de-gaussing built in.

Not that ear buds sitting on top of a TV are going to do that...

There's something very odd about this thread, like it's some kind of click-bait.  I realise Gen Z have not been brought up to have any common sense, but the advice is simple: don't worry so much, and embrace learning from mistakes (there's nothing to learn from things going well every time).
5
Audio Hardware / Re: Question in-ears magnetic driver
Last post by .halverhahn -
Quote from: Chibisteven on
I wouldn't store anything magnetic near a CRT because it screw up the picture on it.  Or anything magnetic near a magnetic storage device.
btw: CRT-TVs have build in speakers in general, so why worry about the magnitude smaller magnetic field of the in-ear-headphones next to the TV?
fun fact: e.g. even laptops with HDDs build in have speakers also build in. And often the screen-lid or the laptop base have magnets build in to "lock" the screen when the laptop is closed.
9
3rd Party Plugins - (fb2k) / Re: JSplitter (splitter + SMP x64 alternative)
Last post by marc2k3 -
Well that component was mine before I abandoned it so I guess I'm to blame.  :D

I'm also guilty of "doing it wrong" in other components too. Oh look, columns UI is not zeroing flags either.

https://github.com/reupen/columns_ui/blob/051448e309e7ab78c723cca9d92dca452fa8a833/foo_ui_columns/menu_items.cpp#L139

In theory, the code above could modify flag values and then return false.

Given the main menu state in fb2k is always correct, it must be doing as I suggested. I don't think there is much to gain by pointing fingers at other components when the fix for yourself is so easy.