New ChromeVox Release - Version 1.22.0 ! And a user survey!

[rshearer]

Hi everyone,

We've just released ChromeVox 1.22.0 to the Web Store and to the open source repository. And we're interested in getting your input on your experiences using ChromeVox, so along with this release we created a user survey! The survey results will help us understand how we can make ChromeVox better. Here's the link to the survey: http://goo.gl/0iKFn

This release includes a few big updates:

- Focus Recovery - ChromeVox now remembers your progress through a web page. That way, even if the page updates and your position is lost, we can restore you to a familiar place.

- Support for multiple keymaps - We now have support for multiple keymaps. To select an alternate keymap, navigate to the “Key assignments” section in the Options page. Go to the “Classic” drop down, use the arrow keys to select an alternate keymap and then press tab to move to the “Select keymap” button.

Please see the release notes at http://www.chromevox.com/release_notes for more information on these and other changes.

If you want the update right away, you can either:

- Go to chrome://extensions and click the "Developer Mode" checkbox at the top of the page. Then click the "Update extensions now" button.

- Or, uninstall ChromeVox and then re-install from the Web Store: https://chrome.google.com/webstore/detail/kgejglhpjiefppelpmljglcjbhoiplfn

Or, you can wait for the automatic update, which should arrive soon(ish).

Stay tuned - we'll be going through and updating the issues in the Issues List that have been resolved in this release.

__Rachel and the ChromeVox Team and the awesome ChromeVox Interns

[Mike Reiser]

A few issues with the survey.With VoiceOver on ios, I can't fill out some forms, for example the feature suggestion edit field. Also some check boxes won't respond. Hope this helps,

Mike

Sent from my iPhone

[Christopher Chaltain]

My google-chrome-stable running on Ubuntu 11.04 64-bit stopped talking
to me after ChromeVox was automatically updated to this new version
1.2.2. Any idea what I can do? Is there a way to fix this or roll back
to the previous version? Also, once I get this resolved, I assume I can
turn off automatic updates in the future. I've kind of gotten dependent
on Google Chrome and ChromeVox. It's the only way I've found to handle
Google Docs efficiently, which I need to do for my job.

--
Christopher (CJ)
chaltain at Gmail

[Rachel Shearer]

Oh no! I'm sorry to hear that. We'll look into it. It would help if we had a little bit more information -- what voice are you using?

