1
Notice
Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
2
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by marc2k3 -Setting these args as zero when the panel has proper dimensions and is visible is just really stupid. If calling the function succeeded, what exactly do you expect to see??
I really hate doing it but I've updated the function to silently bail if the src w/h are bad,
https://github.com/marc2k3/jscript-panel/releases
edit: the difference in behaviour between v3 and previous versions is because I'm using Direct2D instead of Gdiplus. Gdiplus was generally very tolerant of bad args everywhere but it seems more care is needed now. I already have special conditions in place where drawing text isn't even attempted if the width/height are less than 12px. I discovered this quite early on in my testing!
3
General Audio / Re: Downsampling to 44.1 - integer vs non-integer ratio
Last post by binaryhermit -4
General - (fb2k) / Re: I moved computers. How do I get my original foobar2000 customized interface?
Last post by Porcus -After an install on the new computer, you can try to copy the c:\program files (x86)\foobar2000 folder and the %appdata%\foobar2000 folder over to the new computer. For the latter, you can either access it from within foobar2000 by Alt+Shift+F b - or from the OS by presseing the windows logo key, typing %appdata% and hitting enter.
At worst you will have to delete stuff from your new computer and try over.
5
General - (fb2k) / I moved computers. How do I get my original foobar2000 customized interface?
Last post by kvhpkh -6
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by kode54 -7
Lossless / Other Codecs / Re: Lossless codec comparison - part 3: CDDA (May '22)
Last post by rompel -You are right, I could have made that more clear. The software used for timing returns two values: CPU time and real time (wall clock time). These always differ by a little, I'm not sure how it is possible the wall clock time is sometimes shorter than the CPU-time, I guess that it is caused by some inaccuracy of the timing method.Thanks, that makes sense.
8
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by Sickid -Width or height of 0 is not normal in drawing, though. If either dimension is 0, the object is effectively not being drawn.
As you said, a size of 0 means nothing is painted. (JScript Panel 2).
This is exactly what I want.
9
Lossless / Other Codecs / Re: Lossless codec comparison - part 3: CDDA (May '22)
Last post by ktf -[...]Thanks, fixed.
Seems to be copy-pasted from hi-res comparison and doesn't apply to CDDA.
[...]
Shouldn't the resulting filesize be recorded after encoding, rather than decoding?
I also have a question about the CSV file. Fields 1-3 and 8 are obvious. Fields 4-5 seem to represent encoding speed (i.e. reciprocal of cpu-usage) and fields 6-7 seem to represent decoding speed. But what is the significance of each pair? Are they just two separate runs? Does one give average speed and the other the reciprocal of average cpu-usage? Or something else?You are right, I could have made that more clear. The software used for timing returns two values: CPU time and real time (wall clock time). These always differ by a little, I'm not sure how it is possible the wall clock time is sometimes shorter than the CPU-time, I guess that it is caused by some inaccuracy of the timing method.
For the graphs I've only used the first of each pair, which is CPU-time, which I deemed more accurate. I left the PC idle except for running the tests, no network connections were active, anti-virus was shut down and only 1 of the 4 cores was used, so the values shouldn't differ much.
edit: I say CPU-time and wall time, but it's actually audio length divided by either CPU-time or wall-time. In previous comparisons I used to express speed as 'times realtime', and this is still how the script works. Only during graphing this is inverted to 'percentage of CPU used'
10
Lossless / Other Codecs / Re: Lossless codec comparison - part 3: CDDA (May '22)
Last post by rompel -Quote
Not all codecs appear in all results, for example Shorten and La only support 16 bit per sample sources and WMA does not support samplerates above 96kHz.
Seems to be copy-pasted from hi-res comparison and doesn't apply to CDDA.
Quote
The WAV file is encoded by the chosen codec provided with the required settings. The amount of CPU time required to do this conversion is measured
The encoded file is decoded by the chosen codec. The amount of CPU time required to do this conversion is measured and the resulting filesize is recorded
Shouldn't the resulting filesize be recorded after encoding, rather than decoding?
I also have a question about the CSV file. Fields 1-3 and 8 are obvious. Fields 4-5 seem to represent encoding speed (i.e. reciprocal of cpu-usage) and fields 6-7 seem to represent decoding speed. But what is the significance of each pair? Are they just two separate runs? Does one give average speed and the other the reciprocal of average cpu-usage? Or something else?