Date   

locked Re: music production with NVDA

 

On Sun, Oct 6, 2019 at 06:25 PM, Rosemarie Chavarria wrote:
I think telling someone to just google it defeats the purpose of a mailing list.
That depends entirely on what, exactly, is being asked.   This group (and many others like it) has hundreds of members, and each and every message is an imposition on those other members' time.

There are all sorts of questions where it takes longer to type the message for the list than it would to do a web search, and I'm talking for commonly asked questions.  Asking a question on a group like this along the lines of, "What's the keyboard shortcut in MS-Word to make text bold?," deserves a, "Why on earth did you not do a search for this?"  [It would also be off-topic, but I'm trying to give an illustration of the sort of question where irritation is a perfectly valid reaction when the answer can be found faster, and more easily, without asking it on a mailing list.]

There's also the "who's asking" factor, too.  Someone who's a newbie (to anything) can and should get a lot more slack than those who are known to have a significant knowledge base and level of sophistication.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


locked Re: music production with NVDA

Orlando Enrique Fiol
 

At 06:03 PM 10/6/2019, Rosemarie Chavarria wrote:
Amen, Orlando. One of these days she'll need help with something and
I wonder how she'll feel if somebody else tells her something like
"look upp the answer for yourself"� without giving her the tools to
search.
Sarah and others like her feel that if they came by their knowledge through lots of study, trial and error, so should everyone else. But they miss the whole point of email lists, which are explicitly intended for people to converse about specific topics. Anyone can read books, search the web or consult help files. But when they turn to email lists for help, they're after human interaction. Some people learn best through Socratic dialogue, asking a specific person questions and exchanging ideas in a real discussion. Many people want to be able to ask series of questions once they get the first one answered. Googling usually doesn't accomplish that.
Orlando Enrique Fiol


Re: Directing NVDA output to a particular audio device

Luke
 

I don’t know if this makes a difference but my headphones or not USB. They use the headphone jack on the computer  

On Oct 6, 2019, at 1:52 PM, Robert Doc Wright godfearer <godfearer@...> wrote:

As long as you keep plugging and unplugging the headset you are going to have this problem. When you plug in a USB headset it becomes the new default device. When you unplug it the system falls back to the internal default speaker.

 

******If we can't look at ourselves, and ask, why?  then where does the learning start?***     

 

From: Luke
Sent: Sunday, October 6, 2019 11:33 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Directing NVDA output to a particular audio device

 

Hi! I followed Kerryn’s steps and it didn’t work for me. Both The computer and NVDA audio was coming through the headphones. I think I want to do what Sile wants to do. I want NVDA to come through my headphones only when they are plugged in the headphone jack and the Computer audio for example music and game sounds to come out the computer speakers. Maybe you need 2 sound cards for that? Which I don’t know how many I have and don’t know how you can tell.

 

> On Oct 3, 2019, at 7:43 PM, Kerryn Gunness via Groups.Io <k_gunness@...> wrote:

>

> sile

>

> 1. press control NVDA key and s to open synth box

> 2. tab once to a combo box with options

> 3. use arro keys to choose your option, for example u s b head phones

> 4 tab to ok button and press enter

>

> NVDA should be heard in the option you picked

>

> you're done

>

> ----- Original Message ----- From: "Sile via Groups.Io" <somodhrain@...>

> To: <nvda@nvda.groups.io>

> Sent: Thursday, October 3, 2019 7:32 PM

> Subject: [nvda] Directing NVDA output to a particular audio device

>

>

>> Hello

>>

>>

>> I know I have seen a thread about this, but I can't recall what the name of the thread is so couldn't find it in the list archive.

>>

>>

>> I want to be able to set the audio device that NVDA output goes to so that I can separate it from my main headphone output for presentations.

>>

>>

>> --Sile

>>

>>

>>

>

>

>

>

 

 

 


locked Re: music production with NVDA

Rosemarie Chavarria
 

