Date   

Re: very good news about audio conversion soft ware

Christopher-Mark Gilland <clgilland07@...>
 

OK, here's another sollution. Why not just rip with Winamp? Can't it do vorbis, and I think, maybe even Flack? If nothing else, rip with VLC!
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

@AHeart4God316
Phone: (704) 256-8010.

----- Original Message -----
From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 5:40 PM
Subject: Re: [nvda] very good news about audio conversion soft ware


Thats a point actually.
itunes does use gracenote if you have an i device.
You will have to convert the music to mp3, it does not do ogg or flack sadly.
However all tracks are numbered.
if you get winlame which is for now malware free at least the 2010 version is
Sadly I do think this is a dead project but it should do ogg to 500kbps mp3 to 320kbps wav, I am not sure about flack but anyway.
The other thing you can do is buy goldwave or get audacity which is free but not full with malware just yet.
Its ogg encoder has been known to have issues but who knows if its still like that now.



On 4/05/2016 9:14 a.m., Christopher-Mark Gilland wrote:
Goodness gracious, yall! Why not just use ITunes to rip for crying out
loud! Is it mainly because ITunes doesn't support the formats you all
wanna rip into? If so, then OK, point taken, but otherwise... really?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

@AHeart4God316
Phone: (704) 256-8010.



Re: how to tell NVDA to read series of number in single digits.

mohammad suliman
 

hello all,
how is it going Nasrin?

if it helps, pressing numpad 5 twice will spell the number digit by digit.

best,
Mohammad

On 5/4/2016 4:30 AM, nasrin khaksar wrote:
hello.
nvda most times for me the digits completely and sometimes reads single digits.
but i heard that settings this, is a capability of commercial screen readers.
thanks for asking and allah bless you.
please inform me if you found a solution.

On 5/4/16, Ali Abdalkadir <abdalkadir41@...> wrote:
Hello guys,

Does any of you know how to make NVDA read a series of numbers in single
digits?



Best regards,

Ali


Re: how to tell NVDA to read series of number in single digits.

 

hello.
nvda most times for me the digits completely and sometimes reads single digits.
but i heard that settings this, is a capability of commercial screen readers.
thanks for asking and allah bless you.
please inform me if you found a solution.

On 5/4/16, Ali Abdalkadir <abdalkadir41@...> wrote:
Hello guys,

Does any of you know how to make NVDA read a series of numbers in single
digits?



Best regards,

Ali

--
Those who follow the Messenger-Prophet, the Ummi, whom they find
written down with them in the Taurat and the Injeel [who] enjoins them
good and forbids them evil, and makes lawful to them the good things
and makes unlawful to them impure things, and removes from them their
burden and the shackles which were upon them; so [as for] those who
believe in him and honor him and help him, and follow the light which
has been sent down with him, these it is that are the successful.
holy quran, chapter 7, verse 157.
best website for studying islamic book in different languages
al-islam.org


Re: very good news about audio conversion soft ware

Bobby <bvinton@...>
 

no I don't mean rip I mean converting audio that I record or down load from the internet.  I don't know whare or how to add files to convert.


On 5/3/2016 9:04 PM, Robert Mendoza wrote:

Once the Windows media player opens pressed the Control plus 3 to change it to suggestion view panel. Then, right-click and arrow down to select the More Option. Tab till you reach tab panel that says Rip Music. then, select the preferred settings or conversion to rip your music into different format like mp3, wma, and so on.

Robert Mendoza
On 5/4/2016 8:25 AM, Bobby wrote:
Well I just learned some thing new.  I never you could convert audio windows media player I only new you can rip with it.  Can you please tell me ware the convert option is on windows media player because I can't find that option at all.


On 5/3/2016 7:16 PM, Patrick Le Baudour wrote:
Hum, if it's for converting into mp3 or wma, windows media player does it, no need for anything else... and having never used iTunes, i have no idea of what  it can or can't do,  I thought it was mainly for buying music from apple.

-- Patrick
Le 03/05/2016 à 23:14, Christopher-Mark Gilland a écrit :
Goodness gracious, yall!  Why not just use ITunes to rip for  crying out
loud!  Is it mainly because ITunes doesn't support the formats you all
wanna rip into?  If so, then OK, point taken, but otherwise... really?
---
Christopher Gilland












Re: very good news about audio conversion soft ware

Robert Mendoza
 

Once the Windows media player opens pressed the Control plus 3 to change it to suggestion view panel. Then, right-click and arrow down to select the More Option. Tab till you reach tab panel that says Rip Music. then, select the preferred settings or conversion to rip your music into different format like mp3, wma, and so on.

Robert Mendoza
On 5/4/2016 8:25 AM, Bobby wrote:

Well I just learned some thing new.  I never you could convert audio windows media player I only new you can rip with it.  Can you please tell me ware the convert option is on windows media player because I can't find that option at all.


On 5/3/2016 7:16 PM, Patrick Le Baudour wrote:
Hum, if it's for converting into mp3 or wma, windows media player does it, no need for anything else... and having never used iTunes, i have no idea of what  it can or can't do,  I thought it was mainly for buying music from apple.

-- Patrick
Le 03/05/2016 à 23:14, Christopher-Mark Gilland a écrit :
Goodness gracious, yall!  Why not just use ITunes to rip for  crying out
loud!  Is it mainly because ITunes doesn't support the formats you all
wanna rip into?  If so, then OK, point taken, but otherwise... really?
---
Christopher Gilland











how to tell NVDA to read series of number in single digits.

Ali Abdalkadir
 

Hello guys,

Does any of you know how to make NVDA read a series of numbers in single digits?

 

Best regards,

Ali


Re: NVDA still freezing, don't know what the deal is

Sharni-Lee Ward
 

nvda_snapshot_brltbl_20160315 is the name of the file in the list, if
that's what you mean. I got it back in March and although the
experimental UEB tables added to it weren't perfect (Joseph told me it
was no trivial matter to fix the minor problems I brought up when I was
first testing it) it's better than the current one, which lacks "ea",
"cc" and "ff" contractions, as well as only showing format terminators
and emdashes (among other symbols) being replaced with eight cells of
weird code that disrupt the flow of reading.

On 4/05/2016 8:21 AM, Tyler Spivey wrote:
The espeak bug is fixed in next.
That should graduate to master soon, if people don't find problems with it.

For the braille table, what snapshot are you using now? You'll probably
need to merge it when 2016.2 comes out.

On 5/3/2016 1:38 PM, Sharni-Lee Ward wrote:
...What HAPPENED to the espeak voice? It sounds choppy and distorted (at
least Linda does) and it was honestly hurting my ears.


