M-audio drivers and Mavericks

I use an old M-audio Firewire 410 audio interface. The drivers, which have not been supported since OSX 7, worked fine with Mountain Lion, but will they be okay with Mavericks?

I have the same interface as you do .. looking thru Apple doc , it seems that CoreAudio and CoreMIdi are unchanged so it looks good but then I found this :
Important: The code signing technique used for kernel extensions changed in OS X v10.8.3. Kernel extensions signed with earlier versions of OS X are treated as unsigned by OS X v10.9.
Kernel extensions signed using the newer signing tools are incompatible with OS X v10.7.5 and earlier. If you are producing a kernel extension that must support versions of the operating system prior to version 10.8, you must install an unsigned copy in/System/Library/Extensions, in addition to any signed copy in /Library/Extensions. Versions of OS X prior to version 10.9 will ignore the unsigned copy in /Library/Extensions. If the user upgrades to OS X v10.9 or later, the user’s system will prefer the signed copy in /Library/Extensions.
I will do some more research..

Similar Messages

Req to send my audio drivers and control panel

hello,my audio drivers and control panel were lost due to the attack of trojans.I'm unable to select my required drivers and control panel,because an error report is occuring and is closing the opened window.so i request you to please send me the suitable audio drivers and control panel.my laptop is presario c555nr model.please send them as soon as posible.
This question was solved.
View Solution.

http://h20180.www2.hp.com/apps/Lookup?h_lang=en&h_cc=us&cc=us&h_page=hpcom&lang=en&h_client=S-A-R163...
Are any of these yours ??
You may also try to restore your machine to a point before the trojan attack with Microsoft System restore.
Go to start > all programs > accessories > system tool > system restore.
If the trojan corrupted your system to the point where you can't fix it, then you may have to reload your OS using your HP recovery manager. Save all your personal info. before you do this, as it will be deleted.

Problems with MOTU Audio Setup and Mavericks.

Hi!
after installing the latest update of MOTU Audio Drivers (v1.6.59200 | Nov. 12, 2013) for some sessions Motu Audio Setup has worked correctly.
Now, after a week or so, it detects the interfaces (by the way a 828vMk II + 8pre, both FW) when I power them, so it fires up as usual; but when launched is not showing any device connected.
I tried to thrash the Audio Devices preference panels, but no result.
Shall I wait for a new MOTU update or is there any other workaround I could try?
Thanks in advance for help
Massimo

I had the same problem. The fix after multiple configurations is as follows.
1) Reset the PRAM and shutdown - this will clear the FW settings
2) Boot the systems but with on ONE Motu828 powered on.
3) After the system is up and you can see the one device - power the second device on it the Motu Audio Setup program should see both.
there is some kind of FW race problem. Also, go to preference, turn OFF IPV4 stack from the FW device in NW setting. If I do not do this, I cannot get the system to see the devices and it basically is in some sort of "hung" state.
Shawn

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.

Logic Pro 9.1.7 + Imac 2010 + 10.7.4 + Firewire = Audio Error and Solution.