That’s right, Molly. I had a teacher who was like that years ago when I was going to the program called the regional occupation program. She would just hand us the tapes with lessons and would tell us to not ask for help even if we got stuck on something. Eventually it got to the point where I didn’t ask for help anymore even if I really got stuck on something. I did everything myself even if it caused me to have headaches from trying so hard.

 

Rosemarie

 

Sent from Mail for Windows 10

 

From: molly the blind tech lover
Sent: Sunday, October 6, 2019 3:13 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] music production with NVDA

 

I think telling someone to just google it defeats the purpose of a mailing list.  what would be the point of asking questions if all someone is told to look up the answer? It  benefits no one

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: Sunday, October 6, 2019 6:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] music production with NVDA

 

Amen, Orlando. One of these days she’ll need help with something and I wonder how she’ll feel if somebody else tells her something like “look upp the answer for yourself” without giving her the tools to search. If a question is asked repeatedly, then that’s a different story.

 

Rosemarie

 

Sent from Mail for Windows 10

 

From: Orlando Enrique Fiol via Groups.Io
Sent: Sunday, October 6, 2019 2:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] music production with NVDA

 

At 04:14 PM 10/5/2019, Sarah k Alawami wrote:

>We are here to help one another, yes, however just like the franchise

>I'm in they do not hand hold, not all the time. You are after week 2 on

>your own. So yeah on the reaper list we will hold your  hand and give

>you the tools but after that we don't hand hold if you are asking basic

>questions such as How do I go from track 1 to track two. We gave you the

>tools,  now use them.

 

It would be easier not to respond to such people with elementary

questions than make them feel stupid for asking. We've talked about

this on other lists and you just don't get it. Everyone knows they

can Google something; responding to their requests telling them to

Google contributes absolutely nothing; I wish you'd stop doing that.

 

 

Orlando Enrique Fiol

Ph.D. in Music Theory

University of Pennsylvania: November, 2018

Professional Pianist/Keyboardist, Percussionist, Arranger, Performer

and Pedagogue

Home: (980) 585-1516

Mobile: (267) 971-7090

Email: ofiol@...        

 

 

 

 

 


locked Re: music production with NVDA

 

So now, as moderator, I'm posting on this topic, and in opposition to those screaming at Sarah.

Here initial answer was, and I quote, "Google osara and sws for reaper, then follow the directions in the reaper access wiki google that to. As well as joining the group on groups.io that was mensioned already. If you have any issues post them here. We are all happy to help, but we don't do much hand holding."

First.  Telling anyone to do a web search and giving them the necessary search terms, in this case osara paired with reaper and sws paired with reaper, then mentioning that one should access the wiki page for a piece of software is not, in any way, saying, "Just Google it yourself," without providing the means to do so.  I cannot know which of a wide range of resources might be found "most suitable" by any given individual, but giving them the appropriate search terms to get focused results to review to find what they like best is not "being unhelpful" nor is it asking too much of the individual who asked the question.   It is not anyone's responsibility to review and select specific search results for you, just to tell you how to get useful search results for your own review.  If they offer you a favorite, then great, but it's not rude not to have done so.

Also, given how common typos are on this group, I would suggest that folks consider that, given the surrounding context, that "post them here," might very well have been meant as, "post them there," with there being the Reapers without Peepers group.

Contrary to what a lot of people seem to expect, there are lots of groups where a minimal amount of hand holding is done.  This group is not one of those, but it is valuable information to share with folks when you recommend they join and post to a group to set accurate expectations.  There seem to be many here who find "lack of hand holding" to be a personal attack.  Well, it isn't.

I am appalled that so many are willing to leap on someone who offered very useful information, pretty much on a silver platter.  There is no dismissive, "Why don't you just Google it yourself!," element to it.
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Re: Clipspeak addon compatibility status

molly the blind tech lover
 

One of the best add-ons out there

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arlene
Sent: Sunday, October 6, 2019 6:04 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

 

, I too love clipspeak. I have no problems with it. I’m sorry it doesn’t work for some users.

 

Sent from Mail for Windows 10

 

From: molly the blind tech lover
Sent: October 6, 2019 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

 

