setto

joined 11 months ago
MODERATOR OF
[–] setto@fed.dyne.org 1 points 4 days ago

Cheers! True that this map is root specific, pun intended with huge love for the people!

I'm mostly in it for the audio pr0n, which probably requires less of a context (^^,) https://yewtu.be/watch?v=CNLjKLtfFHQ

[–] setto@fed.dyne.org 2 points 3 weeks ago (2 children)

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...

[–] setto@fed.dyne.org 11 points 3 weeks ago (9 children)

The service where they crowd sourced 2/3 of their catalogue from "sharecare" pirate bears?

[–] setto@fed.dyne.org 1 points 4 weeks ago

There's also SCEE available in the f-droid app repository, which is a modified version if street complete for more advanced editing.

https://github.com/Helium314/SCEE

[–] setto@fed.dyne.org 1 points 4 weeks ago

ah wow! Thank you very much!

 

A better understanding of The Nature of Information and communications is now fundamental to our future.

Telluride 2024 is hosting a special series of in-person & #LASER Zoom presentations & conversations with individuals setting creative examples for this most urgent realm of understanding, with insights on the sciences, technologies, economies, ecologies, learning, the arts, & on some inspiring, eco-minded, life affirming ways forward.

You are invited you to join.

[–] setto@fed.dyne.org 1 points 1 month ago

this is the way!

[–] setto@fed.dyne.org 3 points 2 months ago

Very good! Thank you!

[–] setto@fed.dyne.org 5 points 2 months ago (2 children)

Great point! what is your suggestion?

[–] setto@fed.dyne.org 1 points 3 months ago* (last edited 3 months ago)
[–] setto@fed.dyne.org 1 points 10 months ago

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. 😅💜

view more: next ›