Hi all,
This post is the end of a weeks long hair pulling, to save other people the pain of my past week, here is a quick rundown of the issue and the solution that for us at least worked.
All the software is legit and fully updated btw, before people ask.
Logic Pro 9.1.7 on 2010 Imac on 10.6.x, Refx Nexus, Sylenth plus many other VST's and Au's, Mackie Pro + Extender, 2 Midi Keyboards (Oxygen 49 and Alexis 49) and with a M-Audio 410 external soundcard running 10.1.3 driver, all working.. only issue we had was when copying midi between tracks into differing plugins the midi would corrupt the plugin requiring a restart of Logic.
This error we later discovered was due to midi automation for plugins being copied over, but that is not this issue.
Updated OS from 10.6 to 10.7.4 by way of 10.7.4 Combi Update. Removed M-Audio Drivers and then installed 10.7.4,
Installed brand new GRAID 4TB external disk (Raid 0 at 64kb block sixe) and connected M-Audio 410 via daisy chain.
Installed M-Audio Drivers, all ok.. at first..
Graid is 800, M-Audio is 400.. Connected as Imac -> GRaid -> Maudio
At first, its good, no issues.
Copied over a whopping 550GB off Imac onto external.. then later on, rebooted mac and started working on music.
Ran Logic Pro (64bit mode), whilst using Midi with Nexus we discovered the Audio at first was ok, but quickly over time degraded to where the sounds started becoming distorted, the more we went on, the more the distortion increased, after a while the midi notes were just sounding awful.
Rebooted mac
Started using Logic again, not 1 minute in, External drive and M-Audio disconnected themselves from the Mac.
Rebooted
Hard drive now seen, no M-Audio.
Now though, even using Itunes or Quicktime or VLC on any mp3 via internal soundcard, quality was.. well terrible. Within 2 seconds of hitting play, you knew it was bad.
Shutdown, removed external drive from chain, rebooted Mac -> M-Audio
M-Audio now seen, sound quality dreadful, shutdown Mac, rebooted without M-Audio, sound still awful just on Internal audio.
Time passes, I smoke too much, prod and poke and eventually reach for the install media
(Lots of shutdowns and restarts in next bit, after each line, also carefully reset and tested every Audio setting.)
Removed M-Audio driver
Installed 10.7.4
Installed M-Audio
All good again.
Later, as a test, connected External drive on its own, no M-Audio
All good.
Second test, added External Drive plus chain to M-Audio
Not good, M-Audio seen but even though sound bars showing on M-Audio software, no sound out to mixer
Removed External Drive from Chain, M-Audio now straight to Mac.
All BAD; sound was terrible,
Disconnected M-Audio
Playing any Mp3 via internal Audio, terrible..
Whatever happened, has thrown the entire Audio system into a mess, again!.
Removed M-Audio driver.
Reinstalled 10.7.4
Reinstalled M-Audio Driver
All good, on internal or external Audio
Disconnected M-Audio
Reconnected External Drive Only
Drive OK, Internal Sound OK.
Removed External drive
Reconnected M-Audio
All ok, internal or External.
Ok, Final conclusion.
When the M-Audio (400FW) is connected to Mac via External Drive (800) the Audio is knackered from that point onwards on 10.7.4, removing M-Audio drivers and re-installing makes no difference, even the Internal Sound is knackered.
Only solution at this point, remove M-Audio driver, reboot, reinstall 10.7.4, reboot, reinstall M-Audio Driver, reboot.
Then its all good again.
My guess is this, and I am probably wrong but it is all I can think of.
When the M-Audio is daisychained the Mac changes a setting somewhere, probably to adjust for high latency, at this point it is written somewhere (either as a file or as DSP bios setting) that is not being reset.
This is why it is completely broken until 10.7.4 is re-installed at which point whatever setting it is that was changed, is reset.
This is all I can think of, I have posted this so that if someone else in the weeks ahead has a similar issue, it will save you the stress and late nights I had this past week.
Take care all.

I was seeing the same problem... I'm a new Logic user, switching from DP, and so it was a minty fresh install of Logic Pro 9.1.7 under ML.
It turned out to be a third party graphics driver that was screwing up some internal process: specifically, the dirver for AirDisplay, an iOS app that lets you use an iPad as a portable monitor. When I removed the driver, the problem cleared up instantly, and I have done 9 hour sessions in Logic since then without a single hiccup.
If you're running a third party driver, remove it, repair permissions and see if the problem clears up.

Audio drivers for Compaq C770LA for Win XP Pro / integrated mic not working

Hello. I have downgraded a Compaq C770LA to Win XP Pro SP3. Almost everything seem works perfect, but I have tried several audio drivers and still can´t get to control or use the integrated mic which this notebook has. I can hear audio and even record, etc, but there is no way to use or get to the integrated mic and some of the volumen controls I was used to (as "Record whats been listened") are lost. Does anybody knows wheter I have to change the driver or if it´s going to be any difference if I install for example the smartaudio add-on? I tried HP but they replied they don´t provide drivers for notebook for Operating Systems other than the one they gave the notebook with.
Thanks in advance for any clue!

