adrianosbr

Hi. Which version have you installed? 1.17.1214?

I’ve tried 1.17.1214 on Ubuntu and it worked flawlessly.

A colleague here said that Concertmaster was freezing on his Linux machine because it was lacking a notification server. I wonder if it’s not the same issue you are experiencing.

About Arch: thanks so much for the help! Please confirm the notification issue and I’ll sent you a plain zip version, non-DEB, of Concertmaster.

You (and everybody here) may contact me at:

concertmasterteam @ gmail.com

Thanks so much for the feedback :)

I'm studying the sorting thing. Opus/catalogue number: not so easy because the data comes from sources that treat this information as strings. But I can think of a text parser, for example. Year of composition: doable.

Thanks for the suggestion!

I think this is the most common request. Now, Concertmaster is heavily composer/work-oriented. But I see your point and sometimes I find myself willing some sort of musician search.

Maybe we would switch to a more flexible UX in the future.

Amazing feedback, thank you so much :)

I’ll carefully analyze your suggestions for our next releases.

The Spotify message is not related to territorial restrictions. Putting it shortly, Concertmaster database wasn’t pre-checked; it checks the availability of each recording in real-time, after user’s request. That's why Concertmaster keeps showing recordings that don’t exist at all on Spotify.

FIX RELEASED! Please download the new versions at:

Win: http://getconcertmaster.com/latest/?os=win Mac: http://getconcertmaster.com/latest/?os=mac Linux: http://getconcertmaster.com/latest/?os=linux

Thanks! If I can recall correctly, MBz API doesn’t inform UPC numbers - something essential to the Spotify integration. But it seems nice and I’ll study it further.

Which Spotify version do you have? They keep changing things and these changes often break Concertmaster. I'll release a new version tonight and it will, hopefully, fix most bugs. So far, it's running flawlessly on my own computer.

I use Concertmaster all the time on my Mac, with no problems at all. Which OS are you running?

Thanks so much!

I'm very sorry for the bug, it'll be fixed shortly.

Great recordings indeed! I'm specially fond of the classic Blomstedt renditions in San Francisco. Schoenwandt and Alan Gilbert are also very good. I had the pleasure to attend the Gilbert/NYPO rehearsals of 5th and 6th symphonies for these recordings - amazing experience!

Fun to see other people looking into my code. Great job :)

Concertmaster is built over Electron and, as such, it is 100% JavaScript. In fact, it's not a more convenient website only because of Spotify's limitations.

It would be possible to make Concertmaster open source, but it's far from professional - it's more like a hobby I'm keeping for 3, 4 years.

(Concertmaster is more than the client. It has several server-side functions as well.)

I’ll release a fixed version of Concertmaster tonight. Sorry for that and thanks for your patience, folks!

Hi! Nice to hear from you.

Classical music has a very complex taxonomy and the so-called “metadata problem” hasn’t been solved by any streaming provider so far. There are some guys in Berlin that are creating a completely new streamer called Idagio, and it seems promising. But they are struggling to sign deals with labels, the process of adding recordings to their database is understandably slow, and subscribing a new streamer implies an additional cost to listeners.

I tried to solve the “metadata problem” using existing infrastructure: Spotify and All Music Guide. (Scraping AMG website sits in a legal gray area, I know.)

DBTune looks very nice; I recall a similar app in early 2000s called ClassiCat. Anyway, if you have the UPC of an album, it’s fairly easy to play it in Spotify.

Cheers!

PS: I’m a Nielsen fan too :)

Hi, Concertmaster developer here.

Thanks for trying the app. Very surprised by the repercussion!

Well, the current version of Concertmaster has a known bug which freezes the app in its first run. (This issue will be solved in a major update January, but I’m seriously thinking of releasing a fix today or tomorrow.)

Please try closing the app and running it again. It may work