Please help: Can't record more than 1 second in Garageband 11

Question

Please help: Can't record more than 1 second in Garageband 11

Hi everyone,

This is my first post! I'm getting desperate as I can't find any answers elsewhere online and Applecare were no use as they don't help with software issues apparently!

Basically I've used older versions of Garageband for years with no issues, but after upgrading to Garageband '11 (I've got the latest version 6.0.5 (428.5)), I can no longer record any guitar! It will record for a split second, then stop, leaving only a split second of recorded track. If I try again, I get another split second of recording (this time coloured red) and a warning telling me:

Part of the project was not played

This project has too many tracks, effects, or notes to be played in real time.

To optimize performance, see the 'Optimizing GarageBand performance' page in GarageBand Help.

This is crazy as I'm using a brand new iMac 10.6.8 (Snow Leopard) 2.7Ghz Intel Core i5 with 4 GB 1333 MHz DDR3 system and I'm only trying to record 1 track!!!

So it clearly can't be because I've got too many tracks - this is the first one!

I've gone to the Optomizing GarageBand Help page and found that I'm already doing everything it suggests (no other Apps open, 500GB free space on the hard drive etc).

I've run out of ideas. This is really frustrating because older versions worked perfectly on far slower Macs with much less memory!

Please help me if you know how to fix this.

Thanks everyone,.

GarageBand (Mac) '11, Mac OS X (10.6.8)

Posted on Apr 21, 2012 8:37 AM

Reply

Answer 1

léonie

Level 10

194,647 points

Apr 21, 2012 8:45 AM in response to Jeff_Jeffty_Jeff

This looks like some application has a bad memory leak. Do you get the same error message after restarting your system?

Are there any warning messages/ diagnostic messages in Console window?

And what do you see in the Process Monitor - llok for cpu usage and memory usage.

Both "Console" and "Process Monitor" can be launched from Applications -> Utilities.

You may also check, if GarageBand works properly, if you start it from a different user account, to see if some settings in your account may be faulty.

Regards

Léonie

Reply

Answer 2

Apr 21, 2012 9:23 AM in response to léonie

Thanks for the tips! Yes I do get the same issue after restarting the computer.

On the console there is a repeated message relating to a TascamUS122 audio interface that I haven't used in years. Could this be causing the issue?

This is the message:

21/04/2012 12:44:42	pkgutil[16861]	PackageKit: *** Missing bundle identifier: /Library/Receipts/US122Driver.pkg
21/04/2012 12:44:42	[0x0-0x89089].com.apple.garageband[16834]	2012-04-21 12:44:42.501 pkgutil[16861:903] PackageKit: *** Missing bundle identifier: /Library/Receipts/US122Driver.pkg

Thanks again for helping out.

Mark

P.S. couldn't find any Process Monitor in the Apps folder. I'll check on the different user issue.

Reply

Answer 3

léonie

Level 10

194,647 points

Apr 21, 2012 9:38 AM in response to Jeff_Jeffty_Jeff

couldn't find any Process Monitor

That was a typo - sorry 😊; I meant "Activity Monitor" (in Applications -> Utilities)

a repeated message relating to a TascamUS122 audio

This looks like something in your current preferences is referring to the audio interface, but this is not installed in your current GB version. Have you tried, if GarageBand works from a different account? Then we would know, if your User settings in your account refer to this interface or if this is system wide.

Regards

Léonie

Reply

Answer 4

Apr 22, 2012 1:44 PM in response to léonie

Thanks again for the reply.

I tried Garageband logged in on another account - result was the same (unable to record more than a split second) and checking console still mentioned a 'missing bundle identifier (US122 interface I no longer use) and also 'audio engine overloaded, resetting' message.

Also checked out Activity Monitor - CPU is 94% idle.

If I uninstall Garageband (by dragging to trash) and then re-installing it from the iLife disc, will this sort the issue, or will it still be looking for this non-existent library .pkg file?

Kind regards,

Mark

Reply

Answer 5

Apr 25, 2012 2:12 AM in response to Jeff_Jeffty_Jeff

Any other thoughts, anyone? I really am stuck!

Thanks

Mark

Reply

Answer 6

Apr 25, 2012 3:22 AM in response to Jeff_Jeffty_Jeff

Try refreshing your preferences for Garageband (GB).

Quit GB.

Go to: ~/Library/Preferences/

Move these files to the desktop - This keeps a quick backup of them. Garageband will re-create these prefs when you re-launch Garageband.

com.apple.garageband.cs

com.apple.garageband.LSSharedFileList.plist

com.apple.garageband.plist

Re-launch GB.

You might have to reset some of your preferences in GB.

You will have to do this in every user account.

If something unwanted happens, just replace your prefs listed above with your desktop copies.

If it solves your issue, then you can delete the prefs that you dragged to the desktop, othewise, you can place them back, replacing what was recreated.

Have you tried uninstalling your Tascam software? Is there an uninstaller available? Sounds like there is a driver conflict...

Check what your Audio MIDI Setup is doing also (in Applications/Utilities). Make sure you "input" in the same sampling format (e.g. 44.1 KHz, 16 bit) as what GB is doing. GB's preferences say the choice of "Better" is recording at 24 bit, but exporting at 16 bit. Differences in sampling rates between what the mac hardware/GB might be stopping you.

Try the same preferences move to desktop trick (as above) on Audio MIDI Setup's "com.apple.audio.AudioMIDISetup.plist" (in ~/Library/Preferences also).

-oz

Reply

Answer 7

Apr 28, 2012 3:48 PM in response to oz-macnut

Hey Oz,

Thanks for getting involved in this issue!

OK, Here's what I've tried:

1) Complete uninstall/reinstall of Garageband 11 (including removing receipts and all accociated GB files) This has solved the TascamUS122 issue

