Skip to main content

Recent Posts

1
Opus / Re: Opusenc's built-in resampler
Last post by saratoga -
It would seem illogical to have a bad implementation of something, to know it, to know an easy fix, and not fix it just because it's "good enough".

I think trying to find problems in lossy codecs by looking at a power spectrum is a lot less logical. 

I didn't think about that, but it makes sense, a soft rollout filter that partially filters the 21 to 22Khz range, indeed. But then, this is a proof of what I've just said above, the 20Khz filter is of less quality than the 22Khz filter at the resampler.

Again, look at the scale bar before you decide a difference in quality exists. 
2
CD Hardware/Software / Re: REACT 2 Released
Last post by valnar -
Is EAC and Cueripper using the same read offset?

I have tested EAC, DBPoweramp and cueripper and they produce the exact same audio as long as the read offset is the same.

To be fair, I am using a different CDROM now (new PC), but have hundreds of former FLAC files.  The offset is correct for both.  When converted to WAV and stripping out all the non-audio, the files are different.  I'll have to look into it.
3
Whether or not sub sonic frequencies can be perceived, it is more likely to be so than weak, directional +20khz frequencies which vinyl fanbois bang on about.
4
CD Hardware/Software / Re: REACT 2 Released
Last post by A_Man_Eating_Duck -
Is EAC and Cueripper using the same read offset?

I have tested EAC, DBPoweramp and cueripper and they produce the exact same audio as long as the read offset is the same.
5
With these requirements the Sennheiser CX1.0 may be right for you. Great sounding and unexpensive.

I think you may mean the PX-100 which are nice sounding phones but with no isolation or noise cancellation. 

Good luck to the OP for avoiding plastic.  Even the most expensive headphones on the market will generally have plastic diaphragm drivers unless you can find some using metal domes.  And why should you avoid plastic?  Some of the best headphones have plastic bodies.  And plastic diaphragms are generally better and more durable than paper ones.  If you want to come in under a hundred pounds or euros I think you'll have plastic, period.


6
3rd Party Plugins - (fb2k) / Re: foo_discogs
Last post by frogworth -
or is it just a bug in the fine component? which I suspect, because of the "silent" skipping.

The credits can contain all sorts of text. The component will try to interpret what it finds there and tag it in your files, but it bases its interpretation on the Discogs tagging rules. I suppose zoomorph could alert you every time the component found *any* text it could not interpret in the credits, but that would be annoying for users, so I guess in that sense it "silently" skips credits which it can't interpret into actual track numbers.

So you and I might think that dashes of various sorts (with or without spacing, etc) make perfect sense, but the component needs a very specific syntax to understand what's written in the credits. And given that you're also requesting fewer error messages getting in your way (which I fully support!), that's why it's not telling you when it can't understand some bits of the credits :)
7
I search for add the year of album on other column, but I found that and I don't understant what I put in pattern ?
(I found that on Google but don't help me, the english for me... it's quite hard)

http://wiki.hydrogenaud.io/index.php?title=Foobar2000:Preferences:Default_User_Interface:Playlist_View


10
3rd Party Plugins - (fb2k) / Re: foo_discogs
Last post by fuffi -
thank you frogworth,
why are tracks 2-4 (of this release) not tagged with information after using your fine component?
track 1, 5 and 6 are tagged.
I think it's the syntax of the ranges of tracks - it shouldn't have hypens or en dashes. The standard is to use the word "to", so it should say for instance for the orchestra:
Code: [Select]
(tracks 1 to 4, 6)

Hmm.. ok, so the tagging is *silently* skipped because of the data on discogs?

if so, it would be a feature, which I requested, some time ago, because of the big amount of not usable releases with the fine component, when some data on the discogs-db is "broken". there, the fine component just throws errors, instead of tagging the correct data and ignoreing the incorrect data.

or is it just a bug in the fine component? which I suspect, because of the "silent" skipping.