[audacity4blind] Re: getting and Error.

  • From: "jim gamage" <james.gamage@xxxxxxxxxxxxxx>
  • To: <audacity4blind@xxxxxxxxxxxxx>
  • Date: Sat, 14 Sep 2013 23:33:00 +0100

Hello Gale,
No problem with the 2.0.3 version.
O K, some more findings using the various hosts. 
Whether Mme is set for my Soundblaster or Microsoft sound mapper input
pressing enter stops the problem
Windows direct sound if this is set for primary sound capture driver or my
soundblaster it solves the problem when O K is pressed in either case.
Windows wa sapi if this is set for digital audio interface sbx fi stream
audio loop back it does not solve the problem, if it's set for speakers fi
stream audio loop back it does not solve the problem when O K is pressed in
either case.
Windows wdnks if set for microphone, line in or auxiliary the problem is
solved on pressing O K, but not the bottom option
In all cases I am talking of the input device, I haven't tried altering the
output yet.
The common factor still seems to be that whenever my Soundblaster is
involved, the problem appears, the Realtek card has no problems, I don't
want to update the Soundblaster driver yet, it works for everything else
and, of course, it will cloud the issue, one thing at a time as they say. 
By the way, the tone has now gone, to be replaced with the noise, so the
problem seems to be intermittent in this respect, the hardest thing to
solve.


Best Regards, Jim. 