And the Master snapshot doesn't have the braille table I'd prefer to
use, which is why I got that other snapshot when I did. The newer more
experimental table fixed the problem of emdashes being replaced by eight
cells of nonsense that took up more space than necessary, and formatting
representations, and missed contractions...


I can't use this.

On 4/05/2016 5:47 AM, Gene wrote:
I believe the new production version will be released in about a
month. However, I would expect the master snapshot to be probably
stable or reasonably stable. You can use a portable version if you
want to evaluate it without installing it. I haven't used new
snapshots fir a while but my experience in the past has been that the
snapshots I've used have been stable. That doesn't mean that they all
are. They are versions still in development and not beta tested.

The page to see and download the latest snapshots is
http://www.nvaccess.org/files/nvda/snapshots/

Gene
----- Original Message -----

*From:* Sharni-Lee Ward <mailto:sharni-lee.ward@...>
*Sent:* Tuesday, May 03, 2016 1:10 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] NVDA still freezing, don't know what the deal is

Hi,


The reason the driver was still trying to do something was that I had
used the old snapshot I had in conjunction with my display to read for a
bit, then had disconnected the display without resetting the "display"
setting in Braille Settings to "No Braille". As I said, it lasted
longer, but still locked up at the most inconvenient time...


Can I have a link to this master snapshot? And is this building toward
the next release or are some things not ready for that yet? If the
former, when is the next release? Is it some time this month, or next?


On 3/05/2016 6:29 PM, Brian's Mail list account wrote:
No, to me unless there has been some significant malware or crash from
a bit of software, then the registry can be repaired automatically by
windows.

Beware however, as next week is update week.
Brian

bglists@... <mailto:bglists@...>
Sent via blueyonder.
Please address personal email to:-
briang1@... <mailto:briang1@...>, putting
'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene"
<<mailto:nedster66@...>nedster66@...>
To: <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>
Sent: Monday, May 02, 2016 11:25 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


Hey, before you have to format the computer. Why not run chkdsk and
then go
into the bios and see what can be the problem. I'd use format as the
last
resort. Or if you just want to do it and get it over with. then go
ahead and
do one. Good luck!

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@...]
Sent: May-02-16 9:17 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

It just happened AGAIN. This time, with no Braille Display plugged in,
but still in Word. My sister described what she saw as "It's circling
and the screen is foggy," so I'm assuming it was hanging. It took
longer
than normal to shut down, and longer than normal to start up properly,
and apparently Windows Explorer lagged for a few seconds. I don't know
how to recover my writing (I tried one of the previous times this
happened by restoring the auto recovery file from the Recycle bin
but it
didn't work...).


Anyways, here's the log. I hope this time I can get an answer for why
this is happening. I'm getting seriously concerned at this point.


INFO - __main__ (00:26:15):
Starting NVDA
INFO - core.main (00:26:19):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (00:26:20):
NVDA version brltbl20160315
INFO - core.main (00:26:20):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (00:26:20):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (00:26:20):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (00:26:24):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (00:26:24):
Loaded synthDriver ptenglish
INFO - core.main (00:26:24):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (00:26:24):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (00:26:24):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (00:26:24):
Braille input initialized
INFO - core.main (00:26:25):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (00:27:25):
Loaded braille display driver freedomScientific, current display has 40
cells.
ERROR - queueHandler.flushQueue (00:33:30):
Error in func _handleUpdate from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 50, in flushQueue
File "virtualBuffers\__init__.pyc", line 674, in _handleUpdate
File "braille.pyc", line 1645, in handleUpdate
File "braille.pyc", line 906, in update
File "textInfos\offsets.pyc", line 346, in expand
File "virtualBuffers\__init__.pyc", line 314, in _getUnitOffsets
File "textInfos\offsets.pyc", line 328, in _getUnitOffsets
File "virtualBuffers\__init__.pyc", line 256, in _getParagraphOffsets
WindowsError: [Error 1775] A null context handle was passed from the
client to the host during a remote procedure call


On 3/05/2016 12:15 AM, Sharni-Lee Ward wrote:
Just tried another thing that consistently got NVDA to hang recently,
namely, opening the sounds manager in Control Panel and then
arrowing to
the Sound Scheme tab. I thought it only did this because of the
Braille
Display but I wanted to test it to make sure. This time, once the
window
was closed, NVDA started responding again. I also tried to activate
Narrator but it didn't work, though as I said, that didn't end up
mattering. Here's the log for that session, though I warn you, the
warning repeats itself several times. In case each warning was subtly
different, I copied the whole thing. Don't worry about the Braille
error
that shows up first-that's about me starting up the computer and by
extension NVDA without my display plugged in and then saving the
configuration with default as No Braille.


INFO - __main__ (18:51:56):
Starting NVDA
INFO - core.main (18:51:59):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (18:52:00):
NVDA version 2016.1
INFO - core.main (18:52:00):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (18:52:00):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:52:00):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__
(18:52:10):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (18:52:11):
Loaded synthDriver ptenglish
INFO - core.main (18:52:11):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (18:52:11):
Using liblouis version 2.6.5
ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
Error initializing display driver
Traceback (most recent call last):
File "braille.pyo", line 1447, in setDisplayByName
File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in
__init__
RuntimeError: No display found
INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:52:11):
Braille input initialized
INFO - core.main (18:52:12):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager.save (19:30:39):
Base configuration saved
WARNING - watchdog._watcher (23:47:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:47:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

INFO - core.onEndSession (23:54:04):
Windows session ending


On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:
If the master snapshots fixed it, does this mean the next release
(which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to
connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to
sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try
Gene's
method, although I suspect it will be fine. Thank you everyone
for all
your help and tips, and at least I know how to retrieve old log
messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:
I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with
one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@... <mailto:bglists@...>
Sent via blueyonder.
Please address personal email to:-
briang1@... <mailto:briang1@...>,
putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@...
<mailto:nedster66@...>>
To: <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


Hi there: Do you think your computer could have mellwhere to
cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@...]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA still freezing, don't know what the
deal is
Gene <gsasner@... <mailto:gsasner@...>> wrote:
Why wouldn't my workaround accomplish the same end but more
easily.
Because most of the keyboard is frozen when this freeze
happens. The
only
thing that works is the windows key and some function keys.













Re: very good news about audio conversion soft ware

Bobby <bvinton@...>
 

Well I just learned some thing new. I never you could convert audio windows media player I only new you can rip with it. Can you please tell me ware the convert option is on windows media player because I can't find that option at all.

On 5/3/2016 7:16 PM, Patrick Le Baudour wrote:
Hum, if it's for converting into mp3 or wma, windows media player does it, no need for anything else... and having never used iTunes, i have no idea of what it can or can't do, I thought it was mainly for buying music from apple.

-- Patrick
Le 03/05/2016 à 23:14, Christopher-Mark Gilland a écrit :
Goodness gracious, yall! Why not just use ITunes to rip for crying out
loud! Is it mainly because ITunes doesn't support the formats you all
wanna rip into? If so, then OK, point taken, but otherwise... really?
---
Christopher Gilland


Re: very good news about audio conversion soft ware

Patrick Le Baudour
 

Hum, if it's for converting into mp3 or wma, windows media player does it, no need for anything else... and having never used iTunes, i have no idea of what it can or can't do, I thought it was mainly for buying music from apple.

-- Patrick

Le 03/05/2016 à 23:14, Christopher-Mark Gilland a écrit :
Goodness gracious, yall! Why not just use ITunes to rip for crying out
loud! Is it mainly because ITunes doesn't support the formats you all
wanna rip into? If so, then OK, point taken, but otherwise... really?
---
Christopher Gilland


nvda cdex installer

 

Hi all.
Ok, using7zip I extracted the file, then with innosetup 5.9 created this
https://www.dropbox.com/s/apqg3215nxn3dgz/cdex%201.8.1%20win32.exe?dl=0
This is not the entire thing, its just the wizzard with a few default patches.
It has a file in the wrong place which was supposed to be licence, and its not flash.
It will install the program and nothing else.
without the opencandy plugin the installer is harmless.
This has been tested on my 32 bit box and it does work and it does uninstall.
This should stop the whining at least for this version.
If you extract this with 7zip you can see my source, its after all what I did.
Some of these things are incripted so you can't do this easily without something like universal extracter which I don't have as I hardly do this thing anymore.
But at any rate here is my quick and dirty hack for the day.


Re: NVDA still freezing, don't know what the deal is

Tyler Spivey
 

The espeak bug is fixed in next.
That should graduate to master soon, if people don't find problems with it.

For the braille table, what snapshot are you using now? You'll probably
need to merge it when 2016.2 comes out.

On 5/3/2016 1:38 PM, Sharni-Lee Ward wrote:
...What HAPPENED to the espeak voice? It sounds choppy and distorted (at
least Linda does) and it was honestly hurting my ears.


And the Master snapshot doesn't have the braille table I'd prefer to
use, which is why I got that other snapshot when I did. The newer more
experimental table fixed the problem of emdashes being replaced by eight
cells of nonsense that took up more space than necessary, and formatting
representations, and missed contractions...


I can't use this.

On 4/05/2016 5:47 AM, Gene wrote:
I believe the new production version will be released in about a
month. However, I would expect the master snapshot to be probably
stable or reasonably stable. You can use a portable version if you
want to evaluate it without installing it. I haven't used new
snapshots fir a while but my experience in the past has been that the
snapshots I've used have been stable. That doesn't mean that they all
are. They are versions still in development and not beta tested.

The page to see and download the latest snapshots is
http://www.nvaccess.org/files/nvda/snapshots/

Gene
----- Original Message -----

*From:* Sharni-Lee Ward <mailto:sharni-lee.ward@...>
*Sent:* Tuesday, May 03, 2016 1:10 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] NVDA still freezing, don't know what the deal is