And (though you've probably already tried this), it can't hurt to restart your browser to see if speech comes back.

[Christopher Chaltain]

Sorry, I should have mentioned I was running Lois. BTW, I did have some
sighted assistance, and they did go in and verify that ChromeVox had
been updated to version 1.2.2. Both ChromeVox and Lois were still marked
as active.

On 08/08/12 23:01, Rachel Shearer wrote:
> Oh no! I'm sorry to hear that. We'll look into it. It would help if we
> had a little bit more information -- what voice are you using?
>
> And (though you've probably already tried this), it can't hurt to
> restart your browser to see if speech comes back.
>
> On Aug 8, 2012 8:45 PM, "Christopher Chaltain" <chal...@gmail.com

> <mailto:chal...@gmail.com>> wrote:
>
> My google-chrome-stable running on Ubuntu 11.04 64-bit stopped talking
> to me after ChromeVox was automatically updated to this new version
> 1.2.2. Any idea what I can do? Is there a way to fix this or roll back
> to the previous version? Also, once I get this resolved, I assume I can
> turn off automatic updates in the future. I've kind of gotten dependent
> on Google Chrome and ChromeVox. It's the only way I've found to handle
> Google Docs efficiently, which I need to do for my job.
>
> On 08/08/12 19:19, rshearer wrote:
> > Hi everyone,
> >
> > We've just released ChromeVox 1.22.0 to the Web Store and to the open
> > source repository. And we're interested in getting your input on your
> > experiences using ChromeVox, so along with this release we created a
> > user survey! The survey results will help us understand how we can
> make
> > ChromeVox better. Here's the link to the survey: http://goo.gl/0iKFn
> >
> > This release includes a few big updates:
> > - Focus Recovery - ChromeVox now remembers your progress through a web
> > page. That way, even if the page updates and your position is lost, we
> > can restore you to a familiar place.
> > - Support for multiple keymaps - We now have support for multiple

> > keymaps. To select an alternate keymap, navigate to the �Key
> > assignments� section in the Options page. Go to the �Classic� drop

> down,
> > use the arrow keys to select an alternate keymap and then press tab to

> > move to the �Select keymap� button.

[Christopher Chaltain]

Oops, and I should have also said that I did try restarting Chrome.

On 08/08/12 23:01, Rachel Shearer wrote:

> Oh no! I'm sorry to hear that. We'll look into it. It would help if we
> had a little bit more information -- what voice are you using?
>
> And (though you've probably already tried this), it can't hurt to
> restart your browser to see if speech comes back.
>
> On Aug 8, 2012 8:45 PM, "Christopher Chaltain" <chal...@gmail.com

> <mailto:chal...@gmail.com>> wrote:
>
> My google-chrome-stable running on Ubuntu 11.04 64-bit stopped talking
> to me after ChromeVox was automatically updated to this new version
> 1.2.2. Any idea what I can do? Is there a way to fix this or roll back
> to the previous version? Also, once I get this resolved, I assume I can
> turn off automatic updates in the future. I've kind of gotten dependent
> on Google Chrome and ChromeVox. It's the only way I've found to handle
> Google Docs efficiently, which I need to do for my job.
>
> On 08/08/12 19:19, rshearer wrote:
> > Hi everyone,
> >
> > We've just released ChromeVox 1.22.0 to the Web Store and to the open
> > source repository. And we're interested in getting your input on your
> > experiences using ChromeVox, so along with this release we created a
> > user survey! The survey results will help us understand how we can
> make
> > ChromeVox better. Here's the link to the survey: http://goo.gl/0iKFn
> >
> > This release includes a few big updates:
> > - Focus Recovery - ChromeVox now remembers your progress through a web
> > page. That way, even if the page updates and your position is lost, we
> > can restore you to a familiar place.
> > - Support for multiple keymaps - We now have support for multiple

> > keymaps. To select an alternate keymap, navigate to the �Key
> > assignments� section in the Options page. Go to the �Classic� drop

> down,
> > use the arrow keys to select an alternate keymap and then press tab to

> > move to the �Select keymap� button.

[rshearer]

Here's another thing to try: uninstall Lois and install our new TTS voice extension from the web store: https://chrome.google.com/webstore/detail/pkidpnnapnfgjhfhkpmjpbckkbaodldb

The voice data will start downloading after you install the extension and it will speak to you to update you on the percentage downloaded. It shouldn't take too long. Once that finishes, try and see if ChromeVox will start talking again.

If, of course, you install the new TTS extension and you don't hear it speak to you to update you on the download status...that's another data point that can help us figure out what's wrong here.

[Dominic Mazzoni]

Yet another thing to try is to switch from the Chrome stable to unstable channel. Hopefully that should be as simple as apt-get install google-chrome-unstable

Switching Chrome from stable to unstable is pretty easy and shouldn't cause any problems. However, in case you want to switch back, I'd suggest you back up your profile first - before switching - because switching from a newer version of Chrome to an older version of Chrome can cause it to be unable to read your profile.

Your profile is in the .config directory in your home directory, usually ~/.config/google-chrome, or if you actually have the pure-open-source version it might be under ~/.config/chromium. Just make a backup of this directory and restore it if you want to switch back to Chrome stable.

Good luck!

We're definitely looking into what could have broken, but our first priority is to see if we can figure out a way to quickly get you up and running while we investigate. Thanks for your patience!

- Dominic

[Christopher Chaltain]

I did notice that there was a newer google-chrome-stable, so I updated
to that with apt-get, but still no voice. I'll hold off on moving to
unstable for now.

The problem I have now is that I don't have any sighted assistance at
the moment, so there's little I can do inside Chrome itself.

I appreciate the help though, and I'll keep the list posted with what
I've tried and where I end up.

> �Key
> > > assignments� section in the Options page. Go to the
> �Classic� drop

> > down,
> > > use the arrow keys to select an alternate keymap and
> then press tab to

> > > move to the �Select keymap� button.

[Christopher Chaltain]

I still have ChromeVox working in my Windows virtual machine, which was
also upgraded to 1.2.2 BTW, so I'm still able to work with my Google
Docs. I'll try some of these suggestions as soon as I can get some
sighted assistance.

On 09/08/12 00:01, Dominic Mazzoni wrote:

> �Key
> > > assignments� section in the Options page. Go to the
> �Classic� drop

> > down,
> > > use the arrow keys to select an alternate keymap and
> then press tab to

> > > move to the �Select keymap� button.

[Pitermach]

Hi,
really liking the new layout... Now, as far as the survay goes, you did forget about NVDA in the statements. That seems pretty major, also system access, and I do believe, Orca on Linux.

[T.V Raman]

Chris, I did the update on my laptop last evening from the store
on Linux -- and it is talking happily. I'm using the Google TTS
(newer high quality voice) not Lois -- but that should not matter
in this case. Can you confirm that ChromeVox is enabled --
perhaps something got deactivated? Cant guess at what else could
have stopped it talkin

> > > keymaps. To select an alternate keymap, navigate to the “Key
> > > assignments” section in the Options page. Go to the “Classic” drop

> > down,
> > > use the arrow keys to select an alternate keymap and then press tab to

> > > move to the “Select keymap” button.

[T.V Raman]

Dominic's suggestion of Chrome unstable is worth trying -- I
believe that is what I'm running on my laptop as well. And dont
give too much weightage to the word "unstable" it's pretty solid
all the same:-)

> > �Key
> > > > assignments� section in the Options page. Go to the
> > �Classic� drop

> > > down,
> > > > use the arrow keys to select an alternate keymap and
> > then press tab to

> > > > move to the �Select keymap� button.

[Christopher Chaltain]

Thanks, knowing that it's working for someone on Linux makes me feel
better. When I had some sighted assistance last evening, I did verify
that it was enabled. I even enabled it and unenabled it to see if that
would help. I'll make some time this afternoon between meetings to try a
few different suggestions and then I should also have some sighted
assistance as well.

[T.V Raman]

Note: You shouldn't need sighted assistance for switching between
stable and unstable.

The bits to know are:

1. aptitude search chrome will show you that there are three
versions o fchrome you can install.
2. sudo apt-get <google-chrome-xxx> install where xxx is stable,
beta or unstable
This changes the google-chrome you have installed.

I recommend using different user profiles for each --
you specify which profile to use via a command-line flag:
--user-data-dir=<dir>

google-chrome on debian flavored systems defaults to
~/.config/google-chrome

In general, newer versions of chrome are happy to use the profile
from older versions, going the reverse direction is risky.

One receipe you can follow:

Create yourself three shell scripts (or three bash functions or
whatever)
that each invoke google-chrome with a profile appropriate for the
chrome channel you want to run.

Note: when you instal an extension that is in the profile you
were using when you did the install.

Once you have this set up -- you should be able to easily move
amongst the three channels --

[erin rosenthal]

One more thought - Try CVOX A A and see if ChromeVox was temporary deactivated. This is different from disabling the extension in settings. 

[Christopher Chaltain]

Thanks, yep,I tried that.

> �Key
> > > > > assignments� section in the Options page. Go to the
> �Classic� drop

> > > > down,
> > > > > use the arrow keys to select an alternate keymap and
> then press tab to

> > > > > move to the �Select keymap� button.

[Christopher Chaltain]

Yep, understood, but there are a few things I also want to try, like
removing and reinstalling ChromeVox, trying the new TTS and a few other
things that I'll need sighted assistance for. It's not so much that I'm
afraid of unstable, but rather it's more that I'd like to understand
what's going on.

BTW, I'm also grateful for the suggestions and additional information.
I'm sure this will turn out to be something silly.

[Nolan Darilek]

Did the upgrade on my AMD64 Ubuntu 11.04 running Chrome beta and my Orca
TTS module. Worked fine here as well.

If Unstable scares you, perhaps try Beta?

Either way, just thought I'd share a success story since our systems
seem similar.

[Christopher Chaltain]

Thanks. I'm pretty sure now it'll be something trivial. I've gone
through several updates in the past though, and it's always just worked.
BTW, in addition to not getting any speech, I'm also not getting any
ChromeVox sounds, so it does seem to be something with ChromeVox and not
the TTS. I was also wondering if one of my settings could be causing a
problem. For example, I have the CVOX key set to shift+alt instead of
control+alt. It didn't look like I could change that on my Windows
system, so I was wondering if that could be tripping something up on my
Ubuntu install.

[T.V Raman]

I suspect there is a breakage in lois as found on the store --
we'll investigate this and if needed post a fix.

[Christopher Chaltain]

OK, here's what I've tried:

This is with google-chrome-stable running on 64-bit Ubuntu 11.04.

1) I installed the new TTS. I heard the download percentage updates, but
no ChromeVox.

2) I went into ChromeVox options and switched the TTS to the new US
female TTS, and still no ChromeVox.

