Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Audio

github.audio

Post reply on HN
Print view View original

61–70 of 133 posts

Re: GitHub Audio

#61

Post by NickBusey »

eriknstr wrote: post #17
freditup wrote: post #8

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

I think the name "GitHub Audio" is confusing and probably a trademark violation. When I read "GitHub Audio", I figured it was a new service by GitHub for musicians to version control their music.

If you're looking for music version control, check out Splice.

Re: GitHub Audio

#62

Post by gkya »

eriknstr wrote: post #17
freditup wrote: post #8

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

I think the name "GitHub Audio" is confusing and probably a trademark violation. When I read "GitHub Audio", I figured it was a new service by GitHub for musicians to version control their music.

Would a non-profit thing like this violate the trademark? This is just like publishing an interactive graph on Github usage.

Re: GitHub Audio

#63

Post by calinet6 »

I've done sonification of data before, and it's not easy at all. This one is really well done -- it's really difficult to get the tonality and rhythm to be pleasant as well as accurately represent the data. Nice work whoever built this!

Re: GitHub Audio

#64

Post by spudlyo »

stdbrouw wrote: post #49
NikolaeVarius wrote: post #31

Earlier quoted context omitted.

Why wouldn't it be possible to version control in the same way we version control other random files? Just treat it as a stream of arbitrary data.

You'd miss out on all the goodies of version control like seeing what has changed. Ideally, version control for musicians would have the ability to show "change panning of guitar a to 0.3 and volume to 0.1" similarly to a code diff. Otherwise all you've got is just a bunch of backups, possibly with semi-informative commit messages if you really put a lot of effort into it.

I wish that there was a way of getting Logic X to output a list of changes you've made during a session. When I collaborate with my bandmate, I often struggle to describe all the changes I've made since he passed me the project. I'd also like to know the changes he's made.

My bandmate often works on our project while it's in a Dropbox folder, so I get a steady stream of notifications about impulse responses and undo files being changed; not very useful. I can tell when he's tracking because the new .aif files come over but that's about it.

Re: GitHub Audio

#65

Post by nyreed »

If github actually did provide a hosting/version control service for musicians, it might gain users from the musicians who are worried by soundcloud and co's pivots to monetisation.

Re: GitHub Audio

#66

Post by stepanhruda »

freditup wrote: post #8

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

TBL made an unfortunate decision to put .com at the end, instead of keeping the hierarchy like this http:com.github.www/foo

Re: GitHub Audio

#67

Post by Urbanxassassin »

stdbrouw wrote: post #49
NikolaeVarius wrote: post #31

Earlier quoted context omitted.

Why wouldn't it be possible to version control in the same way we version control other random files? Just treat it as a stream of arbitrary data.

You'd miss out on all the goodies of version control like seeing what has changed. Ideally, version control for musicians would have the ability to show "change panning of guitar a to 0.3 and volume to 0.1" similarly to a code diff. Otherwise all you've got is just a bunch of backups, possibly with semi-informative commit messages if you really put a lot of effort into it.

This sounds like a dope and insanely hard startup idea. Splice does something like this already, but it's a little rough around the edges and confined.

Re: GitHub Audio

#69

Post by alexduros »

freditup wrote: post #8

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

Actually, the simple fact that this thread appears in 1st in HN lead me to this wrong way, prior to the TLD.
Post reply on HN