I love clipspeak. It is extremely useful.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, October 6, 2019 5:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

 

I'm not saying that this problem will occur regarding this add-on, I don't think it will, but the possible situation should be discussed.

 

I saw Joseph's message about needing to obtain permission before making the add-on compatible.  This raises the question of providing, in some sort of agreement regarding add-ons, that under specified conditions an add-on will be considered to be in the public domain.  An add-on that is abandoned but not in the public domain is in danger of not being updated and becoming useless or significantly degraded as NVDA or the program it works with changes. 

 

Of course, the rights of those who provide add-ons for profit should be protected but it is, in my opinion, a serious violation of the spirit of NVDA that an add-on can be abandoned by its developer, and still not be able to be modified to keep it current.

 

Gene

----- Original Message -----

Sent: Sunday, October 06, 2019 4:35 PM

Subject: Re: [nvda] Clipspeak addon compatibility status

 

I just looked at the website listing the compatibility of add-ons with python 3.  It says clipspeak isn't compatible. Here's the link

https://addons.nvda-project.org/addons/nvdapy3.en.html

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 5:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps.   i suppose this
is because it is not compatible with python3 yet?   Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
> Well, Clipspeak
> <https://addons.nvda-project.org/addons/clipspeak.en.html> is still
> downloadable from the NVDA Stable Add-Ons Page
> <https://addons.nvda-project.org/index.en.html>, and so long as it
> remains there I presume it works.  Things generally get removed if
> they become incompatible with the current version of NVDA.
>
> Damien Garwood is the author, and is a member of this group.  In the
> case of Add-Ons, consulting with their respective authors is the best
> way to find out whether they're being actively maintained and whether
> they are slated to work with the Python 3 code base.
> --
>
> Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362
>
> *The color of truth is grey.*
>
>             ~ André Gide
>
>



 


Re: After Latest Stable Upgrade: NVDA does not start at system boot

molly the blind tech lover
 

I only experienced this issue on one machine. But after going to NVDA’s general settings and checking the box the problem  went away. Now NVDA starts up at the logon screen as it did before the update.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Roger Stewart
Sent: Sunday, October 6, 2019 6:00 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] After Latest Stable Upgrade: NVDA does not start at system boot

 

Just to say, I upgraded 2 machines to the new NVDA and I didn't have this problem at all. Both running Win 10 64 bit, one home version and the other pro version. This seems to be very machine specific and will be hard to track down.

Roger

 

 

 

 

 

 

 

 

 

 

On 10/6/2019 4:42 PM, Quentin Christensen wrote:

Hi Kevin, everyone,

 

We've certainly seen reports of this from time to time, but as you note - it's difficult to track down - it doesn't always affect the same users, and for most users, the fix should be relatively simple (go into the general settings and check the checkbox again).

 

As I usually say - if you happen to have had your log set to debug when you updated and can send me the logs from around when you updated, I'm happy to have a look.

 

Regards

 

Quentin.

 

On Sat, Oct 5, 2019 at 7:22 AM Kevin Cussick via Groups.Io <the.big.white.shepherd=googlemail.com@groups.io> wrote:

I do not know about this version,   but I can tell you this has been
happening for quite a few versions of nvda and nothing seems to be
getting done about it. rather I might be better rewording a bit it might
be difficult to track down.   but the result is the same for a few
versions now this has been happening and it has been reported on and I
am sure off list to the nv-access people.

On 04/10/2019 16:40, Ron Canazzi wrote:
> Hi Group,
>
> I updated NVDA to the latest build 2019.2.1 a few days ago.  I noticed
> when restarting the system, that NVDA would not start. Thinking that it
> was a glitch---a one time occurrence, I just started it with the hot
> key.  It happened again and again I used the hotkey to start NVDA.  I
> then checked the menu/settings/general and indeed found that the check
> box to start NVDA at start up was unchecked.  I checked it, restarted
> the system and now everything is fine.
>
> Did anyone else experience this with the latest build 2019.2.1?
>



 

--

