News for hackers. Stuff that matters.
Re:An audio engineer explains NPR’s signature sound by Ericson2314 on Sunday June 26, 2016 @08:31PM (#11983549)
Isn't controls on mics the worst UX because the wrong people are always messing with them?

You raise a good point about (even in the bad case) moving headphones around the signal chain---and damn as an (especially functional) programmer I'd like that to be able to tap arbitrary locations in data flow like that. Enough all these control-flow-based debugging tools!

> One button that engages a good EQ is much, much better than something like this

Well there's always overkill, but would one of those be worse than one of those and then, next in the signal chain, a 1-button EQ whose functionality is completely subsumed?

Re:An audio engineer explains NPR’s signature sound by ww520 on Monday June 27, 2016 @01:11AM (#11984301)
Yes. Especially the instrument people who always turn up their instruments' volume mid play because they want to push theirs through. It really messes up the sound engineer's overall tuning.
Re:An audio engineer explains NPR’s signature sound by mrsirduke on Monday June 27, 2016 @02:50AM (#11984530)
> You raise a good point about (even in the bad case) moving headphones around the signal chain---and damn as an (especially functional) programmer I'd like that to be able to tap arbitrary locations in data flow like that. Enough all these control-flow-based debugging tools!

You should look into dtrace and it's new Linux counterpart who's name currently alludes me. It's almost like being able to do just that.

Re:An audio engineer explains NPR’s signature sound by Ericson2314 on Tuesday June 28, 2016 @05:22PM (#11997694)
I'm very aware of dtrace. probes are kinda like faking dataflow on top of control flow I guess.

I was thinking more of a development aid that would render a dataflow graph like max/msp---in the general case the graph itself is changes but thats's OK.