Last post by wcs13 -
OK, so your method works There is just one small problem that needs to be fixed before I can launch the big operation.
About 7 files out of the 3505 generate problems (I hope I haven't missed anything) : - 676 : "Invalid TIFF header as EXIF data" => 676.txt is still OK, I have checked - 1416 : "SEI type 5 size 5544 truncated at 5531" => 1416.txt is still OK - 2159 : "Invalid frame dimensions 0x0" => 2159.txt has 3 lines : 1280x720, then an empty line, then again 1280x720 - 2383 : "Invalid frame dimensions 0x0" => 2383.txt has 3 lines : 1280x720, then an empty line, then again 1280x720 - 3379 : "Invalid frame dimensions 0x0" => 3379.txt has 3 lines : 1920x1080, then an empty line, then again 1920x1080 - 3388 : "Invalid frame dimensions 0x0" => 3388.txt has 3 lines : 1920x1080, then an empty line, then again 1920x1080 - 3416 : "No frame!" => 3416.txt is still OK
So maybe in your code, we should check if the error is "Invalid frame dimensions 0x0", and make sure the resulting .txt file still has only one line, not three. Because the "out.txt" file needs to have exactly 3505 lines, no more, no less. Could you help me with that please ?
Last post by Peter -
Note: bug verified on Windows 10 1803 with 250% text size. From the looks of it it's an old problem (classic Windows controls incompatible with large text sizes) rather than a new one.
Last post by anamorphic -
I had a look at mine with Segoe UI and nothing is cut off, I can see the bottom of the 'g' correctly on a non-active tab.
As a point of comparison, my Windows display scaling is 125% and I'm on Windows 10 v1803, and Segoe UI Regular font is version 5.55. I wonder if it might be the same issue that is effecting rating stars on 1809 or at least a similar glitch that was introduced.
Last post by Peter -
Bug confirmed, thanks for reporting.
However, it's not foobar2000 that is to blame, it's the standard Windows tab control which handles the text display and truncates the bottom of your letters - verified with other instances of the tab control. Any other app using the standard tab control will get the same bug.
I'll see if there's some way to work around (short of inventing own tab control....) this but don't keep your hopes up.
Last post by jsdyson -
This will only work for those who are highly technically inclined, and understand the behavior of filters. If the techie just wants to 'equalize' certain files -- or even process some files with equalization, they can use sox in the same way that I use all of the time -- like this:
The above is fairly obvious -- +3dB@50Hz 1.4q, -3dB@9k 0.707q, LF monotonic (0.707q is monotonic) rolloff at 20Hz, and a peaky rolloff at 16.5kHz (a q=1.0 means a dB or so boost at 16.5kHz, but a quick rolloff after that.) There is also a bass/treble shelf command: bass dB hz q. So, if you want to do a monotonic bass boost of 3dB at around 320Hz, the specify a q of 0.707. (for a 2nd order filter, a q of 0.707 is butterworth. A bessel approximation is about 0.500 q.)
The same kind of thing works with the sox based play command:
play infile.wav equalizer 50 1.4q 3.0
(Any of the frequency modification commands work with 'play' also) There is also a 'sinc' command which does a simple FIR style filter, which can give linear or minimum phase, and can be very sharp without extreme modification of the waveform.