Hi,


The reason the driver was still trying to do something was that I had
used the old snapshot I had in conjunction with my display to read for a
bit, then had disconnected the display without resetting the "display"
setting in Braille Settings to "No Braille". As I said, it lasted
longer, but still locked up at the most inconvenient time...


Can I have a link to this master snapshot? And is this building toward
the next release or are some things not ready for that yet? If the
former, when is the next release? Is it some time this month, or next?


On 3/05/2016 6:29 PM, Brian's Mail list account wrote:
No, to me unless there has been some significant malware or crash from
a bit of software, then the registry can be repaired automatically by
windows.

Beware however, as next week is update week.
Brian

bglists@... <mailto:bglists@...>
Sent via blueyonder.
Please address personal email to:-
briang1@... <mailto:briang1@...>, putting
'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene"
<<mailto:nedster66@...>nedster66@...>
To: <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>
Sent: Monday, May 02, 2016 11:25 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


Hey, before you have to format the computer. Why not run chkdsk and
then go
into the bios and see what can be the problem. I'd use format as the
last
resort. Or if you just want to do it and get it over with. then go
ahead and
do one. Good luck!

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@...]
Sent: May-02-16 9:17 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

It just happened AGAIN. This time, with no Braille Display plugged in,
but still in Word. My sister described what she saw as "It's circling
and the screen is foggy," so I'm assuming it was hanging. It took
longer
than normal to shut down, and longer than normal to start up properly,
and apparently Windows Explorer lagged for a few seconds. I don't know
how to recover my writing (I tried one of the previous times this
happened by restoring the auto recovery file from the Recycle bin
but it
didn't work...).


Anyways, here's the log. I hope this time I can get an answer for why
this is happening. I'm getting seriously concerned at this point.


INFO - __main__ (00:26:15):
Starting NVDA
INFO - core.main (00:26:19):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (00:26:20):
NVDA version brltbl20160315
INFO - core.main (00:26:20):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (00:26:20):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (00:26:20):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (00:26:24):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (00:26:24):
Loaded synthDriver ptenglish
INFO - core.main (00:26:24):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (00:26:24):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (00:26:24):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (00:26:24):
Braille input initialized
INFO - core.main (00:26:25):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (00:27:25):
Loaded braille display driver freedomScientific, current display has 40
cells.
ERROR - queueHandler.flushQueue (00:33:30):
Error in func _handleUpdate from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 50, in flushQueue
File "virtualBuffers\__init__.pyc", line 674, in _handleUpdate
File "braille.pyc", line 1645, in handleUpdate
File "braille.pyc", line 906, in update
File "textInfos\offsets.pyc", line 346, in expand
File "virtualBuffers\__init__.pyc", line 314, in _getUnitOffsets
File "textInfos\offsets.pyc", line 328, in _getUnitOffsets
File "virtualBuffers\__init__.pyc", line 256, in _getParagraphOffsets
WindowsError: [Error 1775] A null context handle was passed from the
client to the host during a remote procedure call


On 3/05/2016 12:15 AM, Sharni-Lee Ward wrote:
Just tried another thing that consistently got NVDA to hang recently,
namely, opening the sounds manager in Control Panel and then
arrowing to
the Sound Scheme tab. I thought it only did this because of the
Braille
Display but I wanted to test it to make sure. This time, once the
window
was closed, NVDA started responding again. I also tried to activate
Narrator but it didn't work, though as I said, that didn't end up
mattering. Here's the log for that session, though I warn you, the
warning repeats itself several times. In case each warning was subtly
different, I copied the whole thing. Don't worry about the Braille
error
that shows up first-that's about me starting up the computer and by
extension NVDA without my display plugged in and then saving the
configuration with default as No Braille.


INFO - __main__ (18:51:56):
Starting NVDA
INFO - core.main (18:51:59):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (18:52:00):
NVDA version 2016.1
INFO - core.main (18:52:00):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (18:52:00):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:52:00):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__
(18:52:10):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (18:52:11):
Loaded synthDriver ptenglish
INFO - core.main (18:52:11):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (18:52:11):
Using liblouis version 2.6.5
ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
Error initializing display driver
Traceback (most recent call last):
File "braille.pyo", line 1447, in setDisplayByName
File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in
__init__
RuntimeError: No display found
INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:52:11):
Braille input initialized
INFO - core.main (18:52:12):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager.save (19:30:39):
Base configuration saved
WARNING - watchdog._watcher (23:47:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:47:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__


init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e


speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

INFO - core.onEndSession (23:54:04):
Windows session ending


On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:
If the master snapshots fixed it, does this mean the next release
(which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to
connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to
sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try
Gene's
method, although I suspect it will be fine. Thank you everyone
for all
your help and tips, and at least I know how to retrieve old log
messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:
I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with
one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@... <mailto:bglists@...>
Sent via blueyonder.
Please address personal email to:-
briang1@... <mailto:briang1@...>,
putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@...
<mailto:nedster66@...>>
To: <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


Hi there: Do you think your computer could have mellwhere to
cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@...]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA still freezing, don't know what the
deal is

Gene <gsasner@... <mailto:gsasner@...>> wrote:
Why wouldn't my workaround accomplish the same end but more
easily.
Because most of the keyboard is frozen when this freeze
happens. The
only
thing that works is the windows key and some function keys.
















Re: very good news about audio conversion soft ware

 

Generally if you have loaded something with opencandy it may or may not load other things.

On 4/05/2016 6:24 a.m., Bobby wrote:
no our hopes are not dashed at all because I just got the new version.
The new version is cdex version 1.81. I never got a message about
malware. I have the program and it works very well and faster than the
older versions.


On 5/3/2016 2:06 PM, erik burggraaf wrote:
Uh oh. That's the official site. For sure. When I went to the old
site http://cdexos.sourceforge.net it redirected me to that cdex.nu
site which looks exactly like the old cdex source forge site. Maybe
our hopes are dashed and the entire project has been highjacked? It's
been at least 10 years since the last upgrade as far as I know.

Best,

Erik Burggraaf


On May 3, 2016, at 10:54 AM, Dan Beaver <dbeaver888@...
<mailto:dbeaver888@...>> wrote:

Hi,


You might want to be careful about getting software from this site.
I too have used cdex for many years and wanted to ghet the new
version. However, when I clicked on the link Sophos stopped my
browser and said that some mal ware had been found on that site.


I am now pondering whether or not I want to get it from there.


Dan Beaver


On 5/3/2016 12:32 PM, erik burggraaf wrote:
This is fantastic news! I've used cdex for over 15 years and I
never thought we'd see another update.

New website address as well:
http://cdex.mu/download

Do not use filehipo or some other third party source like that or
you will risk your computer getting extras you didn't ask for.

Best,

Erik Burggraaf


On May 3, 2016, at 9:17 AM, Bobby <bvinton@...> wrote:

I just wanted to tell you all about an old converter and cd reader
called c dex. Cdex is the fastest audio converter and they just
came out with a new version today. You can get this progran at
filehippo.com <http://filehippo.com/>. Let me know what you think
of it when you get it.





Re: very good news about audio conversion soft ware

Chris Mullins
 

AVG also detected a threat when I attempted to use this download link.

 

Cheers

Chris

 

From: Kwork [mailto:istherelife@...]
Sent: 03 May 2016 21:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] very good news about audio conversion soft ware

 

