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_vis_vumeter
Last post by oops -
Quote from: Defender on
I do not see any difference whether running 0.9.0 or 0.9.0.1. Should there be a difference?
Since I've not outlined how to take advantage of the custom shader/effects publicly, no. There is a prerequisite that you must know how to code HLSL and understand the rendering pipeline to even begin.

Quote from: Defender on
I tested a transparent AIMP skin, which is fine on JS3 ilovefb2k, but displays standard background of Dark Theme with this component.
Thanks for testing.

Quote from: Defender on
Does look a lot better than the BIN version because VU Editor makes a checkerboard of the transparent parts while making the BIN, which doesn't happen in the AIMP version.
The BIN file is composited by the VUEditor into a bitmap with all zeroes for the alpha channel for the base image. If you really wanted transparency, you could probably figure out how to programmatically modify the base image to include the alpha data in the checkerboard area. If you do, with a small header flag it could be made to work, though you will still end up at the same point with the pseudo transparency dilemma.
I do the transforms and compositing for the AIMP versions. To be honest I really, really much prefer the BIN files because it abstracts out all of that complexity, the representation is compact and mapping the audio levels is straightforward.

Quote from: Defender on
Is support for transparency somewhere on your todo list?
I would like to, but I don't know how to do it...yet. I've tried experimenting with what mark2k3 suggested but could not get it to work. Been scouring GitHub and MSDN for other ways to approach the problem but coming up empty.

Quote from: Defender on
Also still missing the option 'Force Lock Aspect Ratio on Fullscreen'. So fullscreen still looks silly on a lot of VU skins.
This RFC does not look very complicated to add support for imo.
A RFC is a formal specification document and includes detailed justification for the change. Our discussions in this forum are far from that ;) When "Lock" is enabled it carries over into fullscreen mode. And even in fullscreen, "Lock" can be set by the context menu. I'm failing to see what the "ask" difference is to the options that are available. Why it is not possible to accomplish what you need with the existing options?
92
MP3 - General / Re: Cjam - simple MP3 editor
Last post by cutandjoin -
@jaybeee
Thank you for your positive feedback.

Regarding the fade-out issue, I’ll consider adding parameters to select the fade type, such as Straight, Convex, or Concave. I plan to implement this in a future version.

As you mentioned, the software does have quite a few options, and some parts may feel less intuitive. Please feel free to ask if you have any questions.
For the main operations, there are shortcut keys assigned, which might make it easier to navigate and use the software.
93
CUETools / Re: How To Rip & Decode HDCDs In CUERipper?
Last post by Porcus -
You have been warned already that HDCD decoding is flawed.
Don't blame CUETools, which included the "at the time only" software decoder (all others were based on that one) - but if you don't want permanently flawed files, then keep your undecoded CDs.
94
3rd Party Plugins - (fb2k) / Re: Made with foo_uie_webview
Last post by ApacheReal -
With a view to completely and totally removing JS script / JS3 script / Spider Monkey Panel / JS Splitter and using only foo_uei_webview, another step for removing the custom track.

The next step is the seek bar.

Currently in JS3 the JS Playlist / Smooth Browser / Last.fm Bio + Images modules remain to be added which will progressively where possible be replaced by equivalent modules to be managed in foo_uei_webview.

95
General - (fb2k) / Re: Title formatting/syntax for proper bitdepth
Last post by wojak -
Quote from: Case on
Sounds like the track uses Peak Extension codes in the wrong places, or the track is too quiet generally for PE to do anything. You can run the track through HDCD scanner and it will report how many frames were altered by PE. I suspect there weren't actually any extended peaks.
Yes - such tracks are usually very quiet - short, one instrument or smth like that. Will check later with the scanner.

Quote from: Case on
I'd like to change decoded_bitspersample to report the actual real decoded bitdepth, like return 16 bits or 17 bits for fake titles depending on settings. But there is a problem, LLE effect will instantly trigger 24-bit accuracy and it's unknown from the first seconds if the code was missing if it will be used later. People may not like decoded_bitspersample changing mid-track.
That might be confusing -  I use both formulas so I see 24 bits as "decoded" and 16 or 17 or 24 as "TPS measured". I would be for leaving "decoded" as 24 as that was the original intention of the hardware (if I am not wrong; but if I remember most HDCD players had 24bit logo on the them). And the values I see now mean to me: I have 16bit file but it measures 17 or 24 because there is HDCD in it so it is decoded to 24 (becuse it is one of the 3 most popular "standards" - those being 16, 24 and 32 - other bitdepths being "exotic").

Quote from: Case on
I hope I don't confuse you furher, but the bit depth reported by TPS is based solely on the lowest bit used by the signal. It could for example report 32 bits for a very quiet signal that could be represented with just two bits if it was amplified. Would there be interest to see the used bit count that computes the unused upper bits?
Does this mean that "bitdepth" is only "used" for loudness? Like 6dB for each bit. And it has nothing to do with digital "precision" of the representation of the analogue signal? I always thought that the more Hz and bits the more accurate the aproximation of the continuous signal. Are bits only for "lowering the noise" or are additional 8 bits (between 16 and 24) only for reproducing signals quieter than -96dB?
Would that mean that the quiet track has audio only in those lowest bits and those "louder" are "zeros"?

