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
3
AAC / Re: New Improved AAC Encoder / FAAC — I'm Looking for Feedback
Last post by Case -
I used -q alone first but it seemed to affect bitrate only minimally. And for example produced the same 94 kbps result.
Also by default the encoder incorrectly writes plain AAC files using M4A extension, hence my extra parameters to ensure I get AAC in MP4.
6
General - (fb2k) / Re: "get tags from freedb" doesn't work
Last post by Case -
The freedb database matches releases by CD layout. Only track lengths and track count matter with the matching. If there are multiple releases with the same disc layout you will see a list of all possible matches.

So the only way it *can* work correctly is if you select all the tracks of an album and use the command for the entire album at once.

According to Musicbrainz The Rolling Stones has an EP release called "Angie" that consists of four tracks.
7
CUETools / Re: unable to find the single-track CD with the file browser
Last post by korth -
CUETools won't show/process a single audio file in a folder unless it has an embedded cue.
CUETools will show and/or process 'support' files in the same folder such as an external cue, m3u, etc.
So a simple m3u playlist with the filename should work.

Note: I just ran 'fix offset' with the CUETools database completely disabled and CUETools applied the offset to the files.
Note2: There is (with the default settings) a pop-up message that will appear when all tracks verify (>2) in the AccurateRip database and the rip does not yet exist in the CUETools database that will ask if you want to submit the rip to the CUETools database.
8
AAC / Re: New Improved AAC Encoder / FAAC — I'm Looking for Feedback
Last post by Case -
I must be doing something wrong, but command line "fimpaac.exe -w -q5000 -b 256 <infile.wav> -o <outfile.m4a> does not produce even close to 256 kbps files. A longer test file turned out at ~180 kbps, a short one at 94 kbps.
Same parameters with faac.exe do produce 256 kbps files and they sound better.

The 94 kbps sample sounds awful but its bitrate isn't comparable with competition. The 178 kbps file is noticeably noisier in quiet parts. The 178 kbps file sounds worse to me than ffmpeg AAC encode at 128 kbps. I used track Heal from Heather Nova's 1994 album Oyster.