Try XP downgrade guide, here
Your model is in Part 2.
Pavilion DV2922TX, XP-SP3 32bit, Intel T5750 2.0Ghz, Nvidia Geforce 8400M GS with 128MB, 4GB 667 DDR2, 250GB HDD

Adobe Crashes upon adjusting Audio Gain and when exporting

First a bit about the systems in question
I have four identical edit bays. Each has a Dual Core 2.5 Ghz Pentium processor, 3.0 gbs of ram, a single sata drive split into two partitions (system 30 gb and video 470 gb). I am running up to date PPro 5.0.2, freshly installed on virgin drives. I was running Avsynth and FFdshow as a way to be able to import my old MJPEG footage, but thanks to Colin Brougham, I have that particular demon slain (and I am removing those two programs).I have two of the bays with the most up to date 64 bit manufacturer video and audio drivers, and two bays with Windows 7 automatically installed video and audio drivers. The problem is the same in all four bays.
We dump in one of two ways: either a direct DV dump via firewire or downloading .MXF files from our Panasonic P2 cameras via USB (can't seem to get the firewire PC dump to work correctly). The project settings I am using are DV-NTSC - Standard 48 Khz, with a slight change of requiring upper fields first (we're using a Maxx500 playout server, and it requires upper fields first). We have been experiencing intermittent crashes for a week and a half, but in the last few days they have picked up (no new updates applied, so its not that). I have two culprits:
One is an error code that thanks to this thread I know is related to the audio gain. My problem is that I have done everything I can think of and still no luck. It's been crashing with such regularity that my reporters are saving every few minutes, and I have the auto save set to 5 minutes. Today I had to reinstall this bay because it was crashing every time audio gain was adjusted.
My other problem relates to export. I use the MainConcept MPEG Encoder to output mpegs for the playout server, and about every fourth or fifth time the program will crash on export. Its not a pain to recover from, since at that point the reporters have saved and merely have to reopen and reset up the export, but it is happening far to regularly. Event Viewer references windows/system32/ntdll.dll as the faulting module. Again, I am having this error on two different bays, one with manufacturer drivers and one with Windows 7 installed drivers.
I know that despite my efforts I've probably not given enough info, so let me know what you need.

...downloading .MXF files from our Panasonic P2 cameras via USB (can't seem to get the firewire PC dump to work correctly).
That's correct. Avoid FW offloading on a PC; in fact, while it used to be the way to interface a P2 camera with a Mac, it's all USB there now, as well. Stick with USB, and you'll be fine. (I know this wasn't the gist of your thread, but I thought I'd shine a little light on that.)
One is an error code that thanks to this thread I know is related to the audio gain. My problem is that I have done everything I can think of and still no luck. It's been crashing with such regularity that my reporters are saving every few minutes, and I have the auto save set to 5 minutes. Today I had to reinstall this bay because it was crashing every time audio gain was adjusted.
This is known/acknowledged/as-yet-unsquashed bug, assuming that you're remapping your MXF audio channels from the two mono channels that are originally produced by the camera to a single stereo channel. You may be doing this manually, in the bin, or you might have a preference set to do this automatically on import (Edit > Preferences > Audio > Source Channel Mapping; if it's set to Stereo, try setting it to Use File). This bug only seems to rear its head when the mono channels of an MXF clip are remapped to stereo; if they remain as mono, you can use the Audio Gain command successfully.
If, however, your audio channels aren't stereo, post back; there might be something else going on.
My other problem relates to export. I use the MainConcept MPEG Encoder to output mpegs for the playout server, and about every fourth or fifth time the program will crash on export. Its not a pain to recover from, since at that point the reporters have saved and merely have to reopen and reset up the export, but it is happening far to regularly. Event Viewer references windows/system32/ntdll.dll as the faulting module. Again, I am having this error on two different bays, one with manufacturer drivers and one with Windows 7 installed drivers.
When you say "MainConcept MPEG Encoder," are you referring to the MPEG2 encoder that is part of Premiere/AME, or are you referring to some sort of add-on encoder?

