onetagger
onetagger copied to clipboard
Marekkon5
Shazam error decoding response body
In the autotag feature, having the Shazam force on throws the following error:
Error Shazaming File: error decoding response body: expected value at line 1 column 1
This Shazam feature is so key to identify songs pre-auto tag so hopefully this can get fixed.
Hello, can you try the latest Actions build? There were some recent shazam related changes that might fix this or give more info. Thanks
I've tried a few different builds from actions and on my MAC they all crash when I hit the play button on Auto Tag. It does not take me to the next screen where I can visually see the app iterating over each file in the folder I have selected.
I've tried a few different builds from actions and on my MAC they all crash when I hit the play button on Auto Tag. It does not take me to the next screen where I can visually see the app iterating over each file in the folder I have selected.
I'm having the same issue. In the latest Actions builds, when I click the "Play" button, it doesn't seem to cause the app to do anything other than show a message that says "Settings Saved". If I check the log file though, it seem to start scanning the files successfully, they just aren't actually getting updated tags saved to them.
@Marekkon5 thanks looks like it works better but upon closing the app on my mac, it throws a crash error. Not a big deal as it's already completed the scan, but doesn't look great that it throws a crash error just by closing the app.
@Marekkon5 thanks looks like it works better but upon closing the app on my mac, it throws a crash error. Not a big deal as it's already completed the scan, but doesn't look great that it throws a crash error just by closing the app.
We're aware of that bug, however it's difficult for us to track down what's actually causing it. Since it happens when closing the app, it shouldn't be a problem. Iirc bascurtiz also found out you can "stop the bug" by dragging OneTagger into applications or by closing it thru the dock.
@Marekkon5 thanks looks like it works better but upon closing the app on my mac, it throws a crash error. Not a big deal as it's already completed the scan, but doesn't look great that it throws a crash error just by closing the app.
We're aware of that bug, however it's difficult for us to track down what's actually causing it. Since it happens when closing the app, it shouldn't be a problem. Iirc bascurtiz also found out you can "stop the bug" by dragging OneTagger into applications or by closing it thru the dock.
@dsmoothdaboogie @RossGGG @Marekkon5 Yep, as Marekkon5 described, see it in action: https://youtu.be/hn8RX9se1JM
