Welcome Guest
Pages: 1 2 3
Beatport Support?
LappenPostAugust 17, 2015, 05:23
Beginner
Posts: 34
Registered:
November 8, 2014, 11:13
Very Hot topicRe: Beatport Support?

Hi again,

Yes, some kind of attended metadata matching through a UI would be great, and a best match as default chosen in the UI. I don't know anything about matching algorithms but I believe it should be possible to sort the results and the best match as pre-choosen.
Unattended should only be used when track identifier is present.

It doesn't seem that the catalog number is part of the Beatport integration???
Other than that, I had some difficulties getting the key imported, but will look into the exact issue and return to you.

Tia/Jake
2MR2PostAugust 17, 2015, 07:16
Avatar photo
Administrator
Posts: 2364
Registered:
August 23, 2012, 19:27
Very Hot topicRe: Beatport Support?

I have a standard best match method which is based on a fuzzy compare of the Title, Album and Artist fields as well as the length and the presence of a unique identifier which always wins (Track Id in this case). It's what I use in the Discogs and MusicBrainz wizards.

Unfortunately the label's catalog number is not present in the metadata returned by the API. Nor is their key2 value. However the key has been present in all the tracks I tested and is stored in the Initial Key field. If you have a track which is not getting the key send me the Track Id and I can test it out here.
2MR2PostAugust 17, 2015, 14:31
Avatar photo
Administrator
Posts: 2364
Registered:
August 23, 2012, 19:27
Very Hot topicRe: Beatport Support?

Here's some good news. The next Preview will extract the Catalog Numbers 🙂 Turns out it is returned in a track's associated release.
LappenPostAugust 17, 2015, 15:50
Beginner
Posts: 34
Registered:
November 8, 2014, 11:13
Very Hot topicRe: Beatport Support?

Good news....looking forward to the next Preview 🙂
LappenPostAugust 26, 2015, 15:37
Beginner
Posts: 34
Registered:
November 8, 2014, 11:13
Very Hot topicRe: Beatport Support?

Thx for the 2nd preview of 3.8. I need some more time to playing around with the new Beatport Import functionality (UI).
I had some difficulties getting the UI to actually import and write the metadata after lookup, but perhaps im doing it the wrong way?

Other than that I do get some funny results when writing the key. A# min is shown as A♯min
I'm using Traktor and Traktor is using the Open Key notation. I would be great to have an option to write the key in Open Key Notation or Camelot Notation. Or I could just write an action that writes/converts the key to correct format.

I can confirm that the catalog number is included now 🙂
2MR2PostAugust 26, 2015, 16:08
Avatar photo
Administrator
Posts: 2364
Registered:
August 23, 2012, 19:27
Very Hot topicRe: Beatport Support?

Hmm...the importer is working for me. You have to make sure that the track line is blue, which means there is something marked for import. The import button only imports whatever you've marked.

I simply display the key in the format that Beatport returns it. Can you get me the Track Id of a track that returns: A♯min. Also one that returns flat if possible. I'll see what characters are in the data stream.

As far as the other key notations, none them are actually accurate as far as the field where they are stored. However, if you or anyone else can supply the conversion tables (text file) I can look at what I can do. I know it's all online but my understanding as to how the mappings occur is a little limited. Then again, if you have the info an action will do the trick. 🙂
2MR2PostAugust 27, 2015, 12:48
Avatar photo
Administrator
Posts: 2364
Registered:
August 23, 2012, 19:27
Very Hot topicRe: Beatport Support?

Just had some time to look at this some more. It looks like the API is returning HTML escape sequences for # in the 'short form'. I will switch to building the key description as opposed to simply using what is returned.

The issue is what to use for Sharp and Flat characters. It seems as if Beatport never returns a Flat.....at least I can't find a track which has one. For SHARP I can use the ASCII # character or the unicode ♯ character. For FLAT (just in case) I can use the Unicode ♭ character
2MR2PostAugust 27, 2015, 13:19
Avatar photo
Administrator
Posts: 2364
Registered:
August 23, 2012, 19:27
Very Hot topicRe: Beatport Support?

Wow...two emailed responses to this post in 5 minutes.

I've decided to represent the key in the ID3 notation. There are two advantages. First it is the intended format for the field and other applications could expect it to be formatted that way. Second, it is a trivial format to parse if you want it displayed otherwise.

It is represented as a string with a maximum length of three characters. The ground keys are represented with "A","B","C","D","E", "F" and "G" and halfkeys represented with "b" and "#". Minor is represented as "m".

As I said, parsing the above format is trivial so displaying it otherwise should be easy in an action.
LappenPostAugust 27, 2015, 16:20
Beginner
Posts: 34
Registered:
November 8, 2014, 11:13
Very Hot topicRe: Beatport Support?

Hi again,
Great. I've send you a link to a spreadsheet with the conversion between the key beatport returns and the open key notation and the camelot system.
You can find it here: https://docs.google.com/spreadsheets/d/1BqT_4w1zRPpDLevcNgYVTXv_ks7RxrJHnpZUyFLPqNc/edit?usp=sharing
//Jake
2MR2PostAugust 27, 2015, 17:02
Avatar photo
Administrator
Posts: 2364
Registered:
August 23, 2012, 19:27
Very Hot topicRe: Beatport Support?

Thank much appreciated. I responded to your email presenting a few alternatives.
Pages: 1 2 3
Mingle Forum by Cartpauj | Version: 1.1.0beta | Page loaded in: 0.051 seconds.