Google Chrome may soon get audio indicators to show you noisy tabs
thenextweb.com
thenextweb.com
The reason this feature hasn't existed is that Chrome (like all browsers other than IE) would use just a single instance of Flash for all tabs so the browser could not control the volumes independently nor tell which Flash instances were playing sound or might ever play sound. You can read this explanation from Chrome devs here: http://www.reddit.com/r/IAmA/comments/gdyun/iama_we_are_thre...
My understanding (just from reading comments in the bug tracker) is that Google was able to get Adobe to cooperate with them and add some hooks so they could keep track of the sounds for each Flash plug-in separately.
I was able to try this feature out in today's Canary build and it worked for me on the two sites I tried it on: youtubedoubler.com and homestarrunner.com.
The URL chrome://media-internals is also interesting in that it will show an entry for each plug-in instance browser-wide. Hopefully they will have a UI element similar to this or like MuteTab so that a person can find the tab making sound when they have a huge number of tabs open in multiple windows and cannot see all of the audio indicators.
Maybe you'd have to get a hook with some platform specific OS API that tells you when sound is playing (does this even exist though)? You could then match this to user interactions within the browser - did the user click inside my browser window when the event started? Then it's probably happening within that tab and I'm gonna show him that animation. False positives wouldn't be very harmful here, so you could let that slip.
My company has done that for multiple applications: http://www.nektra.com/products/audio-recorder-api/
Remember that on Google Chrome there is a separation of processes so you can differentiate what tab iis related to the sound.
For instance, if it's on the extreme side of the right monitor, play a sound in the right speaker.
Unfortunately, it doesn't work that way. While Chrome can run each tab in its own process, all Flash gets run through a single Flash process.
But with the new code they at the very least have it working with Flash. You can try it out right now by downloading a canary build and going to a Flash site (such as homestarrunner.com.)
The reason it works now while it didn't before is that they are passing extra information between Chrome and Flash so that Chrome can keep track of which Flash instances are making sound.
Edit: Thanks justinschuh for being more specific as to how this communication happens.
and that's why this should be a browser feature and not an extension.
The extension may live on if there are features that people want but that Google decides do not need to be a part of the browser.
...as I meant to imply by replying under an FF issue.
But speaking of Chrome, I'd prefer the activity indicator in the tabs themselves... mapping the Task Manager names to my many tabs distinguishable only by not-necessarily-unique favicons is a pain.
I even tried to write a little chrome extension which injects a content script into every open tab, which calls settimer to get the highest timer-id and kills all timers with ids from 1 to this id. But for some reason it didn't work.
This feature could significantly negatively affect Firefox's market share.
There's alternatives such as Shumway.
Also, in my experience lack of Flash or it crashing is seen as a way bigger problem than nasty tabs, as of now.
I have no clue.
for Chrome – extension “Stop Autoplay for YouTube” https://chrome.google.com/webstore/detail/stop-autoplay-for-...
for Firefox – user script “YouTube Auto Buffer & Auto HD & Remove Ads” http://userscripts.org/scripts/show/49366
However, the search results were not what I was expecting. Searching 'fname + lname' would return all records with the lname field. No amount of Googling helped and I'm still stuck. I started googling by using phrases such as 'dynamic query not returning results in solr'. When the results didn't solve my problem I got more specific. 'Dynamic query solr with relative boosts not returning results'. No luck. I am learning all about Solr, the schema, eDisMax query processor and all the other good stuff but am not finding any resolutions. Also this process is very exhausting.
I have found this kind of learning to be not stick in memory. Meaning - nothing sits in memory. So tomorrow if an interviewer asks anything about Solr setup - I'll have no answers, or if I have to setup Solr again - I'll have to follow the Google route or follow a manual. Not sure if this is effective but I'd be comfortable having stuff in my memory rather than depend on Google for a majority of my tasks.
E.g. http://www.bbc.co.uk/programmes/b01qrn4y
Perhaps this is common but I hadn't seen it until recently.
EDIT: wanted to add that this means you can see that the page is 'playing', but it doesn't work if you pin the tab in Chrome.
So yeah, a CPU indicator in the tab could be handy.
How about visual indicators of CPU-burning tabs, especially when in the background?
How about a ctrl-C that kills all JavaScript executing in the foreground page (or something)? In my experience Chrome is good for three infinite loops or similar bugs before it needs to be restarted (manually process killed in Windows) while Firefox is pretty much dead after one. Isn't Chrome the "one thread per tab" browser? Why is it so hard to kill JavaScript when debugging?
EDIT: here's the github - https://github.com/PhilGrayson/MuteTabs
I look forward to a setting (or simply changing the default for non-active windows) to disable autoplay.
Fantastic, I've wanted this feature for years; and counting browser tabs is easy. FYI, This isn't my feed, just some public one I found. https://cosm.com/feeds/63631
I'm currently building a voice-to-text transcriber using the Web Speech API.
See kids, this is what happens when your OS vendors decide that its more important to add shiny to their products than it is to fix deep architectural problems. In this case, that problem is that the AUDIO API's do not already have a native way to add this indicator, anywhere in the OS ..
IF there were a real Digital Audio Mixer implemented in your average Consumer OS, then we'd have per-app audio controls natively being included in such a Mixer interface .. however, the OS vendors have decided its more fun to make shiny things than actually .. you know .. provide valuable OS services.
Color me grumpy. It sucks that the Google Chrome team are having to implement this..
Can I also get a bandwidth/data transfer rate indicator per tab too?
(Really, this is another way to say, "I'm a lazy HTML5 developer and I think having to create a 'sound-effects preferences' view on every project I do is a bit silly, if the browser could just be handling it for me." ;)
Trying to figure out which page is making noise, was most of the reason for installing an ad blocker.
"CONGRATULATIONS, YOU'RE A WINNER!"
Congratulations, you're a jackass. You do NOT interrupt Black Sabbath.