No luck! Still only records for a split second. Tascam warning (in the Console report) gone, but still get the warning for 'audio engine overloaded resetting'.

2) Refreshing preferences (as you suggested)

No change.

3) Checked Audio MIDI Setup - matched (e.g. 44.1 KHz, 16 bit) with 'Good' on GB also 16 Bit. Couldn't find any kHz settings in GB.

No luck.

4) Did the "com.apple.audio.AudioMIDISetup.plist" (in ~/Library/Preferences thing.

No luck!

Here's a copy of what the Console is saying (note no receipts for JamPacks etc since deleting the receipts for the re-install - hope this isn't a problem).

28/04/2012 23:42:13	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.GarageBand_Jam_Pack' found at '/'.
28/04/2012 23:42:13	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPack1' found at '/'.
28/04/2012 23:42:13	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.RemixTools_Instruments' found at '/'.
28/04/2012 23:42:13	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.RhythmSection_Instruments' found at '/'.
28/04/2012 23:42:13	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPack4_Instruments' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.WorldMusic_Instruments_Tiger' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.Voices_Instruments_Tiger' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPackWorldMusicInstruments' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPackWorldMusicInstruments' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPackOneInstruments' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPackOrchestralInstruments' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPackRhythmSectionInstruments' found at '/'.
28/04/2012 23:42:14	[0x0-0x76076].com.apple.garageband[11514]	No receipt for 'com.apple.pkg.JamPackRemixToolsInstruments' found at '/'.
28/04/2012 23:42:15	MIDIServer[11534]	MIDIServer [11534] starting; arch=x86_64
28/04/2012 23:42:15	MIDIServer[11534]	PlugIn EmagicUSBMIDIDriver.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
28/04/2012 23:42:15	MIDIServer[11534]	MIDIServer relaunching because a 32-bit driver was found
28/04/2012 23:42:15	MIDIServer[11534]	MIDIServer [11534] starting; arch=i386

Does this give any clues? Thanks again for your help - really apprecaite it!

Mark

Reply

Answer 8

Apr 28, 2012 3:52 PM in response to Jeff_Jeffty_Jeff

.

Reply

Answer 9

Apr 29, 2012 4:50 AM in response to Jeff_Jeffty_Jeff

Suggest looking for an update to the emagic midi driver.

Failing all that, make sure you have at least one valid backup of your system, two backups to be safe, then try reinstalling snow leopard from the installer DVD.

https://discussions.apple.com/thread/2362057?start=0&tstart=0

Then install GarageBand, jam packs, other extras, then replace your files from backup. Very important...

If you have time, you could just try reinstalling SL without erasing the hard drive first, but it might be better to start from scratch. It's a lot of work, but it might make your headache go away for good!

Still, try finding that emagic driver first.

-oz

Reply

Answer 10

Apr 29, 2012 7:17 AM in response to oz-macnut

Thanks Oz. Couldn't find anywhere to update the emagic driver. I reinstalled the Session I/O driver just to make sure.

I'll consider reinstalling Snow Leopard, but I'm hoping there's a solution we havent thought of.

My iMac is a system migrated from my old MacBook Pro. Just to be sure, I fired up the old Macbook Pro and successfully recorded using the same OS, the same audio interface and the same version of Garageband!

Does this give any clues as to why the iMac might not be working? Is there some setting on the new iMacs that is different to the old MacBook Pros (2006)?

Thanks again for your help!

Mark

Reply

Answer 11

Apr 29, 2012 8:45 PM in response to Jeff_Jeffty_Jeff

Interesting.

The should be nothing technically different between the MacBook pro and the iMac. Are you using the same interface? I.e. USB on both MacBook and iMac? Make sure you are obtaining the latest driver for your Session driver from the web too.

What about installing a fresh install of snow leopard onto an external drive, install GarageBand and all your jam packs etc, and see if you can get the issue to present itself there. You should be able to boot using your external drive. Best if it is a FireWire enclosure. Perhaps leave your session I/o driver out of that installation.

Perhaps another post of your system log might help again.

What is your recording interface make and model? How does it connect? USB or FireWire?

Sorry mark. Not being very helpful, am I?

-oz