For me, it did a clean install. I do have unchecki installed, but it didn't tell me it blocked anything, and I didn't see anything odd being installed at the same time. Of course I'll scan and check for viruses and malware, but the problems that have plagued previous installers seem to have not been present for me with this one.

In case the site doesn't throw a fit, and prevent hot linking, here is the direct link for the latest installer, though it's easy enough to follow links on the website to get to it anyway:

Travis

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

Sent: Tuesday, May 03, 2016 1:10 PM

Subject: Re: [nvda] very good news about audio conversion soft ware

 

Did it just do a clean install, or did it keep asking you to install this, that and the other thing? If not, then this is good news and I'll try this newest one.

Roger








On 5/3/2016 1:24 PM, Bobby wrote:

no our hopes are not dashed at all because I just got the new version.  The new version is cdex version 1.81.  I never got a message about malware.  I have the program and it works very well and faster than the older versions.

 

On 5/3/2016 2:06 PM, erik burggraaf wrote:

Uh oh.  That's the official site.  For sure.  When I went to the old site http://cdexos.sourceforge.net it redirected me to that cdex.nu site which looks exactly like the old cdex source forge site.  Maybe our hopes are dashed and the entire project has been highjacked?  It's been at least 10 years since the last upgrade as far as I know.

 

Best,

 

Erik Burggraaf

 

On May 3, 2016, at 10:54 AM, Dan Beaver <dbeaver888@...> wrote:

 

Hi,

 

You might want to be careful about getting software from this site.  I too have used cdex for many years and wanted to ghet the new version.  However, when I clicked on the link Sophos stopped my browser and said that some mal ware had been found on that site.

 

I am now pondering whether or not I want to get it from there.

 

Dan Beaver

 

On 5/3/2016 12:32 PM, erik burggraaf wrote:

This is fantastic news!  I've used cdex for over 15 years and I never thought we'd see another update.

 

New website address as well:

 

Do not use filehipo or some other third party source like that or you will risk your computer getting extras you didn't ask for.

 

Best,

 

Erik Burggraaf

 

On May 3, 2016, at 9:17 AM, Bobby <bvinton@...> wrote:

 

I just wanted to tell you all about an old converter and cd reader called c dex.  Cdex is the fastest audio converter and they just came out with a new version today.  You can get this progran at filehippo.com.  Let me know what you think of it when you get it.



 

 

 

 

 


Re: Those using Outlook expres with multiple identities

 

where do you get outlook express for win10?
I don't need this but if ever thunderbird dies I may use that instead.

