I was looking to combine IIR Filter or possibly a VST EQ with resampler into one pass.
Try with this one.
EasyQ - http://www.rs-met.com/freebies.html
Even if you can't hear a difference there technically is more potential in higher bitrates or different algorithms.No there isn't.
I would suggest to use anything above ~192kbps and you will be safe.
... or else it would probably be significant in size, if it were, say, providing a complete copy of V8, like nodejs does.Dunno about V8, but SpiderMonkey (Firefox JS engine) takes only ~18Mb, so it's not really that bad =)
My car stereo only plays mp3 and aac. So flac in the car is sadly not an option.
But I want to get as close to that as possible. Size is not an issue.
I do not care about "audible difference" or something.
Even if you can't hear a difference there technically is more potential in higher bitrates or different algorithms.
I use foobar2000 to transcode my flacs to aac, so forgive me if I don't know the exact corresponding command line parameters.
I have the following options:
- VBR Q 127 : 320 kbps
- Constrained VBR 512 kbps
- ABR 512 kbps
- CBR 512 kbps
Should I just go with CBR 512? Is CBR 512 the absolute maximum AAC can do? Like 320 CBR mp3?
Or is it possible to get even closer to "lossless" with VBR, CVBR or ABR?
I am looking forward to being enlightened. Thanks
Everything your Google product does it does on its own.
The developer doesn't have Google Home and no tester has such devices either. I made a quick google search about the product the day you posted first and it looks like one is supposed to program some cloud products for it and try to make money that way. I didn't see any means to use it on desktop world in C++ programs, but such information could of course be hidden or I just suck at googling.
Empty UI elements suck but these components are waveform seekbars, not spectrogram visualizers. If I used streaming audio more than to quickly test something, I'd probably be more willing to hack together something.