grooveroom

Options > Song Information > "Reorganize Memory" ...works for me every time.

Yes and no - in my particular case i'm reconforming a session to a new picture cut, by aligning transients. And these sample-errors add up and give me ugly phase-issues when tuning in the reference track. But in the end you are right... no one will notice, when there's no reference track. It just hurts my ears while working on it. :/

Hi logicprohelpers, Short things short: when i make cuts, they don't always happen at the SPL, but are one sample off. Sometimes even the region moves, leaving a tiny gap. So.. now i have to zoom in and manually check and correct every cut-- did i miss something? Is there some hidden "make-sample-accurate-cuts"-button in the prefs? :/ I am using Logic 9.1.1 with 10.6.4 and this is getting really annoying-- does anyone else have the same problem? Thanks! RG

Well, you could build yourself a timer with Quickeys. What i mean is a Shortcut that: - hits the record Key-Command in Logic - waits 31 minutes - stops Playback (hits space).... easy as that. Hmm, i guess you could do something similar with Automator. And if you're feeling fancy, you could write a tiny apple-script that asks for the desired recording time before it starts recording.

Unpacking (into new tracks) is working for me, as long as there are no overlapping regions/duplicate tracks... it starts getting messy, when a track lives in more than one folder. On Topic: This thread got me thinking, and i found a workaround for the problem i described earlier (having to unpack all folders, when doing global reconforms) ---- 1. i move the folders (with "never move automation") 2. open the automation event list 3. link the arrange page to it (it then shows all automation as regions) 4. move the "automation regions" -- voilâ not great, but it's certainly faster than unpacking...

Oh yeah... it's really a pain. I do all my short movie-projects (up to 40 minutes) in Logic, using Region-Folders for each scene and DAMN, is it painfull, when i have to reconform anything... i'm forced to unpack all carefully sorted scene-folders in a 200++ tracks mega arrangement, make the edits (+ pray for the automation to move correctly), and finally pack the folders again... i usually create an extra project for that, because there are so many things that can go wrong... but well... i guess i HAVE to be punished somehow, for still doing Film Sound in Logic... i just love the workflow/the mixing power so much. This is getting ridiculously off topic, but: would be great if Apple decided to merge Logic & Soundtrack Pro into one program-- "Logic Post Pro" or something. -- will never happen *sigh*, here we go Nuendo.

Cubendo has Track Folders/Folder Tracks too. The main difference is: You can sort your tracks in a hierarchical way. http://www.soundonsound.com/sos/apr09/images/IT_Apr_02.jpg

There are no track folders in Logic, but you can assign tracks to a group and show/hide this group(s) via the group preferences window (Logic 9). Or: Create region folders and delete the (now) unused tracks in the top level arrange window.

Hi fellow logicprohelpers, Lately i've been wondering whats behind the Fade-Values in the Inspector-Tab-- ticks? Samples? Subframes? Do these Values give different results with different samplerates/framerates? When looking at the waveform in Sample-Editor, a fade of "1" seemed to be 38 samples long in a 48khz/25fps project. ... but that didn't get me anywhere, bcause what i would like to do, is to create fades that are exactly one, two, three... frames long, and with 38 samples a 1-frame-fade would need a fade-value of 50,5263... (=48000/25/38) which i can't insert in the property-inspector. I'm not sure if i measured the 38 samples correctly... Could someone please enlighten me: what math is behind these Fade-Numbers? Tanks! grooveroom

Go, play with the Quickeys Demo: http://startly.com/products/quickeys/mac/4/