On 3/05/2016 11:59 p.m., Brian's Mail list account wrote:
Now that we have a version of Outlook Express that works on windows 7 to
10, I thought it might be a good idea to repeat this little batch file
here.
As many have found when switching identities a lot O-E can get confused
if nvda is running and refuse to display messages or indeed allow entry
of messages. The reasons for this are unclear but have been going on
even in windows xp at times even when the preview pane is disabled.
My quick and dirty fix is not really a fix but reboots Outlook express
into the same identity that has stopped working properly. You put this
batch file in the working directory of Outlook Express. the one with the
exe file in it, and call the batch file from a desktop shortcut instead
of its normal entry shortcut.
Here is the batch file.

@echo off

taskkill /f /im msimn.exe
ping -n 5 127.0.0.1>nul

start MSIMN.EXE
exit



This then reboots or runs Outlook Express either in its default identity
if its the first time you ran it, or in the current one if its stopped
working correctly as above.
For the curious, it forcibly terminates Outlook Express and everything
else it has running, then waits for the dust to settle, and reboots it
in the same identity.

Hope it helps.
I'm sure this is due to an interaction with nvda, but nobody seems to
have found the culprit in some years now, so at least this is a work
around.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.


.


Re: NVDA still freezing, don't know what the deal is

 

Thats true brian.
update week is next week, and I hope the patches I made to the main box hold up otherwise if my office breaks again and my fixits don't work its a reformat, I don't know if they will break but lets see if they do.

On 3/05/2016 8:29 p.m., Brian's Mail list account wrote:
No, to me unless there has been some significant malware or crash from a
bit of software, then the registry can be repaired automatically by
windows.

Beware however, as next week is update week.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@...>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 11:25 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


Hey, before you have to format the computer. Why not run chkdsk and
then go
into the bios and see what can be the problem. I'd use format as the last
resort. Or if you just want to do it and get it over with. then go
ahead and
do one. Good luck!

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@...]
Sent: May-02-16 9:17 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

