Motu Mac Photo Album

MOTU-MAC L.A., Jim Watson attacks Boston 2007

How (not) to Blame MOTU for DP Crash

	Open Console.app /Applications/Utilities/Console.app or use Spotlight
	If Log List Pane is now show, click the icon as shown
	Find LOG Files → ~/Library/Logs → CrashReporter Find the log titled by "Digital Performer_year_month_date_time..." Make sure you locate the correct one identified by the date and the time.
Here is a header of a crash log sample: Process: Digital Performer [692] Path: /Applications/_Music/Digital Performer 7.1.app/Contents/MacOS/Digital Performer Identifier: com.motu.DigitalPerformer Version: 7.1 (7.1) Code Type: X86 (Native) Parent Process: launchd [162] Date/Time: 2010-01-20 00:44:36.200 -0500 OS Version: Mac OS X 10.6.2 (10C540) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000005631314e Crashed Thread: 15 The crash log header above indicates the crash occurred at Thread 15. Scroll down and locate Thread 15. This example shows the crash was caused by a 3rd-party AU plug-in.
How to read Kernel Panic Log Instead of ~/Library/Logs/CrashReporter explained above, KP log is kept under root directory: /Library/Logs/DiagnosticReports/kernel_year_date_time_<hostname>.panic Note: above example is under Snow Leopard. Here is a sample log block: Interval Since Last Panic Report: 4270934 sec Panics Since Last Report: 3 Anonymous UUID: 41BB49D1-9291-4896-9425-6B7C7D4698F3 Sun Jan 10 01:40:23 2010 panic(cpu 1 caller 0x2a7ac2): Kernel trap at 0x56803fe9, type 14=page fault, registers: CR0: 0x8001003b, CR2: 0x56803fe9, CR3: 0x00100000, CR4: 0x00000660 EAX: 0x08e7db00, EBX: 0x08e65100, ECX: 0x312f0000, EDX: 0x08e7de00 CR2: 0x56803fe9, EBP: 0x5bd63ad8, ESI: 0x07cf7780, EDI: 0x0085ff18 EFL: 0x00010246, EIP: 0x56803fe9, CS: 0x00000008, DS: 0x01e60010 Error code: 0x00000011 Backtrace (CPU 1), Frame : Return Address (4 potential args on stack) 0x5bd638d8 : 0x21b2bd (0x5cf868 0x5bd6390c 0x223719 0x0) 0x5bd63928 : 0x2a7ac2 (0x591c30 0x56803fe9 0xe 0x591dfa) 0x5bd63a08 : 0x29d968 (0x5bd63a20 0x246 0x5bd63ad8 0x56803fe9) 0x5bd63a18 : 0x56803fe9 (0xe 0x48 0x5bd60010 0x230010) 0x5bd63ad8 : 0x5d30b821 (0x8e65100 0x0 0xffff 0x15f) 0x5bd63af8 : 0x4fcc12 (0x8e65000 0x85ff18 0x1 0x0) 0x5bd63b18 : 0x50cc50 (0x8e65000 0x85ff18 0x5bd63b48 0x4fcf95) 0x5bd63b48 : 0x50cdc4 (0x7cf7780 0x0 0x1 0x0) 0x5bd63b68 : 0x4fcc12 (0x7cf7780 0x0 0x1 0x1) 0x5bd63b88 : 0x4fcc2d (0x7cf7780 0x0 0x5bd63bb8 0x4fcc12) 0x5bd63ba8 : 0x52ef30 (0x7cf7780 0xffff 0x7cf7a44 0x4fcc2d) 0x5bd63bc8 : 0x52ef63 (0x7cf7a40 0x246 0x5bd63c08 0x917a3f0) 0x5bd63be8 : 0x4fcc12 (0x7cf7a40 0x0 0x1 0x1e) 0x5bd63c08 : 0x4fcc2d (0x7cf7a40 0x0 0x5bd63c58 0x0) 0x5bd63c28 : 0x2830b4 (0x7cf7a40 0x917a3f0 0x1e 0x5bd63c58) 0x5bd63c78 : 0x21d676 (0x8812698 0x75fd5a0 0x817b584 0x1) 0x5bd63cb8 : 0x2107f7 (0x8812600 0x12 0x5bd63d18 0x20f258) 0x5bd63d18 : 0x21db45 (0x8812600 0x10000 0x0 0x210588) 0x5bd63d48 : 0x23f12d (0x5bd63d6c 0x24 0x91bc944 0x0) 0x5bd63d98 : 0x214d2c (0x917a3f0 0x1 0x1 0x221959) Backtrace continues... Kernel Extensions in backtrace (with dependencies): com.digidesign.mbox2.driver(8.0.3f1)@0x5d306000->0x5d325fff dependency: com.apple.iokit.IOAudioFamily(1.7.2fc1)@0x5c316000 dependency: com.apple.iokit.IOUSBFamily(3.8.5)@0x5b620000 dependency: com.apple.driver.AppleUSBMergeNub(3.8.5)@0x5bb63000 BSD process name corresponding to current thread: coreaudiod

Easy preparation for CD burning from Digital Performer project

Digital Performer Tip: Easy Preparation for CD Sequencing

I often bounce CD project which contains several selections into one CD long SDII file then slice it up into multiple regions so Roxio Jam will read each selections as individual track ID when played on audio CD player.
Note that if your CD burner software does not support Region and/or Split Stereo SDII format, you'd need to export each region into AIFF file.

I am going to explain as if 2 track recording into DP file is prepared for CD burning without significant editing.

Note: the term "Selection" here is such as an individual song, a movement of a Sonata, and so on.

1) While tracking (or playing back after tracking), hit Ctrl+M to mark the selections.

Note: If you bounced from sequence which was built from multiple chunks within DP, do use existing marker for conveniences. Otherwise, you will need to do fine adjustment once tracking has stopped because Ctrl+M while running can not be that accurate.

2. Edit Marker names so they will identify each selection.

3. Have Marker window and Sequence Editor window side by side.

4. Using Marker window, locate the first marker which is the beginning of the first selection.

5. Hit F5 key, which marks the region edit start point.

6. Using Marker window, locate the second marker which is the ending of the first selection.

7. Hit F6, which marks the region edit end point.

8. Click on the track name of the target track so the first selection (Track-1) will be highlighted.

9. Hit Cmd+Y so the selection becomes an individual Soundbite (region).

10. Rename the Soundbite (regions) according to the selection name.

Note: Prefixing by number is strongly recommended so porting into a playlist will automatically sort as it appears in your project sequence.

11. While the wiper is still parked at the end of the first selection, hit F5 key so this location becomes the beginning of the next selection.

12. Go back to Step 6.

13. Delete unused regions within the SDII file you have been editing so imported playlist will contain only the numbered selections, such as 01.Track-1, 02.Track-2, and so on.

Note: Remove Unused Soundbite command will not remove junk regions. Delete command is necessary.