Page 2 of 3

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Mon Jun 25, 2018 2:39 am
by Ludek
Thanks for the list of your scripts, I am going to install them and try to replicate and fix the issues as https://www.ventismedia.com/mantis/view.php?id=14898

Stigg wrote:
Sun Jun 24, 2018 9:01 pm
Ludek wrote:
Sun Jun 24, 2018 3:33 pm
Hi Stigg,
thank you very much for your feedback.

Unfortunately the debug logs don't include any MediaMonkey messages, they were probably generated using the release build, could you please download and install debug builds and generate them again?
1864 debug: http://www.mediamonkey.com/beta/MediaMo ... _Debug.exe
1871 debug: http://www.mediamonkey.com/beta/MediaMo ... _Debug.exe
Thanks!
Thanks, I can replicate this, to be fixed as https://www.ventismedia.com/mantis/view.php?id=14897
Do I still use DebugView with the MediaMonkey Debug versions?

I used DebugView on 4.1.20.1864 and 4.1.21.1871 RC normal versions separately. It produced different logs.
I don't know why it didn't give you what you needed.
Normal builds don't produce any MM messages into DbgView, please download and install the debug builds (links above), start DbgView, start the debug builds and re-attach the new set of logs from the DbgView.
Thanks!

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Mon Jun 25, 2018 5:42 am
by Ludek
I've tried to install the same set of scripts as you and based on my testing the startup time of 1864 and 1871 is nearly the same, BUT:

with 1864:
- splash screen is shown (2 seconds)
- nothing is shown (from 2 seconds) - scripts are loading silently
- main window is shown with loaded scripts and panels
Overall time: 4 - 5 seconds

with 1871:
- splash screen is shown (2 seconds)
- main window is shown immediately and scripts are loading for 2 seconds with progress like this:
https://www.dropbox.com/s/7equefkm2u4rm ... 8.png?dl=0
i.e. the panels for "Lyrics and Comment" and "Monkey Rok" are blank until scripts are loaded (2 seconds)
Overall time: 4 - 5 seconds

i.e. the only change is that loading of the scripts is visible which was intention because of issue https://www.ventismedia.com/mantis/view.php?id=14820 where some scripts (like RegExp Find & Replace) took 60 seconds to load after recent Windows 10 update and users were not aware what is happening and what is causing the startup slowdowns.

Are you seeing the same or the overall loading time of 1871 is much worse for you?
Could you generate the logs to compare?
BTW: How you got the "Comment Viewer" window to the left? I can't seem to do this, it is not dragable.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Mon Jun 25, 2018 8:28 am
by Ludek
FYI: I've done some optimizations in 1872.

1) there were some actions (related to system tray) that could take some time and were performed before scripts loading, previously (in 4.1.20.1864) the actions were performed _after_ the scripts loading. So maybe it could do the difference for you.
2) I've made UI loading more fluent whenever there is a lot of scripts with long loading times

EDIT: You can test the changes by replacing your current MediaMonkey.exe (from build 1871) by this one:
https://www.dropbox.com/s/q0e0phjxptl7u ... y.exe?dl=0
It is also debug exe so it will produce messages in the DbgView too.

Thanks.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Mon Jun 25, 2018 11:11 am
by Lowlander
Yes, you still need to use the debug version of Beta/RC releases to get DBGView to capture from MediaMonkey.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Mon Jun 25, 2018 3:57 pm
by Peke
Hi,
Only debug versions send all the data as normal version only send partial data. So you need to use debug versions to create logs.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Tue Jun 26, 2018 8:45 pm
by Stigg
Here they are.
They're big. 10 MB each.

I have zipped them up, and you can download it here.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Wed Jun 27, 2018 3:10 am
by Ludek
Thanks for the logs, I've analyzed the logs and it seems to confirm my experiences and test results described above (note that my startup times were better because I haven't started DbgView).

Based on your logs:
- with 1864 it took 12 seconds to show the main window (with scripts loaded)
- with 1871 it took 10 seconds to show main window and scripts were loading for 2 seconds

So the overal time is nearly the same, but in case of 1871 there were the blank panels with progress "Loading... scriptNameX.vbs" shown for 2 seconds.
Can you confirm?

Could you please also replace your current MediaMonkey.exe (from build 1871) by this one:
https://www.dropbox.com/s/q0e0phjxptl7u ... y.exe?dl=0
And generate one more log? It should improve the loading time and experience slightly.

Thanks!

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Wed Jun 27, 2018 8:12 pm
by Stigg
Here is the new log.

My original problem seems to be fixed with this version :), although it is very, very slow monitoring all my files (tracks). But, I also noticed it being very slow with other debug versions. Maybe it's just a debug issue.