3) I removed and readded ChromeVox. I heard ChromeVox start to read the
release notes, but it stopped after a line or two and then no ChromeVox.

4) I installed google-chrome-unstable but still no ChromeVox.

I think that was all of my ideas. Any other suggestions? Again, thanks
for all the help and suggestions.

[Dominic Mazzoni]

It started to read the release notes? Hmmm, it sounds like ChromeVox is starting to work. Does it read anything if you tab to links? Do you hear sounds when you open a new tab?

- Dominic

[lucia greco]

hello:
this may be a dum questen but here goes do the voices work on a chrom
book i tryed running one or to of them and it did not seem to make a
diference. lucy

[Christopher Chaltain]

No, I just hear enough to know that the release notes are up on the
screen and then nothing, no speech and no ChromeVox sound effects.

Note, I think this was also my behavior with Lois when the ChromeVox
1.2.2 extension was first installed. I wasn't paying too much attention
to ChromeVox at the time, I heard Lois say something about release notes
and then nothing. Like I said, I wasn't really paying attention, but
this is what got me to thinking that maybe the automatic updates had
just updated ChromeVox for me.

> > > > > > > > <mailto:chal...@gmail.com

> navigate to the �Key
> > > > > > > > > assignments� section in the Options page. Go
> to the �Classic� drop

