Closed darwincr closed 2 years ago
Not without some code rewrite. Compatible decoders are filtered by file extension and then tried sequentially, for performance reasons. So for example, if you have an .m4a file it'll only try to decode it as AAC or ALAC. I suppose we could have a switch to have it try all of them, but it seems pretty niche. You should just fix your files IMO.
I used the error output to fix incorrect filenames manually thanks for your powershell module nice work
I am having an issue where some files are sometimes named .wav but they are of .mp3 or .wma format (incorrect extension)
When I do a Get-AudioFile it fails:
if i remove the file extension, it fails with this error:
Is there a way I can get these to work without manual intervention?
88c37d0d-918e-4c6a-860a-1865c3285da2.zip