Since I only have my experience and the report of one other user and since the reports have been pretty much negative on the page you cite, this may not be a common or very common problem. However, to answer one question raised by a respondent to the forum, I was referring to continuous recording. I haven't tried pausing and resuming the recording before the problem began. It's been a number of months since I've used this version of Audacity for recording so I don't recall all the details. I do know that there would be problems such as the program freezing or perhaps not closing properly. the file I was recording wouldn't be able to be saved. When I would attempt to recover it, I would be informed that there was junk in this or that part of the file and the recovery would be terminated. Not every detail of my description of the behavior of the program may be correct after all this time but the main points are correct. Since I have no idea if this is a common problem, it may not be easy to test. Perhaps list members could do some testing by just letting audacity record for an hour or two repeatedly with a new file each time to see what happens.
Maybe this is a rare or pretty rare problem. Gene----- Original Message ----- From: "Leland" <audacity4blind@xxxxxxxxxxx>
To: <audacity4blind@xxxxxxxxxxxxx> Sent: Tuesday, June 10, 2008 8:09 AM Subject: [audacity4blind] Re: Since I've decloaked...
--On June 10, 2008 1:13:53 AM -0600 Gene <gsasner@xxxxxxxxx> wrote:I hear that. I just recently tried Satogo and found that it and Audacity didn't cooperate very well. But, I also found that NVDA read some things better than Jaws or Window Eyes. And I don't know where Hal95 was getting its information from, but it wasn't Audacity. ;-)It depends on how you define accessible. JAWS and Window-eyes can read many items in dialogs that System Access can't. I don't know how much work would be involved in changing this nor whether the changes would require other changes to make the interface look the same to sighted users. However, you may want to be aware of the fact that some controls in dialogs aren't accessible to less sophisticated screen-readers for reasons I don't have the technical knowledge to discuss.The way Audacity provides information to screen readers is via Active Accessibility. If the product supports that interface, then it "should" function well. I say "should" because it seems that everybody has a different way of interpreting the Active Accessibility documentation and this is causing me some headaches. Heck, even different versions of Jaws utilize the interface differently.I'll be curious what responses you get regarding the apparent recording bug.Here's a couple of responses. Nothing from the main devlers yet: http://www.nabble.com/Any-reports-of-recording-issues--td17747720.htmlLooks like I may have to dig into this one myself. (Again with the path straying. ;-))Leland The audacity4blind website is at http://users.northlc.com/sberry/ Subscribe and unsubscribe information, message archives, Audacity keyboard commands, and more... To unsubscribe from audacity4blind, send an email to audacity4blind-request@xxxxxxxxxxxxx with subject line unsubscribe
The audacity4blind website is at http://users.northlc.com/sberry/ Subscribe and unsubscribe information, message archives, Audacity keyboard commands, and more... To unsubscribe from audacity4blind, send an email to audacity4blind-request@xxxxxxxxxxxxx with subject line unsubscribe
