Opus and Explorer show the same things here.
You'll probably need to give us an example file.
Opus and Explorer show the same things here.
You'll probably need to give us an example file.
Yes, I understand that it does Jon.
What code shows the actual encoder (codec) used? That is what I am after.
Tell us which MP3 frame you want and we can add it.
Ah, there's the rub, I don't know what it is, because apparently, it isn't part of the official spec, but it is there, as well as other stuff, which is also probably not part of the official spec. It is the same bit of the file that Windows is showing when you turn on the poorly named "ENCODED BY" field.
dBpoweramp also sees this info, as well as a bit of other stuff, such as encoder settings, and contains. If you could add them, that would be mighty fine.
Sure, we'll add it when you tell us what frame it is.
Jon: 1, Gus: 0
(Windows explorer: 2)
or you could use TSSE
Thanks Jon
"Software/Hardware and settings used for encoding"
Is that the one you want?
Yes please, that be it. Not sure how that comes out when you look it at.
Media info for example shows
Writing library : LAME3.98r
where dBpa shows
LAME 3.98r
and
CBR 64K
as separate entries.
Ideally, just the actual encoder used is what I am after.
Also, ss there a way to get the DURATION {mp3songlength} shown any custom way, so instead of 7:49:13 for example, it would show
7 hours 49 minutes 13 seconds?
The below works fine, until you hit a file that is less than an hour, in which case it shows 12 hours x minutes y seconds
Duration : {mp3songlength|T#h 'hours' m 'minutes' s 'seconds'}
Try H (24 hour clock) instead of h (12 hour clock).
(Not sure what happens in either case when it's over 23 hours, though. I'm not sure it's intentional that the date/time format codes work with duration fields.)
Perfect, H works, now why didn't I think of that? Thanks Leo.
We've added a column to show the TSSE frame to Beta 9. The keyword for it is {mp3encodingsoftware}.
Cool, thanks Jon, that was fast