• Features & Ideas
  • why doesn't Sonar simply tell me the name of the corrupt audio file it intends to pad?
2016/09/20 17:01:40
GregGraves
It really is a nuisance every time I open this one project I get the msg about Sonar finding a corrupt audio file.  Obviously, if Sonar found it, then it knows the name of it ... so why doesn't it simply say "filename 17R12z.wav is corrupt" instead of the message that it gives which is useless toward correcting the issue.  The project functions properly, but it certainly is annoying that I get that error every time, and it doesn't make my clients feel "secure" I know what I am doing.  Since there are 169 files in the audio folder, I simply do not have time or inclination to dig through all of them to see which might be corrupt in some way or other.
2016/09/21 02:25:10
kevinwal
This is a great suggestion. Have you logged it as a feature request?
2016/09/21 03:54:28
GregGraves
I did now.
2016/09/21 06:30:39
tenfoot
Have you resaved the project after the corrupt/padding message? I had a couple of projects with that message but it never recurred after resaving.
2016/09/21 10:30:47
Sacalait
I agree it would be a great feature.  I hasn't happened in a while for me but when it does it's frustrating.
2016/09/21 10:44:24
GregGraves
Yes, I"ve resaved, renamed and resaved but it is still there.  After thinking about this problem a bit more, I've come to the idea that the best way to resolve is for Sonar to color the offending clip in stripes or something.
2016/09/26 14:21:19
GregGraves
Well, folks, its still there, and I can't find it, and it bugs me.
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account