by fugusushi » Tue Mar 23, 2010 5:25 am
so this thread and it caught my eye -- i made this
http://www.mediamonkey.com/forum/viewto ... 27crack%27 bug report Aug. last year...
i'm still using MM 3.0.7.1191 and until v.recently, that had solved the 'static pop' i was getting at the start of some tracks. But then the issue resurfaced. I read this thread which made me reconsider what the hell i had done that could have brought it back.
Turns out 'the culprit' was an input plug-in as suggested here. But for me, it was AAC format pugin v1.06 (AAC/M4A Encoder / Decoder Plug-in 1.06). I can't remember why, but for some reason i thought was good at the time, I installed this a few weeks ago. I'd forgotten all about it, and certainly not paid for it after the 30day trail.
Anyway, I removed this, removed/re-synced the content, and all is well again, no static pops at the beginning of tracks...
Perhaps GRW you can check and see if you have this plug-in and kick it out if you have (although of course, it may not be the plug-in, just some other issue - perhaps two plug-ins vying to do the same job? or perhaps if you don't buy this plug-in, this is the result?)...
so this thread and it caught my eye -- i made this http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=41883&hilit=static+%27crack%27 bug report Aug. last year...
i'm still using MM 3.0.7.1191 and until v.recently, that had solved the 'static pop' i was getting at the start of some tracks. But then the issue resurfaced. I read this thread which made me reconsider what the hell i had done that could have brought it back.
Turns out 'the culprit' was an input plug-in as suggested here. But for me, it was AAC format pugin v1.06 (AAC/M4A Encoder / Decoder Plug-in 1.06). I can't remember why, but for some reason i thought was good at the time, I installed this a few weeks ago. I'd forgotten all about it, and certainly not paid for it after the 30day trail.
Anyway, I removed this, removed/re-synced the content, and all is well again, no static pops at the beginning of tracks...
Perhaps GRW you can check and see if you have this plug-in and kick it out if you have (although of course, it may not be the plug-in, just some other issue - perhaps two plug-ins vying to do the same job? or perhaps if you don't buy this plug-in, this is the result?)...