First of all, thank you for your clear cut response. Now, instead of nitpicking every word and being an edgy asshole full of yourself, do you possess any relevant knowledge on how to get the bit depth value with ffprobe? That was my main point of asking the question, in the first place, in case you were “missing”.
Thank you. > On 4 Aug 2020, at 09:11, Carl Eugen Hoyos <[email protected]> wrote: > > > >> Am 04.08.2020 um 02:57 schrieb scrutinizer <[email protected]>: >> >> This is, in effect, relates to the similar topic raised in January 2018 no >> this forum (“Sample types 's32 (24 bit)' and 's16 (24 bit)' are confusing to >> me”). > > There are „links“ nowadays, have you ever used them? Not necessary, since it seems you were > >> In it, the user was given a very contradicting response to the concern that >> ff-utilities couldn’t discern between 32 and 16-bit on one side and 24-bit >> on the other > > (Still) true and will not change. > >> talking about RAW audio whose source was digitized analogue audio. > > This is misleading. In what way? An answer as blunt as yours, that's misleading. The output the user provided showed the audio created from an LP. But that’s not what my question was about, so we move on. > >> THe responder claimed that it was both a bug and intended behaviour and not >> a bug which looks confusing at the very least. > > This interpretation is ridiculous: > The OP mentioned two „issues“ (you mentioned them in your summary above), one > was a bug that was fixed long ago (back then), one is a technical detail > about internal properties of libavcodec that do not lead to limitations in > the output files. If that was misunderstanding then it’s on your quite disrespectful, rude and brazen way of communicating your thoughts. Something to think about. Or is it a common trait of tech people - to treat people like scam and unidentified blocks of corrupt data? > >> I faced the same issue today > > Command line and complete, uncut console output missing. If you want me to > guess: mp3, aac, ac3 and friends do not have a „bit depth“, they store > coefficients. > Mr. Car Eugen, if you pretend to be in possession of the fullest expert-level knowledge then you don’t need a log for what should be a commonly used option - retrieving the value. I’m asking once again: is it possible to retrieve the bit depth value of an audio-file like the application I mentioned in my OP with ffprobe or another ff-utility? Yes, no. If yes - how. Nothing more required. > Carl Eugen > _______________________________________________ > ffmpeg-user mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
