-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse or change order input #4
Comments
Regex for beatport id is defined here Line 16 in c51451e
I added input argument for specifying the regex format. For now it's "--beatport-id-regex". If you have any other suggestions, feel free to create new issues or PRs. Also star/share if this tool provides you any value. |
On second thought, I changed the default beatport id regex to "^[0-9]+". It will work fine for the original beatport naming and your case too. |
Hello thanks for your very quick fix. But i'm sorry I did a mistake, it appaers border-country12775735 and not the oppisite as i mentioned, I'm sorry. |
I mean do you think it's possible to user ./tracktagger.py -tsari some/path on a folder with content like this : border-country12775735 ; human-reason1928330 |
Then you can set --beatport-id-regex "[0-9]+$". That regex matches for number at the end of string. If you have different naming, you need to create regex that matches for the number part only. |
So you want me to use the command ./tracktagger.py --beatport-id-regex "[0-9]+$" whithout the other ones ? And I should write the id ? But where I specify the folder? |
Note that it currently takes beatport id from file name, not from track name. I guess you don't want to have ids in track names, but it can be done. |
Run it like this ./tracktagger.py -tsar -i mymusicfolder --beatport-id-regex "[0-9]+$" |
What I mean it's I have a lot of track to replace but they are name like conventional Artist - Title (Original Mix). And then I want to use your command that works very well on this. I will try thanks |
I tried python.exe ./tracktagger.py -tsar -i C:\Users...\test --beatport-id-regex "[0-9]+$" but didn't find any files. |
Is the beatport id in the filename? (e.g. border-country12775735.mp3) It currently looks for beatport id in the filename. I'm going to add more examples to readme, so it's more clear. |
Yes https://www.beatport.com/track/border-country/12775735 and yes border-country12775735.mp3 |
Have you tried ? I want to ask another thing, then this will work, do you allow me to use your script ? |
Get latest commit and try this If you want, you can build that frontend. beatport_tracktagger is using the MIT license. Just please comply with the LICENSE, and include it with notion that you use this software. I intended to write that frontend, but no one expressed the need for it yet. My plan was writing it as local one, instead of hosted as you plan. Reason for that is you can't easily edit local files from web service. |
Thanks king it works very fine now ! Last year I used a scrapping script and execute it with Firebase function, then I put what I get inside the nosql database. I used Ionic for hybrid mobile application as frontend. |
I did connexion fire firestore db, I will check to execute the script now. |
I've noticed one bug, when the trakc end with a number. |
Glad it works for you. Hit that star button, if you enjoy this tool. You can use this regex As for your frontend, if you have any suggestion for change, feel free to submit a new issue or PR. |
Thanks i will come back to you when i'm done with the front end. So about ideas suggestion, maybe the same thing with Bandcamp or Discogs, because not all the music is on Beatport. |
Hello look this one is invalid : https://www.beatport.com/track/kao-staklo-deepbass-remix/9744498 |
Hello following url on beatport appears nu-moon/10887306
So when I rename my file it name like this : 10887306nu-moon, so do you think there is a way to use the script with this input and not 10887306_nu-moon.
I tried to find where I can change this order or parse, but I don't know exactly where, could you help me please.
The text was updated successfully, but these errors were encountered: