A-NO-NE Studio

A-NO-NE Studio Services: DAW, MOTU-MAC, Metric Halo, and more

 


AES NYC 2007 Photo Album: MOTU, Metric Halo, Fxpansion, SoundToys, and more »

Winter NAMM 2007 Photo Album: MOTU, PSP, AKAI, WaveArts, and more »


A-NO-NE MIDI CC Finder Widget

About A-NO-NE MIDI CC Finder

It is difficult to memorize MIDI Continuous Control number yet you need it to program your MIDI devices such as synthesizer, virtual instrument, lighting system, etc.

This Widget let you type MIDI Continuous Control number to find its description, or find related CCs by keyword, or even finds Undefined free spaces.

Click Here to Download from Apple

A-NO-NE DAW Disk Space Calc

About A-NO-NE DAW Disk Space Calc

Calculate how much disk space needed for digital audio recording based on bit depth, sample rate, length in time, and number of tracks.

Click Here to Download from Apple

A-NO-NE Wave Length Calc

About A-NO-NE Wave Length Calc

In a studio environment where standing waves in a range can mess up your perception of the actual sound. A so-called standing wave is a resonating frequency between, e.g. 2 parallel walls which distance is the same (or even 2 or more times) as the actual wave length.

A-NO-NE Wave Length Calc will help you find the location of the offending reflection.

Click Here to Download from Apple

A-NO-NE Studio Service

A-NO-NE Studio offers

  • On Site Recording

  • Project Production

  • Studio Recording

Classical On-Site Recording Example

Live recordings for 2 CDs of Cappella Clausura

Earthworks microphones and Metric Halo hardware

Denis Leary Show Recording

  • Denis Leary and Allen Rowand of Metric Halo
  • Hiro Honshuku and Charles "C.P." Ross
  • Metric Halo Boxes and Digital Performer
  • November 10, 2007
  • THE AGGANIS ARENA, Boston

ProSoundNews

PDF Read the article on PDF

Track List

  1. Room L
  2. Room R
  3. Kick
  4. Snare
  5. Hi Hat
  6. Rack
  7. Floor
  8. OH L
  9. OH R
  10. Bass D.I.
  11. Bass Mike
  12. Guitar 1
  13. Guitar 2
  14. Guitar 3
  15. Trumpet 1
  16. Trumpet 2
  17. Tenor Sax
  18. Trombone
  19. RF 1
  20. RF 2
  21. RF3
  22. Hard Wire Backup
  23. Vox 1
  24. Vox 2
  25. Vox 3
  26. Vox 4

AES NYC 2007

Winter NAMM 2007

Welcome to the Private MOTU-MAC Party

Go TO MOTU

Motu Mac Photo Album

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

How (not) to Blame MOTU for DP Crash

Console.app

Open Console.app

/Applications/Utilities/Console.app

or use Spotlight

Console Pane If Log List Pane is now show, click the icon as shown
Crash Reporter

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.

Thread

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.

UREI Click for Mark of the Unicorn Digital Performer

Click to Enlarge

» Download UREI Clipping for Digital Performer (60 kb)

» Download AIFF files to use with application other than Digital Performer (5 kb)

» Download WAV files to use with application other than Digital Performer (5 kb)


How to Install

Copy Click Clippings folder to Home/Library/Preferences/MOTU Clippings folder then launch DP4: Click image to enlarge

Click to Enlarge Click to Enlarge

Welcome to the Private Metric Halo Party

Go to MH Web Site

Go to Metric Halo Site »
Go to Metric Halo Mailing List »
Go to Metric Halo Forum »
Go to Mobil I/O FAQ Site »

MIO on the Job

 

How to automate MIO Console Mixing Board Channel Fader from Digital Performer

How to automate MIO Console Mixing Board fader from Digital Performer
automation

Fader Automation

MIO Console Mixing Board channel fader can receive Pitch Bend MIDI information, which can be used as automation from Digital Performer.

Here is a step by step instruction to link Digital Performer to MIO Console Mixing Board channel fader


[Mute]/[Solo] Automation explained below

Interapplication MIDDI

1. You will create virtual MIDI I/O ports in DP by opening Setup > Interapplication MIDI dialog box

Interapplication MIDI Config

2. Click [Add] for Inputs and Outputs. The default name appears.

Track Assignment

3. Create a MIDI track in DP, click-open a MIDI track output assignment popup window, and select DP Output-1 as the destination.

MIDI Plug-in

4. Insert a "Reassign Continuous Data" MIDI plug-in for the MIDI track.

MIDI Plug-in Config

5. Set the source to CC7, and the target to Pitch Bend.

UPDATE:
You need to engage "Copy" mode instead of "Change" mode, or you will not see DP fader moving with the MIO fader.

MIO Config

6. In MIO Config, set the Controller input to DP Output.

That's it!

Enjoy!

 

UPDATE:
Be sure not to create MIDI Loop.  It will bring MIO Console into SWOD (Spinning Wheel of Death). Yes, I have been there!

You can automate [Mute] and [Solo] as well

Once the above channel fader automation is working, you can toggle [Mute] and [Solo] by inserting a MIDI note. For example, I found MIDI note E-1 (this is negative 1) toggles [Mute] and MIDI note G#-2 toggles [Solo] on channel 1 in the MIO Console Mixing Board.

The hardest part is to find the exact MIDI note value. I used MIDI Monitor application for this.

This text will be replaced

MIO2882 Microphone Matching List

High Sensitive Microphones which works best with Mobile I/O
~ Sensitivity c.a. 20mV/Pa recommended to use with MIO ~
Note: High sensitivity may be only needed when tracking quiet source such as classical music from distance.

The Fomula

If x = sensitivity in dBV e.g. -66dBV/microbar(.1Pa)

then sensitivity in mV is

10^(x/20) * 1000

or .5mV/microbar - to get mV/Pascal multiply by 10 which gives 5mV/Pa for the Core Sound mics.

- Joe Buchalter, Metric Halo


The list of matching microphones for MIO2882

MIOConsoleConnect and MIO FW Process Return with DigitalPerformer

While Metric Halo web site has a very good Digital Performer (DP) Tutorial, being a long time DP user and MIO user, I have a slightly different way of setting this up, and wished to share to anyone who is interested. Remember that you should set it up on your new DP project file and save it as one of your template, or even default template. That's what I did.

MIOConsoleConnect with DigitalPerformer

MIOConsoleConnect makes MIOConsoleX setting saved with your DP project. Whether you wish to save one setting per project file or one setting per sequence within single project file, the best way is to use one of the MasterFaders as the place holder.

Note: To avoid the real MIOConsoleX to keep restarting, you may wish to have it launched before you use MIOConsoleConnect in DP.

Note: For people like me who dislike floating window in general and is too used to switch applications with Cmd+Tab, MIOConsoleConnect offers Conduit Mode via its preferences, which still gives great benefits of saving MIO settings with project.

Preparation steps

This preparation steps, which will be saved as template, are to avoid later confusion and accident such as feedback loop.

  1. Open Audio Bundle (Shift+U)
  2. Click on Busses tab
  3. Click Add
    The default is Stereo pair. Even though MIOConsoleConnect does not need to be stereo, I leave it because it is easier to keep things in even numbered pairs.
  4. RENAME newly created "bus 1-2" to "MIO Dummy" to avoid later confusion.
  5. Scroll to the right end and double-click at bus 63 so both bus 63 and 64 are selected.

Instantiate MIOConsoleConnect

If you need one MIOConsoleX setup saved per project, you should use DP's V-Rack for where MIOConsoleConnect instantiated. On the other hand, I use 4 MIO boxes for mixing with MIO+DSP mix bus, and it becomes necessary to instantiate MIOConsoleConnect per sequence especially when I am mixing for album. In this case, I instantiate within each sequence instead of using V-Rack.
  1. Create MasterFader (Ctrl+Cmd+F) where you desire, sequence or V-Rack
  2. RENAME MasterFader
    This is very important for me because it is just a place holder and is not really functioning as MasterFader. I would rename it as MIOConsole
  3. Assign MasterFader's output to "MIO Dummy"
  4. Insert MIOConsoleConnect as you usually insert effect plug-in on MasterFader

If you wish to use a normal MasterFader for your analog output, you may do so by ignoring MIOConsoleConnect Master Fader

TIP: The MasterFader that holds MIOConsoleConnect, which was instantiated in a sequence, can be moved to V-Rack easily by selecting "MIOConsole" MasterFader track in Track Overview Window first then Project Menu » Sequences » Move Selected Tracks to V-Rack…

MIO FW Process Return with DigitalPerformer 5.12

Again, Metric Halo site has very good tutorial page and tutorial movie. I would like to share slightly different approach for my conveniences especially the goal is to create a template for future use. In this tutorial, the differences between 2882+DSP and ULN2+DSP will be noted when applicable.

  1. 2882+DSP only: Set Digital Output from ADAT to FW Return
  2. Open DP's Audio Bundle (Shift+U)
  3. 2882+DSP: Create 3 stereo pair of outputs and 6 mono outputs

    ULN2+DSP: Create 2 stereo pair of outputs and 4 mono outputs

    IMPORTANT: RENAME them to "Send" — To avoid feedback loop, it is very important to rename them so there will be no confusion when assigning
    NOTE: These DP outputs will be labeled DAW in MIOConsoleX
    Remember that DAW 1-2 is reserved for Analog output monitoring
  4. Under MIOConsoleX Patchbay, patch Process output to FW Return/ADAT
    Tip: Holding Opt when selecting makes result in stereo pair
  5. Back to DP, Create 4 stereo pair of inputs and 8 mono inputs, and RENAME them to "RETURN"
  6. At this point, send—return path has been established.
    • You can send the track signal to +DSP by selecting the track output
    • You can send the channel signal to +DSP
    • Audition the +DSP return signal by using AUX track
    • Print the +DSP return signal

    You could skip using AUX track by returning the signal to an audio track via Audio Patch Thru option under DP's Studio menu, which may cost your CPU usage, however.

Time Slip Mystery

The blue soundbite on the top is the source, one of the click samples for DP I created. The pink soundbite on the bottom is the printed FWReturn.

Oddly, it is ahead by 50 samples.

This project is 24 bit / 44.1k. The MIO +DSP on this test has one instance of MIOStrip with every param engaged. The mystery here is that this 50 samples offset does not change whether Plug-in Compensation is engaged or hardware buffer is set to low/high.

My Jensen ULN-2 2d

jensen Joe Buchalter handing me the first Jensen ULN2+DSP mod.

This thing sounds sweet!

My MIO Car!

My MIO Car!: Look the plate: 138 MIO!My MIO Car! - Look at the plate: 138 MIO!

 

 

That's 321,868.8 Km!!  32万1千8百68.8キロ!