oh, wait, i forgot about all the sharecare non-pirate bears that just upload good stuff for the careshare... you know, that other 3/12 of the catalogue...
The service where they crowd sourced 2/3 of their catalogue from "sharecare" pirate bears?
There's also SCEE available in the f-droid app repository, which is a modified version if street complete for more advanced editing.
ah wow! Thank you very much!
Very good! Thank you!
Great point! what is your suggestion?
10
Maurizio Napolitano on the importance of OSM in the world of digital commons
(tube.network.europa.eu)
1
Zen - A JS / browser based live coding system primed for pattern interference
(zen.cephasteom.co.uk)
I don't really have any tips regarding theory, i never picked it up mostly due to laziness. Admittedly, i never felt the need as my lack of knowledge didn't keep me from cutting records and touring. But your post cheered me up, and it made me want to point out the incredible satisfaction of sharing a musical moment with other people. Doesn't have to be a band or a committed project. Just having another instinct leading the music in unexpected direction is a great way to learn new stuff. It's not something you need to do to grow, music is its own person in some senses: even when you play alone it's you AND music. But if you get the chance to play with someone: take it!
Best of luck in your endeavour!
"It's free and always will be"
Seems like a great idea!
I'm somewhat surprised by the choice of XML, but why not?
This goal worries me a bit:
The format should be able to express the track and timeline structures of the exporting DAW as is, leaving it up to the importer to use this data and flatten it as needed.
Leaving things up to one side or the other seems like a hard way to reach any meaningful consensus. But I'm basing this on gut feelings from seeing i.e. how ActivityPub is only partially adopted by the different fediverse apps who tend to "leave it up to the importer to use the data and flatten it as needed". I have no experience in interoperable data-structures on my own, so there are probably 6372 reasons why i am wrong here.
My main hurdle with collaboration has never been DAW data, as lossless audio + midi will get my counterparts and myself a long way. The issue has always been platform interoperability of addons.
But over all, this is music to my ears! It seems like a sane path to better interoperability and that's exactly what i wish upon the (computer) world. 😅💜
Finanical gain was never the purpose of Spotify. What spotify provides is the closest channel we know to monitor human emotions. The ability to corelate this data with all the other data gathered from social networks and search engine is well worth the loss.
I think the modality of spotify is ok, but the model could be very different. In exemple, imagine if you payed 10$ month, but instead of those being distributed across all of spotify statistically, they where divided and distrubuted to the author YOU actually listened to, on a monthly basis.
Maybe one month you only listened to 10 songs, so 1$ for each song author that month.
Of course, there should be a cut for the platform from that monthly fee, after all they have maintenance and administrative costs. And perhaps it should also take into account how much of a song you listened to, down to the second.
This is not a new model, but it is not an interesting one for venture capitalist funds, because it is too egalitarian. It is up to us to create it.
"To have a fair music market, there needs to be a fair market".
view more: next ›
Both ingredients are valid, but i prefer mine with a zest of not letting that which i cannot control burden me, over a handful of IDGAF.