When I look at my example I can see a portion in binary looks still the same (so intact partially) but in decimal the number is a completely different after shortening.Burillo wrote: ↑Thu Feb 14, 2019 9:57 pm"truncated decimal" would rather be 200377, not 120037. truncation starts from the top.Etienne1973 wrote: ↑Thu Feb 14, 2019 9:56 pm Does binary keeps information partially intact when truncated instead decimal looses info completely?
For Example:
24Bit word truncated to 16Bit
1011 1111 0101 1101 1010 0110
____ ____ 0101 1101 1010 0110
decimal number truncated
1'200'377
120'037
The truth about bit-depth (and digital audio ‘resolution’)
- KVRAF
- 1754 posts since 8 Feb, 2013 from Switzerland
- KVRAF
- 4439 posts since 15 Nov, 2006 from Hell
that's because you did the truncation wrongly. you truncated binary from the top, but you've truncated decimal from the bottom. if you truncate it from the top, just like you do with binary, you'll keep "a portion of the information".Etienne1973 wrote: ↑Thu Feb 14, 2019 10:37 pmWhen I look at my example I can see a portion in binary looks still the same (so intact partially) but in decimal the number is a completely different after shortening.Burillo wrote: ↑Thu Feb 14, 2019 9:57 pm"truncated decimal" would rather be 200377, not 120037. truncation starts from the top.Etienne1973 wrote: ↑Thu Feb 14, 2019 9:56 pm Does binary keeps information partially intact when truncated instead decimal looses info completely?
For Example:
24Bit word truncated to 16Bit
1011 1111 0101 1101 1010 0110
____ ____ 0101 1101 1010 0110
decimal number truncated
1'200'377
120'037
what you did:
1'200'377
120'037
what you should have done:
1'200'377
'200'377
I don't know what to write here that won't be censored, as I can only speak in profanity.