5 ms·
I fixed the loading screen bug like this: sudo pacman -S asar cd Concertmaster/resources asar e app.asar app rm app.asar printf "1018a1019\
by mafrasi2 9y ago
I fixed the loading screen bug like this:
sudo pacman -S asar
cd Concertmaster/resources
asar e app.asar app
rm app.asar
printf "1018a1019\n> var listul = '';\n" | patch app/js/lib.js
I was able to start playing something, but then it freezes. Currently looking into that...
- cannam 9y agoOoh! That works for me (so far). Thank you. This is a very nice UI, I'll have to explore it more. I especially like the play timeline for the whole piece with movements as subdivisions. Only complaints so far: the horizontal scrollbar is a bit thin and hard to grab; and, er, when I click the yellow button at top right (of the three Mac-style blobs) the window disappears entirely without leaving any way I can find (under Gnome) to get it back again. Terrific work though.
- adrianosbr 9y agoFun 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.)
- mafrasi2 9y agoDon't worry about code quality, it's perfectly readable. Although I only have very limited javascript knowledge, I would love to contribute if you make this open source. It's really a great project! After a few seconds, it still freezes for me, so that's one thing I could try to fix :)
- adrianosbr 9y agoI use Concertmaster all the time on my Mac, with no problems at all. Which OS are you running?
- mafrasi2 9y agoI'm running Arch Linux with spotify version 1.0.67.582.g19436fa3. It gets stuck at this screen as soon as I start playing something: https://i.imgur.com/WJZKiUA.png https://i.imgur.com/WJZKiUA.png After that, the GUI elements just don't respond at all. There is no CPU usage, so it's probably not an infinite loop. I enabled logging, but don't see anything significant.