.italic { font-style: italic }
from [0]This is certainly odd considering how far we've come in embracing semantic markup and styling.
1,024 karma · joined May 29, 2013
.italic { font-style: italic }
from [0]This is certainly odd considering how far we've come in embracing semantic markup and styling.
Also from CJR: "What was the single point of failure at Rolling Stone? The authors of Columbia's investigative report answer that and more" - http://article.cjr.org/q_and_a/columbia_journalism_school_in...
"Statement from writer of Rolling Stone rape article, Sabrina Erdely" (also includes statement from UVA President Teresa A. Sullivan) - http://www.nytimes.com/2015/04/06/business/media/statement-f...
"The journalism community reacts to the review of 'A Rape On Campus' " -http://www.poynter.org/news/mediawire/332683/the-journalism-...
I'll repeat my comment from the time:
"For what it's worth, the presence of seemingly significant signal in the difference between the original and compressed tracks does not necessarily mean that significant sonic/perceptual loss has occurred. Operating correctly, the encoder is designed to cut not just sounds that the human ear cannot hear in general (e.g. sounds above 22kHZ) but also sounds which may not be perceptible in context (e.g. the quietest signals in a loud section). So if you find something beautiful about the ghost tracks (and I think there is something beautiful to find), don't immediately jump to concluding that mp3 is awful for cutting these sounds—they might be hardly perceptible when added to the mix.
Of course, at high-compression rates mp3 does begin to significantly degrade fidelity.
Edit: all of this is not to put down the project—I still think it's pretty cool as art and as a demonstration of the encoder, I just didn't want people to think that this was some sort of massive failing of mp3."
Out of curiosity, are you already embedded in the amazon cloud music ecosystem? I'm one of those luddites who still has a library of mp3s—I don't want to have to figure out what I can or can't get on some compatible streaming service here. That would be a lovely feature—if it had an aux-in port or bluetooth compatibility so I could still use it as a dumb speaker. Smart TV's still have inputs, e.g.
Additionally, if I'm not mistaken, it's monophone? Dual-driver, but only one "360-degree" channel of some sort?
[0]: http://arstechnica.com/business/2014/10/googles-product-stra...
The fact that the residual spectrum is uninteresting I totally acknowledge; that was admittedly an afterthought. I'm going to check out your hydrogenaudio link for details on how to better that section/figure.
As far as the fact that I only used MP3—that was kind of the point. I wanted to pick a seemingly low-hanging fruit so that I would have some nontrivial results to work with (i.e., cases where I could hear the difference). If I'd used high bitrate AAC and it was entirely transparent for my ears 100% of the time, I wouldn't be able to do much talk about false positives and hits and misses—talk which was ultimately the meat of the assignment, and thus of the article. The goal was, as I say in the "nota bene" at the top, not to say "Hey, look how unreliable MP3 128 is at being transparent," but rather to use MP3 128 to demonstrate the concepts of transparency and compression perceptibility.
As far as converting MP3 back to a WAV for ABX playback, I hadn't heard of that but I have to think that it would have made little to no effect for my test. I have a solid state hard drive so had no disk noise, and I did not hear the cpu fan on for either type of playback. It is something I'll consider for the future.
Again, I appreciate your feedback and thanks for taking the time to comment!
I guess applying compressed sensing techniques would mean making assumptions about your image which allow you to fill in some of the blanks created by the incomplete angle and position coverage (i.e. the fact that the system is underdetermined). If you could somehow assume a certain redundancy, you could probably make guesses about what goes in the spots that didn't get well-covered.
Disclosure: I'm an intern at Godine.
http://maxbittker.github.io/Mojulo/#cip0aW1lKih0aW1lKnNpbih4...
Speeding it up (increase the first "time" to "time^9") you can see that it eventually "heats up" all the way to black, but it's a nice journey.
Edit: also this one has a nice strobe. You can strobe any pattern you make by replacing a time with some variant of B*sin(time/C) where B and C are appropriately chosen coefficients.
https://maxbittker.github.io/Mojulo/#MTAwKnNpbih0aW1lLzEwKSp...
http://99percentinvisible.org/episode/episode-23-you-are-lis...
http://grand-army.com/work/projects/project.php?project=usps...
Of course, at high-compression rates mp3 does begin to significantly degrade fidelity.
Edit: all of this is not to put down the project—I still think it's pretty cool as art and as a demonstration of the encoder, I just didn't want people to think that this was some sort of massive failing of mp3.
edit: on my comp now, so I can add this link to some cool EN API demos, many of which are Paul's if I recall correctly: http://static.echonest.com/labs/demo.html