Hi there! The Eucon 2.5.2.65567 driver crashes my Logic install when it's starting up ("starting up eucon support" ... -> crash). This happens with Logic 8.02, 9.02 and 9.1. The MIO Console/Mixer works fine with Eucon. I already tried crashing Preferences & reinstalling the Eucon Drivers with no success -- would be great, if someone could give me a hint here, because i don't understand that ugly crashlogs. Thanks! Here's the crashed thread: Process: Logic Pro [898] Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro Identifier: com.apple.logic.pro Version: 9.1.0 (1697.23) Build Info: Logic-16972300~1 Code Type: X86 (Native) Parent Process: launchd [154] Date/Time: 2010-02-05 10:12:06.002 +0100 OS Version: Mac OS X 10.6.2 (10C540) Report Version: 6 Interval Since Last Report: 240 sec Crashes Since Last Report: 4 Per-App Interval Since Last Report: 376120 sec Per-App Crashes Since Last Report: 13 Anonymous UUID: 6AF9C157-005A-43AC-8B4E-53F2A329D38F Exception Type: EXC_BAD_ACCESS (SIGABRT) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x90395732 __kill + 10 1 libSystem.B.dylib 0x90395724 kill$UNIX2003 + 32 2 libSystem.B.dylib 0x9042898d raise + 26 3 libSystem.B.dylib 0x9043e9d9 __abort + 124 4 libSystem.B.dylib 0x9043ea55 abort_report_np + 0 5 com.apple.logic.pro 0x00402689 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3963097 6 libSystem.B.dylib 0x9039a9bb _sigtramp + 43 7 ??? 0x0000000a 0 + 10 8 com.apple.logic.pro 0x006e9950 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 7007136 9 com.apple.logic.pro 0x0040329f std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3966191 10 com.apple.logic.pro 0x001e776e std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 1755582 11 com.apple.logic.pro 0x001eb33b std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 1770891 12 com.apple.logic.pro 0x0062e873 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6240963 13 com.apple.Foundation 0x97e5e1c7 _nsnote_callback + 176 14 com.apple.CoreFoundation 0x91cfd9a9 __CFXNotificationPost + 905 15 com.apple.CoreFoundation 0x91cfd3da _CFXNotificationPostNotification + 186 16 com.apple.Foundation 0x97e53094 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128 17 com.apple.Foundation 0x97e60471 -[NSNotificationCenter postNotificationName:object:] + 56 18 com.apple.AppKit 0x9055173a -[NSApplication _postDidFinishNotification] + 125 19 com.apple.AppKit 0x9055164a -[NSApplication _sendFinishLaunchingNotification] + 74 20 com.apple.AppKit 0x906a8595 -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 274 21 com.apple.AppKit 0x906a81b5 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 101 22 com.apple.Foundation 0x97e93404 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511 23 com.apple.Foundation 0x97e931c8 _NSAppleEventManagerGenericHandler + 228 24 com.apple.AE 0x9532bf3a aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166 25 com.apple.AE 0x9532be39 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43 26 com.apple.AE 0x9532bd46 aeProcessAppleEvent + 197 27 com.apple.HIToolbox 0x96fde2a1 AEProcessAppleEvent + 50 28 com.apple.AppKit 0x90521d02 _DPSNextEvent + 1420 29 com.apple.AppKit 0x90521306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 30 com.apple.AppKit 0x904e349f -[NSApplication run] + 821 31 com.apple.prokit 0x00fc5a01 NSProApplicationMain + 326 32 com.apple.logic.pro 0x0002a729 DummyConnection::DummyConnection() + 197 I'm running 10.6.2 on a C2D Imac.

It is in the About Screen--- Logic Pro -> About.

Here i am with one of those workflow-questions again... Is it possible to make an automation node snap&stick to region boundaries? When i lengthen a region, i always have to grab and move the automation with it manually, in (an) additional step(s)-- that can get really ugly, when there's more then one automation-parameter. My workaround up till now, is to 1. cut the edge of the region of, 2. move the tiny new helper region(with all automation) to the desired bar, 3. delete that helper region 4. finally drag out the region boundary I know there has to be a better way to do this! cheers, grooveroom

There's some misunderstanding: I don't have 101 regions lying there, waiting to be faded-- yes, that's pretty easy with selecting them all + inspector. I want to create the fades while working on the individual region and often need the same Length+Curve Parameters for smooth transitions (doing post for short films-- yes, with logic, and my protools is crying ). But now i know how it works: I just made some QuicKeys Macros, that fill the Inspector with the desired numbers. When i got some more time, i'll try a copy/paste macro (storing the ctrl+c values in variables and sending them out to logic again). That'll be a great time saver!

Yes, in the inspector- that's how i'm doing it right now- and still want to get faster. So... there is a (lenghty) way? Could you pleeease explain it? Perhaps i can build a Macro for it. thanks!