I also get this UPnP.dll error.
Error: UPnP.dll is not compatible with this version of MediaMonkey! Reinstall MediaMonkey.
Image

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 6:13 am
by Ludek
My original problem seems to be fixed with this version :)
Thanks for confirmation.
although it is very, very slow monitoring all my files (tracks). But, I also noticed it being very slow with other debug versions. Maybe it's just a debug issue.
Yes, debug builds are slower (especially when DbgView is started)
I also get this UPnP.dll error.
That's ok, this is just that you copied MM.EXE from another build that is not compatible with UPnP.dll from older build.
We are going to post another RC (1872), so just install build 1872 to that folder to fix the issue. It will be posted hopefully today (I am just revising one more issue).

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 7:08 am
by ZvezdanD
Ludek wrote:
Thu Jun 28, 2018 6:13 am
That's ok, this is just that you copied MM.EXE from another build that is not compatible with UPnP.dll from older build.
That is not OK, as I explained here: https://www.ventismedia.com/mantis/view.php?id=14870

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 7:28 am
by Ludek
ZvezdanD wrote:
Thu Jun 28, 2018 7:08 am
Ludek wrote:
Thu Jun 28, 2018 6:13 am
That's ok, this is just that you copied MM.EXE from another build that is not compatible with UPnP.dll from older build.
That is not OK, as I explained here: https://www.ventismedia.com/mantis/view.php?id=14870
What's strange about the fact that the interface between UPnP.dll and MM.exe was updated? If you don't want to see the message at all then just remove UPnP.dll entirely or copy the UPnP.dll corresponding to the given MediaMonkey.exe (i.e. UPnP.dll from the same build as MediaMonkey.exe)

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 9:25 am
by ZvezdanD
Ludek wrote:
Thu Jun 28, 2018 7:28 am
What's strange about the fact that the interface between UPnP.dll and MM.exe was updated?
It is strange because it worked fine without that message until recently. I don't know exactly in which build that message started to appear.
Ludek wrote:
Thu Jun 28, 2018 7:28 am
If you don't want to see the message at all then just remove UPnP.dll entirely
Ok, thanks for the hint. I didn't expect it will work with that file removed.
Ludek wrote:
Thu Jun 28, 2018 7:28 am
or copy the UPnP.dll corresponding to the given MediaMonkey.exe (i.e. UPnP.dll from the same build as MediaMonkey.exe)
It seems you didn't understand my explanation. I have a bunch of the MediaMonkey-xxxx.exe files from different builds in the _same_ folder and I can start any of them without reinstalling that particular build, but all other files in that folder are from the latest installed version (dlls and such). I cannot have a bunch of UPnP_xxxx.dll files in the same folder. Well, I can, but exe will not link to them, but only to UPnP.dll.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 9:36 am
by ZvezdanD
Here are the files that I have in the same folder:

Code: Select all

DeskPlayer.temp.0
MediaMonkey.chm
unins000.dat
DeskPlayer.dll
Equalize.dll
FastMM_FullDebugMode.dll
Gain.dll
hpCDBurn.dll
id3lib.dll
iPhoneCalc.dll
lame_enc.dll
libeay32.dll
libresample.dll
MMHelper.dll
mp3gain.dll
ogg.dll
PrimoBurner.dll
SQLite3_iOS8.dll
SQLite3MM.dll
ssleay32.dll
Unzip32.dll
vorbis.dll
WMAFunct.dll
WMAuth.dll
4gb_patch.exe
DBUpgrade.exe
Decoder.exe
MediaMonkey.exe
MediaMonkey (non-skinned).exe
MediaMonkey-1333-x.exe
MediaMonkey-1343-x.exe
MediaMonkey-1344-x.exe
MediaMonkey-1345-x.exe
MediaMonkey-1346-x.exe
MediaMonkey-1348-x.exe
MediaMonkey-1349-x.exe
MediaMonkey-1351-x.exe
MediaMonkey-1352-x.exe
MediaMonkey-1358-x.exe
MediaMonkey-1364-u.exe
MediaMonkey-1365-u.exe
MediaMonkey-1367-u.exe
MediaMonkey-1368-u.exe
MediaMonkey-1383-u.exe
MediaMonkey-1389-u.exe
MediaMonkey-1391-u.exe
MediaMonkey-1392-u.exe
MediaMonkey-1394-u.exe
MediaMonkey-1395-u.exe
MediaMonkey-1422-u.exe
MediaMonkey-1436-u.exe
MediaMonkey-1442-u.exe
MediaMonkey-1459.exe
MediaMonkey-1466.exe
MediaMonkey-1470.exe
MediaMonkey-1501.exe
MediaMonkey-1504.exe
MediaMonkey-1511.exe
MediaMonkey-1609.exe
MediaMonkey-1646.exe
MediaMonkey-1650.exe
MediaMonkey-1652.exe
MediaMonkey-1656.exe
MediaMonkey-1658.exe
MediaMonkey-1661.exe
MediaMonkey-1662.exe
MediaMonkey-1683.exe
MediaMonkey-1703.exe
MediaMonkey-1737.exe
MediaMonkey-1867.exe
MediaMonkey-1868.exe
MediaMonkey64Helper.exe
MediaMonkeyService.exe
MediaMonkeyVHelper.exe
unins000.exe
UninstDP.exe
VisHelper.exe
winamp.exe
WinAmp.ini
QTSource.lic
readme.txt
whatsnew.txt
MediaMonkey.url
UPnP.dll.z
I could start any of these MediaMonkey-xxxx.exe files just by double-click. These builds that have -u and -x in suffix have some strange behaviors with enlarged fonts. These builds that have -x in suffix additionally display some error on the startup, but after that they work fine at least for testing my scripts with them.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 12:07 pm
by ZvezdanD
Ludek wrote:
Thu Jun 28, 2018 7:28 am
If you don't want to see the message at all then just remove UPnP.dll entirely
Actually, this suggestion doesn't work. The program becomes unresponsive after a while. This is happening with 1866, 1867 and 1868, but not with 1737 and older that I tested.

Could you please tell me which was the last build which had UPnP.dll that doesn't check version of the program?

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 2:01 pm
by Ludek
Zvezdan, testing MediaMonkey.exe in build folder from another build will mostly cause issues, because not only the EXE is changing, but also the plugins and DLLs, so in short this isn't realiable method of testing that would make a sense.

I am also testing older builds, but I have each build installed in another folder like this:
C:\MediaMonkey 4.1.20.1864\
C:\MediaMonkey 4.1.21.1868\
C:\MediaMonkey 4.1.21.1870\
C:\MediaMonkey 4.1.21.1871\

This way I am sure that all DLLs and plugins are compatible with corresponding MM.exe