> > > > > > > > down,
> > > > > > > > > use the arrow keys to select an alternate
> keymap and then press tab to

> > > > > > > > > move to the �Select keymap� button.

[T.V Raman]

Chris,

Given that you heard "some audio" I'm beginning to suspect audio
configuration issues -- has anything changed recently? From what
you're describing, it sounds like a potential alsa/pulseaudio
buffering issue.

[Christopher Chaltain]

Well, I got it working. I think what did it was uninstalling Lois and
the Google US female TTS and reinstalling Google's US female TTS. I
didn't need to do this on Windows, which is why I didn't think to do it
earlier. I think someone suggested this earlier, but I think the key was
uninstalling Lois altogether (not just disabling her) and then
installing the new Google US female TTS.

Now I need to figure out how to change my CVOX key back to shift+alt.
Any clues?

[T.V Raman]

Not sure abou tShift-alt --- all keys are changed in the
chromevox options page. I personally use the prefix key --
default is ctrl-z which I change to " control semicolon" (caps
lock is control on all my machines.

[Christopher Chaltain]

I can see an edit field where I can change the CVOX key combination, but
it seems to be grayed out. I can't get to it with the tab key or by
clicking on it. I know I had this changed before.

I have changed the prefix key to control+;, but I've gotten in the habit
of using both shift+alt and control+;.

BTW, thanks to all for the help and the suggestions and of course the
work on ChromeVox!

[rshearer]

Hi CJ,

The CVox key combination is not user-modifiable in this release -- the previous implementation was buggy and was causing problems.  We'll bring back the ability to customize the modifier once we've made it more stable.

In the meantime, you should use the prefix key (set by default to Ctrl+Z, but you can change that... sounds like you already have :) ) or Sticky Mode if the default modifier (Ctrl+Alt on Linux) doesn't work out for you.

___rachel

[Kevin Fjelsted]

I was able to fill out the survey by going to Safari. No capability existed to do it in ChromeVox. As soon as I tried to change the value in a popup button or selection everything would freeze.
No amount of up arrow down arrow left or right arrow would help.

There seems to be a general over reaching issue regarding stability in that interacting with elements just causes a mess and things freeze up.
-Kevin

[T.V Raman]

Couple of things to try Tim:

1. Make sure you have the latest display drivers for your video
card --- Chrome increasily uses a lot of advanced features
with respect to direct rendering.

2. Given what you're saying about GMail and Groups:

Try running Chrome with this flag:

--disable-renderer-accessibility

this disables the partially implemented ATK features --- which
has been known to cause performance issues.

