Skip to main content

Recent Posts

1
What better way to ask help than to violate Hyrdogenaudio TOS (#6). You have your thread here no need to post it again in the columns ui thread,  It only serves to annoy people.

That being said, it is best you familiarize yourself with how panel stack splitter works and how to ad/remove panels. What you want isn't that difficult to achieve. Look at the panel stack structure and how the panels and panel stacks are layered on top of each other (display-colums ui-layout). Change the dimensions of a panel within the stack with $movepanel_c(panel-name,x,y,w,h) and force the layout. Your waveform seekbar is probably the easiest, you only need to replace that panel, which if I'm not mistaken is a jscript panel. Remove the jscript panel, insert a waveform seekbar panel in the correct stack and give it the same name as that jscript panel and force layout.
2
Of course this can be made audible by enough amplification. We all know this!
Except greynol and ajinfla who are arguing against this.


I don't see that at all.  You might want to reconsider your view of the conversation.  I'm 100% with pelmazo , you've built an argument upon a narrow band of pedantic trivialities and are (supposedly) shocked nobody else is in agreement.
3
There you go Case, an appeal to intellectual honesty.
Except greynol and ajinfla who are arguing against this.
Which you apparently can't manage to muster.

This has gone on for far too long. You can't seriously be this dense.
4
Case, I do wonder why you prefer to listen to the noise produced by DACs instead of what is generally considered to be music. I know that musical tastes differ, but this seems extreme.
You won't win the argument by saying that if you amplify the DAC output enough, you'll always hear noise. That's a "well, duh". What matters is if you hear the noise while listening to music - and the final answer to that is if you do, you're "doing it wrong."
5
Except greynol and ajinfla who are arguing against this.
Nope, just your purported "DAC noise".
Now when you claim to hear this "DAC noise", what >16 bit files are you listening to?
Are the polled believers hearing this same noise as you? Using the same "DAC noise" finding method?
6
3rd Party Plugins - (fb2k) / Re: Columns UI appearance
Last post by jdotpeacock -
Hello all,

Just looking for some pointers and advice in regards to achieving some custom features on an already modified skin.

I'm using Osaka underground and my skin looks something like this:



But I'm looking to try and achieve something resembling this:



Basically looking to add Waveform seekbar, Spectrum analyser and VU meters, but I have trouble with panel stack and not being able to move them around freely. Depending on the stacking the waveform panel stack disables or hides some buttons which is not good.

Any help would be greatly appreciated.

This is my portable directory for anyone who could possibly mod this for me:
http://www.mediafire.com/file/n5blu6guv3kqy2o/foobar2000.zip

Thanks in advanced.
Joe.
7
FLAC has a decoder. WavPack has a decoder. MP3 (though not lossless) is defined in terms of what a decoder should do, isn't it?

You can define whatever you want in a decoder, but if you specify something that software cannot reasonably do given normal playback application organization, applications will simply ignore the spec.  Ogg and MP4 define all sorts of features for instance, many are seldom or never supported, even ones that are supposed to be mandatory.  If you want to specify things like DSP effects, you had better implement them entirely inside the decoder in a way that is transparent to the application using the codec. 

So having to specify decoding is not an argument per se, but of course too high complexity could become troublesome.

It is not just about complexity.  If you specify a thing that software usually cannot do, people are unlikely to rewrite their software to support a single codec. For instance, if you give the codec the ability to specify to a playback application track ordering, nothing is going to support that because most audio applications decide what to decode before they decide which codec to load to do it.  Information is generally not going to flow back the other way without a lot of work from the developer. 

Even things like loops can be tricky.  It is pretty common for applications to buffer audio under the assumption that you move forwards in a file. If your loop tries to seek back to before the beginning of an application's current buffer, a lot of software will not be able to decode the loop. 

If you want to define a good format, you need to consider carefully what features you add and how practical they actually are for software that is likely going to have been designed for formats like MP3, AAC or FLAC.

DSP instructions, on the other hand, is something that playback software could choose not support, and could end up being "ignored" the same way that those ID3 tags are ignored.  I see that issue.

Realistically, all software will choose not to support DSP instructions.  You should implement these in your decoder or not at all. 
8
Hello all,

Just looking for some pointers and advice in regards to achieving some custom features on an already modified skin.

I'm using Osaka underground and my skin looks something like this:
22

But I'm looking to try and achieve something resembling this:


Any help would be greatly appreciated.

This is my portable directory for anyone who could possibly mod this for me:
http://www.mediafire.com/file/n5blu6guv3kqy2o/foobar2000.zip

Thanks in advanced.
Joe.
9
General - (fb2k) / Re: Working with cue sheets
Last post by SmartOne -
Less-abandoned, and has the beneficial side effect of elegantly separating metadata from data, behold m-TAGS: https://superuser.com/questions/677207/foobar2000-library-flac-ape-vs-cue

Still, ignoring files referenced from a CUE as tracks seems like a simple missing feature from foobar2000.
10
FLAC has a decoder. WavPack has a decoder. MP3 (though not lossless) is defined in terms of what a decoder should do, isn't it?  So having to specify decoding is not an argument per se, but of course too high complexity could become troublesome.

I politely disagree that loops belong to a workstation. Loops for a working project may do, but loops for an end-user (like a locking groove on an LP) belongs in an end-user format - provided that anyone has use for it, of course. And clicks from being misimplemented off one sample, that could be avoided the same way one actually manages to do gapless playback, right?
I would figure that instructions on loops could be implemented in a way that would work on playback - transcoding, on the other hand could frustrate developers just the same way loss of information between file formats does in other applications. Not to mention, devs would be annoyed over users' questions on the matter, and HA would have to stopp touting "lossless is lossless" (which is strictly speaking already false, unless target format can carry the audio contained in the source).

DSP instructions, on the other hand, is something that playback software could choose not support, and could end up being "ignored" the same way that those ID3 tags are ignored.  I see that issue.