Quentin Christensen
Training and Support Manager

 

 


locked Re: music production with NVDA

molly the blind tech lover
 

I think telling someone to just google it defeats the purpose of a mailing list.  what would be the point of asking questions if all someone is told to look up the answer? It  benefits no one

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: Sunday, October 6, 2019 6:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] music production with NVDA

 

Amen, Orlando. One of these days she’ll need help with something and I wonder how she’ll feel if somebody else tells her something like “look upp the answer for yourself” without giving her the tools to search. If a question is asked repeatedly, then that’s a different story.

 

Rosemarie

 

Sent from Mail for Windows 10

 

From: Orlando Enrique Fiol via Groups.Io
Sent: Sunday, October 6, 2019 2:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] music production with NVDA

 

At 04:14 PM 10/5/2019, Sarah k Alawami wrote:

>We are here to help one another, yes, however just like the franchise

>I'm in they do not hand hold, not all the time. You are after week 2 on

>your own. So yeah on the reaper list we will hold your  hand and give

>you the tools but after that we don't hand hold if you are asking basic

>questions such as How do I go from track 1 to track two. We gave you the

>tools,  now use them.

 

It would be easier not to respond to such people with elementary

questions than make them feel stupid for asking. We've talked about

this on other lists and you just don't get it. Everyone knows they

can Google something; responding to their requests telling them to

Google contributes absolutely nothing; I wish you'd stop doing that.

 

 

Orlando Enrique Fiol

Ph.D. in Music Theory

University of Pennsylvania: November, 2018

Professional Pianist/Keyboardist, Percussionist, Arranger, Performer

and Pedagogue

Home: (980) 585-1516

Mobile: (267) 971-7090

Email: ofiol@...        

 

 

 

 


Re: Clipspeak addon compatibility status

 

Hi,
Let's do this then:
1. Do let NVDA add-ons list know about your add-on and asking the community to maintain it.
2. I'll ask someone to take a look at this add-on, and if nobody steps up, I'll at least correct the manifest problem so it can at least install on future NVDA releases.

Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Damien Garwood
Sent: Sunday, October 6, 2019 2:57 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

Hi Joseph,
I'll leave this one up to you. It does have a few bugs that I wouldn't know how to resolve, not knowing enough about the NVDA codebase and Windows API programming (perhaps one of the biggest being that sometimes seemingly at random, operations fail to work, with a close second being that it can easily interfere with applications which have a different purpose for the keys that Clipspeak uses). Based on this, if you still feel that the community has use for it, then anyone who likes may take up the reins.
Meantime, for me, I think I need to do a heck of a lot more reading and experimenting and private failing (yes Damien, note to self, private being the key word there), before I start trying to publish another addon, let alone update my existing ones. I feel like I've already let the community down as it is with my lousy attempts. I'm determined not to metaphorically flood the kitchen next time I wash up.
Cheers,
Damien.

On 06/10/2019 10:13 pm, Joseph Lee wrote:
Hi,
Mostly having to do with add-on manifest issue. I'm willing to make it "compatible" but if and only if Damien gives the community permission to do so.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin
Cussick via Groups.Io
Sent: Sunday, October 6, 2019 2:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps. i suppose this
is because it is not compatible with python3 yet? Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
Well, Clipspeak
<https://addons.nvda-project.org/addons/clipspeak.en.html> is still
downloadable from the NVDA Stable Add-Ons Page
<https://addons.nvda-project.org/index.en.html>, and so long as it
remains there I presume it works. Things generally get removed if
they become incompatible with the current version of NVDA.

Damien Garwood is the author, and is a member of this group. In the
case of Add-Ons, consulting with their respective authors is the best
way to find out whether they're being actively maintained and whether
they are slated to work with the Python 3 code base.
--

Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362

*The color of truth is grey.*

~ André Gide






Re: Clipspeak addon compatibility status

Arlene
 

, I too love clipspeak. I have no problems with it. I’m sorry it doesn’t work for some users.

 

Sent from Mail for Windows 10

 

