11
Lossless / Other Codecs / Re: Monkey's Audio 11.00 (MULTI-THREADED ENCODING / DECODING)
Last post by MonkeysAudio -Monkey's Audio 10.96: 9.94, 9.50
Monkey's Audio 11.00: 2.45, 2.52
So around 4x faster with my machine.
Options looked into so far:
- MP3, AAC with icy-metadata
Very limited metadata capabilities, there does not appear to be any official specification of the icy-metadata protocol despite being in mainstream use for over 20 years. No metadata beyond artist - title, no proper delimiting of these two, unspecified character encoding (though everyone seems to have finally agreed to send UTF-8 by now). Some radio stations even transmit album cover picture links.- Ogg Vorbis
Historically the first format to get of this stuff right, by sending new Vorbis stream headers with each new song. Sadly seems to be dying out.- Opus
Technically possible to send live info as with Vorbis, but nobody seems to do actually it?- FLAC
Live metadata capability missing, libFLAC won't decode concatenated FLAC files with new metadata.- Ogg FLAC
Live metadata capability missing, libFLAC won't decode concatenated Ogg FLAC files with new metadata.
EDIT: libFLAC 1.5.0 can decode chained Ogg streams, this looks like the most promising option so far.
Certain radio station uses Ogg FLAC with icy-metadata, which is a horrible idea but works.
Attached you will find the new log (and cue) files.Just to be clear, the cue file ACCURATERIPID tag replaces adding 14:20:55 to the Data Track box in the Extra section. You don't do both.
Still weird but seem to be getting closer.
How do you feed the bin/cue into CUETools?A very kind person by the name of Adam Gashlin (hcs64) created a few modified dll/pdb files which when added to CueTools 2.2.6, they enable it to understand multi-bin/cue images.
Walls of Jericho, the 14th track, has zeroes for the last 4200-ish samples. The difference to mine - after correcting for offset - is ninety dB down. That is, only in the least-significant bit.
Looks like your drive and/or ripping application cannot handle lead-out?
I use "Ape tags, write stream tags to SQLite, read all three tag types" (not Only Ape). If I tag local *.m2ts file the tag is created in the folder conaining that m2ts audio file. That is great. If I create a tag for radio stream - does it go to the "external-tags" file?I run a normal item in VU meter and adjust the level so it is more or less at 0db.
What would be the best way to find proper peak in radio stream? If it can't be measured should I guess/estimate it from the graphic peakmeter by eye or measure with external dB meter (installed on the phone)?
Change the tag writing option in advanced preferences to "Prefer folder tags, write stream tags to SQLite, read all three tag types" and it will do exactly as the setting suggests. Folder tags will be used when there is a folder to write to, streams will use database and all supported tag types will be read.