iTunesMonkey 1.0 + Acoustid

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: iTunesMonkey 1.0 + Acoustid

Re: iTunesMonkey 1.0 + Acoustid

by MMuser2011 » Tue May 09, 2017 1:35 am

Actually it's not possible.
Please have a look inside "iTunesMonkey.vbs", there is no such query for composer.

Re: iTunesMonkey 1.0 + Acoustid

by MaximusPrime » Tue May 09, 2017 12:50 am

is it possible to tag the composer from itunes?

Re: iTunesMonkey 1.0 + Acoustid

by MMuser2011 » Sat Mar 25, 2017 5:12 am

The error code #1006 says:
Expected ')' (VBScript)

You attempted to enclose an expression within a set of parentheses, but did not include the closing parenthesis). Some expressions must be enclosed within a set of opening and closing parentheses.

To correct this error:
Add the right (closing) parenthesis) to the evaluation expression.
Source: https://msdn.microsoft.com/de-de/librar ... s.84).aspx

I suggest that you deinstall and reinstall this script. Please use the newest version from: http://www.happymonkeying.com/plugin.php?q=300103

Re: iTunesMonkey 1.0 + Acoustid

by gallonofmilk » Sat Mar 25, 2017 12:12 am

I'm getting this error whenever I try to open AutoTag By Web

Image

The Chinese at the top reads something along the lines of
compile error, missing ')'
Anyway to fix it?

Re: iTunesMonkey 1.0 + Acoustid

by Peke » Tue Jan 10, 2017 10:59 pm

Hi,
Does anyone know Price for the API?

Re: iTunesMonkey 1.0 + Acoustid

by oddBeat » Tue Jan 10, 2017 8:17 am

thank you MMuser2011, that sounds promising.

if the fee is acceptable, then we could have a Shazam script :)
unfortunately, I am not aware of the Shazam API price.

Is there someone, who can do a script and approx. price for it, including Shazam API?

Re: iTunesMonkey 1.0 + Acoustid

by MMuser2011 » Tue Jan 10, 2017 5:47 am

oddBeat wrote:maybe one can found here something for future development:
https://www.quora.com/Is-there-an-API-f ... SoundHound
Just for the records:
Q: Does Shazam have an API?
A: (Written Dec 2, 2015)
Richard Earney, A senior UX professional and the original designer of the Shazam app:
It does, it just isn't public unless you do a monetary deal with them.

Re: iTunesMonkey 1.0 + Acoustid

by oddBeat » Tue Jan 10, 2017 3:30 am

ok, thank you anyway and keep on good work!

edit:
maybe one can found here something for future development:
https://www.quora.com/Is-there-an-API-f ... SoundHound

Re: iTunesMonkey 1.0 + Acoustid

by MMuser2011 » Tue Jan 10, 2017 2:30 am

I'm not sure if Shazam offers a public API.

Anyway, I'm not able to do such a script. Sorry, oddBeat.

Re: iTunesMonkey 1.0 + Acoustid

by oddBeat » Mon Jan 09, 2017 11:23 pm

Hi.

First kudos to iTunesMonkey!

Then, I have some songs, which can't be found by iTunesMonkey, but Shazam finds them just fine.
Is it possible to make a script as Shazam, to find names via the web?

Roger

Re: iTunesMonkey 1.0 + Acoustid

by MMuser2011 » Fri Dec 16, 2016 6:02 pm

Unfortunately, I have no more ideas... :( Sorry!

Re: iTunesMonkey 1.0 + Acoustid

by AlanH » Fri Dec 16, 2016 2:03 pm

I've tried the modified code and its the same result I'm afraid. C: Drive works fine but nothing on D: Drive.

Thanks for the time you put in trying to fix it, I think going forward I'm going to have to make a temp folder on the SSD if I want to run the plug in, unless you have a crystal ball and can find out whats happening.

Alan

Re: iTunesMonkey 1.0 + Acoustid

by MMuser2011 » Thu Dec 15, 2016 4:50 pm

AlanH wrote:The only thing I can see is the working one seams to remove all spaces from the file path but in the non working one the spaces are there. As far as I can see the file path is the correct path in the non working one.
Your working example is using the so called "ShortPath", using a max 8 characters long abbreviation for every part of the full file path.

The problem is: there is absolutely no difference in the procedure if you use C: or D: or L: or any other drive letter.
As you see correctly in the second example, your D-path-parts are no more max 8 characters long without spaces.

What you could try is this modified content of AcoustidFingerprint.vbs:

Code: Select all

Set oArguments = WScript.Arguments
Set MyFSO = CreateObject("Scripting.FileSystemObject") 
CreateObject("WScript.Shell").Run oArguments(0) &" "& MyFSO.GetFile(oArguments(2)).ShortPath &" > "& oArguments(1), 0, True
The oArguments(2) will be forced to be executed as short path.

Re: iTunesMonkey 1.0 + Acoustid

by AlanH » Thu Dec 15, 2016 3:09 pm

Here is the results, I copied the same file to both locations and ran it on both.

The top three are from the C: Drive and the Bottom 3 are from the D: Drive
Working
Image
Image
Image

Not Working
Image
Image
Image

The only thing I can see is the working one seams to remove all spaces from the file path but in the non working one the spaces are there. As far as I can see the file path is the correct path in the non working one.

EDIT
I have just plugged in an external drive with the label G: and rerun the same file and it works as expected, giving the same result as the C: Drive
EDIT 2
I changed the drive letter on the D: drive to L: drive and it still wouldn't work

Re: iTunesMonkey 1.0 + Acoustid

by MMuser2011 » Thu Dec 15, 2016 1:58 pm

If you like, you can try the following debug step:

Open this existing small (1kb) file in a editor (like Notepad++):

Code: Select all

%appdata%\MediaMonkey\Scripts\iTunesMonkey\AcoustidFingerprint.vbs
This file contains only two lines of working code.

Please enter 3 new lines between the line
Set oArguments = WScript.Arguments
and
CreateObject("WScript.Shell").Run oArguments(0) &" "& oArguments(2) &" > "& oArguments(1), 0, True

It should finally look like this:

Code: Select all

Set oArguments = WScript.Arguments
MsgBox ("oArguments(0): " & oArguments(0))
MsgBox ("oArguments(2): " & oArguments(2))
MsgBox ("oArguments(1): " & oArguments(1))
CreateObject("WScript.Shell").Run oArguments(0) &" "& oArguments(2) &" > "& oArguments(1), 0, True
Save this file and then try to start fingerprinting ONE song.
The above lines should show* you:
a) where the calculation tool "fpcalc.exe" is started from
b) the full filepath to your song
c) where the output should be written to

I assume, the line b) will show you an incorrect path, right?

* Please be warned:
This msgbox is hidden behind the result window and MediaMonkey. You have to switch to this window or minimize all other windows to see it. It doesn't pop up on top, unfortunately...

Top