The name Github Audio reminds me of something I've been searching for: Version control for Musicians. A lot of music is now made over the internet. When I'm working on a track with a remote bandmate my workflow consists of recording, exporting the track, uploading it to dropbox, and then he needs to download, and import the track into his DAW. Surely there must be a better way. Is there a way for musicians to work to…
GitHub Audio
121–130 of 133 posts
Re: GitHub Audio
#122This is an interesting example where the new expanded set of TLDs can get confusing. My brain interpreted the URL as something semantically like "audio.github.com". Put another way, I thought the site was actually GitHub-made at first glance at its domain. Of course, this was possible in various ways before expanding TLDs, but I think the problem, and thus the ease of phishing, is greater now.
Agreed. The name made me expect an official "GitHub for Audio" type service, something like: https://splice.com/
The closest thing to collaborative music I've found is https://www.audiotool.com/
Why? You can edit other people's music. Watch this magic: https://www.audiotool.com/app/soundlab/
Re: GitHub Audio
#123Earlier quoted context omitted.
Yea I will admit, when I saw the title, I thought Github was getting into the SoundCloud space, except where people could upload music source or midi files and it would render/play them. :)
Exactly what I thought as well. We're not all crazy to think that'd be a good idea, right?
Isn't that sort of the idea of splice.com? (And if it isn't, it is still a great idea!)
Re: GitHub Audio
#124This is an interesting example where the new expanded set of TLDs can get confusing. My brain interpreted the URL as something semantically like "audio.github.com". Put another way, I thought the site was actually GitHub-made at first glance at its domain. Of course, this was possible in various ways before expanding TLDs, but I think the problem, and thus the ease of phishing, is greater now.
Why are people more interested in what they thought it was than what it is?
Re: GitHub Audio
#125If I was a manager and a music geek as I am now, I'd totally request integration of this thing with my repository, JIRA and Confluence :-)
Re: GitHub Audio
#126Earlier quoted context omitted.
If this is all you have to say about something on Hacker News, we kindly ask that you avoid saying anything at all.
It's shorthand for "I have a distaste for this thing which I presume to be understood if not necessarily shared." I was wrong about that. This isn't musical at all! It's some lazy shit a high-schooler with free time and a vague understanding of the Web Audio API could do. Moreover, there's no value in it. The abstract "sonificiation of real data" is such a low bar, there's so much room for creativity, and there are s…
This brings up a good point.. what is a valuable mapping of the type [ stream of data ] => [stream of Sound] ?
If the input was a stream of random bytes you could immediately list an infinite number of different ways to turn that into sound of some kind. Most of those would probably be as interesting as listening to random tones.
In this case, it would be interesting if the music communicated something meaningful about the github pull requests rather than just using github as a random number generator to make pleasant bell tones.
One example might be that a pull request that solved some long-standing much discussed bug would stand out musically by being loud, introducing a new sound, or resolving a tension present in the music. To contrast, a PR that changed some documentation might generate hardly any change in the music.
Re: GitHub Audio
#127Re: GitHub Audio
#128Earlier quoted context omitted.
It seems that HN is encouraging people to post the same Show HN projects multiple times until they get traction. I have been restraining myself from doing that with my own projects because I care a little about this community, but since moderators and the majority of users don't, I will not restrain myself anymore.
To be fair, unless it's sockpuppet accounts the author only posted it twice (potentially in error, the second one got flagged). Can't really stop other people from resubmitting your Show HN.
Ok, maybe I overreacted, but it is because I saw the other two submissions, coincidentally, then I thought it was maybe submitted more (perhaps because it was flagged at the first time I saw it).
I've seen other cases of overposting in the recent past, so I became suspicious of everything.
Re: GitHub Audio
#129Earlier quoted context omitted.
It seems that HN is encouraging people to post the same Show HN projects multiple times until they get traction. I have been restraining myself from doing that with my own projects because I care a little about this community, but since moderators and the majority of users don't, I will not restrain myself anymore.
It's great that you care about the community. People caring about HN is what makes it good. The repost thing is in the FAQ: https://news.ycombinator.com/newsfaq.html . It's a well-known weakness of HN's structure that many good stories get posted to /newest and then fail to get noticed before they get washed out to see. There are just so many submissions here. Over the last couple of years we've developed techniques…
I know it is in the fact, I just thought this one was posted more times than it actually was (if it was actually only posted 3 times, one flagged).
Thank you for all the clarifications anyway. I actually complained knowing that achieving the correct mix of fairness, having-good-stories, and overposting prevention is a kind of impossible task (and HN seems to be doing well), so I was a kind of a troll, we may say. I'm sorry.