Audio cracking and popping

These are my system specs,
CPU: AMD Phenom II X6 1100T 3.3GHz
RAM: 4GB Kingston HyperX @ 2000MHz
GPU: Sapphire HD4890 VaporX 1G
HDD: Seagate SATA11 500GB
MOBO: ASUS M4A89TD PRO
PSU: Corsair TX850W
OS: Windows 7 x64bit Home Edition
So i have an AMD system running windows 7. Now whenever i scroll through my music or playlists in itunes my music suffers severe cracking and popping sounds. It also happens when i am scanning photo's and editing them not sure if that helps. I am at a massive loss in why this is happening i have tried rolling back audio drivers and what not any solutions?

hi i just like to say i had a similar fault though i would be surprised if it causing yours,but you never know,my fault was my laptop lid, [9 months old] it contains the mic ,and when the lid was in a certain angle crackles could be heard worse when i had my external sound card in, it was a faulty membrane [ lid to body] easily missed by engineer because it was the same angle all the time it happened,good luck, PS you English is very good
Message was edited by: sido1

HP Pavilion a1210n with Windows Vista 32bit. looking for audio drivers. Can you point me to a link?

Hello,
I have an HP Pavilion a1210n running Windows Vista 32bit. I'm missing the audio drivers and can't seem to find them. Can you point me to a link for these drivers?
Thanks, It's much appricieated!

I found this link but it doesn't talk about audio drivers in the multimedia package. Am I missing something? Does Vista need to have all OS updates installed for this to work?
Thanks again!

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.

X200 Vista 64Bit Audio Drivers

I let System Update attempt to update the Connexant audio drivers and it failed because the update that was available was not signed. 64Bit requires all signed drivers. Now I can't even get back to how the machine originally shipped as the driver available for download appears to have the same issue.
Pointers to where I can find the right driver?

ChrisKinsman wrote:
Did you even read my post?
This isn't an issue with UAC. This isn't an issue with an ActiveX control and the authenticode prompt.
This is an issue with 64Bit Windows only loading signed drivers. Hvae you ever run a 64Bit OS?
EXCUSE ME?how do you expect to get an answer without reading your "COMPLETE" post? try following this method and the next time mind your language if you can!
go to cmd
2. Right-click on the shortcut and select Run as administrator
3. When the command window opens, type or paste the following and press ENTER:
Bcdedit.exe /set nointegritychecks ON
4. Reboot and then try installing the driver.
Message Edited by samavedam_vijay on 11-14-2008 08:44 PM
Message Edited by samavedam_vijay on 11-14-2008 08:45 PM
Message Edited by nonny on 11-14-2008 11:42 AM
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

My solution for No Audio -- Conexant drivers and Windows 7 x64

