Error code- 38 – Forum Post & Discussion Thread : macProVideo.com

Kizujoy

Posts: 100

Joined: Oct 13th, 2007, 10:21

Error code- 38

Jan 22nd, 2008, 09:31

Hi again I keep getting an Error message . It says (Error code 38 was returned by Audio driver) . When it appears I reboot Logic . Does anybody know whats causing this ?

Reply

Christian L

Posts: 1410

Joined: Aug 7th, 2006, 11:50

Re: Error code- 38

Jan 22nd, 2008, 09:43

What are you doing exactly when you get the error ? Did you try repairing permissions... What audio interface do you use and do you have the latest drivers ?

Reply

Kizujoy

Posts: 100

Joined: Oct 13th, 2007, 10:21

Re: Error code- 38

Jan 22nd, 2008, 10:44

It Usually happens when I change the title during a save as . I record into an Apogee that goes into the 828 via spdf cable Playback is with an 828 .

Reply

Rounik Admin

Posts: 8713

Joined: Dec 16th, 2006, 08:13

Re: Error code- 38

Jan 23rd, 2008, 12:06

Hi As Christian says, try repairing permissions (Applications > Utilities > Disk Utility) and then restarting. If that doesn't help the issue unplug your interface and see if you can replicate the issue using built-in audio. Let us know how it goes, Rounik

Reply

Kizujoy

Posts: 100

Joined: Oct 13th, 2007, 10:21

Re: Error code- 38

Jan 23rd, 2008, 07:38

Thanks a lot I'll try that .

Reply

Noisenet

Posts: 8

Joined: Dec 30th, 2007, 11:58

Re: Error code- 38

Jan 29th, 2008, 08:31

Heya, I've frequently gotten this error as well. It's not something that I can readily reproduce (I've tried), just seems random. My setup is as follows: iMac 2.4GHz, 4Gb RAM, 320Gb HDD, M-Audio MobilePre USB I/O, M-Audio MIDISport 1x1 Uno. All project files are stored on a 250GB Western Digital Firewire External Drive. I have had this error both using the M-Audio I/O as well as the built in hardware. I was running Leopard 10.5.1 but two days ago reverted my system to 10.4.11 - besides this issue I was having others, like Bluetooth hanging everytime I resumes the machine from Sleep. I have not seen the error since then, and I was in Logic for roughly 12 hours yesterday, so mayhaps this did it for me? Also, since the reversion to Tigger, I haven't seen the "Overload" error either, which I had on occasion...... Hope this is helpful to someone.

Reply

Rounik Admin

Posts: 8713

Joined: Dec 16th, 2006, 08:13

Re: Error code- 38

Jan 29th, 2008, 09:34

Hi Noisenet Thanks for posting your experiences and welcome to MacProVideo forums! It's interesting that Tiger doesn't reproduce these issues as much as Leopard. I wonder if the upcoming 10.5.2 update will help with these issues. Cheers Rounik

Reply

Noisenet

Posts: 8

Joined: Dec 30th, 2007, 11:58

Re: Error code- 38

Jan 29th, 2008, 09:50

Heya Rounik, Ya know, I was wondering that too. I was hoping 10.5.2 would drop on Friday, but when it didn't, I decided to cut my frustrations and go back to Tiger. I'm still running Leopard on my MacBook, but for my production machine I'm gonna stick with Tiger for a while. Nice Forum ya'll have here, BTW.

Reply

Rounik Admin

Posts: 8713

Joined: Dec 16th, 2006, 08:13

Re: Error code- 38

Jan 29th, 2008, 03:21

[quote:38285]but for my production machine I'm gonna stick with Tiger for a while. Nice Forum ya'll have here, BTW.[/quote] same here. I'd like to try Leopard out soon but I'll definitely wait for 10.5.2 and keep my eyes peeled for people's opinions. If you do upgrade to 10.5.2 do let us know your logic experiences! Cheers:) Rounik

Reply

Noisenet

Posts: 8

Joined: Dec 30th, 2007, 11:58

Re: Error code- 38

Feb 21st, 2008, 10:38

After being in Tiger a little while, I started having problems in Tiger so I figured I might as well go back to Leopard, try 10.5.2 and the other recent updates (Pro Kit 4.5, etc....). I did all this last Saturday and things SEEM to be fine. I've only had a chance for one all day session, but for the most part, things are smooth. I'm going to start a new thread detailing one issue I continue to have, it'll be called something along the lines of "Core Audio Overload" or something......... But on the whole, while not 100% satisfied, it's workable.

Reply