From: molly the blind tech lover
Sent: October 6, 2019 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

 

I love clipspeak. It is extremely useful.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, October 6, 2019 5:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

 

I'm not saying that this problem will occur regarding this add-on, I don't think it will, but the possible situation should be discussed.

 

I saw Joseph's message about needing to obtain permission before making the add-on compatible.  This raises the question of providing, in some sort of agreement regarding add-ons, that under specified conditions an add-on will be considered to be in the public domain.  An add-on that is abandoned but not in the public domain is in danger of not being updated and becoming useless or significantly degraded as NVDA or the program it works with changes. 

 

Of course, the rights of those who provide add-ons for profit should be protected but it is, in my opinion, a serious violation of the spirit of NVDA that an add-on can be abandoned by its developer, and still not be able to be modified to keep it current.

 

Gene

----- Original Message -----

Sent: Sunday, October 06, 2019 4:35 PM

Subject: Re: [nvda] Clipspeak addon compatibility status

 

I just looked at the website listing the compatibility of add-ons with python 3.  It says clipspeak isn't compatible. Here's the link

https://addons.nvda-project.org/addons/nvdapy3.en.html

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 5:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps.   i suppose this
is because it is not compatible with python3 yet?   Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
> Well, Clipspeak
> <https://addons.nvda-project.org/addons/clipspeak.en.html> is still
> downloadable from the NVDA Stable Add-Ons Page
> <https://addons.nvda-project.org/index.en.html>, and so long as it
> remains there I presume it works.  Things generally get removed if
> they become incompatible with the current version of NVDA.
>
> Damien Garwood is the author, and is a member of this group.  In the
> case of Add-Ons, consulting with their respective authors is the best
> way to find out whether they're being actively maintained and whether
> they are slated to work with the Python 3 code base.
> --
>
> Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362
>
> *The color of truth is grey.*
>
>             ~ André Gide
>
>




 


locked Re: music production with NVDA

Rosemarie Chavarria
 

Amen, Orlando. One of these days she’ll need help with something and I wonder how she’ll feel if somebody else tells her something like “look upp the answer for yourself” without giving her the tools to search. If a question is asked repeatedly, then that’s a different story.

 

Rosemarie

 

Sent from Mail for Windows 10

 

From: Orlando Enrique Fiol via Groups.Io
Sent: Sunday, October 6, 2019 2:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] music production with NVDA

 

At 04:14 PM 10/5/2019, Sarah k Alawami wrote:

>We are here to help one another, yes, however just like the franchise

>I'm in they do not hand hold, not all the time. You are after week 2 on

>your own. So yeah on the reaper list we will hold your  hand and give

>you the tools but after that we don't hand hold if you are asking basic

>questions such as How do I go from track 1 to track two. We gave you the

>tools,  now use them.

 

It would be easier not to respond to such people with elementary

questions than make them feel stupid for asking. We've talked about

this on other lists and you just don't get it. Everyone knows they

can Google something; responding to their requests telling them to

Google contributes absolutely nothing; I wish you'd stop doing that.

 

 

Orlando Enrique Fiol

Ph.D. in Music Theory

University of Pennsylvania: November, 2018

Professional Pianist/Keyboardist, Percussionist, Arranger, Performer

and Pedagogue

Home: (980) 585-1516

Mobile: (267) 971-7090

Email: ofiol@...        

 

 

 

 


Re: After Latest Stable Upgrade: NVDA does not start at system boot

Roger Stewart
 

Just to say, I upgraded 2 machines to the new NVDA and I didn't have this problem at all. Both running Win 10 64 bit, one home version and the other pro version. This seems to be very machine specific and will be hard to track down.
Roger










On 10/6/2019 4:42 PM, Quentin Christensen wrote:
Hi Kevin, everyone,

We've certainly seen reports of this from time to time, but as you note - it's difficult to track down - it doesn't always affect the same users, and for most users, the fix should be relatively simple (go into the general settings and check the checkbox again).

As I usually say - if you happen to have had your log set to debug when you updated and can send me the logs from around when you updated, I'm happy to have a look.