My son and I have the L2000 laptop that came with 32 bit XP and used the Conexant chipset for Audio. I had been using an SB Audigy PCMCIA card so I am not sure when Audio was really lost; however, he noticed it when I upgraded his PC. I scoured various forums looking for 64 bit Windows 7 drivers for Conexant audio but to no avail. Microsoft and Conexant both said that HP should supply the drivers. By the way HP, the Conexant website says that they do not supply drivers even though they make the chipsets "at the request of the OEM's." Another post said that HP was not going to supply these drivers for Windows 7. The solution from HP for my model and Windows 7 was the "HP Software Advisor" which was 67MB and totaly useless. It appears that this is a very common problem. Anyway, here is what you do:
First you need 2 files which ironically enough come from HP, they are SP35558.exe and SP35558.cva They contain the Conexant drivers for Vista x64. (I subsequently have found the 32 bit drivers and the procedure should be very similar except the files are SP34789.exe and SP34789.cva). Type the following into your browser address bar ftp://ftp.hp.com/pub/softpaq/ About half way down you will find the sub-directory with these files. Just right click each one and save to your desktop.
Double click SP35558.cva and tell Windows to use Notepad to open it. Scroll about half way down to "[Operating Systems]" and after "WV64UL=OEM" insert:
W764HB=OEM
W764HP=OEM
W764PR=OEM
W764UL=OEM
( For 32 bit systems use W732HB=OEM, etc.)
I next went up about 10 lines to "[System information]" and added
SysId3=0x3091
SysName3=HP Pavilion ze2000 series
SysId4=0x3096
SysName4=Compaq presario M2000 series
SysId5=0x3097
SysName5=Compaq Presario M2000 series
SysId6=0x3097
SysName6=HP Special Edition L2000 series
SysId7=0x3093
SysName7=Compaq Presario M2000 series
SysId8=0x3093
SysName8=HP Special Edition L2000 series
I got this information from another cva file on my PC at C;/swsetup/ This is the directory where HP updates default to.
After modding the cva file, I saved it to C;/swsetup/sp35558/
I then executed the SP35558.exe file. It did not work the first time -- I missed a line in my cva file. However, I then manually installed the Conexant drivers as follows and voila I had sound, nice crisp clear sound.
Under Device Manager, right click "Multimedia Audio Device" under "Other" and choose "Update Driver" Then" Browse your PC" and "Choose from a list". Select "Sound, audio and game controllers", then Conexant, then "Have Disk" . Browse to C:/swsetup/sp35558/ and open "cp6308Ba.inf" (64bit remember). Now choose "OK" and ignore any warnings about incompatibility, WHQL, etc. Give it plenty of time, you might think you are in a loop, but you are not. Congratulations, you are done.
This question was solved.
View Solution.

I thought that I would recompile my answer and then mark this thread as solved since it was not a post about a problem but rather how I solved a very common problem that might be of benefit to others.
My son and I have the L2000 laptop that came with 32 bit XP and used the Conexant chipset for Audio. I had been using an SB Audigy PCMCIA card so I am not sure when Audio was really lost; however, he noticed it when I upgraded his PC. I scoured various forums looking for 64 bit Windows 7 drivers for Conexant audio but to no avail. Microsoft and Conexant both said that HP should supply the drivers. By the way HP, the Conexant website says that they do not supply drivers even though they make the chipsets "at the request of the OEM's." Another post said that HP was not going to supply these drivers for Windows 7. The solution from HP for my model and Windows 7 was the "HP Software Advisor" which was 67MB and totaly useless. It appears that this is a very common problem. Anyway, here is what you do:
First you need 2 files which ironically enough come from HP, they are SP35558.exe and SP35558.cva They contain the Conexant drivers for Vista x64. (I subsequently have found the 32 bit drivers and the procedure should be very similar except the files are SP34789.exe and SP34789.cva). Type the following into your browser address bar ftp://ftp.hp.com/pub/softpaq/sp35501-36000 About half way down you will find these files. Just right click each one and save to your desktop.(The 32 bit files are in a different subdirectory at ftp://ftp.hp.com/pub/softpaq/sp??????-??????)
Double click SP35558.cva and tell Windows to use Notepad to open it. Scroll about half way down to "[Operating Systems]" and after "WV64UL=OEM" insert:
W764HB=OEM
W764HP=OEM
W764PR=OEM
W764UL=OEM
( For 32 bit systems use W732HB=OEM, etc.)
I next went up about 10 lines to "[System information]" and added
SysId3=0x3091
SysName3=HP Pavilion ze2000 series
SysId4=0x3096
SysName4=Compaq presario M2000 series
SysId5=0x3097
SysName5=Compaq Presario M2000 series
SysId6=0x3097
SysName6=HP Special Edition L2000 series
SysId7=0x3093
SysName7=Compaq Presario M2000 series
SysId8=0x3093
SysName8=HP Special Edition L2000 series
I got this information from another cva file on my PC at C:/swsetup/ (This is thedefault directory for HP updates.)
After modding the cva file, I saved it to C;/swsetup/sp35558/
I then executed the SP35558.exe file and voila I had sound, nice crisp clear sound.
The use of the cva file is to streamline the driver install and it is kind of cool if it works. If you cannot find it or you are not successful the first time or you do not want to bother with modding anything, do not worry, the manual install will work for sure.
Run sp35558.exe to extract everything and let it strike out. Then go to Device Manager and update the driver manually as follows:
Under Device Manager, right click "Multimedia Audio Device" under "Other" and choose "Update Driver" Then "Browse your PC" and "Choose from a list". Select "Sound, audio and game controllers", then "Conexant", then "Have Disk". Browse to C:/swsetup/sp35558/ and open "cp6308Ba.inf" (64bit remember). Now choose "OK" and ignore any warnings about incompatibility, WHQL, etc. Give it plenty of time, you might think you are in a loop, but you are not. Congratulations, you are done.
Hope this helps.

