bertox

Don't feed him bro, he only wants to argue... "Cheap storage"... yea sure. Right. 🙃

CPU use for FLAC decoding is next to absolute NOTHING, and we are on 2025 with modern CPUs so that would equal to ZERO usage really... is a matter of devs finally modernizing their software i think. I think the real problem is maybe the lack of full 32bits full support for the FLAC codec still. I mean, FLAC as today supports 32bits, but not the whole community using it. So i think that would be sole problem.. the community adoption. Nope. My PC shows all extensions, just i didnt realize so quickly that this DAW cannot use direct reading FLACs and im so used to play FLACs on my PC that i feel it really natural now.. so i forgot that FLACs are not a 'base' format (btw i repeat, they should be now! 40% less space than WAVs and almost zero impact on CPU while decoding!)

OK i've found the culprit: ME. 😅 I was importing FLAC files not Wavs.. 🤦‍♂️ So it stored every converted file on the Audio Data global folder, of course, as it supposed to do. Btw NOW... i find it pretty bad that today -in 2025- this DAW still converts the FLAC files instead of read em' directly from storage.

LOL 😅 you both above me saying contradictory things... Besides that, seems no one really reads what i said... mostly the part of I TRIED ALL.

I just need to IMPORT my audio files and mix em'. Nothing more. No need to copy em' to another location nor move em'. I need em' to stay where they are. And a DAW should use em' no problem if same sample rate and bit depth of the project. Well, sadly thats NOT HAPPENING here. No matter how i try. It always copy my audio files to the C:\ global folder, wasting my ssd space.

Well, as i said: its not happening to me, no matter what i set or what file im importing.

Yes, i unchecked the "Always copy.." setting and all that.. but every audio file i import gets copied to the Audio Data global folder on C:\. No matter the bitrate or the freq, or if new or old project, ALWAYS get copied despite i say it to don't do that. I think this is a BUG. I remember old Sonars not having this nonsense issue.