Regards

Quentin.

On Sat, Oct 5, 2019 at 7:22 AM Kevin Cussick via Groups.Io <the.big.white.shepherd=googlemail.com@groups.io> wrote:
I do not know about this version,   but I can tell you this has been
happening for quite a few versions of nvda and nothing seems to be
getting done about it. rather I might be better rewording a bit it might
be difficult to track down.   but the result is the same for a few
versions now this has been happening and it has been reported on and I
am sure off list to the nv-access people.

On 04/10/2019 16:40, Ron Canazzi wrote:
> Hi Group,
>
> I updated NVDA to the latest build 2019.2.1 a few days ago.  I noticed
> when restarting the system, that NVDA would not start. Thinking that it
> was a glitch---a one time occurrence, I just started it with the hot
> key.  It happened again and again I used the hotkey to start NVDA.  I
> then checked the menu/settings/general and indeed found that the check
> box to start NVDA at start up was unchecked.  I checked it, restarted
> the system and now everything is fine.
>
> Did anyone else experience this with the latest build 2019.2.1?
>





--
Quentin Christensen
Training and Support Manager



Re: Clipspeak addon compatibility status

Damien Garwood <damien@...>
 

Hi Joseph,
I'll leave this one up to you. It does have a few bugs that I wouldn't know how to resolve, not knowing enough about the NVDA codebase and Windows API programming (perhaps one of the biggest being that sometimes seemingly at random, operations fail to work, with a close second being that it can easily interfere with applications which have a different purpose for the keys that Clipspeak uses). Based on this, if you still feel that the community has use for it, then anyone who likes may take up the reins.
Meantime, for me, I think I need to do a heck of a lot more reading and experimenting and private failing (yes Damien, note to self, private being the key word there), before I start trying to publish another addon, let alone update my existing ones. I feel like I've already let the community down as it is with my lousy attempts. I'm determined not to metaphorically flood the kitchen next time I wash up.
Cheers,
Damien.

On 06/10/2019 10:13 pm, Joseph Lee wrote:
Hi,
Mostly having to do with add-on manifest issue. I'm willing to make it "compatible" but if and only if Damien gives the community permission to do so.
Cheers,
Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 2:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status
this addon does not work with the latest alpha snaps. i suppose this
is because it is not compatible with python3 yet? Joseph or someone
else can answer.
On 06/10/2019 16:04, Brian Vogel wrote:
Well, Clipspeak
<https://addons.nvda-project.org/addons/clipspeak.en.html> is still
downloadable from the NVDA Stable Add-Ons Page
<https://addons.nvda-project.org/index.en.html>, and so long as it
remains there I presume it works. Things generally get removed if
they become incompatible with the current version of NVDA.

Damien Garwood is the author, and is a member of this group. In the
case of Add-Ons, consulting with their respective authors is the best
way to find out whether they're being actively maintained and whether
they are slated to work with the Python 3 code base.
--

Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362

*The color of truth is grey.*

~ André Gide


Re: Clipspeak addon compatibility status

molly the blind tech lover
 

I love clipspeak. It is extremely useful.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, October 6, 2019 5:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

 

I'm not saying that this problem will occur regarding this add-on, I don't think it will, but the possible situation should be discussed.

 

I saw Joseph's message about needing to obtain permission before making the add-on compatible.  This raises the question of providing, in some sort of agreement regarding add-ons, that under specified conditions an add-on will be considered to be in the public domain.  An add-on that is abandoned but not in the public domain is in danger of not being updated and becoming useless or significantly degraded as NVDA or the program it works with changes. 

 

Of course, the rights of those who provide add-ons for profit should be protected but it is, in my opinion, a serious violation of the spirit of NVDA that an add-on can be abandoned by its developer, and still not be able to be modified to keep it current.

 

Gene

----- Original Message -----

Sent: Sunday, October 06, 2019 4:35 PM

Subject: Re: [nvda] Clipspeak addon compatibility status

 

