Jump to content

balancedcreativity

Member
  • Posts

    60
  • Joined

  • Last visited

balancedcreativity's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I know that problem well, and there is definitely a sync issue happening with your MIDI timecode. When you open Settings > Sync > Audio, do you see the sample rate or deviation changing on playback? Do you have external sync engaged in Logic? Ie. Is the area where the bar numbers are listed in blue?
  2. I don't know if you had posted an update on this… but thought I'd check! I'm looking for the coveted Environment session that has all the different hardware synth names, etc. I'll see if it pops up anywhere else. Thanks!
  3. An offline bounce in Logic with 'Include audio trail' results in a bounce that continues with no end in sight... until manually interrupted (Command - period)... I suspect that it's because I'm using the UAD Ampex ATR-102 plugin on my master output, which adds hiss... and Logic see this as an audio signal and keeps bouncing it as an audio trail... Anyone else having this issue? I'm going to post this on the UAD forum as well, just to see if there's anyone else experiencing the same.
  4. I think the issue is when you start using other non-Logic software plugs... not all of them seem to be compensated correctly, which makes for an unpredictable usage scenario. Hit & miss ain't fun for laying down tracks...!
  5. Just a suggestion... It may take longer to import someone else's multi-instrument setup into your template than setting it up from scratch. The aux assignments don't always carry over to your session correctly, and that's MOST of the setup. My 2-cents.
  6. I just posted this on the Apple Support forum as well... After much troubleshooting, the cause of this error in my setup was the Highpoint RocketRaid 2314 eSata PCIe card. The Highpoint RocketRaid driver is included in OS X 10.8 with no additional drivers / installers to run. However, it isn't compatible with the old driver when upgrading the kernel (ie. 10.6 - 10.8) I was bouncing to an external drive connected through eSata to the RocketRaid PCIe card... error message. Time Machine backup connected through eSata... error message. The drives were being dismounted rudely, or losing connection momentarily and reconnecting, resulting in the error messages. Here are the instructions from Highpoint tech support to manually uninstall the embedded driver, and then reinstall the old Snow Leopard driver for use in Mountain Lion (10.8)... which works as it's suppposed to. 1. Go the folder System > Library > Extensions >, look for the file HighPointRR.kext and delete that file. 2. Second, download the driver from the link below, then run the Un-install script to remove any previous installed driver. http://www.hptmac.com/productfiles/bios_driver/hptrr-mac106-driver-v11... Then re-install the driver, but do not reboot or restart the system. 3. Third, download the webGUI from the link below. And run the un-install script to remove any previous installed web GUI. http://www.hptmac.com/productfiles/WebGUI-Mac-v168-091120.dmg Then re-install the web GUI and reboot after installation is complete. Once the system has booted up, open a browser and type URL to log into web GUI. http://localhost:7402 User Name: RAID Password: hpt I hope that this helps someone!
  7. Agreed, real world ALWAYS trumps theory Perhaps JBOD was the wrong term to identify what I was referring to.... I meant having multiple drives, no RAID config, with each drive mounting. It means for more organizing & spreading the libraries out in an efficient manner... but great performance increase all around. I'll go the SSD way when the drive sizes are much larger, and don't cost a kidney Cheers, Roy
  8. I believe it's because of multiple drive heads operating independently, not relying on a Raid controller to locate the corresponding info on each striped drive. When I have some time, I'll look up the tech resources that I gleaned this nugget from. I was running my OS X & apps from an SSD, project drive on eSata, and raid 0 for my sample libraries over 2x 1TB drives, and since moving to multiple drives JBOD, I'm able to run my sessions at a lower buffer rate, and decreased overload msgs. And that was before I integrated Vienna into my setup. Now, I'm running sessions at 64-128 buffer rate, NO CPU overload msgs (unless toggling between multiple screen sets with video opened), and core distribution within Logic AND outside Logic is balanced. Using Play, NI, LASS, Omni, and tons others that I wasn't able to use before. Also, 32-bit bridge: gone forever. Needless to say, after 14 yrs of programming, waiting for the technology to catch up and work within my budget, I'm extremely happy!
  9. Bump on an old post... Having personally upgraded from Snow Leopard to Mountain Lion, Snow Leopard is DEFINITELY a much smoother experience. However, the downside is that the further along you go, more apps / libraries / plugs will be geared towards ML with less support as time progresses. I'm willing to live with some of the quirks of ML as they're not affecting my workflow. Based on the machine you have, I'd recommend Snow Leopard over Mountain Lion. Other things you can do to get the most out of your machine is max out the RAM for your machine. You'll need to see what your motherboard can accommodate. OWC is great for affordable RAM & drives. RAID 0 will NOT improve performance for sample libraries. There are several threads on the technical aspects of why this is the case. You will see better performance by having your libraries spread out over multiple drives, than you will in RAID O. Not just what I've read, my personal experience having run both setups over the last year. I would highly recommend getting Vienna Ensemble Pro and running Vienna server with Logic. I am running a TON of libraries with Vienna being the shell outside of Logic, and I'm basically using Logic as A MIDI player, with the odd library engaged. Takes time to set up, but WELL worth it in the end. Logic still has quirks when distributing processes over multiple cores... resulting in a single core spiking, which halt the software and returns the CPU overload message. Here's how I would recommend setting up your system: Drive 1: OS X & apps (WD Black Caviar or an SSD, and make sure that you have enough space to never come close to the 15-20% remaining point. Drive 2: Projects / sessions / scratch drive. Drive 3 & 4: Sample libraries spread out over the 2 drives. If your budget can afford it, get yourself a Highpoint RocketRaid Sata PCIe card, a Kingwin or Wiebetech external drive enclosure in a JBOD setup, and run your sample libraries over 4-5 drives externally. They don't have to be huge drives, because you're libraries will be spread over multiple drives. If after a few years you find that things are starting to slow down a bit, buy yourself a Mac mini and dump a few libraries to that computer, and run Vienna server (each copy comes with 3 licences) on you mimi, and use it as an external synth.... all over CAT 5 or CAT 6 cable!! As always, make sure EVERYTHING is backed up. Time Machine is great when it works... but I feel more secure having a cloned drive or incremental backup of everything I would Need to restore.... OS X drive, sample libraries, projects, up-to-date installers. You could use a drive doc for these, and slip OEM drives into it like the old 3.5" floppy disks That's my recommendation. Take it, leave it... it's your system, and you gotta go with what's going to work for you. Now, time to work!
  10. Bump on this post.... I just started receiving this error message after updating my OS to Mountain Lion. Just doing a simple offline bounce in Logic, 3 plugs on one track, 2 on the output master. Any solution for this?
  11. I'm all ears to both suggestions... or maybe they're the same...?
  12. Are you recommending bouncing out stems and mixing in another session to mix, and keeping the midi session separate?
×
×
  • Create New...