HT5628 How to fix track pad and audio drivers if we install windows 8 on macbook pro??

Can anyone help me how to install track pad and audio drivers for my MBP if i install windows 8 on it?

Run Boot Camp Assistant and select the menu option to download the Windows Support software, Then start Windows and install the Windows Support software. Follow the Boot Camp instructions which detail how to download and install the drivers (Windows Support software).

Windows 7 Wireless and Audio Drivers on 2010 MacBook Pro

I have a new MacBook Pro i7 2.66 Mhz with Snow Leopard and dual boot to Windows 7 64 bit Ultimate. I can't find the correct drivers (Windows 7 side) to get the audio and the wireless networking operating. I ran the bootcamp setup from the Snow Leopard install disc on Windows 7. It gave an error message that this model is not supported. I then ran each software driver individually from the install disc and was able to get all to work except the audio and wireless. I then installed the Bootcamp 3.2 update from the Internet with no improvement.
Does anybody know where the audio and wireless drivers can be located for Windows 7? (Apple Support has not been able to resolve the problem yet) Thank You!

I'm having the same problem with Windows 7 64-bit Professional. I had to go through the same process to get most of the drivers installed. I've had the same issues with the wireless and audio drivers.
To get the Apple drivers installed, I followed the instructions from this blog post.
http://michael.anastasiou.me/index.php?option=com_content&view=article&id=22:qbo ot-camp-x64-is-unsupported-on-this-computer-modelq-solution&catid=7:how-to&lang= en
Has anyone had any luck with the rest of the drivers?

G60-235dx no audio seen and drivers refuse to install

what can I do to get audio back? I have had a HD failure and reinstalled the OS when it finished I see nothing but red x at speaker and no audio seen.

Quote from: Bigglesw0rth on 16-December-07, 09:48:28
The system stats are irrelevant. The mobo is in the subject. 7125-60 is the exact model.
Windows install (the whole XP line) only needs two files in the initial phase of install (after F6). This is simply so the installer itself can see the RAID. After that (directly after the format if you choose to format) and right before the install starts loading all the files it needs before the first restart, it will access teh floppy to get the rest of what it needs for XP itself to be able to see the RAID. That is what is not happening.
In Xp Pro (non Media Center Edition), the second access of the floppy after the format goes though perfectly fine. In Media Center Edition it tried to access teh floppy, then simply refuses to load the files off teh floppy.
Its pissing me off at this point. Right now my theory is that some sort of asinine protection Microsoft "protection" (possibly driver sig) is blocking the drivers from loading, and XP MCE is loading its own non-working retarded drivers.
Ive tried slipstreaming and it didnt work the first time. I dont have vmware to test it on and I dont want to screw up too many DVDs, and simply using XP Pro is not a solution, its a 'i give up' stage.
Hi,
A couple of thoughts:
1) When you load the initial driver floppy (F6), does it give you a choice of which drivers to load? Typically, when I've had to do the F6 thing, there'd be multiple sets of drivers, and I'd get a menu and have to select the correct one. If so, was there a menu item specifically for XP Media Edition (or whatever it's called)?
2) Are you by any chance using a USB floppy drive? There's a reference here to an MS KB article (916916) about compatible USB floppies:
http://groups.google.com/group/comp.sys.intel/msg/df7b2411c347566f
but, I searched the MS KB, and couldn't find that article.
Jim

M-audio drivers and Mavericks

Similar Messages

Maybe you are looking for