Switching Core Audio Drivers - No Audio Out

I have a project in Logic Pro 8. It was recorded with Presonus Core Audio drivers on a Powerbook. The Project was then handed off to me to complete here in the studio.
I re-opened the Logic Express Project in Logic Pro 8 using Digidesign HD hardware and Digidesign's Digidesign HW (HD) Core audio driver. All was well.
We decided to try some changes in routing, using some new equipment M-Audio (ProFire Lightbridge) to take advantage of some Apogee I/O units in the studio. Loaded up the M-Audio Core Audio Drivers (ProFire Lightbridge Multichannel), made sure everything appeared properly in the Apple AMS (Audio Midi Setup) panel and did test tracks in Logic. All was well still
Then I opened the Project, which had been working in Logic 8 and interfacing with the Digi HD hardware, now using the Lightbridge Multichannel driver to access the Apogee I/O, and...no audio.
No indication of activity on the hardware interfaces. I checked Logic 8, onscreen everything appeared normal. Channel meter activity. Channel routing remained unchanged and should have appeared at the appropriate D/A convertor. Digital activity which would have normally been indicated at the ADAT to Firewire interface was non-existent. So, I would deduce that the computer was not directing the Logic channel activity through the new driver to the firewire interface from this project.
I rechecked the test project with tones. I/O activity normal. Audio out. I opened another of the series of sessions from Logic Express to Logic using DAE now using the M-Audio interface. Nada. No firewire/ADAT activity?
I have reverted without problem back to using the DAE/Digi Core Audio model with no problems, but I would like to get the ADAT/Core Audio model running on these same projects as a proof-of-concept, and see no reason why it shouldn't.
Opinions, suggestions, ideas, questions?
...JB
Message was edited by: J A Bohrer

When I was on the phone with M-Audio Tech Support (they're quite helpful) we noted the following:
1. If you switch over to Core Audio using the Mac's Internal speaker in one of these projects (switch to Apple's internal Core Audio Driver). All Channels are immediately updated to show only Output 1-2 available. and the project plays through channels 1-2 and the MacPro Speaker.
2. Switching back to DAE Core Audio, all available channels are updated and all plays/records normally using the Digidesign HW (HD) Core Audio Driver.
3. When the ProFire Lightbridge Core Audio Driver is selected, all channels are updated (now 1-18) and available, but if you select a channel or channel pair on one of the Channel Strips that was not in use previously in this session, an "out" bus for that channel is not created in Logic (which it normally does, assuming you choose a new channel pair for output from a channel strip...)
When a 'new' project is created with the Lightbridge setup selected as the Core Audio output, all channels will auto create an appropriate channel output strip.
My problem only exists when opening a previously created project. (In this case using DAE Core Audio...and I'm not implicating that as the cause, I don't think it is.)
It's like having previous sessions/projects, buying new hardware to improve your ability to work with them only to find out you can't use your new stuff with the old sessions. (Not like that hasn't happened before.)
Either Logic is at fault, not being able to accomodate the driver change from DAE to M-Audio, or the M-Audio driver is, being unable to get Logic to update its Environment to accomodate the new channel availability.
...J
Message was edited by: J A Bohrer
Message was edited by: J A Bohrer

Similar Messages

  • Downgrade to win7 problem with audio drivers. beats audio software for win7?

    I recently purchased the HP Envy 700-074 from best buy.  it was necessary to downgrade to windows 7 for some work software and I would like proper audio drivers/software for windows 7. Right now it seems to be detecting as Nvidia audio driver but in this case it doesnt allow my front panel audio ports to output audio. I would also like to have beats working. 
    here are the hardware ID's associated with the card
    HDAUDIO\FUNC_01&VEN_10DE&DEV_001C&SUBSYS_38423619&REV_1001
    HDAUDIO\FUNC_01&VEN_10DE&DEV_001C&SUBSYS_38423619
    and here's a quick screenshot of the driver that is associating with it right now.. 
    http://gyazo.com/23499c19d5e2a21f81b9124ad822c07d.png
    even those VEN_10DE's seem to associate to nvidia, but from HP the driver is meant to be IDT high definition audio? is something going on here? 
    the only change i've made to the computer is upgraded to an EVGA Nvidia GT 610 video card.,

    Hi, Paul.
    I have similar problem here.
    I bought HP Envy 810-200nr and I hate W8, so I installed Windows Server 2008 R2, which is my favourite.
    Then I solved numerous problems with chipset drivers and finally it all works, but Audio (IDT HD Audio) does not work.
    Completely silent.
    HDAUDIO\FUNC_01&VEN_111D&DEV_76C7&SUBSYS_103C2AF3&REV_1001
    HDAUDIO\FUNC_01&VEN_111D&DEV_76C7&SUBSYS_103C2AF3
    It looks okay, when playing audio - indicator blinks and shows level, volume can be adjusted, all parametrers - speakers, etc seems okay but silent!
    I tried numerous drivers for W8 and W7 64 but they give "Incompatible version" error.
    Can you advise me what to do? I really want WS2008R2 here, but this audio is weird..

  • Apple's Core Audio drivers have been corrupted?

    Since upgrading to Leopard, my Alesis USB Multimix8 mixer has been increasingly getting more and more static output and has become about useless. After trying everything I could think of, I wrote to Alesis and this is what their support said...
    "With Apple’s latest updated OS Leopard, it seems Apple’s Core Audio drivers have been corrupted and affects many class compliant devices such as the Multimix 8 USB which relies on these drivers. Until Apple addresses this with a fix, the best workaround is to back-down to 10.4.10, especially if this will be used in a professional studio."
    Does this sound correct to anyone? Is theAudio Core drivers that bad on Leopard and is this something that Apple even plans to address?
    Thanks!

    Hi, everyone.
    Alesis is VERY quick to point the finger at Apple for all their woes, but after my last experience, I'm thinking this is Alesis' problem.
    At one time I was running my Alesis MultiMix8 FireWire and getting constant kernel panics while working on audio and video deadlines. As this was the famed 8-core (rolling off the assembly lines in May and all that) I was banging my head against the wall. It finally came down to me bringing in all of my office into Apple's Genius Bar at Tysons Corner, VA and trying to duplicate the occurrence.
    The culprit was the Alesis driver.
    When I upgraded to Leopard and the new Alesis FireWire driver, I have encountered no KPs or odd audio issues. Confident, I decided to try out the Alesis iMultiMix8 USB for the Second Edition of Podcasting for Dummies. I got a high-pitched whine/static when I tried working with the audio mixing between iPod and mixer. I returned the mixer and exchanged it for another one. Same problem. I then went and tested the iMultiMix on my PowerBook G4 running 10.4.11. Problem still existed. I wrote to Alesis and told them about the iMultiMix, asking them if this was a common issue.
    No response.
    While Leopard has solved the issues of the KP and continues to perform like a champ, I have been talking to other friends working on both 10.5 and 10.4 having issues with Alesis mixers and USB-powered pre-amps. It sounds less of an Apple issue and more of an Alesis issue.
    I think all we can do is wait for Alesis to resolve the problem they are failing to acknowledge is theirs. Not much of an answer, but apparently this the way things appear to be.

  • Core Audio Drivers not Found Error (no Logic Pro Installed)

    I am receiving the following error in GarageBand 08 and was hoping someone might be able to assist.
    When recording with a USB mic in GarageBand 08 (MXL USB.006) I sometimes get the following error: (Core Audio Drivers not Found). The error occurs after I have completed a recording session and removed the USB mic. (The error occurs regardless of if I close GB before removing the mic; but only occasionally)
    In checking the GB preferences, the Built-In audio option has disappeared from the drop down menu entirely for both Audio Input and Audio Output (although it still can find the USB mic if I reattach). In the Utilities folder, audio preferences, the Built-In audio option is also missing from the drop downs. (Not grayed out -- missing).
    In researching the problem, it looks like a similar problem occurs with the Logic Pro suite but I don't have that installed on my Mac (and never have). In contacting MXL support, they noted that it was a problem with Leopard and they didn't have a fix.
    At this point, I'm looking for either (1) a fix I've missed in my research or (2) an easy way to reinstall/replace/find the drivers without having to restore my system from backup. I've received the error three times now and restoring from back up - which clears the error and restores the drop down - is getting tiresome.
    Thank you!

    Thank you for the suggestion! I believe that was the issue the first time I lost the drivers. Unfortunately, even resetting the inputs and closing GB before disconnecting doesn't guarantee my Built-In audio won't disappear. Thank you for trying though!

  • A quick primer on audio drivers, devices, and latency

    This information has come from Durin, Adobe staffer:
    Hi everyone,
    A  common question that comes up in these forums over and over has to do  with recording latency, audio drivers, and device formats.  I'm going to  provide a brief overview of the different types of devices, how they  interface with the computer and Audition, and steps to maximize  performance and minimize the latency inherent in computer audio.
    First, a few definitions:
    Monitoring: listening to existing audio while simultaneously recording new audio.
    Sample: The value of each individual bit of audio digitized by the audio  device.  Typically, the audio device measures the incoming signal 44,100  or 48,000 times every second.
    Buffer Size: The  "bucket" where samples are placed before being passed to the  destination.  An audio application will collect a buffers-worth of  samples before feeding it to the audio device for playback.  An audio  device will collect a buffers-worth of samples before feeding it to the  audio device when recording.  Buffers are typically measured in Samples  (command values being 64, 128, 512, 1024, 2048...) or milliseconds which  is simply a calculation based on the device sample rate and buffer  size.
    Latency: The time span that occurs between  providing an input signal into an audio device (through a microphone,  keyboard, guitar input, etc) and when each buffers-worth of that signal  is provided to the audio application.  It also refers to the other  direction, where the output audio signal is sent from the audio  application to the audio device for playback.  When recording while  monitoring, the overall perceived latency can often be double the device  buffer size.
    ASIO, MME, CoreAudio: These are audio driver models, which simply specify the manner in which an audio application and audio device communicate.  Apple Mac systems use CoreAudio almost exclusively which provides for low buffer sizes and the ability  to mix and match different devices (called an Aggregate Device.)  MME  and ASIO are mostly Windows-exclusive driver models, and provide  different methods of communicating between application and device.  MME drivers allow the operating system itself to act as a go-between and  are generally slower as they rely upon higher buffer sizes and have to  pass through multiple processes on the computer before being sent to the  audio device.  ASIO drivers provide an audio  application direct communication with the hardware, bypassing the  operating system.  This allows for much lower latency while being  limited in an applications ability to access multiple devices  simultaneously, or share a device channel with another application.
    Dropouts: Missing  audio data as a result of being unable to process an audio stream fast  enough to keep up with the buffer size.  Generally, dropouts occur when  an audio application cannot process effects and mix tracks together  quickly enough to fill the device buffer, or when the audio device is  trying to send audio data to the application more quickly than it can  handle it.  (Remember when Lucy and Ethel were working at the chocolate  factory and the machine sped up to the point where they were dropping  chocolates all over the place?  Pretend the chocolates were samples,  Lucy and Ethel were the audio application, and the chocolate machine is  the audio device/driver, and you'll have a pretty good visualization of  how this works.)
    Typically, latency is not a problem if  you're simply playing back existing audio (you might experience a very  slight delay between pressing PLAY and when audio is heard through your  speakers) or recording to disk without monitoring existing audio tracks  since precise timing is not crucial in these conditions.  However, when  trying to play along with a drum track, or sing a harmony to an existing  track, or overdub narration to a video, latency becomes a factor since  our ears are far more sensitive to timing issues than our other senses.   If a bass guitar track is not precisely aligned with the drums, it  quickly sounds sloppy.  Therefore, we need to attempt to reduce latency  as much as possible for these situations.  If we simply set our Buffer  Size parameter as low as it will go, we're likely to experience dropouts  - especially if we have some tracks configured with audio effects which  require additional processing and contribute their own latency to the  chain.  Dropouts are annoying but not destructive during playback, but  if dropouts occur on the recording stream, it means you're losing data  and your recording will never sound right - the data is simply lost.   Obviously, this is not good.
    Latency under 40ms is  generally considered within the range of reasonable for recording.  Some  folks can hear even this and it affects their ability to play, but most  people find this unnoticeable or tolerable.  We can calculate our  approximate desired buffer size with this formula:
    (Sample per second / 1000) * Desired Latency
    So,  if we are recording at 44,100 Hz and we are aiming for 20ms latency:   44100 / 1000 * 20 = 882 samples.  Most audio devices do not allow  arbitrary buffer sizes but offer an array of choices, so we would select  the closest option.  The device I'm using right now offers 512 and 1024  samples as the closest available buffer sizes, so I would select 512  first and see how this performs.  If my session has a lot of tracks  and/or several effects, I might need to bump this up to 1024 if I  experience dropouts.
    Now that we hopefully have a pretty  firm understanding of what constitutes latency and under what  circumstances it is undesirable, let's take a look at how we can reduce  it for our needs.  You may find that you continue to experience dropouts  at a buffer size of 1024 but that raising it to larger options  introduces too much latency for your needs.  So we need to determine  what we can do to reduce our overhead in order to have quality playback  and recording at this buffer size.
    Effects: A  common cause of playback latency is the use of effects.  As your audio  stream passes through an effect, it takes time for the computer to  perform the calculations to modify that signal.  Each effect in a chain  introduces its own amount of latency before the chunk of audio even  reaches the point where the audio application passes it to the audio  device and starts to fill up the buffer.  Audition and other DAWs  attempt to address this through "latency compensation" routines which  introduce a bit more latency when you first press play as they process  several seconds of audio ahead of time before beginning to stream those  chunks to the audio driver.  In some cases, however, the effects may be  so intensive that the CPU simply isn't processing the math fast enough.   With Audition, you can "freeze" or pre-render these tracks by clicking  the small lightning bolt button visible in the Effects Rack with that  track selected.  This performs a background render of that track, which  automatically updates if you make any changes to the track or effect  parameters, so that instead of calculating all those changes on-the-fly,  it simply needs to stream back a plain old audio file which requires  much fewer system resources.  You may also choose to disable certain  effects, or temporarily replace them with alternatives which may not  sound exactly like what you want for your final mix, but which  adequately simulate the desired effect for the purpose of recording.   (You might replace the CPU-intensive Full Reverb effect with the  lightweight Studio Reverb effect, for example.  Full Reverb effect is  mathematically far more accurate and realistic, but Studio Reverb can  provide that quick "body" you might want when monitoring vocals, for  example.)  You can also just disable the effects for a track or clip  while recording, and turn them on later.
    Device and Driver Options: Different  devices may have wildly different performance at the same buffer size  and with the same session.  Audio devices designed primarily for gaming  are less likely to perform well at low buffer sizes as those designed  for music production, for example.  Even if the hardware performs the  same, the driver mode may be a source of latency.  ASIO is almost always  faster than MME, though many device manufacturers do not supply an ASIO  driver.  The use of third-party, device-agnostic drivers, such as  ASIO4ALL (www.asio4all.com) allow you to wrap an MME-only device inside a  faux-ASIO shell.  The audio application believes it's speaking to an  ASIO driver, and ASIO4ALL has been streamlined to work more quickly with  the MME device, or even to allow you to use different inputs and  outputs on separate devices which ASIO would otherwise prevent.
    We  also now see more USB microphone devices which are input-only audio  devices that generally use a generic Windows driver and, with a few  exceptions, rarely offer native ASIO support.  USB microphones generally  require a higher buffer size as they are primarily designed for  recording in cases where monitoring is unimportant.  When attempting to  record via a USB microphone and monitor via a separate audio device,  you're more likely to run into issues where the two devices are not  synchronized or drift apart after some time.  (The ugly secret of many  device manufacturers is that they rarely operate at EXACTLY the sample  rate specified.  The difference between 44,100 and 44,118 Hz is  negligible when listening to audio, but when trying to precisely  synchronize to a track recorded AT 44,100, the difference adds up over  time and what sounded in sync for the first minute will be wildly  off-beat several minutes later.)  You are almost always going to have  better sync and performance with a standard microphone connected to the  same device you're using for playback, and for serious recording, this  is the best practice.  If USB microphones are your only option, then I  would recommend making certain you purchase a high-quality one and have  an equally high-quality playback device.  Attempt to match the buffer  sizes and sample rates as closely as possible, and consider using a  higher buffer size and correcting the latency post-recording.  (One  method of doing this is to have a click or clap at the beginning of your  session and make sure this is recorded by your USB microphone.  After  you finish your recording, you can visually line up the click in the  recorded track with the click in the original track by moving your clip  backwards in the timeline.  This is not the most efficient method, but  this alignment is the reason you see the clapboards in behind-the-scenes  filmmaking footage.)
    Other Hardware: Other  hardware in your computer plays a role in the ability to feed or store  audio data quickly.  CPUs are so fast, and with multiple cores, capable  of spreading the load so often the bottleneck for good performance -  especially at high sample rates - tends to be your hard drive or storage  media.  It is highly recommended that you configure your temporary  files location, and session/recording location, to a physical drive that  is NOT the same as you have your operating system installed.  Audition  and other DAWs have absolutely no control over what Windows or OS X may  decide to do at any given time and if your antivirus software or system  file indexer decides it's time to start churning away at your hard drive  at the same time that you're recording your magnum opus, you raise the  likelihood of losing some of that performance.  (In fact, it's a good  idea to disable all non-essential applications and internet connections  while recording to reduce the likelihood of external interference.)  If  you're going to be recording multiple tracks at once, it's a good idea  to purchase the fastest hard drive your budget allows.  Most cheap  drives spin around 5400 rpm, which is fine for general use cases but  does not allow for the fast read, write, and seek operations the drive  needs to do when recording and playing back from multiple files  simultaneously.  7200 RPM drives perform much better, and even faster  options are available.  While fragmentation is less of a problem on OS X  systems, you'll want to frequently defragment your drive on Windows  frequently - this process realigns all the blocks of your files so  they're grouped together.  As you write and delete files, pieces of each  tend to get placed in the first location that has room.  This ends up  creating lots of gaps or splitting files up all over the disk.  The act  of reading or writing to these spread out areas cause the operation to  take significantly longer than it needs to and can contribute to  glitches in playback or loss of data when recording.

    There is one point in the above that needed a little clarification, relating to USB mics:
    _durin_ wrote:
     If  USB microphones are your only option, then I would recommend making  certain you purchase a high-quality one and have an equally high-quality  playback device.
    If you are going to spend that much, then you'd be better off putting a little more money into an  external device with a proper mic pre, and a little less money by not  bothering with a USB mic at all, and just getting a 'normal' condensor  mic. It's true to say that over the years, the USB mic class of  recording device has caused more trouble than any other, regardless.
    You  should also be aware that if you find a USB mic offering ASIO support,  then unless it's got a headphone socket on it as well then you aren't  going to be able to monitor what you record if you use it in its native  ASIO mode. This is because your computer can only cope with one ASIO device in the system - that's all the spec allows. What you can do with most ASIO hardware though is share multiple streams (if the  device has multiple inputs and outputs) between different software.
    Seriously, USB mics are more trouble than they're worth.

  • No Audio Drivers recognised

    My GB2 is not working.
    Don't quite know when it started as I have been updating lots due to Apples updates recently, but when I try to boot GB2 it will not startup.
    I have managed to get my preferences window open to find that no audio drivers are being recognised. Does anybody know why ? It used to work flawlessly.
    I think core audio is the problem ?
    Help !
    Any suggestion would be appreciated.....

    I haven't seen a responce as of yet.
    I did some of my own investigating though.
    I did hear a pop when I plugged into the Macbook. As a musician I knew that the "pop" wasn't good but I had no idea it would be this fatal!
    The things to look for are these:
    Make sure that there is no "red light" on in the line in port. That would indicate that the source is wrong. Search the forums for that easy fix.
    If your still able to hear anything out of the internal speakers (start up chime, system sounds ect) then check the utilities folder and check the Audio midi device.
    If (like me) you have nothing. No system sounds, nada, then go under *Apple>About this Mac>More Info* and see if there is anything listed under "Audio (built in)". If there is nothing listed their then it's time to head to your local Apple store for a repair.
    I have not taken mine their and won't be able to until after the holidays, but I did find a recording work around until then by using a little device by Griffin Technologies called the iMic. It does the job and it's under $50.
    Here's the link to the iMic:
    http://www.griffintechnology.com/products/imic
    I should note that this is a version 1 Blackbook. I do have the screen flicker problem that the first gens had, as well as the complaint that the internal speakers, even at the highest settings, were not enough for any listening other than in a completely silent room. There also was some clicking on the hinge when you open it. Once I get it to the Apple store then I'll get it fixed proper but until then this workaround is a cheap solution for now. After all, the band MUST play on.
    Fenix

  • Updating my audio drivers

    Hello,
    Recently, I've been trying to find out how I update my Audio Drivers for my 2.4GHZ Intel Core Duo iMac, because also recently, I was playing Counter Strike:Source Via 'Crossover' on leopard. Turned it off for the night, came back on the next day and I'm getting No Audio in CSS, but all my other programs are working fine.
    I've tried reinstalling CSS already to no avail, so I'm gonna try and see if I can update my Audio Drivers and see if that works, because right now, this is the only thing I can think off.
    Unless anyone else knows what might be causing this problem.
    Thanks in advance,
    Sharp

    If you don't have the latest software for your Mac run software update from the Apple menu. Macs aren't like PCs, you don't need to go hunting for drivers for the internal stuff like sound cards or graphics cards software update looks after all of this.
    You may want to try trashing the plist for Counterstrike, if you can find it, as it could well be corrupted.

  • Audio Drivers for an XP install of a dv7t-1200?

    I had to reformat my laptop and since Vista is still a mediocre at best OS, I decided to switch back to XP. Unfortunately, it seems as though HP has no audio drivers for this operating system. Is there any known way to get audio working on a dv7t-1200 under windows XP? Thank you in advance

    Have you tried driver in C:\swsetup\driver ?
    Pavilion DV2922TX, XP-SP3 32bit, Intel T5750 2.0Ghz, Nvidia Geforce 8400M GS with 128MB, 4GB 667 DDR2, 250GB HDD

  • W520 audio line in / line out

    Whenever i connect a 3.5mm cable with the line in/out it gets interpreted as a line out (headphone) cable. The line in gets displayed as not connected. Is there any way of switching the interpretation? I don"t need line in + out simultaneously, but i"d really like to use the line in as well

    Does any one know how to setup or switch Audio line-in port in "W520 conexant 20672 in Windowns 7 64 bit"?
    Does W520 Microphone jack support 3.5 mm audio in from iPod or any other sound device.
    I have Mac book pro, they can do switch between Internal Microphone to Audio Line in.
    How come this expensive W520 laptop can't do this?
    Lenovo service group people doesn't know how to do it. Please help fix this problem that very appreciated.

  • What are the iTunes digital audio levels in and out

    I am having a lot of trouble with finding out and setting the audio levels in and out of iTunes.
    Digital audio has 16bits at '1' with an analog signal level of +12dB, 24bit has all'1's at +18dB. Making the overhead capability for CD 16bit 12dB and that for HD 24bit 18dB.
    I would like to record (using SoundStudio) a set of standard audio tones from 20-20kHz with digital levels of "all 1's" 16bit, or +12 dB analog level, "all 1's" 24bit ditto, and the same for levels of analog 0dB (-12dB digital) for 16bit and 0dB(-18dB digital) for 24bit.
    What I am finding is that if I get Sound Studio to inert a tone at what it calls 0dB, save it as AIFF, then the output it from iTunes I get a much higher level, around +8dB or so!
    Any ideas?

    As an addition to my first question. I asked the makers of Sound Studio about levels. They tell me that the Mac standard is to have all '1's in the digital stream defined as 0dB.
    Which helps as I can now record a tone at the CD level of -12dB and the HD audio level of -18dB. And if I make recordings I know to keep the input levels well into the green, not yellow and definitely not up to the red.
    As you say the output of iTunes is boosted, and from my measurements this boost is in the analog circuitry and is about +8dB.
    I woul dnot recommend turing down the iTunes volume control as this brings in the digital volume reduction, which depends on the algorithm they have implemented. This is not so bad for iTunes as the Audio Core software works at 32bit and can handle 16bit volume changes fairly well. But on the iPad it is different as iOS is only 16bit audio so the volume algorithm is poor. So always leave the volume at maximum and turn down your HiFi volume control!
    Or use a digital output to an external DAC as the iTunes volume control is then disabled. Set Audio MIDI for 24bit output and you are ready to go with HD Audio.

  • Added audio drivers, now reboots before Xserver starts

    to fix my audio problem, I installed the audio drivers from http://www.tools.de/solaris/audio/, now after getting to the interactive boot prompt, the system restarts back at the bios..
    doah..
    help
    Sam

    I fixed this with a re-install. couldn't figure out how to get in to a command line prompt with enouhg system access to fiddle with the driver install.
    Sam

  • Problems with the latest Windows 7 Conexant HD Audio Drivers For WIndows 7

    Hi,
    I have a Toshiba Satellite P305-S8997E with the Conexant High Definition SmartAudio 211 speakers. I have recently upgraded with the Windows 7 32/64-bit audio drivers posted within the last week in the Drivers section, and have had a few problems with them. Namely that whenever I listen to music (and etc), the volume is fairly low, and even when the speaker AND media player (Foobar, FYI) volumes are cranked, they flucuate, and eventually end up being much lower than they should. Is there any fix to this? I recently downgraded to the last Vista 64-bit drivers for them and that has ended the volume problem, but it doesn't sound as good as it should to my ears. Any help is appreciated.
    Also, this computer is only about two months old, and this problem hasn't surfaced until very lately, so I doubt it's something like the speakers going out or anything.

    Windows 7 is still a PRE-RELEASE OS until the OFFICIAL release date of October 22nd.  Toshiba and other manufacturers are still working on their drivers and may not have fully functioning drivers until then.  My advice is be patient and wait for them to get all of the bugs out.
    If you don't post your COMPLETE model number it's very difficult to assist you. Please try to post in complete sentences with punctuation, capitals, and correct spelling. Toshiba does NOT provide any direct support in these forums. All support is User to User in their spare time.

  • Garage Band Audio Drivers

    After Upgrading my OS to 10.5.8 from 10.4.1 I am unable to run Garageband '08. When I try to play one of my old projects the following message appears:
    ! GARAGE BAND HAS DETECTED A POSSIBLE CONFLICT BETWEEN ONE OR MORE THIRD PARTY MIDI OR AUDIO DRIVERS. BE SURE TO INSTALL THE LATEST DRIVERS FOR ALL AUDIO AND MIDI EQUIPMENT.
    Can someone please tell me what the latest drivers are and what is a reliable place to acquire them.
    I did download and installed PACE drivers, which I believe allow you to open protected files.
    Thank you.
    RL

    Thanks for the prompt reply  Cristoph. That is exactly what I did. It turns out there were a few prior discussions
    regarding this issue, all advocating for the same method:  I went to the Library folder,  took out both Digidesign drivers from the Audio Midi Folder created a new folder within the Library and dumped them into it.
    Voilå!! Garage Band works again! Thank you.

  • Audio does not come out of my left speak

    Hello,
    I just installed a fresh installation of Vista two days ago.
    When I installed it, I had a Sound Blaster Li've! 5. card in my machine, and the card did not work until I installed KM audio drivers (which made only the 2 rear speakers work).
    Today I went out and bought the X-Fi Xtreme Audio card.
    The installation appeared to work, and I installed the Vista drivers from www.soundblaster.com.
    When I go to audio management, and test the speakers, audio comes out of all 5.
    BUT - when Windows Media Player, MediaSource 5, and any other system sound plays... my front left and rear left speakers do not play a thing.
    I know they are working, because when I tried the surround audio from http://www.microsoft.com/windows/windowsmedia/democenter/9series/avquality/wmapromp3/default.htm
    they all played, but when I played stereo... it only came out of front right and rear left.
    ALSO - I can't seem to find the Entertainment Mode, and some other features advertised on the box and guide that came with the CD.
    Does anybody know what I can do to fix these issues? Help would be greatly appreciated.
    Thanks,
    Anthony Coy

    Hello, Alexander meerkat. 
    Thank you for visiting Apple Support Communities.
    I would start with resetting the System Management Controller.  Here is the article on how to process these steps.
    Intel-based Macs: Resetting the System Management Controller (SMC)
    http://support.apple.com/kb/ht3964
    Cheers,
    Jason H.

  • How to install Audio drivers???

    KT3 ultra2 board (ms-6380e)  When trying to install the Audio drivers/Energize the On-Board Audio (MSI DVD 5.1ch) from the CD the pesky thing asks for a Serial #!?? What # do I put in ??
    Hope it's not on that sticky onna Back of the board.. where I have to take everything out of the case to access.:-(
    Any suggestions?

    serial # should be printed on the CD .....

Maybe you are looking for