|
|
It is expected behavior. The file is not leveled because of clipping prevention - there is very loud sound between 1:46 and 1:47, this sound would be clipped. |
|
|
|
It's fine that the track can't/won't be leveled, but there needs to be feedback to the user as to why it wasn't leveled and with the feedback perhaps an option to level anyway. |
|
|
|
I've replied to the user immediately. Maybe you looked on the older ticket (user inserted two for the same issue). Both tickets are now closed (user confirmed solution). |
|
|
|
I din't mean a response to the ticket (I saw it). I meant that MediaMonkey needs to provide feedback to the user as to why nothing happened. So users aren't forced to contact support, provide file and wait for an answer as to why it wasn't working as they expected. |
|
|
|
But I think, it is working as expected, the file is leveled as much as it could be with the given settings, as it should be. In this case, it was already on the max level before (because of the peak), so no change to the file was required. It is the basic characteristic of the leveling with clipping prevention. It could be in the help/KB (in case it is not already there), but I don't think, it should be in some message dialog. There are more situations, what about, if, because of some smaller peak, it is leveled, but not as much as some user expected?
Jiri, what do you think? |
|
|
|
I'm not sure whether it's worth implementing, but on the other hand, if it could reduce the # of support tickets, it might be worth it. Maybe something like showing our standard error dialog after leveling of _all_ the tracks saying something like 'the track couldn't be fully leveled in order to avoid clipping'. Rusty? |
|
|
|
Even I thought that there was something wrong with MediaMonkey or the file, thus the user should be informed why nothing happened. |
|