-----Original Message-----
From: audacity4blind-bounce@xxxxxxxxxxxxx
[mailto:audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of Gale Andrews
Sent: 14 September 2013 18:46
To: audacity4blind@xxxxxxxxxxxxx
Subject: [audacity4blind] Re: getting and Error.


| From "jim gamage" <james.gamage@xxxxxxxxxxxxxx> Sat, 14 Sep 2013 
| 17:47:05 +0100
| Subject: getting and Error.
> That's exactly right, the setting will not hold for subsequent 
> loadings of Audacity, I have to go into devices each time, after that 
> all is well, it's not much trouble now that I know how to sort it out 
> and the program is perfectly workable in all other respects once this
setting has been made.

OK, and this did not happen with 2.0.3? 

And if in 2.0.4 you choose any of the other hosts (Windows DirectSound,
Windows WASAPI or Windows WDM-KS), am I correct that you cannot stop the
tone sound and low volume occurring? 

Or is that problem only with WASAPI and WDM-KS and not with DirectSound? 


Thanks


Gale 


> -----Original Message-----
> From: audacity4blind-bounce@xxxxxxxxxxxxx
> [mailto:audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of Gale Andrews
> Sent: 14 September 2013 14:21
> To: audacity4blind@xxxxxxxxxxxxx
> Subject: [audacity4blind] Re: getting and Error.
> 
> 
> | From "jim gamage" <james.gamage@xxxxxxxxxxxxxx> Sat, 14 Sep 2013 
> | 08:11:25 +0100
> | Subject: getting and Error.
> > Thank you again for all your information, the only thing I would make 
> > clear at this time is that, even if I set MME as host and close and re 
> > open Audacity, the low volume and tone are still present. I will leave 
> > well alone for the moment but study your suggestions carefully .
> > As nobody else seems to have this problem, I must assume it's my 
> > Soundblaster card at fault.
> 
> Hi Jim,
> 
> I understood that choosing MME fixed it, from what you wrote.
> 
> Do you mean that having reopened Audacity, you have to reselect MME to fix
> the low volume and remove the tone? 
> 
> 
> 
> Gale 
> 
> > -----Original Message-----
> > From: audacity4blind-bounce@xxxxxxxxxxxxx
> > [mailto:audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of Gale Andrews
> > Sent: 13 September 2013 17:37
> > To: audacity4blind@xxxxxxxxxxxxx
> > Subject: [audacity4blind] Re: getting and Error.
> > 
> > 
> > | From "jim gamage" <james.gamage@xxxxxxxxxxxxxx> Fri, 13 Sep 2013
> > | 16:58:56 +0100
> > | Subject: getting and Error.
> > > I have now done some more experimenting and am now convinced that it 
> > > is my Soundblaster card that the new Audacity doesn't like. Plugging 
> > > in and configuring the realtek card has no problem, I can use the 
> > > new version of Audacity without altering any settings in devices by 
> > > using the
> > realtek card.
> > > I can still use my Soundblaster by going into Devices and pressing OK.
> > > If I load Audacity with my Soundblaster as the default device, I get 
> > > a reduced volume and a fairly quiet tone in the background, I would 
> > > describe the latter as a sine wave at about middle C, [I am not a 
> > > musician, so forgive me if this is not quite correct.
> > > If I load Audacity and then set the loop option, press OK on this, 
> > > the audio doesn't change, in other words it's still low and with the 
> > > tone in the background, closing Audacity and re loading it leaves 
> > > the tone etc, but going back to MME sorts it.
> > > If I load Audacity and stop the problem by just using MME and 
> > > pressing OK, the audio increases in volume and the tone disappears, 
> > > if I then set the loop option the  audio remains normal.
> > > I hope someone more technical than me can make some sense of that, 
> > > but it seems that my Soundblaster is the culprit.
> > 
> > Jim,
> > 
> > 2.0.4 has support for new "hosts" called "Windows WDM-KS"
> > and "Windows WASAPI".  
> > 
> > Hosts are different software interfaces for your sound devices.
> > 
> > "KS" is short for Kernel Streaming. You can record with very little 
> > latency using this host if you reduce "Audio to buffer" in the 
> > Audacity Recording Preferences (as long as you don't reduce the buffer 
> > too low). 20 ms buffer should work fine.
> > 
> > When you start Audacity or press OK in Preferences, Audacity interacts 
> > with all the devices it recognises and with all the audio hosts (MME, 
> > Windows DirectSound, Windows WDM-KS and Windows WASAPI). So you may 
> > hear a click in the speakers at that point.
> > 
> > If you did not hear that click in 2.0.3, then and it may be that 
> > WDM-KS or WASAPI are the cause.
> > 
> > Both new hosts are somewhat experimental. If selecting MME solves the 
> > SoundBlaster tone and volume-changing problems, I suggest exiting 
> > Audacity with MME selected, then MME will be selected for you next 
> > time you start Audacity.
> > 
> > The alternatives would be to update your SoundBlaster to the driver I 
> > indicated (assuming it does not already have that driver), or just 
> > wait to see if PortAudio changes in future
> > Audacity versions improve the situation.     
> >  
> > If you are happy using MME then probably you can just leave things as 
> > they are.
> > 
> > 
> > 
> > Gale
> > 
> > > -----Original Message-----
> > > From: audacity4blind-bounce@xxxxxxxxxxxxx
> > > [mailto:audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of Gale 
> > > Andrews
> > > Sent: 11 September 2013 16:31
> > > To: audacity4blind@xxxxxxxxxxxxx
> > > Subject: [audacity4blind] Re: getting and Error.
> > > 
> > > 
> > > | From "jim gamage" <james.gamage@xxxxxxxxxxxxxx> Wed, 11 Sep 2013 
> > > | 08:08:10 +0100
> > > | Subject: getting and Error.
> > > > My soundcard is,
> > > > 
> > > > Creative Soundblaster X-Fi xtreme.
> > > > it is a bit old now but not ancient.  
> > > 
> > > Jim,
> > > 
> > > I found you were on Windows 7 64-bit in one of your other posts.
> > > 
> > > The latest driver for X-Fi Xtreme is here: 
> > > http://tinyurl.com/pxyvvam
> > > 
> > > (in the "Latest Downloads" section near the bottom of the page). 
> > > 
> > > You may want to check if you have that driver. But also if nothing 
> > > is
> > badly
> > > broken, it is often best not to fix it.  
> > > 
> > > 
> > > 
> > > 
> > > Gale
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: audacity4blind-bounce@xxxxxxxxxxxxx
> > > > [mailto:audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of Gale 
> > > > Andrews
> > > > Sent: 10 September 2013 17:10
> > > > To: audacity4blind@xxxxxxxxxxxxx
> > > > Subject: [audacity4blind] Re: getting and Error.
> > > > 
> > > > 
> > > > | From "jim gamage" <james.gamage@xxxxxxxxxxxxxx> Tue, 10 Sep 2013
> > > > | 16:45:32 +0100
> > > > | Subject: getting and Error.
> > > > > Hello Gale,
> > > > > I am the one who got the error with MME, after going into 
> > > > > devices and OK several times, the noise has disappeared,I don't 
> > > > > know why,  but I still have a peculiarity, the level of sound 
> > > > > increases slightly if I go into devices and O K after loading 
> > > > > Audacity
> > > > 
> > > > The output level should not increase of course, unless you changed 
> > > > the output device in Preferences.
> > > > 
> > > > 
> > > > > the program is now usable, but it gets more curious all the time.
> > > > 
> > > > I hope that some quirks will be resolved for 2.0.5 if we update to 
> > > > the latest version of PortAudio.
> > > > 
> > > > 
> > > > > I don't think my soundcard driver is broken, it works on all 
> > > > > other applications now and I do have two soundcards, a Realtek 
> > > > > and a
> > > > Soundblaster,
> > > > > both work alright. 
> > > > 
> > > > Many SoundBlaster cards are now very old and no longer supported 
> > > > by Creative.  Do you know exactly what make and model number your 
> > > > SoundBlaster is?
> > > > 
> > > > Audacity must keep updating PortAudio (as above) so that we 
> > > > support the latest devices. Occasionally this may create problems 
> > > > for very old devices.
> > > > 
> > > > 
> > > > 
> > > > Gale
> > > > 
> > > > 
> > > > > It's good to get feedback, so thanks to all who have answered.
> > > > > 
> > > > > Best Regards, Jim. 
> 



The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind

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 web site is at
//www.freelists.org/webpage/audacity4blind

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

Other related posts: