Rusty had this "Metadata lookup undefined" already reported in:
https://www.ventismedia.com/mantis/view.php?id=18316
But here its more serious than just failing to auto tag.
The first time in a MM session using auto-tag lookup simply results in "failed" and can be closed by "cancel".
But after the second or third time MM completely crashes "not responding" and has to be forcefully closed.
Several auto-generated reports have been sent.
Let me know if you need something tried.
[Solved in 2526] MM5.2503 Auto-tag unusable at the moment
Moderator: Gurus
[Solved in 2526] MM5.2503 Auto-tag unusable at the moment
Last edited by Friedrich on Thu Dec 09, 2021 10:39 am, edited 1 time in total.
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Re: MM5.2503 Auto-tag unusable at the moment
Will check your bugreport. Thanks for a feedback.
How to make a debuglog - step 4b: viewtopic.php?f=30&t=86643
MM5.2508 Auto-tag still crashing MM
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Re: MM5.2508 Auto-tag still crashing MM
Hi,
Due the recent changes in 2508 I have tested Auto Tag extensively past few days and, no crashes happen on 10-1000 tracks in Auto Tag.
Can you please open support ticket and supply debug log with crash in it as described here viewtopic.php?f=30&t=86643 so that we cn analyze why it crashes on your system.
Due the recent changes in 2508 I have tested Auto Tag extensively past few days and, no crashes happen on 10-1000 tracks in Auto Tag.
Can you please open support ticket and supply debug log with crash in it as described here viewtopic.php?f=30&t=86643 so that we cn analyze why it crashes on your system.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Re: MM5.2508 Auto-tag still crashing MM
[Ticket #2883] opened with the latest log-id.
1 or 2 autogenerated logs referring to auto-tagging problems had also been sent previously.
Sometimes its complete "white out" though and no auto-log dialog appears.
1 or 2 autogenerated logs referring to auto-tagging problems had also been sent previously.
Sometimes its complete "white out" though and no auto-log dialog appears.
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Re: MM5.2503 Auto-tag unusable at the moment
Hi,
Can you please rename "persistent.json" to "1Persistent.json", delete "Persistent.json.bck"" and start MM5 to see if crash still occurs?
Can you please rename "persistent.json" to "1Persistent.json", delete "Persistent.json.bck"" and start MM5 to see if crash still occurs?
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Re: MM5.2503 Auto-tag unusable at the moment
Still occurs. No difference.
Latest: 4E550000
P.S.:
1. In a win10 virtual machine (virtualbox/Debian11): same problem
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Re: MM5.2503 Auto-tag unusable at the moment
Update: Problem persists in 2516.
Happening so far in:
1. This machines win10 installation, 2. a virtualbox win 10, 3. a virtualbox win7 and 4. a fresh win10 install on a different machine.
As written in the support ticket here are the steps to reproduce this:
After selecting a track and hitting auto-tag:
1. let auto-tag til finished ("done" or "fail")
2. Hit "Cancel"
3. Repeat auto-tag with the same selected file til finished ("done" or "fail")
4. Hit "Cancel"
5. Repeat auto-tag a third time
Result:
The auto-tag window is empty of track(s); buttons and description above remain
The auto-generated debug-log appears after a while and was send
6. Hit "Cancel" button in auto-tag window or wait.
Result: crash/white out
Maybe someone else is able to reproduce.. .
Happening so far in:
1. This machines win10 installation, 2. a virtualbox win 10, 3. a virtualbox win7 and 4. a fresh win10 install on a different machine.
As written in the support ticket here are the steps to reproduce this:
After selecting a track and hitting auto-tag:
1. let auto-tag til finished ("done" or "fail")
2. Hit "Cancel"
3. Repeat auto-tag with the same selected file til finished ("done" or "fail")
4. Hit "Cancel"
5. Repeat auto-tag a third time
Result:
The auto-tag window is empty of track(s); buttons and description above remain
The auto-generated debug-log appears after a while and was send
6. Hit "Cancel" button in auto-tag window or wait.
Result: crash/white out
Maybe someone else is able to reproduce.. .
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Re: MM5.2503 Auto-tag unusable at the moment
Hi,
Can you replicate same if you physically access PS (I guess 1. and 4. are physical one). I can't replicate using VMWare and RDP to either Physical PCs or remote using for example AnyDesk.
EDIT: I am suspecting Some sort of Rendering problem. Try to locate eureka log files from crash as described at viewtopic.php?f=30&t=86643 because they could help see where crash happen.
Can you replicate same if you physically access PS (I guess 1. and 4. are physical one). I can't replicate using VMWare and RDP to either Physical PCs or remote using for example AnyDesk.
EDIT: I am suspecting Some sort of Rendering problem. Try to locate eureka log files from crash as described at viewtopic.php?f=30&t=86643 because they could help see where crash happen.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Re: MM5.2503 Auto-tag unusable at the moment
Hi, Peke
To give you a visual impression what I meant by
Just finished a fifth test on a friends "Surface Pro":
Took maybe a few more auto-tag/cancel cycles to reproduce.
But only in this last test-case even the win 10 task-manager (necessary to kill the MM5 process) suffered from some rendering problems; apart from the usual "white-out".
Please, explain what you mean by: "physically access PS".
Yes, 1 and 4 are physical ones. (2 and 3 are virtual machines (virtualbox))(I guess 1. and 4. are physical one).
I haven't tried that.I can't replicate using VMWare and RDP to either Physical PCs or remote using for example AnyDesk.
To give you a visual impression what I meant by
https://ibb.co/VBXmTt6Friedrich wrote:The auto-tag window is empty of track(s); buttons and description above remain
Rendering problem definitely seems at least part of the problem:EDIT: I am suspecting Some sort of Rendering problem.
Just finished a fifth test on a friends "Surface Pro":
Took maybe a few more auto-tag/cancel cycles to reproduce.
But only in this last test-case even the win 10 task-manager (necessary to kill the MM5 process) suffered from some rendering problems; apart from the usual "white-out".
Eureka log is empty; auto-generated logs usually work.Try to locate eureka log files from crash as described at viewtopic.php?f=30&t=86643 because they could help see where crash happen.
MM5 (2606)and MM4 (1919) installed and running well on:
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit
Debian 11 KDE, EndeavourOS KDE (wine 7.4 via playonlinux), Win10 64bit