I just looked at the website listing the compatibility of add-ons with python 3.  It says clipspeak isn't compatible. Here's the link

https://addons.nvda-project.org/addons/nvdapy3.en.html

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 5:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps.   i suppose this
is because it is not compatible with python3 yet?   Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
> Well, Clipspeak
> <https://addons.nvda-project.org/addons/clipspeak.en.html> is still
> downloadable from the NVDA Stable Add-Ons Page
> <https://addons.nvda-project.org/index.en.html>, and so long as it
> remains there I presume it works.  Things generally get removed if
> they become incompatible with the current version of NVDA.
>
> Damien Garwood is the author, and is a member of this group.  In the
> case of Add-Ons, consulting with their respective authors is the best
> way to find out whether they're being actively maintained and whether
> they are slated to work with the Python 3 code base.
> --
>
> Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362
>
> *The color of truth is grey.*
>
>             ~ André Gide
>
>






locked Re: music production with NVDA

Orlando Enrique Fiol
 

At 04:14 PM 10/5/2019, Sarah k Alawami wrote:
We are here to help one another, yes, however just like the franchise
I'm in they do not hand hold, not all the time. You are after week 2 on
your own. So yeah on the reaper list we will hold your hand and give
you the tools but after that we don't hand hold if you are asking basic
questions such as How do I go from track 1 to track two. We gave you the
tools, now use them.
It would be easier not to respond to such people with elementary questions than make them feel stupid for asking. We've talked about this on other lists and you just don't get it. Everyone knows they can Google something; responding to their requests telling them to Google contributes absolutely nothing; I wish you'd stop doing that.


Orlando Enrique Fiol
Ph.D. in Music Theory
University of Pennsylvania: November, 2018
Professional Pianist/Keyboardist, Percussionist, Arranger, Performer and Pedagogue
Home: (980) 585-1516
Mobile: (267) 971-7090
Email: ofiol@verizon.net


Re: Clipspeak addon compatibility status

Gene
 

I'm not saying that this problem will occur regarding this add-on, I don't think it will, but the possible situation should be discussed.
 
I saw Joseph's message about needing to obtain permission before making the add-on compatible.  This raises the question of providing, in some sort of agreement regarding add-ons, that under specified conditions an add-on will be considered to be in the public domain.  An add-on that is abandoned but not in the public domain is in danger of not being updated and becoming useless or significantly degraded as NVDA or the program it works with changes. 
 
Of course, the rights of those who provide add-ons for profit should be protected but it is, in my opinion, a serious violation of the spirit of NVDA that an add-on can be abandoned by its developer, and still not be able to be modified to keep it current.
 
Gene

----- Original Message -----
Sent: Sunday, October 06, 2019 4:35 PM
Subject: Re: [nvda] Clipspeak addon compatibility status

I just looked at the website listing the compatibility of add-ons with python 3.  It says clipspeak isn't compatible. Here's the link

https://addons.nvda-project.org/addons/nvdapy3.en.html

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 5:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps.   i suppose this
is because it is not compatible with python3 yet?   Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
> Well, Clipspeak
> <https://addons.nvda-project.org/addons/clipspeak.en.html> is still
> downloadable from the NVDA Stable Add-Ons Page
> <https://addons.nvda-project.org/index.en.html>, and so long as it
> remains there I presume it works.  Things generally get removed if
> they become incompatible with the current version of NVDA.
>
> Damien Garwood is the author, and is a member of this group.  In the
> case of Add-Ons, consulting with their respective authors is the best
> way to find out whether they're being actively maintained and whether
> they are slated to work with the Python 3 code base.
> --
>
> Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362
>
> *The color of truth is grey.*
>
>             ~ André Gide
>
>







Re: After Latest Stable Upgrade: NVDA does not start at system boot

Quentin Christensen
 

Hi Kevin, everyone,

We've certainly seen reports of this from time to time, but as you note - it's difficult to track down - it doesn't always affect the same users, and for most users, the fix should be relatively simple (go into the general settings and check the checkbox again).