Reply

Answer 12

May 1, 2012 10:56 PM in response to oz-macnut

Thanks Oz, really appreciate your help on this.

I'll think about the fresh install etc. The trouble is, I'm a musician who bought a Mac back in the day, precicely because I'm not a techy and I was sick to death of daily ctrl+alt+delete wrestling matches with my old PC. I'm still hoping there's a simpler solution which won't require too much fiddling with the OS.

Another weird thing is that the Audio interface (Native Instruments Session I/O, bundled with Guitar Rig 3) works perfectly with Audacity, when recording guitar or voice.

So the question is, what's wrong with GarageBand '11 that even a reinstall of GB won't cure, yet a free piece of audio software works fine!! I'm really confused. I may try uninstalling it and going back to an older version of GB to see if that works.

Here's the latest console message:

02/05/2012 06:46:01	MIDIServer[1695]	MIDIServer [1695] starting; arch=x86_64
02/05/2012 06:46:02	MIDIServer[1695]	PlugIn EmagicUSBMIDIDriver.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
02/05/2012 06:46:02	MIDIServer[1695]	MIDIServer relaunching because a 32-bit driver was found
02/05/2012 06:46:02	MIDIServer[1695]	MIDIServer [1695] starting; arch=i386
02/05/2012 06:49:39	GarageBand[1670]	Audio engine overloaded, resetting
02/05/2012 06:49:44	GarageBand[1670]	Audio engine overloaded, resetting

06:46:01 = me starting GarageBand

06:49:39 = me pressing record on the guitar channel - only a split second was recorded.

06:49:44 = me trying again to record - result as above.

See screenshot image below.

Thanks again for your ideas.

Mark

Reply

Answer 13

May 2, 2012 7:22 AM in response to Jeff_Jeffty_Jeff

Happy to try and assist Mark.

I understand your reluctance to do the whole re-install. I have found in the past, sometimes it takes less itme in the long run.

Interesting that good old Audacity works OK. So it must be indeed GB that's giving you the issue.

Lets check this next:

Go the the Finder and launch System Preferences.

Go to the Audio pref pane and look at the Input and Output sections there. Again, I don't have an interface connected, but...

Is your Native Instruments Session audio interface listed and definately highlighted in both the input and output sections/tabs?

Now launch GB and go to your preferences (⌘-, (Command-comma))

Under Audio/MIDI, do you see your Native Instruments Session audio interface listed there under both Audio input and Audio output? This pic below was taken on my MacBook Pro (which I don't actively use for audio recording myself) so that's why I have System Setting listed there.

If you change it, it will probably tell you that GB must change the audio driver, click Yes.

Go across to Advanced. Does your Audio Resolution say "Good"?

Start with that and if sucessful we can try and go higher to say "Better" or "Best", if you want to record at a better audio resolution.

My Console shows this when I launch GB:

com.apple.midiserver[33460]: PreSonus FireStudio MIDI Driver - 3.5.6.11675 - x86_64 - Aug 16 2011 05:08:04

It shows the MIDI driver loading (where yours reports un-supported architecture and a 32-bit driver). The previous entries in your log indicate that the 64-bit MIDI is being loaded. (x86_64), but the driver is still 32-bit). I still think that perhaps an updated driver for the Native Instruments needs to be found... Audacity wouldn't care, as it does not support MIDI, but GB does, and would need to load both before being able to record sucessfully.

I'll see what I can find out for you Mark.

Hold tight!

Reply

Answer 14

May 2, 2012 7:42 AM in response to oz-macnut

Mark

If you are using a USB input, make sure you are plugging into one of the USB ports on the back of the iMac, not a keyboard/hub etc.

Check the driver version for your Native Instruments Session I/O. You should be able to check the version number from System Profiler (Applications>Utilities), then click the interface your Session I/O is connected by (USB or Firewire), select your device and see what driver version is listed in the RHS panel's info. I would say it would be 2.4.xx (if your interface isn't that old.)

You might need to un-install all Native Instruments drivers etc first though using the "Mac OS X Uninstaller Utility 1.1.0"

http://co.native-instruments.com/index.php?id=freeupdates#Utilities

Then install the driver "Guitar Rig Session IO Driver 2.4.23 - Mac"

http://co.native-instruments.com/index.php?id=freeupdates#Guitar_Rig_Session_IO

regards

- Oz

Reply

Answer 15

May 2, 2012 12:46 PM in response to oz-macnut

OZ, thanks for the latest tips - you're a legend.

Tried all you suggested (thanks for the rookie-proof pictoral instructions!) - no change

Also agree that it must be something to do with The Session I/O communicating with GarageBand.

I tried recording guitar through the built in line input on the mac and had no issues - perfect recording (albeit lesser quality than through the USB input).

I've downloaded the new Native Instruments Drivers Guitar Rig Session IO Driver 2.4.23 - Mac

This is the most recent one and supposedly has no compatibility issues with Snow Leopard or Lion.

Still no change.

Any thoughts?

Reply