It just happened AGAIN. This time, with no Braille Display plugged in,
but still in Word. My sister described what she saw as "It's circling
and the screen is foggy," so I'm assuming it was hanging. It took longer
than normal to shut down, and longer than normal to start up properly,
and apparently Windows Explorer lagged for a few seconds. I don't know
how to recover my writing (I tried one of the previous times this
happened by restoring the auto recovery file from the Recycle bin but it
didn't work...).


Anyways, here's the log. I hope this time I can get an answer for why
this is happening. I'm getting seriously concerned at this point.


INFO - __main__ (00:26:15):
Starting NVDA
INFO - core.main (00:26:19):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (00:26:20):
NVDA version brltbl20160315
INFO - core.main (00:26:20):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (00:26:20):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (00:26:20):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (00:26:24):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (00:26:24):
Loaded synthDriver ptenglish
INFO - core.main (00:26:24):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (00:26:24):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (00:26:24):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (00:26:24):
Braille input initialized
INFO - core.main (00:26:25):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (00:27:25):
Loaded braille display driver freedomScientific, current display has 40
cells.
ERROR - queueHandler.flushQueue (00:33:30):
Error in func _handleUpdate from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 50, in flushQueue
File "virtualBuffers\__init__.pyc", line 674, in _handleUpdate
File "braille.pyc", line 1645, in handleUpdate
File "braille.pyc", line 906, in update
File "textInfos\offsets.pyc", line 346, in expand
File "virtualBuffers\__init__.pyc", line 314, in _getUnitOffsets
File "textInfos\offsets.pyc", line 328, in _getUnitOffsets
File "virtualBuffers\__init__.pyc", line 256, in _getParagraphOffsets
WindowsError: [Error 1775] A null context handle was passed from the
client to the host during a remote procedure call


On 3/05/2016 12:15 AM, Sharni-Lee Ward wrote:
Just tried another thing that consistently got NVDA to hang recently,
namely, opening the sounds manager in Control Panel and then arrowing to
the Sound Scheme tab. I thought it only did this because of the Braille
Display but I wanted to test it to make sure. This time, once the window
was closed, NVDA started responding again. I also tried to activate
Narrator but it didn't work, though as I said, that didn't end up
mattering. Here's the log for that session, though I warn you, the
warning repeats itself several times. In case each warning was subtly
different, I copied the whole thing. Don't worry about the Braille error
that shows up first-that's about me starting up the computer and by
extension NVDA without my display plugged in and then saving the
configuration with default as No Braille.


INFO - __main__ (18:51:56):
Starting NVDA
INFO - core.main (18:51:59):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (18:52:00):
NVDA version 2016.1
INFO - core.main (18:52:00):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (18:52:00):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:52:00):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (18:52:10):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (18:52:11):
Loaded synthDriver ptenglish
INFO - core.main (18:52:11):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (18:52:11):
Using liblouis version 2.6.5
ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
Error initializing display driver
Traceback (most recent call last):
File "braille.pyo", line 1447, in setDisplayByName
File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in
__init__
RuntimeError: No display found
INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:52:11):
Braille input initialized
INFO - core.main (18:52:12):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager.save (19:30:39):
Base configuration saved
WARNING - watchdog._watcher (23:47:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:47:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__

init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e

speak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

INFO - core.onEndSession (23:54:04):
Windows session ending


On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:
If the master snapshots fixed it, does this mean the next release
(which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to
sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try Gene's
method, although I suspect it will be fine. Thank you everyone for all
your help and tips, and at least I know how to retrieve old log
messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:
I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@...>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


Hi there: Do you think your computer could have mellwhere to cause
this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@...]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@...> wrote:
Why wouldn't my workaround accomplish the same end but more easily.
Because most of the keyboard is frozen when this freeze happens. The
only
thing that works is the windows key and some function keys.













.


Re: very good news about audio conversion soft ware

 

Thats a point actually.
itunes does use gracenote if you have an i device.
You will have to convert the music to mp3, it does not do ogg or flack sadly.
However all tracks are numbered.
if you get winlame which is for now malware free at least the 2010 version is
Sadly I do think this is a dead project but it should do ogg to 500kbps mp3 to 320kbps wav, I am not sure about flack but anyway.
The other thing you can do is buy goldwave or get audacity which is free but not full with malware just yet.
Its ogg encoder has been known to have issues but who knows if its still like that now.

On 4/05/2016 9:14 a.m., Christopher-Mark Gilland wrote:
Goodness gracious, yall! Why not just use ITunes to rip for crying out
loud! Is it mainly because ITunes doesn't support the formats you all
wanna rip into? If so, then OK, point taken, but otherwise... really?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

@AHeart4God316
Phone: (704) 256-8010.



Re: very good news about audio conversion soft ware

 

Well they all get adds now days.
dvdvideosoft had lots of em.
A lot of these projects on sourceforge are full of malware.
I don't think sourceforge projects travel well.
audacity and 7zip are ok for the moment though.
But others have gone off the map, unless you get some big sponsors and with the echonomy situation as it has been opensource does not pay the bills.
Right now the only way to handle this is donate cash or time to whatever projects you have.
the reason audacity and 7zip are probably ok for now is because they are getting donations and maybe have large communities maybe sponsors with big pockets.
Its why we must take care of the projects we love.
Before the malware thing came in and this was a few years ago projects either stopped or just went silent.
look at draggonunpacker 5 or winlame, both are not updated in ages.
look at izarc, its full of malware now to.
Then look at things like powerarchiver, it was free now it isn't.
Point is opensource is really great, its not a lifetime fund making venture which is what I think a lot have realised and may still are realising.
Truth is that free doesn't pay the bills, adds do, malware does, spam does, scams do, actually selling it does, anything else bar free.
A good way to describe this is the free net revolution in new zealand or the rest of the world.
I know for a fact we had free net for a couple years, done off the back of big communications companies.
I know for a fact that even with advertising, quality was poor, and eventually it was not worth keeping it free, so it died.
If your project is full of malware, chances are its not getting the funds it needs.
Chances are that it may allready be dead.
Ofcause contact those that make the projects and ask them what would be needed to remove their adds, chances are you will find out that their funding is really low.
While I don't do opensource projects I do actually do university research projects and other projects for a local game company in nz.
Funding for things is a really big problem, next to getting those to do the work, projects to work on, and people to test.
Funds make it to just about every meeting with my bosses.
Its hard all round.
The net as a lot of people have realised will not make you rich, not immediately anyway and if you don't attack it the right way it won't.
Ok you can join the malware stream but while you will survive its not the way I would choose to live.
I have had people who I have listened to video casts for years suddenly have adds on their videos and sites, then they get videos and promos saying they really need cash to continue to survive.
I usually don't give it for those that put malware up since I won't use anyone that will put viruses on pcs, I do think opensourcers and those that give free software because they want to, because the net is turning away from free anything these days.

On 4/05/2016 6:06 a.m., erik burggraaf wrote:
Uh oh. That's the official site. For sure. When I went to the old site http://cdexos.sourceforge.net it redirected me to that cdex.nu site which looks exactly like the old cdex source forge site. Maybe our hopes are dashed and the entire project has been highjacked? It's been at least 10 years since the last upgrade as far as I know.

Best,

Erik Burggraaf


On May 3, 2016, at 10:54 AM, Dan Beaver <dbeaver888@...> wrote:

Hi,


You might want to be careful about getting software from this site. I too have used cdex for many years and wanted to ghet the new version. However, when I clicked on the link Sophos stopped my browser and said that some mal ware had been found on that site.


I am now pondering whether or not I want to get it from there.


Dan Beaver

On 5/3/2016 12:32 PM, erik burggraaf wrote:
This is fantastic news! I've used cdex for over 15 years and I never thought we'd see another update.

New website address as well:
http://cdex.mu/download <http://cdex.mu/download>

Do not use filehipo or some other third party source like that or you will risk your computer getting extras you didn't ask for.

Best,

Erik Burggraaf


On May 3, 2016, at 9:17 AM, Bobby < <mailto:bvinton@...>bvinton@... <mailto:bvinton@...>> wrote:

I just wanted to tell you all about an old converter and cd reader called c dex. Cdex is the fastest audio converter and they just came out with a new version today. You can get this progran at filehippo.com <http://filehippo.com/>. Let me know what you think of it when you get it.




Re: very good news about audio conversion soft ware

 

Jean cdex has for a while included adds, sadly a lot of sourceforge projects are full of them.
Obviously donations are not enough.
Its why I quit the dvdvideosoft stuff because of this.
Sadly the applian stuff I heard about and brought is not accessable at least I have never been able to edit the interface for the video capcha or other converters or anything at all and it cost me a lot.
It is obvious though that unless you have youtube dl-g or pontes media which while ok can not do playlists you are prity much in the poopoo.
To much free software has opencandy related stuff with it and while you could disable it I'd have to potentially have a batch file for every install.
At the end of the day none of the free software I use is that important for me to have adds on my system and these things can screw up the system, install malware and even if they work the software in question for me has no value.
That isn't saying I don't mind software bundles especially if you can buy packaged software but a lot of programs are loaded with random stuff including uniblue stuff which is reguarded as bad so I decided ages ago to buy software.
goldwave has a good enough cd reader.
cdburner xp does my cds though I must say I did donate to it.
7zip does my zip files.
The only free apps I have that for now are not full of software are the old winlame and audacity.
Which I hardly use either.
Thing is if any app above had a buy link so I don't get adds I would, some of them I did use a lot but oh well its life I guess someone needs to make cash somehow I just wish that malware was not the way.
Sadly I do know some sourceforge projects have died so opensource is not everyone's cup of tea either.
Nothing is for free I just don't want to get dammaged in the process of free.
Even java and codecguide have adds now but at least you can turn them off.
I have unchecky installed in all my computers now though.

On 4/05/2016 7:40 a.m., Gene wrote:
It may simply be one more case of a free program now incorporating potentially unwanted programs in it, which is becoming increasingly frequent. Whatever the case, is there any reason to use the new program? those who have used it might be able to advise if anything has been added that matters.

Gene
----- Original Message -----

From: erik burggraaf
Sent: Tuesday, May 03, 2016 1:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] very good news about audio conversion soft ware


Uh oh. That's the official site. For sure. When I went to the old site http://cdexos.sourceforge.net it redirected me to that cdex.nu site which looks exactly like the old cdex source forge site. Maybe our hopes are dashed and the entire project has been highjacked? It's been at least 10 years since the last upgrade as far as I know.


Best,


Erik Burggraaf




On May 3, 2016, at 10:54 AM, Dan Beaver <dbeaver888@...> wrote:


Hi,




You might want to be careful about getting software from this site. I too have used cdex for many years and wanted to ghet the new version. However, when I clicked on the link Sophos stopped my browser and said that some mal ware had been found on that site.




I am now pondering whether or not I want to get it from there.




Dan Beaver




On 5/3/2016 12:32 PM, erik burggraaf wrote:

This is fantastic news! I've used cdex for over 15 years and I never thought we'd see another update.


New website address as well:
http://cdex.mu/download


Do not use filehipo or some other third party source like that or you will risk your computer getting extras you didn't ask for.


Best,


Erik Burggraaf