As I usually say - if you happen to have had your log set to debug when you updated and can send me the logs from around when you updated, I'm happy to have a look.

Regards

Quentin.

On Sat, Oct 5, 2019 at 7:22 AM Kevin Cussick via Groups.Io <the.big.white.shepherd=googlemail.com@groups.io> wrote:
I do not know about this version,   but I can tell you this has been
happening for quite a few versions of nvda and nothing seems to be
getting done about it. rather I might be better rewording a bit it might
be difficult to track down.   but the result is the same for a few
versions now this has been happening and it has been reported on and I
am sure off list to the nv-access people.

On 04/10/2019 16:40, Ron Canazzi wrote:
> Hi Group,
>
> I updated NVDA to the latest build 2019.2.1 a few days ago.  I noticed
> when restarting the system, that NVDA would not start. Thinking that it
> was a glitch---a one time occurrence, I just started it with the hot
> key.  It happened again and again I used the hotkey to start NVDA.  I
> then checked the menu/settings/general and indeed found that the check
> box to start NVDA at start up was unchecked.  I checked it, restarted
> the system and now everything is fine.
>
> Did anyone else experience this with the latest build 2019.2.1?
>





--
Quentin Christensen
Training and Support Manager


Re: Clipspeak addon compatibility status

molly the blind tech lover
 

I just looked at the website listing the compatibility of add-ons with python 3. It says clipspeak isn't compatible. Here's the link

https://addons.nvda-project.org/addons/nvdapy3.en.html

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 5:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps. i suppose this
is because it is not compatible with python3 yet? Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
Well, Clipspeak
<https://addons.nvda-project.org/addons/clipspeak.en.html> is still
downloadable from the NVDA Stable Add-Ons Page
<https://addons.nvda-project.org/index.en.html>, and so long as it
remains there I presume it works. Things generally get removed if
they become incompatible with the current version of NVDA.

Damien Garwood is the author, and is a member of this group. In the
case of Add-Ons, consulting with their respective authors is the best
way to find out whether they're being actively maintained and whether
they are slated to work with the Python 3 code base.
--

Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362

*The color of truth is grey.*

~ André Gide


Re: Clipspeak addon compatibility status

Gene
 

I imagine it will be made compatible but unless new students are going to benefit somehow or work with features in the upcoming possibly incompatible version of NVDA, they may use the current version of NVDA.  I haven't followed what is in the new version but I suspect that for new students, it may not be important.
 
Gene

------ Original Message -----
Sent: Sunday, October 06, 2019 4:10 PM
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps.   i suppose this
is because it is not compatible with python3 yet?   Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
> Well, Clipspeak
> <https://addons.nvda-project.org/addons/clipspeak.en.html> is still
> downloadable from the NVDA Stable Add-Ons Page
> <https://addons.nvda-project.org/index.en.html>, and so long as it
> remains there I presume it works.  Things generally get removed if they
> become incompatible with the current version of NVDA.
>
> Damien Garwood is the author, and is a member of this group.  In the
> case of Add-Ons, consulting with their respective authors is the best
> way to find out whether they're being actively maintained and whether
> they are slated to work with the Python 3 code base.
> --
>
> Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362
>
> *The color of truth is grey.*
>
>             ~ André Gide
>
>



Re: Clipspeak addon compatibility status

 

Hi,
Mostly having to do with add-on manifest issue. I'm willing to make it "compatible" but if and only if Damien gives the community permission to do so.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 2:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps. i suppose this
is because it is not compatible with python3 yet? Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
Well, Clipspeak
<https://addons.nvda-project.org/addons/clipspeak.en.html> is still
downloadable from the NVDA Stable Add-Ons Page
<https://addons.nvda-project.org/index.en.html>, and so long as it
remains there I presume it works. Things generally get removed if
they become incompatible with the current version of NVDA.

Damien Garwood is the author, and is a member of this group. In the
case of Add-Ons, consulting with their respective authors is the best
way to find out whether they're being actively maintained and whether
they are slated to work with the Python 3 code base.
--

Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362

*The color of truth is grey.*

~ André Gide