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
11
CD Hardware/Software / Re: Nowadays what is the most respectyed way to rip CDs to FLAC?
Last post by Porcus -
WindowsOS considerations: I ripped my entire collection with dBpoweramp (paid "reference" version), but you cannot do much wrong about neither that nor EAC nor CUERIpper except:
* If you want EAC style logs, you cannot use dBpoweramp. But I don't know if you need them if you have the AccurateRip ID that dBpoweramp writes.
* For those pesky pre-emphasis CDs that may or may not flag it properly (properly means both in the TOC and in subcode, but that is not a given in practice), then CUERipper does both, but IIRC the two others don't.
* If you want proper index marks in your cuesheets ... I am not sure. Anyone?

Also, IIRC: CUERipper is not that hard to script by command-line, if that is a concern.

@Feilakas knows Redumper, which rips not only the audio but also subcode. I have no experience with that, but my hunch is that you don't need it if the disc verifies AccurateRip and the others agree it doesn't have pre-emphasis.
13
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Case -
My recommendation has always been not to pretend that fake HDCDs are HDCD-enabled. That way you do not get any confusions anywhere. Note that the bit depth is purely what the source reports, it will never be fact checked to see if the bits are actually present.

I strongly disagree that log should contain values that are irrelevant, like what the source file specs are prior to decoding.
14
News Submissions / Re: Lyra V2 - a better, faster, and more versatile speech codec
Last post by mosin jack -
Really exciting to see how far Lyra has come! The improvements in V2—especially the better audio quality, scalable bitrate, and wider platform support—are exactly what many developers (myself included) were hoping for. Huge thanks to the team and community for making this codec even more versatile. Looking forward to seeing the innovative applications that come out of this!
15
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by wojak -
@Case
thank you for new additions to the component.
One remark regarding new method of bitdepth display in the log. In case of HDCDs it can be misleading/confusing as we have 16bit file and get 24bits in the log. Plus I scanned a file that has TF but no PE nor LLE so your TPS shows 17bits but new DR shows 24bits which may again be confusing (I presume those are different values - "measured" vs. "decoded to"). Maybe it would be better to show both values in the log - input bitdepth (16) and decoded bitdepth (24) or at least name or rename the visible value so that we know which one is displayed.
18
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by sveakul -
Quote from: always.beta on
Quote from: sveakul on
@always.beta :  since updating to 1.0.2.0 (but also present in 1.0.1.8 ) I have noticed that lyric returns from the genius.js searcher have begun including lines at the top of the lyrics text panel that refer to # of "contributors" and occasionally notes about the song itself.  This is present on EVERY SONG.  Is there a way to pre-trim these out?
You can try to write a js script parser, remove the part without timestamp or process the lyrics to see if there are common features. I don't know how to program, so I don't know if the above method can meet your requirements. I remember someone discussed it before, and there is no option to remove it by default.
Thanks always.beta for commenting.  I don't know how to program either so we are in the same boat there.  Hopefully, TT who wrote the original searcher will post a method.