On May 3, 2016, at 9:17 AM, Bobby <bvinton@...> wrote:


I just wanted to tell you all about an old converter and cd reader called c dex. Cdex is the fastest audio converter and they just came out with a new version today. You can get this progran at filehippo.com. Let me know what you think of it when you get it.












Re: NVDA still freezing, don't know what the deal is

Gene
 

Also, I wonder if you can remove the Braille tables that are provided and put in tables from an older version of NVDA.  I don't know anything about this but again, this might be a topic of value that someone else might discuss here or that you might be able to discuss with developers.
 
Gene

From: Gene
Sent: Tuesday, May 03, 2016 4:11 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Maybe it's good that you tried a snapshot.  You may have comments that would be of value to developers.  I believe there is a developers list or perhaps a way to leave comments for developers on the web site but someone else will have to comment on that further.
 
Gene
----- original Message -----
Sent: Tuesday, May 03, 2016 3:38 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

...What HAPPENED to the espeak voice? It sounds choppy and distorted (at least Linda does) and it was honestly hurting my ears.


And the Master snapshot doesn't have the braille table I'd prefer to use, which is why I got that other snapshot when I did. The newer more experimental table fixed the problem of emdashes being replaced by eight cells of nonsense that took up more space than necessary, and formatting representations, and missed contractions...


I can't use this.

On 4/05/2016 5:47 AM, Gene wrote:
I believe the new production version will be released in about a month.  However, I would expect the master snapshot to be probably stable or reasonably stable.  You can use a portable version if you want to evaluate it without installing it.  I haven't used new snapshots fir a while but my experience in the past has been that the snapshots I've used have been stable.  That doesn't mean that they all are.  They are versions still in development and not beta tested.
 
The page to see and download the latest snapshots is
 
Gene
----- Original Message -----

Sent: Tuesday, May 03, 2016 1:10 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi,


The reason the driver was still trying to do something was that I had
used the old snapshot I had in conjunction with my display to read for a
bit, then had disconnected the display without resetting the "display"
setting in Braille Settings to "No Braille". As I said, it lasted
longer, but still locked up at the most inconvenient time...


Can I have a link to this master snapshot? And is this building toward
the next release or are some things not ready for that yet? If the
former, when is the next release? Is it some time this month, or next?