Tim Cross writes:
> Well, good and bad news.
>
> I updated to chrome unstable. Now chromevox seems to be working. However, I get MAJOR rendering probolems running chrome unstable on my ubuntu 11.04 system (64 bit). In fact, so bad that chrome
> is essentially unusable. I removed all extensions, including chromevox and the US English TTS stuff just in case something odd was occuring due to an extension, but that had no effect. In the
> end, I had to revert back to google-chrome stable.
>
> Some o0f the issues I noticed included
>
> 1. Pages being incompletely rendered. For example, when viewing a message in gmail, hitting the back button would result in a page that was a mix of both the inbox message list and the text from
> the last viewed message
>
> 2. In web forms, selecting an item from a drop down list would not be displaed in the list after selection
>
> 3. Google groups was nearly impossible to navigate. Seloecting an item from a conversation would display part of it in some sort of mini window on top of the original list from the discussion.
>
> 4. Lots of weird scrolling behaviour. For example, in gmail, I woujld end up with just a few lines of text at the top of the page, the rest of the page would be blank and I could not scroll the
> content down to use the full display.
>
> All of these seem to be javascript issues as they only apper to occur on pages with considerable javascript.
>
> For now, I've uninstalled chromevox and will just have to wait until things settle. A little frustrating, especailly given the US English Female TTS seems to be a real improvement over Lois and
> I'd really like to give it a go.
>
> Tim

[Dominic Mazzoni]

If you're having graphics issues, I agree that it's most likely that you're running into an incompatibility with your graphics card. You can disable all of those features in about:flags, or here's a webpage where someone's collected all of the gpu-related command-line flags:

http://jamisondance.com/post/22387219496/turning-off-gpu-acceleration-in-google-chrome/

- Dominic

[David Tseng]

Hi Kevin,

On Sat, Aug 11, 2012 at 1:25 PM, Kevin Fjelsted <kfje...@gmail.com> wrote:
> I was able to fill out the survey by going to Safari. No capability existed to do it in ChromeVox. As soon as I tried to change the value in a popup button or selection everything would freeze.
> No amount of up arrow down arrow left or right arrow would help.
>
> There seems to be a general over reaching issue regarding stability in that interacting with elements just causes a mess and things freeze up.

Are you running VoiceOver side by side with ChromeVox? If not, you may
want to try doing this in the future.

Let us know if that doesn't resolve the issues you're seeing.

- David

[Christopher Chaltain]

I've been having trouble getting ChromeVox 1.2.2 to talk on my other
systems. It doesn't look like uninstalling Lois and installing the new
US female voice by Google is sufficient. I'll try reinstalling ChromeVox
to see if that fixes it or not. I'll also see if the trick is moving up
to chrome-unstable.

On 12/08/12 20:19, Tim Cross wrote:
>
> I have experienced the same problem on multiple systems, all running
> Ubuntu 11.04 and current google-chrome stable. I have tried restarting,
> have re-installed chromevox and ahve installed the US Female tts.
> However, no voice.
>
> A coujple of interesting things to note:
>
> - At first, I had some voice, but it was inconsistent. Would stop
> working and then I could not get it working again. Restart does not help
>
> 2. If I hit cvox A A, it tells me chromevox is now inactive. Hitting it
> again does not tell me it is active.
>
> 3. When installing the US Femal TTS data, the install did speak and
> giave me a progress update, but that was it.
>
> 4. I no longer get any additional sounds, such as the chime I use to get
> when selecting the tickbox for an email message in google mail
>
> 5. Using pavolumecontrol, I can see the chrome connections to pulse, but
> no data is being received.
>
> I've also noticed some 'odd' rendering behaviour in google chrome since
> the last update. I'm going to try unstable and see if that fixes the
> problem.

>
> On Friday, August 10, 2012 6:41:21 AM UTC+10, CJ wrote:
>

[Tim Cross]

Hi Raman,

thanks fot the tip re: turning off renderer accessibility. I will give that a go. There is certainly something wrong here. 

As an example, when trying to view your post in google groups, I just get a blank page. However, hitting cvox+A_A to make cromvox inactive and now I can view your post. I notice google-chrome was updated yesterday, but still having problems. Cannot get cromvox to speak. It will tell me that it has been made inactive when I hit cvox A A, but does not tell me it is active when I hit it a second time. The highlight cursor is there and it moves, but no speech and no auditory icons. 

I have noticed this error from chrome

ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream

All other sound apps are running fine. I am running PulseAudio, but have been for a long time. There was anupdate to PuseAudio acouple of weeks ago, which may or may not be related. 

My sound setup is stock standard - no asoundrc file and no changes to pulse config.

The problems I've observed are on two different 64 bit Ubuntu installs. One using an nvidia graphics card, the other intel. One box has dual sound cards, one soundblaster Audigy and a built-in intel HDA, the other box, one card, Intel HDA. 

I will try the switch you suggested and report back.

Tim

[Tim Cross]

Hi Raman,

OK, I tried runing with the --disable-renderer-accessibility, but with no luck. I tried this with all three versions of google-chrome, stable, beta and unstable. 

1. With stable and beta, did not seem to make any difference at all

2. With unstable, did not make any difference. However, with unstable, chromvox does speak and all sounds good. However, the pages are completely blank - in fact, they are just black. No text, no colours, nohting. However, I can move around the page using the chromvox navigation keys and hear parts of it being rendered in speech - so the content is there, it just doesn't get rendered at all.

So, my choice for now is either run stable/beta and have pages visually rendered, but no speech or run unstable, have speech from chromvox but no pages rendered on the display. 

I am running the current version of the nvidia driver (post release update) from Ubuntu. 

Tim

On Tuesday, August 14, 2012 3:08:49 AM UTC+10, raman wrote:

[T.V Raman]

Tim, In addition to the disable accessible rendering flag I
pointed out, try unsetting GtK_MODULES
in the shell where you run chrome unstable --- if that still
gives you unrendered pages, please try filing a bug against
chromium with details of your nvidea driver.

[Tim Cross]

Hi Raman,

some good news. I tried your suggestions, but no joy. This morning I was going to log a bug report against google-chrome unstable. However, I noticed there was an update, so I installed that first. Afterwards, I ran google chrome and now the pages are rendering and chromevox is working. 

Things are not perfect, but hey, this is a work in progress and I am running google-chrome unstable, so I expect some issues. In general, things are not too bad. The new US English female voice is MUCH MUCH clearer than Lois. Not saying Lois isn't good, but this new voice is quite amazing. 

Issues I've noticed so far :

1. At times, speech just stops working. It does tend to come back. De-activating and re-activating chromevox seems to help with this i.e. cvox A A.

2. When running chromevox and attempting to reply to your g groups post, hitting the reply button on the right just gives me a blank page with no rendered content. Going back, deactivating chromevox and hitting reply seems to work around this issue. This does not seem to be consistent. Soetimes, reply seems to work and you get the rendered reply page, sometimes it fails.

I won't report these as formal bugs just yet as I only want to do this if I can generate a recipe that can reproduce them. I will use the system over the weekend and see how it all goes.

regards,

Tim

[T.V Raman]

The TTS high-quality voice randomly stopping is a known
issue. If you can create a reproduceable case where a page fails
to render if cvox is running -- but renders without it, I'd
really like to get those

[Tim Cross]

Hi Raman,

the most reproducable rendering problem I am able to reproduce is with google groups. If chromevox is running and I attempt to post a reply to a discussion (like I"m doing now), hitting the "post a reply" button on the right side of an existing message results in a blank page. If I then hit 'back' to return to the discussion thread, disable chromvox with cvox A A and then hit "post a reply" again, I get the expected reply box and can enter a reply. 

Once chromvox does stop speaking, it stops completely and nothing I do seems to bring it back. Re-starting chrome does not help. The only way I've found to get it working again is to log out of the current session, log back in and re-start chrome. 

When chromevox stops working, all other sound apps, such as emacspeak, continue to work fine. Only chromevox seems to be affected. Note that the chromvox cursor still seems to be there even when speech has stopped working i.e. I can see the yellow box cursor move around the page as I navigate with the chromvox keys - just no speech and no sound icons (such as the sound you get when you tick a tickbox in gmail etc). 

I think the speech stopping may have something to do with load and/or pulseaudio. I've noticed that if I run an application which is quite resource intensive, when I return to chrome, speech is no longer working. When I have time, I will see if re-starting pulseaudio may fix the problem. 

Tim

[T.V Raman]

Tim, Thanks for this detailed summary. I'm pulseaudio free.

We'll chase down the rendering bug; suspecting the active
indicator (orange thingy)