Last post by jsdyson -
A very horrible thing with float 32 file is they can be encoded in different "normalized" fashions. If the decoder misinterpret the format, the result will be horrible full scale square wave-ish like crap which may destroy your equipment. I experienced this nightmare several times, sometimes in foobar2000, sometimes in Audition.oh my!!! Most of the files that I have dealt with are +-1.0 floating point, but I do know that it is theoretically possible to sent out files with bigger numbers. I always believed that +-1.0 floating point is the same as +-32767 for 16 bit signed -- and so be it... So, you have seen different? But of course, invalid files with >+-1.0 (assumed that they were invalid) should be clipped and/or flagged. In between running my Unix pipelines, I do (incorrectly, I believe) SOMETIMES during my experiments, take advantage of being able to deal with greater than normal floating point values. For example, I might have an expander whose output might peak at +-2.828 (just as an example) due to exceptional material, but then future normalization stages will fix it. On the other hand, 'sox' will complain about such files, and probably should process the file if the results are correctly normalized, or MAYBE SHOULD BASED UPON COMMAND LINE FLAGS simply bounce the file somehow?.
Your point about nonstandard floating point values is definitely a valid issue, however. (By the way, the term normalized/un-normalized has a specific meaning the the floating point realm -- when the term different 'normalization' was used -- I assumed being able to handle differing/odd ranges of values, right?)
So, to me, it seems like the FP format should be standardized, or avoided for interchange. I suspect that for most (all) PRACTICAL purposes, the signed 24 bit should be sufficient, but wonder if it also has such scaling issues? (I use 24bit only so that I can use flac with reasonably high resolution.)
Minimize with a hotkey seems fine, but who really needs to password protect just their music player, and not the whole bloody user session? Nobody but me is ever getting to use my user session without permission, I'll just give them the Guest account.
Last post by kode54 -
I've bought a few CDs, and also acquired lossless and even lossy rips either by shady means or by purchasing downloads directly, but mostly these days I listen to streaming music. I just switched from Spotify to Apple Music again last month.
Never mind that half of the built in equalizer's bands are brickwalled on either side.
I've already proposed this once, foobar2000 should do it like mIRC:
sorry i was wrong, it does work, i simply made a silly mistake.Here too, much faster: http://tmkk.undo.jp/lame/index_e.html
Thanks for the suggestions everyone.
20-30 feet of shielded coax shouldn't normally be a problem with line-level signals. I believe you, I'm just saying there might be something wrong with the wires... Maybe they are not shielded. You say there are two... You only need one for the sub, so have you tried them separately?To be clear, it’s one conductor with a ground shield around it. Spdif is digital, and with the kind of voltages and frequencies it operates at I really doubt household ground noise would have any effect at all on its signal integrity.
The electrician probably routed the cable right next ac lines. I really should have a lot more attention when they were doing work.
Last post by bennetng -
A very horrible thing with float 32 file is they can be encoded in different "normalized" fashions. If the decoder misinterpret the format, the result will be horrible full scale square wave-ish like crap which may destroy your equipment. I experienced this nightmare several times, sometimes in foobar2000, sometimes in Audition.
Of course, in DAWs if people find the decoded waveform looks like crap, they won't hit the play button, but that's not the case with typical audio players.
I don’t know how he compiled, is there any reason we shouldn’t use tmkk?All builds sometimes create different files, even the x86 and x64 version from the same bundle. From the null test results I am unable to tell which particular build has more differences than the others, plus I can't ABX them. Therefore I am going to use tmkk's version for the speed.
It's been discussed in detail before, but basically floating point numbers have rounding error, so each of the many ways you can compile a mathematical operation may give slightly different results due to how the numbers round. If you need deterministic output, you're probably looking for a lossless codec.