has anyone foudn the changes required to update the API for getting meta data, sinc eit appears that 2.1 which this uses is now gone?
"page": 1,
"results": [
{
"adult": false,
"backdrop_path": "/4iJfYYoQzZcONB9hNzg0J0wWyPH.jpg",
"id": 11,
"original_title": "Star Wars: Episode IV - A New Hope",
"release_date": "1977-05-25",
"poster_path": "/jMw3JoZXB6CIkWUNwQdaHrIdkeb.jpg",
"popularity": 15.0902541593392,
"title": "Star Wars: Episode IV - A New Hope",
"vote_average": 7.5,
"vote_count": 1904
},
tmdbSearch=`$curlCmd "http://api.themoviedb.org/3/search/movie?query=$searchTerm&api_key=XXX" | grep '<id>' | awk -F\> '{print $2}' | awk -F\< '{print $1}'`
I got a v3 API key from TMDB today, I'm just not sure about the location and name of the script I'm supposed to edit to fix this.
Any help?
Will post write up if successful.
The file is in Applications/Batch Rip Actions for Automator.app/Contents/Library/Automator/Add Movie Tags.action/Contents/Resources/main.command
Line 55 I think.
If you want a hand, I'm happy to help.
The file is in Applications/Batch Rip Actions for Automator.app/Contents/Library/Automator/Add Movie Tags.action/Contents/Resources/main.command
Line 55 I think.
If you want a hand, I'm happy to help.
I believe that is the file that needs the change. I updated the command file with the new URL and my API key but the syntax isn't correct. All I changed was the 2.1 to a 3 per their documentation and changed the API key in that command file to my personal v3 key.
http://docs.themoviedb.apiary.io/
Here is the URL for their new API documentation if anyone could assist.
TMDB will provide API keys instantaneously to individuals from their website all you have to do is create a TMDB user account and request a key.
We didn't each have to go out an dget a key before though?
It appears to be written using cURL, which I am not fluent in at all. Anyone?
Essentially, I have quite an elaborate set of actions with hazel setup to use handbrakecli to do all the heaving lifting. Once thats complete, I use the identify program to tag and rename the program, and the hazel takes it from there again. Adding it right into Itunes and everything.
I utilize colour coding and such to work with hazel, and it works pretty damn good. The API change and the introduction of identify has been the only part that requires interaction for the most part (or if you are ripping, manual disk insertion).
Just wondering if anyone cares to see the setup I have. If so, I will create a new thread and start from there in the future. I dont want to bust my arse if no one cares though.
Keep in mind, you will need hazel, and identify. Both $$, but well worth it in my opinion.
Hello all, I have this forum bookmarked, and have used the ever living crap out of these type of actions. In the last few months, I have moved away from them, and now with the movie api changing, I have moved 100% away from them for movies.
Wanted to drop a line here and let everyone know that there are ways of doing it without these actions. Although its not as elegant, and with the API being changed, its actually one more step involved. I am ok with it. I dont know if all of you are up for it or not.
Essentially, I have quite an elaborate set of actions with hazel setup to use handbrakecli to do all the heaving lifting. Once thats complete, I use the identify program to tag and rename the program, and the hazel takes it from there again. Adding it right into Itunes and everything.
I utilize colour coding and such to work with hazel, and it works pretty damn good. The API change and the introduction of identify has been the only part that requires interaction for the most part (or if you are ripping, manual disk insertion).
Just wondering if anyone cares to see the setup I have. If so, I will create a new thread and start from there in the future. I dont want to bust my arse if no one cares though.
Keep in mind, you will need hazel, and identify. Both $$, but well worth it in my opinion.