• Adobe Premiere CC 2019 blowing out speakers on Macbooks
    12 replies, posted
https://9to5mac.com/2019/02/06/adobe-premiere-cc/amp/ I have a new 2 month old 15″ MBP. I Was working on a project, macbook volume was about on half, when suddenly an audio bug occurred with really loud screatching noise and not letting me pause it. After it stopped, the speakers were really quiet, and after the next restart they’re clearly blown. One Adobe rep reportedly advised ensuring that the microphone was off when using these tools. This can be done in Preferences > Audio Hardware > Default Input > No Input. This suggests that a feedback loop may be responsible, the microphone picking up the speaker output and amplifying it.
Now video editors can finally know the true suffering that games experience every day https://www.youtube.com/watch?v=ObBh9c8FP8Y&ab_channel=HelpingHans
Is it really standard that a laptop can even deliver the amount of power necessary to fry its own speakers?
I remember one of the lectures I caught on audio programming said something along the lines of: "This is basically the only thing left in programming that stands a chance of causing physical damage to the hardware or the user." You'd think that apple would have limits on the sort of shit that can be played so that users don't accidentally blow their shit up with stock hardware though.
I own an Alienware M14x, and I've had to replace the subwoofer at least 3 times. Anytime the audio driver starts, a rather audible pop sound occurs, which over time causes the fabric that acts as a spring to rip, resulting in the bassier audio crackling like mad. Yes this even occurs with headphones in, it's not a matter of if, only when.
This really is an issue that should have been addressed in the driver software, which should not be hard at all since the machines have a finite and predictable set of hardware. They don't need to account for varying impedance or durability of speakers... they know exactly which hardware will be employed. This is really silly and shouldn't have been possible at all.
Yeah but it takes real courage to not do that so..
I remember that shit, Relic chased that bug for a year, every time they thought they fixed it, it was still there. Not their finest moment(s).
https://files.facepunch.com/forum/upload/219126/4b465e0e-99fb-42d6-9e91-2413f18ec1e6/1ED3FDBC-4E5C-4DCB-A0B4-BCC7095836A9.png
I've had this feedback loop when working in my DAW and accidentally setting the input as the laptop's mic and leaving output as its speakers. That coupled with some amp simulators on the tracks themselves and I've got myself an air siren in the middle of the night.
mate i thought i fucked my hearing up while messing about with delay feedback in Logic - my finger slipped and i whacked the feedback up to 100% with no limiter to keep it quiet. always put a master limiter on now whenever I'm working on anything like that
why are audio bugs so funny https://youtu.be/lChdLY6FVuw
Sorry, you need to Log In to post a reply to this thread.