I have two versions of this software, the newest I bought today v8.03 and v4.33, the new version will not convert, I just get "Conversion Failed" when trying to convert .dss/.ds2 files to .mp3. What gives? This thread started in 2017 with no answers?
I should note v.4.33 was installed on Windows 7 and 10 and it worked fine.
I installed v8.03 on our Server 2008 r2 box because that's where our dictations are. I've already opened a ticket, hoping to find an answer somewhere though. I've tried running in compatibility mode and even installed the k-lite codec pack, thought maybe that'd fill the gap somewhere.
Same here, except I'm using version 8.00 on an old Mac running High Sierra (10.13.6), and trying to convert from .flac to .AAC.
It was working fine, but now it gives me an error for every file I try to convert (and I've tried well over 50 at this point): "An error has been encountered when converting the file "/Users/macName/Library/Caches/0sJ9D5e/OKmIRCp.flac". Do you wish to continue converting files?" Then in the converter window under the Extended Information column, it says "No audio detected in the file", but there's definitely audio, because all files play in QuickTime Player with no issues. I'm guessing the problem has more to do with the fact that the location shown in the error message is definitely not where the file is located though...
Conversion of The File Has Failed - to MP3
in Switch Sound Converter
Posted
Same here, except I'm using version 8.00 on an old Mac running High Sierra (10.13.6), and trying to convert from .flac to .AAC.
It was working fine, but now it gives me an error for every file I try to convert (and I've tried well over 50 at this point): "An error has been encountered when converting the file "/Users/macName/Library/Caches/0sJ9D5e/OKmIRCp.flac". Do you wish to continue converting files?" Then in the converter window under the Extended Information column, it says "No audio detected in the file", but there's definitely audio, because all files play in QuickTime Player with no issues. I'm guessing the problem has more to do with the fact that the location shown in the error message is definitely not where the file is located though...
Guess I'll be filing a ticket as well!