On 3/05/2016 6:29 PM, Brian's Mail list account wrote:
> No, to me unless there has been some significant malware or crash from
> a bit of software, then the registry can be repaired automatically by
> windows.
>
> Beware however, as next week is update week.
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal email to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Arlene" <nedster66@...>
> To: <nvda@nvda.groups.io>
> Sent: Monday, May 02, 2016 11:25 PM
> Subject: Re: [nvda] NVDA still freezing, don't know what the deal is
>
>
>> Hey, before you have to format the computer. Why not run chkdsk and
>> then go
>> into the bios and see what can be the problem. I'd use format as the
>> last
>> resort. Or if you just want to do it and get it over with. then go
>> ahead and
>> do one. Good luck!
>>
>> -----Original Message-----
>> From: Sharni-Lee Ward [mailto:sharni-lee.ward@...]
>> Sent: May-02-16 9:17 AM
>> To: nvda@nvda.groups.io
>> Subject: Re: [nvda] NVDA still freezing, don't know what the deal is
>>
>> It just happened AGAIN. This time, with no Braille Display plugged in,
>> but still in Word. My sister described what she saw as "It's circling
>> and the screen is foggy," so I'm assuming it was hanging. It took longer
>> than normal to shut down, and longer than normal to start up properly,
>> and apparently Windows Explorer lagged for a few seconds. I don't know
>> how to recover my writing (I tried one of the previous times this
>> happened by restoring the auto recovery file from the Recycle bin but it
>> didn't work...).
>>
>>
>> Anyways, here's the log. I hope this time I can get an answer for why
>> this is happening. I'm getting seriously concerned at this point.
>>
>>
>> INFO - __main__ (00:26:15):
>> Starting NVDA
>> INFO - core.main (00:26:19):
>> Config dir: C:\Users\pc\AppData\Roaming\nvda
>> INFO - core.main (00:26:20):
>> NVDA version brltbl20160315
>> INFO - core.main (00:26:20):
>> Using Windows version 6.1.7601 service pack 1 workstation
>> INFO - core.main (00:26:20):
>> Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015,
>> 20:32:19) [MSC v.1500 32 bit (Intel)]
>> INFO - core.main (00:26:20):
>> Using comtypes version 0.6.2
>> INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (00:26:24):
>> Using eSpeak version 1.48.03  04.Mar.14
>> INFO - synthDriverHandler.setSynth (00:26:24):
>> Loaded synthDriver ptenglish
>> INFO - core.main (00:26:24):
>> Using wx version 3.0.2.0 msw (classic)
>> INFO - braille.initialize (00:26:24):
>> Using liblouis version 2.6.5
>> INFO - braille.BrailleHandler.setDisplayByName (00:26:24):
>> Loaded braille display driver noBraille, current display has 0 cells.
>> INFO - brailleInput.initialize (00:26:24):
>> Braille input initialized
>> INFO - core.main (00:26:25):
>> NVDA initialized
>> INFO - braille.BrailleHandler.setDisplayByName (00:27:25):
>> Loaded braille display driver freedomScientific, current display has 40
>> cells.
>> ERROR - queueHandler.flushQueue (00:33:30):
>> Error in func _handleUpdate from eventQueue
>> Traceback (most recent call last):
>>   File "queueHandler.pyc", line 50, in flushQueue
>>   File "virtualBuffers\__init__.pyc", line 674, in _handleUpdate
>>   File "braille.pyc", line 1645, in handleUpdate
>>   File "braille.pyc", line 906, in update
>>   File "textInfos\offsets.pyc", line 346, in expand
>>   File "virtualBuffers\__init__.pyc", line 314, in _getUnitOffsets
>>   File "textInfos\offsets.pyc", line 328, in _getUnitOffsets
>>   File "virtualBuffers\__init__.pyc", line 256, in _getParagraphOffsets
>> WindowsError: [Error 1775] A null context handle was passed from the
>> client to the host during a remote procedure call
>>
>>
>> On 3/05/2016 12:15 AM, Sharni-Lee Ward wrote:
>>> Just tried another thing that consistently got NVDA to hang recently,
>>> namely, opening the sounds manager in Control Panel and then
>>> arrowing to
>>> the Sound Scheme tab. I thought it only did this because of the Braille
>>> Display but I wanted to test it to make sure. This time, once the
>>> window
>>> was closed, NVDA started responding again. I also tried to activate
>>> Narrator but it didn't work, though as I said, that didn't end up
>>> mattering. Here's the log for that session, though I warn you, the
>>> warning repeats itself several times. In case each warning was subtly
>>> different, I copied the whole thing. Don't worry about the Braille
>>> error
>>> that shows up first-that's about me starting up the computer and by
>>> extension NVDA without my display plugged in and then saving the
>>> configuration with default as No Braille.
>>>
>>>
>>> INFO - __main__ (18:51:56):
>>> Starting NVDA
>>> INFO - core.main (18:51:59):
>>> Config dir: C:\Users\pc\AppData\Roaming\nvda
>>> INFO - core.main (18:52:00):
>>> NVDA version 2016.1
>>> INFO - core.main (18:52:00):
>>> Using Windows version 6.1.7601 service pack 1 workstation
>>> INFO - core.main (18:52:00):
>>> Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015,
>>> 20:32:19) [MSC v.1500 32 bit (Intel)]
>>> INFO - core.main (18:52:00):
>>> Using comtypes version 0.6.2
>>> INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (18:52:10):
>>> Using eSpeak version 1.48.03  04.Mar.14
>>> INFO - synthDriverHandler.setSynth (18:52:11):
>>> Loaded synthDriver ptenglish
>>> INFO - core.main (18:52:11):
>>> Using wx version 3.0.2.0 msw (classic)
>>> INFO - braille.initialize (18:52:11):
>>> Using liblouis version 2.6.5
>>> ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
>>> Error initializing display driver
>>> Traceback (most recent call last):
>>>     File "braille.pyo", line 1447, in setDisplayByName
>>>     File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in
>> __init__
>>> RuntimeError: No display found
>>> INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
>>> Loaded braille display driver noBraille, current display has 0 cells.
>>> INFO - brailleInput.initialize (18:52:11):
>>> Braille input initialized
>>> INFO - core.main (18:52:12):
>>> NVDA initialized
>>> INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
>>> Loaded braille display driver noBraille, current display has 0 cells.
>>> INFO - config.ConfigManager.save (19:30:39):
>>> Base configuration saved
>>> WARNING - watchdog._watcher (23:47:35):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> WARNING - watchdog._watcher (23:47:50):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> WARNING - watchdog._watcher (23:48:05):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> WARNING - watchdog._watcher (23:48:20):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> WARNING - watchdog._watcher (23:48:35):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> WARNING - watchdog._watcher (23:48:50):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> WARNING - watchdog._watcher (23:49:05):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> WARNING - watchdog._watcher (23:49:20):
>>> Core frozen in stack:
>>>     File "nvda.pyw", line 190, in <module>
>>>     File "core.pyo", line 382, in main
>>>     File "wx\_core.pyo", line 8657, in MainLoop
>>>     File "wx\_core.pyo", line 7952, in MainLoop
>>>     File "core.pyo", line 353, in Notify
>>>     File "queueHandler.pyo", line 83, in pumpAll
>>>     File "queueHandler.pyo", line 50, in flushQueue
>>>     File "eventHandler.pyo", line 61, in _queueEventCallback
>>>     File "eventHandler.pyo", line 138, in executeEvent
>>>     File "eventHandler.pyo", line 162, in doPreGainFocus
>>>     File "eventHandler.pyo", line 143, in executeEvent
>>>     File "eventHandler.pyo", line 91, in __init__
>>>     File "eventHandler.pyo", line 98, in next
>>>     File "NVDAObjects\__init__.pyo", line 868, in event_foreground
>>>     File "speech.pyo", line 107, in cancelSpeech
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__
>>
>> init__.py",
>>> line 117, in cancel
>>>     File
>>>
>> "C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_e
>>
>> speak.py",
>>> line 224, in stop
>>>     File "nvwave.pyo", line 244, in stop
>>>     File "threading.pyo", line 174, in acquire
>>>
>>> INFO - core.onEndSession (23:54:04):
>>> Windows session ending
>>>
>>>
>>> On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:
>>>> If the master snapshots fixed it, does this mean the next release
>>>> (which
>>>> is hopefully coming sometime this month or next) will have the fix?
>>>> Because if so, I can just change the configuration so I have to
>>>> connect
>>>> it manually when I want to use it, which isn't a problem as I usually
>>>> have to re-activate the Braille settings if I have to disconnect the
>>>> display for one reason or another, or if the computer's put to
>>>> sleep. If
>>>> the fix is implemented next release, I'll adjust the configuration
>>>> again. If it does happen again despite this measure, I will try Gene's
>>>> method, although I suspect it will be fine. Thank you everyone for all
>>>> your help and tips, and at least I know how to retrieve old log
>>>> messages
>>>> now! :D
>>>>
>>>>
>>>> On 2/05/2016 7:02 PM, Brian's Mail list account wrote:
>>>>> I don't think its malware, reading the thread it sounds like the
>>>>> braill table part of nvda and the master snapshots are supposed to
>>>>> have now fixed it. Its been a while since I had a computer with
>>>>> one of
>>>>> those displays. fartoo expensive for the low usage I have.
>>>>> Brian
>>>>>
>>>>> bglists@...
>>>>> Sent via blueyonder.
>>>>> Please address personal email to:-
>>>>> briang1@..., putting 'Brian Gaff'
>>>>> in the display name field.
>>>>> ----- Original Message ----- From: "Arlene" <nedster66@...>
>>>>> To: <nvda@nvda.groups.io>
>>>>> Sent: Monday, May 02, 2016 4:15 AM
>>>>> Subject: Re: [nvda] NVDA still freezing, don't know what the deal is
>>>>>
>>>>>
>>>>>> Hi there: Do you think your computer could have mellwhere to
>>>>>> cause this
>>>>>> freezing?
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Rob [mailto:captinlogic@...]
>>>>>> Sent: May-01-16 6:31 PM
>>>>>> To: nvda@nvda.groups.io
>>>>>> Subject: Re: [nvda] NVDA still freezing, don't know what the deal is
>>>>>>
>>>>>> Gene <gsasner@...> wrote:
>>>>>>> Why wouldn't my workaround accomplish the same end but more easily.
>>>>>> Because most of the keyboard is frozen when this freeze happens. The
>>>>>> only
>>>>>> thing that works is the windows key and some function keys.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>






Re: very good news about audio conversion soft ware

Christopher-Mark Gilland <clgilland07@...>
 

Goodness gracious, yall! Why not just use ITunes to rip for crying out loud! Is it mainly because ITunes doesn't support the formats you all wanna rip into? If so, then OK, point taken, but otherwise... really?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

@AHeart4God316
Phone: (704) 256-8010.