View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009270 | MMW v4 | Conversion/Leveling | public | 2012-04-13 15:23 | 2013-05-24 02:23 |
| Reporter | Assigned To | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | won't fix | ||
| Product Version | 4.0.4 | ||||
| Summary | 0009270: Repeated requests to run decoder.exe | ||||
| Description | Windows 7 x64 with a portable installation on a NAS. While synching MM auto conversions from wma to mp3 require decoder.exe to be run. There are repeated requests from Windows to run the executable - once per invocation: "Do you want to run this file?". What is annoying it the repeated aspect. I had 20 wma files that I was converting to mp3 as part of the sync activity and so I get 20 prompts. This is just part of my test suite - imagine what it would be like for 1000 conversions. I can imagine what MM's implementation is - it simply shells out to DECODER.EXE for each file. It would be better if 1. It shelled out once for all of the necessary decodes (so there was just one prompt) 2. It shelled out differently such that the pop-up doesn't occur at all (suspect not possible) 3. Convert DECODER.EXE into a DLL and call it directly. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=65401 | ||||
| Tags | todoc-help | ||||
| Fixed in build | |||||
|
|
The big advantage of current way of calling is, that if the decoder crashes for some reason, it will not affect main process MediaMonkey.exe (because it is different process), it just fail gracefully. The same situation is with video playing/converting and MediaMonkeyVHelper.exe and it was the reason, why it was separated to different process. |
|
|
As described at the forum report, the fact that Windows prompts for each time a remote process is run needs to be resolved at the level of Windows. The solution to this is: 1 Run gpedit.msc 2 Go to User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager 3 Add "*.exe" to the "Inclusion list for moderate risk file types" setting. |
|
|
Another workaround by using Control Panel > Internet Options > Security > Select Local intranet > Sites > Advanced > Add the mapped drive (e.g. Z:\) or UNC path (e.g. \\sharename) |