Quote from: Case on
The fields are non-standard, they are against foobar2000 logic, a decoder should not report permanent tech info fields (visible in properties dialog) that change depending on user preferences. Tech info fields are supposed to report file specs. I know I kind of abuse this with foo_outinfo, but I don't want to push nonsense any further. Peter has already dropped features from titleformat code because developers abused the system, I don't want such things to happen ever again and most certainly not because I do something stupid.
I can't agree with that. To me it seems obvious that decoder should report info of its behaviour and it happens with sacd_input now. If I play 2,8/1 file and chose to play it as NativeDSD it bypasses the pipeline so the decoder should and reports 2,8/1 and my DAC also sees such 2,8 signal. If I play the same DSD file but chose to output it as PCM and chose 192kHz as the resolution the decoder converts the DSD signal do such parameter and reports that it has been decoded to 192/64 (input_sacd uses 64 and udsd uses 32) but then it is changed to 32bits by foobar output (or my DAC input) so my DAC sees 192. I do not have bits display in my DAC I can only set it to 32 or 24. 
Tech info fields should report file specs and they do - those are:
$info(samplerate)
$info(bitspersample)
$info(channel)
%channel_mask%
$info(hdcd)
$info(hdcd_active)
$info(hdcd_peak_extend)
$info(hdcd_gain)
$info(hdcd_transient_filter)

But the fields "decoded_*" are not tech info from the file - those are infos from  the decoder showing how the file was treated/unpacked/decoded by apropriate decoder hence changing values in DSD files. Note that "samplerate" in DSD always shows 2,8 independent of my mode of playing as this one is tech info from the file. But "decoded_samplerate" shows 2,8 for DSD mode and chosenPCMvalue for PCM mode.
Isn't that what happens? Are those values and my logic wrong?
If I understand it correctly for now "decoded_bitspersample" show smth and it is 24 for HDCD because that value is different than the original tech info from file whichis 16. If hte decoded value is equal to "tech from file" the "decoded" is not reported/displayed. So we do not see "decoded_samplerate", "decoded_channels", "decoded_channel_mask" and "decoded_bitspersample" (the last one is seen with HDCD) because they have not beenchanged by the apropriate decoders. My question is why can't we see that those were not changed? Why do we have to assume that? What is there to abuse? What I want to achieve is to be able to see that 44,1/16/2(FL FR) file that was measured as 16 with TPS is decoded to 44,1/16/2(FL FR) and outputted as 44,1/32/2(FL FR) or 44,1/16/2(FL FR) HDCD file that was measured as 17 with TPS is decoded to 44,1/24/2(FL FR) and outputted as 44,1/32/2(FL FR). What abusive is in that?

Just for clarification - all of the above is just my seeing of things as an end user and it surely might be technically wrong (as it already turned out to be on many occasions here).
97
Site Related Discussion / Re: How To Delete Posts And Account
Last post by itisljar -
In our country on one IT forum, when you delete an account, all user info is deleted EXCEPT users posts; but the posts don't show username anymore, just a placeholder that says [AccountRemoved]. The idea behind it is that these posts might have valuable information, and they are willingly posted in public place, and the forum rules have a statement about that, and what data will be kept in case of account deletion, and why; you can agree to that or not when joining the forum.
Yes, I am in EU, yes, GDPR is something we take care of.

Of course, forum owner can't be responsible if user willingly posts some sensitive information about itself, but those can be tracked down by users, mods notified, and relevant parts removed after the account has been deleted.
99
General - (fb2k) / 回复：UPnP MediaRenderer输出 | 讨论
Last post by clark8888 -
Help BUG!  PGGB upsampling 32bit 768khz as foobar plugin will pause play around 25 minutes after uPnP 1.4 plugin streaming to all kinds of uPnP bridges.  Once click progress slide of foobar will resume playing.  If down to 16bit device  384khz, around 50minutes will pause play.  I guess this bug is related to cache running out.  Can Peter update uPnP plugin for better hires?  Thanks in advance!
100
General - (fb2k) / Re: Title formatting/syntax for proper bitdepth
Last post by Case -
Quote from: madoka@ex-sounds on
"titleformat" doesn't seem to work anymore.
Has the format changed?
In previous versions it was something like "%__hdcd%".
As @Defender already replied, I changed the logic. The old fields are all still present. I know people want to see HDCD track is HDCD track throughout the playback. foobar2000 component doesn't need to be as limited as a hardware player that doesn't work per-track but by constant stream of data.
If a track is considered HDCD the %__hdcd% info field will stay on and instead temporary hdcd code disappearances can be tracked with %__hdcd_active%.