Jump to content

paboblaustein

Member
  • Posts

    13
  • Joined

  • Last visited

paboblaustein's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. is this true? i use hyperdraw for all automation, and since i do changes to picture and automation can't be smpte locked, it's rendered useless. and now i'm using takes for audio...but unable to use hyperdraw? just verifying this is true and wondering if there's any workaround...
  2. Check your activity monitor...I get that error when Logic creeps towards it's 4GB limit in Virtual Memory. Even at 3.5 I start getting errors.
  3. RME HDSPe MADI card running to an Aurora Lynx 16. Any other equipment connected? MIDI control surfaces, keyboards..? It would help if you can list all your equipment in your signature: Read Me Before Posting - Forum Guidelines (#5) Aiee! Where is my board etiquette! Got an APC40 hooked up usb, a Yamaha CP33 going into the RME, a slew of external hard drives...but nothing that has changed since I started this incessant crashing. And the Kontakt reload bug is weighing heavy upon me, as well. Canopus firewire box putting out vid. Running Logic 9.1.1 on 10.5.8.
  4. Nope running in plain 'ol 32 bit. RME HDSPe MADI card running to an Aurora Lynx 16.
  5. I lose too many plugs to go 64 bit. Plus, isn't the limit once you get close to 4 GB?
  6. I'm running Kontakt in Logic as well as in VE Pro on the slave. Do you suspect it's a conflict between Kontakt (using the memory server) and VE Pro in Logic? Or Kontakt in VE Pro on the slave? Why do you suspect that?
  7. I've easily had 500 crashes in a year. I crash 20+ times a day lately. Rewire is just Ableton. All programs are up to date. But I crash even when not using Ableton.
  8. Getting lots of memory errors, but I've streamlined things hugely with memory...Logic is only using less than 2GB physical ram. The virtual memory is hovering between 3.5-3.75GB. I know that may be part of the problem but...thought maybe someone who can read crash logs might be able to give me some insight on what might be causing so much trouble. Here's one: Btw- I'm using a 2009 8 core 3.2 ghz w/16 GB RAM. Using VE Pro heavily to a slave mac mini (which is running like a champ). And the crashes come at completely random and different times, sometimes in the middle of something, other times when I try to save (this happens a lot). Any insight is greatly helpful. Thanks! Process: Logic Pro [201] Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro Identifier: com.apple.logic.pro Version: 9.1.1 (1697.53) Build Info: Logic-16975300~1 Code Type: X86 (Native) Parent Process: launchd [99] Interval Since Last Report: 20678499 sec Crashes Since Last Report: 494 Per-App Interval Since Last Report: 10021469 sec Per-App Crashes Since Last Report: 1 Date/Time: 2010-09-29 16:38:31.966 -0400 OS Version: Mac OS X 10.5.8 (9L31a) Report Version: 6 Anonymous UUID: 78B8248E-643D-4E4B-8AD0-D72876DE53E7 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Crashed Thread: 27 Thread 27 Crashed: 0 libSystem.B.dylib 0x902b1136 __semwait_signal_nocancel + 10 1 libSystem.B.dylib 0x902aa013 usleep$NOCANCEL$UNIX2003 + 61 2 libSystem.B.dylib 0x902c162e __abort + 109 3 libSystem.B.dylib 0x902c168a _cproc_fork_child + 0 4 com.apple.logic.pro 0x00405649 std::basic_ostream >& TraceOutContainer(std::basic_ostream >&, CEvs, char const*, int) + 3974297 5 libSystem.B.dylib 0x902412bb _sigtramp + 43 6 com.apple.logic.pro 0x00127a18 std::basic_ostream >& TraceOutContainer(std::basic_ostream >&, CEvs, char const*, int) + 968808 7 com.apple.logic.pro 0x0012891b std::basic_ostream >& TraceOutContainer(std::basic_ostream >&, CEvs, char const*, int) + 972651 8 ...le.music.apps.MAAudioEngine 0x02ce8a49 MD::ReadPlaybackFiles(int) + 1177 9 ...le.music.apps.MAAudioEngine 0x02cea5b5 MD::CallReadPlaybackFiles(long) + 37 10 ...le.music.apps.MAAudioEngine 0x02d03188 GetCurrentCoreAudioDeviceNameFromUserDefaults(signed char) + 17752 11 libSystem.B.dylib 0x90206155 _pthread_start + 321 12 libSystem.B.dylib 0x90206012 thread_start + 34
  9. I'm having the same problem. And now I'm crashing quite a bit. No chance to go back to a previous project. Anyone have a solution or at least a reason why this is happening? I am using Play. I've tried pulling that, but I'm working in a project I can't abandon and it didn't fix it. Thanks! Setup: Dual Core 2.66 Mac Pro, 10.4.11, Logic 8.0.1, FF800
  10. I'm getting the same thing. When running Plogue (doesn't take much loaded into Plogue at all) I instantly get CPU spikes and overloads resulting in clicks, pops and error messages. I heard it's because Rewire can only make use of one core...so all my dreams of tearing the roof off Logic's RAM limit bumped right up against Rewire's CPU limits and my Pogue dreams got flushed right down the Bidule. It should be noted that turning off 'multiprocessor support' in Kontakt's prefs lightened the load on the CPU's. But I'm desperate to hear from anyone successfully loading up Plogue and piping it into Logic without overloading a core. Is there another program besides Rewire that isn't hampered by the single core problem that can be used to pipe in audio/midi?
  11. Hello all on this board... I have been using a trusty Roland EV5 expression pedal for many years, and it has always done me well. However, lately I've been finding that the resolution of the input into Logic seems a bit...stepped. It doesn't create as smooth of curves up and down as I would like and on certain patches, it sounds downright jittery, causing me to spend time smoothing out those swells so they sound natural. So my question is: has anyone upgraged from the EV5 to something they thought was better? I tried a Rocktron and hated it. It had less depth in the angle than the EV5 and it stood too tall off the ground (only have so many inches to spare under my desk). Suggestions for pedals that give higher resolution in Logic? Line6 EX1? Yamaha FC7? EV7? Boss FV-500H? Gracias, mi amigos.
×
×
  • Create New...