1
General - (fb2k) / columns ul panels
Last post by telboy1812 -any idea many more thanks in advance
Please check input and output (compressed as FLAC, because it fits within the 30 MB of files per post limit for the forum). ABX them, and listen them carefully. Post the results when done!
foo_abx 2.2.1 reportDuring the first second the input sounds more metallic. The codec simplified the output. But I don't think this kind of thing is even meant to be transparent. Just a tech demo to squish things slowly into tiny space, modern day VQF.
foobar2000 v2.2 preview 2024-05-01
2024-05-06 17:12:22
File A: input.flac
SHA1: bd824f975ffb8eaa36eedef18a8fba79dc40eb39
File B: output_q5.flac
SHA1: 5b197642f52a03d74215a21597c93cc826a93b37
Output:
XAudio2 : Default Sound Device
Crossfading: NO
17:12:22 : Test started.
17:15:03 : Test restarted.
17:15:03 : 01/01
17:15:08 : Test restarted.
17:15:08 : 02/02
17:15:15 : Test restarted.
17:15:15 : 03/03
17:15:22 : Test restarted.
17:15:22 : 04/04
17:15:28 : Test restarted.
17:15:28 : 05/05
17:15:33 : Test restarted.
17:15:33 : 06/06
17:15:38 : Test restarted.
17:15:38 : 07/07
17:15:43 : Test restarted.
17:15:43 : 08/08
17:15:43 : Test finished.
----------
Total: 8/8
p-value: 0.0039 (0.39%)
-- signature --
22abf4db7b1e2113f428dde825de5fe41b6c6325
The recordings have good quality, but using just my ears I've got a hard time to tell them apart (i.e. Foobar v1 vs Foobar v2).A note: you can load both tracks into fb2k (either v1 or v2), select both, right click, Utilities > ABX tracks and you can do a ABX blind test to see if you can actually tell the difference between the two tracks. Please consider doing this and posting your ABX results!
I am conducting the listening test of the TSAC, and comparison is possible.
Sorry about the bug, I didn't take the same track repeating into account at all. The first version didn't need any special handling for any situation as its logic was super simple.No sweat, continual use has seen no errors so far, you've done it mate!!
New version has been uploaded that outsources time tracking to a separate thread, track switch time should now be accurate to 10 milliseconds, assuming all components report latency correctly.
The component will now detect if it's the same track we are playing and won't seek to the last recorded timestamp, fixes for example the repeat track play mode.
If the timestamp is beyond the current track's duration the component will start the track from the beginning. Previous versions seeked past the end skipping the track entirely.
E:\tsac-2024-04-08-win64>tsac -m E:\tsac-2024-04-08-win64\dac_stereo_q8.bin -M E:\tsac-2024-04-08-win64\tsac_stereo_q8.bin -q 5 c "C:\Users\Public\New folder (14)\New folder (2)\New folder (2)\y2mate.com - Vluarr They Dont Know_44k_s_flac_16sec.wav" "C:\Users\Public\New folder (14)\New folder (2)\New folder (2)\output_q5.tsac"
E:\tsac-2024-04-08-win64>tsac -m E:\tsac-2024-04-08-win64\dac_stereo_q8.bin -M E:\tsac-2024-04-08-win64\tsac_stereo_q8.bin d "C:\Users\Public\New folder (14)\New folder (2)\New folder (2)\output_q5.tsac" "C:\Users\Public\New folder (14)\New folder (2)\New folder (2)\output_q5.wav"
Since lvqcl still hasn't released a 64-bit version I wanted to see if I can improve the quick conversion I did earlier.
Here's a new build that supports both 32-bit and 64-bit foobar2000 versions, dark mode is supported and now fast mode works also on 64-bit variant.
I also added options to resample only chosen samplerates or to resample everything else but the chosen samplerates, so it should allow doing everything mod and mod2 versions did in one file. I didn't see sources for lvqcl's mod variants so this is my custom implementation.
Hello.
I just discovered a new version of the program, and the fact of translation to x64.
And I had only one problem (apart from the fact that the latest version of the plugin for APE is not suitable) - activating the saved edited version of the base shell from the previous version does not work.
The size of the window itself and the panels were not applied. Ok, it doesn't matter, I adjusted it by combining with the previous version of the player, BUT... the player window does not "lock" from changing its size (if you pull the corner / side), despite the fact that I set "lock" to three blue separators shown in the screenshot:
[attach type=thumb]25646[/attach]
In all previous versions, this procedure ensured that the size of the entire player window did not change.
How to achieve this in version 2.0?
Thank you.