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
91
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
Your conclusions seem completely backwards. It's DR that would get completely bogus temperature results for the hospital as it only accounts for a minor sample. LRA takes the entire scene into account.
Also your description of the Dua Lipa song perfectly demonstrated that LRA took the unusual silent part into account as it seems to be different track from the others on the album.
92
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Case -
@ApacheReal : Nothing about your config is related to PNG handlig in foobar2000. You use only third party components and hacks to render your UI. The transparency hack for example is very inefficient, especially if the component behind there drawing the image was only designed to render the image on resize. It may keep re-decompressing and rescaling it a hundred times per second.

@oops : you keep making claims that everything leaks memory. I'm confident SDK exposed methods don't leak memory, but when used incorrectly your component can. If you disagree, should be simple to show what leaks. Your current claim is equal to saying Visual C runtime leaks memory because it has malloc and new.
Also I haven't noticed any leaks in libebur128. If it indeed does, I'd appreciate you telling the source file name and line where memory is allocated that then isn't freed?
93
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by ApacheReal -
I thank you for your plugin but soon I will completely abandon foobar2000 because it does not allow correct management of embeddeb image files, especially if they are .png, I have to use these, because without internal images everything works perfectly as soon as I insert a png image, let alone 5 vu meter waveform seekbar all go jerky and this has always been foobar2000's problem.
94
General - (fb2k) / Re: Composer Metadata
Last post by toralilejit -
Quote from: Porcus on
Pattern: %composer%

Sorry for reviving this, but I was looking for this. I spent half an hour trying to do this myself, sadly foobar isn't as intuitive as it should be in some things. I don't get why some metadata can be easily selected from the columns options, but others, like in this case, we have to do this kind of thing.

Anyway, thanks again
95
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by oops -
Quote from: foobrik on
Can you tell me why foobar doesn't see the plugin update? I have to download and install it manually.
Since I assume only Peter's components get updated automatically, here is the release notice for 0.8.0.

Quote from: boxerfan88 on
When foobar is started, it will throw the error below, and get stuck in an infinite loop throwing the same error. foobar cannot start.
This is fixed now. It will append the backslash now if not added. I made a copy/paste mistake when I copied the same function from foo_vis_milk2.

Quote from: Majestyk on
Thanks for posting Version: 0.8.0. I don't know if you worked on the skinloader or not but in this version it still only loads one instance. Plus sometimes it won't even load that one instance as you can see when I load the color cyan, at the end of the animation.
Try now. I tried to replicate the original's behavior. There are a few skins that take a longer time to load where all might not change together. Mainly it's the ones where the BIN is packed inside a RAR with the settings. The way this works is using a mailbox. So, try adding a delay in between the two fb.* commands. I'm going to take a shot in the dark and guess that the reason only VU is changing is that it clobbers the PEAK change before the render/uncompress thread opens the mailbox.

In addition, I added a few extra things. Let me elaborate:
  • There is now a EBU R 128 mode that uses libebur128. So, if you prefer an alternative loudness calculation to my implementation of BS.1770 that is it. It is a bit leaky. I squashed some of the issues with the CRT memory debugger and address sanitizer. There may still be some more, and I cannot vouch for the accuracy of the calculations. Use at your discretion.
  • I found a "tap and press" gesture in the original component to change skins when testing how skins changed in groups, so I implemented it.
  • The skin change menu will ONLY change skins within the group. It is a NOP otherwise. I put a watchdog timer of 2 seconds on it to avoid issues.
  • Since I got tired of right clicking the menu to change the tuning parameter, holding Esc, Right Alt or AltGr while moving the mouse wheel with do the same. Also, mouse buttons 4 and 5 will change it but since foobar2000 grabs those by default to move to the prev/next track in the playlist it might not be as good as the modifier methods. One small issue is that I didn't have time to fix the tooltip to reflect the change in real-time since I got sidetrack searching for the EBU R 128 memory leaks. I'll get to it soon.
  • To try to keep some loose feature parity with the BoringName's MusicBee plugin, I added ability to open separate left/right panel files (ending in 1.bin or 2.bin). I finally found the explanation for the curve adjustment parameter so that should work as well. But if you don't like any of the RAR skin's INI file overriding your settings, there is now the option to ignore the INI file.
  • Do not expect write back of the custom settings into the INI file due to the licensing restrictions of the RAR format.
97
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Majestyk -
Thanks for posting Version: 0.8.0. I don't know if you worked on the skinloader or not but in this version it still only loads one instance. (VU's in the corners should change color as well).

Plus sometimes it won't even load that one instance as you can see when I load the color cyan, at the end of the animation.

99
General Audio / Re: Unusual sampling rates
Last post by saratoga -
Quote from: Klymins on
Quote from: saratoga on
In the real world sounds are not made of little connected straight lines, so it is not at all a natural way to do resampling.  Probably you mean "easiest to understand".  It is used because it is easy, not because it is good.

They're artifacts resulting from the error introduced by approximation of a curve with lines.  You may personally like that sort of distortion, but as many people have pointed out there are much better ways to accomplish the same thing than trying to find specific ratios of sampling rates that make the distortion less harsh or whatever you're looking for. 

Linear interpolation is not completely natural but it's the most natural interpolator because generating absolutely nothing above a frequency limit is much more artificial than generating filtered reflections (lower frequencies generate weaker and weaker reflections in linear interpolation, that's the filtering).

The most natural thing to do is not introduce artifacts.  Then you don't have these strange issues with specific sampling rates making distortion more or less annoying to the ear.