So refalac can be used to encode AAC and not just ALAC??
What's the difference between qaac.exe and refalac.exe? Don't the resulting files are identical?
Also, if I may add, and any foobar developers are reading this - as a programmer myself, I can't help but notice that the way Foobar handled this crash was pretty bad. The situation was that the computer is left with no RAM, causing foobar to crash. My question is why does Foobar attempt any writing with no available memory? I know it's usually saving all the data upon the closing, but in this case it resulted in overwriting empty bits over the actual data...Simply no writing whatsoever in a special circumstance like this would be much better.
Could anybody compile recent revision, I would like to test this fixopus-tools x64 v0.1.10-9-gbd65450 (using libopus v1.2.1-25-g43dfdc08)
You are right. Its shorter than 500ms. About 200ms as you said. Sometimes its longer, sometimes even shorter.When I'm skipping a song (from within the default f2k control button: next) the stub image is shown for about 500ms.So it takes over 500ms to skip to the next song on your setup?
I recorded a video.
The first skips are from the f2k controlbutton 'next' button (with activated component foo_preview).
Then from the f2k controlbutton 'next' button with deactivated component foo_preview.
Then I used the buttons from DBC.
You see the stub image very good 8-)
When I'm skipping a song (from within the default f2k control button: next) the stub image is shown for about 500ms.So it takes over 500ms to skip to the next song on your setup?
I've set the delay to 200ms... I guess I just make this delay configurable to be able to handle slower setups.
the changelog sounds great!
Link detection works nice! Its now so simple to check out the, i.e. WWW-tag or discoGS information!
* Version 3.5.0that seems not to be changed.
When I'm skipping a song (from within the default f2k control button: next) the stub image is shown for about 500ms.
I've tested with old path to the stub E:\m\p\f2k\foo_httpcontrol_data\kevo\nocover.jpg
and also a new relative oath: .\foo_httpcontrol_data\kevo\nocover.jpg
Last post by knik -
18.104.22.168 is very fast, to the point I'm running out of the legend space!I'm afraid I have a plan to speed it up even more, like several percent. Maybe you could remove faac-1.28 and put legend to the bottom.
Anyway, new bugfix release:
Last post by Gehirnmaehung -
i used the same configuration for many years now, some rather old version of EAC with REACT. On my new PC i cant install this combination of software and i have to move on to newer versions.
That new version doesnt work yet, the FLAC seems to be different from my old setup, and i cant figure out why.
If i am not mistaken, there arent any new versions of REACT, right? At least i cant find them ... if there are, i will surely give it a try!
What i did instead was installing the latest EAC and just trying to rip CDs, comparing them to the files i already have, with the goal to find a configuration that works the same as the old one (the automation-aspect of REACT will be adressed later, for the first step i want to reproduce the old files).
I rip CDs as whole album, to get one FLAC file with the corresponding cuesheet. I want the gaps to be before the next track (index 00) and i use album-replaygain.
After some toying around i managed to produce the files, but something seems to be wrong. I play them with foobar, and foobar displays just the second track (for every CD i tried), but when i play it, it plays the whole CD starting with track 1. It should display every track individually, obv
At first i thought the problem might be the cuesheet, so i compared them, but they are roughly the same (replaygain still missing, and an empty "composer" variable). Then i copied an old cue to use with the new flac, which didnt change a thing.
Then i used an old flac (ripped with my old setup) with a new cue, and voila - it works as intended.
Now my question is: what setting might be wrong, to produce flacs that behace like that? How can i compare them to one another? Why is always only the second track displayed in foobar?
I hope someone can point me in the right direction
Thanks in advance!
Perhaps the embedded album art is too big.