Last post by Anakunda -
I bet that you won't recognize any difference between CBR 512 and VBR Q127 unless you have a high end setup in the car, and you highly probably won't even notice a difference between VBR @Q100. That's just a placebo feeling. I would suggest to use anything above ~192kbps and you will be safe.
Last post by SigHunter -
I'm sure I'm not the first one asking this, but I could not find a definitve answer.
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 Regards
Last post by Case -
The lack of replies means people can't help you.
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.
Last post by Case -
I saw it but I had nothing to comment.
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.
Last post by kode54 -
And he is suggesting that foobar2000's converter automate the process of converting to a faster storage medium, then move the resulting file set to the destination. Sounds like a doable feature, maybe? Still needs a configuration option for where to store the converter output while operating, and what to do if the application crashes while conversion is happening. (Then it will also need to know what to do with partial or completely converted files in the configured directory on startup.)