Discussion in 'Microphones (live or studio)' started by chris lannon, Apr 10, 2001.

  • AT5047

    The New AT5047 Premier Studio Microphone Purity Transformed

  1. chris lannon

    chris lannon Guest

    Here's a thread for tips..this one from Les at Motu.

    >>Dither in the Audio menu only applies to audio operations that convert 24-bit to 16-bit audio. Examples of this may include converting 24-bit to 16-bit audio, computing crossfades, processing 24-bit audio through Premiere effects (which is a 16-bit architecture), or tranferring 24-bit audio to a sampler.

    The rule of thumb: leave it checked by default. If your project is entirely 16-bit, it has not effect (ie. Dithering does not take place during 16-bit playback). If your project is 24-bit and you want dithering in any of the above operations, you'll want it enabled. The alternative is that the above opererations will truncate 8-bits (24 bit
    to 16 bit) of your audio if Dither is disabled.

    Best regards,



    Les Quindipan

    Mark of the Unicorn, Inc. (email) (web)<<
  2. chris lannon

    chris lannon Guest

    Here's a tip/expanation

    >>From: Paul Johnson <>
    Subject: Re: [MOTU-MAC] Managing Soundbites and soundfiles, by removing,
    deleting or compacting

    Related Notes:

    As was just pointed out, a Soundbite is NOT an actual file--it is a region
    marker within a sound file on your disk. A single sound file can have dozens
    or even hundreds of soundbite regions (take a look at a multi-soundbite file
    in the sample editor in DP and you'll see what I'm talking about.)
    If you delete the last used soundbite from a soundfile, DP will ask you if
    you wish to delete the file or leave it. You can't (that I know of) delete
    unused sound files from within DP any other way than by deleting the last
    used region (soundbite) from a soundfile and then asking DP to toss the
    region-less soundfile. DP does not ever check the project's Audio Files
    folder for unused sound files. You have to keep things tidy as you go or you
    can end up with unused audio files that are in a projects Audio Files folder
    but not used in the project. So opting to NOT delete the file when removing
    the last soundbite from it, will leave an unassociated sound file in that
    project's Audio Files folder (assuming that's where the file was imported
    All of this is obviously destructive--there's no getting regions/soundbites
    back if you delete them except for remaking them from the original sound
    file--which is also not possible if you delete THAT as well. So do be
    So, to recap: deleting soundbites (regions) does not reduce disk usage
    unless it is accompanied by audio file deletion. Specifically, since
    soundbite regions themselves are not audio data but only markers taking up
    no disk space, deleting a soundbite will not free up any disk space because
    the audio data is not actually deleted. However, "compacting" DOES remove
    data and free up disk space. Here's how that works:
    Unlike deleting a soundbite which only removes the region markers from an
    audio file, or deleting a sound file which removes EVERYTHING including all
    soundbite regions within the file, COMPACTING removes the sound file's
    unused parts that are between the soundbites (soundbites indicate a used
    area of the file). This is also destructive, so once you compact, you won't
    be able to grab the edge of a soundbite and drag it outward to reveal the
    previously hidden file content--because that's what gets deleted in
    compacting. For this reason, compacting is a good idea if for instance you
    have a vocal take the full length of a song, but are only using half of one
    verse or something. It's not so good for a heavily-edited track with lots of
    individual soundbites, because chances are, you're going to want to
    edge-edit something down the line and won't be able to because the
    in-between data is now GONE die to compacting.
    For instance, just last week I nearly compacted a set of files used to make
    up a vocal track in a song. A day later, I happened onto the idea of
    doubling the vocal line in a prechorus section, and I had the multiple takes
    to be able to do that--had I compacted those takes, I would NOT have had the
    alternate material I then used to double the main vocal track.
    So, generally, I consistently delete unused soundbite regions as I edit,
    just to keep thing tidy. But I seldom compact, and then only selectively
    (just the tracks that will give back the most file space and the least risk
    of removing data that I might want later) and only after backing up
    Hope this helps clear things up. This is just my working methiods, others
    may have other/better ideas.<<
  3. chris lannon

    chris lannon Guest

    Here's a tip

    From: David Das <>
    To: Motu-Mac List <>
    Date: Sunday, November 19, 2000 4:14 AM
    Subject: [MOTU-MAC] Das's Universal Guide to Fixing Problems With Your MOTU

    In response to a whole lot of e-mails that I see and get trying to get to
    the bottom of mysterious Digital Performer/MOTU system problems, I've
    compiled the following list of troubleshooting tips to help you get running
    smoothly. It's mostly written to resolve crashing problems, so if you're
    having problems editing your MIDI, this won't help you much. Keep it at hand

    | version 1.0 (9/25/00) |


    These are listed roughly in order of magnitude. If you have time to
    experiment, try one step at a time, and you may save yourself some recovery
    time. If you're desperate, go down the list and do them all!

    1. Make sure you're running the latest version of everything -- Performer,
    Digital Performer, MOTU Audio System (MAS), FreeMIDI, and anything else
    you're running. Generally every bug fix release MOTU has released (e.g.
    2.51, 2.61, 2.71) has increased stability for the majority of users. So
    trust them.

    2. Check Performer/Digital Performer's memory allocation. (Go to the Finder,
    and get info on the actual P/DP application.) MOTU's factory ideal
    allocation is a little low, and if you've added plug-ins to MOTU's default
    plug-ins, you'll need to up it some. However, be careful not to give it too
    much. I've never seen a system need more than about 40 megs. If you give it
    too much, you'll rob memory from the MOTU Audio System (MAS), which is a
    separate batch of memory that DP needs to run properly. (MAS's allocation
    can be viewed within DP in the Studio Size dialog box.) Another thing to
    check is the Memory window within DP -- check that it has at least a few
    megs free at all times. If not, go back to the Finder and increase the
    allocation. If there's more than 10 megs free, that's probably too much.

    3. Check your audio clock source (in DP). If it's not set correctly, you can
    get audio playing at weird rates, or clicks and pops in your audio.

    4. Go into DP's Hardware Config and check your buffer setting. 1024 is the
    default; lower than that can improve performance but is harder on your
    processor and can potentially cause pops and clicks in your audio. If you're
    having those kinds of problems, raise the buffer some.

    4. Try switching off the MOTU Audio System (DP Basics Menu). See if your
    problems still persist.

    5. Alternately, you can try running your audio through another driver; if
    you normally use a MOTU interface (2408, 1224, etc.) then you usually have
    it set to PCI-324. Try running your audio through the Sound Manager to see
    if it cures your problems. (To do this, go into the Hardware Config dialog
    box in Performer/Digital Performer.)

    6. Go into your Sound control panel and make sure you haven't chosen the
    PCI-324 for either your input or output. According to several sources, the
    driver isn't written very stably and can cause crashes. It seems to be
    particularly bad when Bitheadz software is involved in the loop.

    7. Go to the Finder and trash some of the MOTU-related prefs. Be advised you
    may lose a few of your preferences (sorry, had to say it -- idiot check).
    Trash any of these files that you find: Digital Performer Preferences,
    FreeMIDI Preferences, FreeMIDI Setup Prefs, FreeMIDI Softsynth Prefs, MOTU
    Audio System Prefs, MOTU 324 Prefs, etc.

    8. Rebuild the Desktop. This can cure some file-related issues. (Restart
    your Mac, and hold down option and command until you get the dialog box that
    asks if you want to rebuild the Desktop. Click yes.)

    9. Try zapping the PRAM of the Mac. Go to the Finder, restart, and hold down
    command-option-P-R simultaneously. Hold it down until the Mac has sounded
    its startup chime three times. Then release and allow the Mac to boot

    10. Check your hard drive with a disk utility like Disk First Aid (included
    free with all Macs from Apple), Norton Utilities, or Techtool Pro. It's
    always safe to follow their recommendations to repair stuff that they find
    wrong on your hard drive.

    11. Defrag your hard drives, using a utility like Norton Utilities or
    Techtool Pro. Be aware that Techtool has a tendency to mess with some
    invisible authorization files, and you may need to reauthorize some of your
    software. A heavily fragmented hard drive can potentially cause clicks and
    pops in your audio.

    12. If you're having problems opening one particular file, first try opening
    DP first and choosing Open from within DP (not just double-clicking the file
    from the desktop). It's worked more than once for me. If that doesn't work,
    try opening a completely new DP file, then trying to Load (File menu) the
    chunk(s) from the problem file into a fresh file. Sometimes this can get you
    in to a corrupt file. If you do get in, immediately save a fresh copy of it!

    13. Another tip for problem files that don't open: drag the problem file's
    Audio Files folder to the trash (but DON'T EMPTY TRASH!), then see if it
    will open. If it does, chances are that you may have a corrupt soundbite in
    that Audio Files folder. Create a new Audio Files folder, and then manually
    drag a few audio files from the trashed folder into the new Audio Files
    folder, and see if it'll open. Repeat as necessary.

    14. Pull out some/all of the plug-ins you've added to DP (they're in System
    Folder-->Extensions-->MOTU-->Plug-ins). Sometimes they can cause weird
    problems. AutoTune, Pluggo, and other third-party software has at various
    times caused weird crashes within DP. Once they're removed, reenter DP to
    see if your problems persist. You may also want to pull out Unity, Retro,
    Tokyo, etc. if you run them. (To disable them, go into FreeMIDI, pull up the
    Preferences screen, and disable their check boxes. Quit everything and

    13. Reinstall your MOTU software (P/DP, FreeMIDI, MAS, USB software driver,
    etc.) This is a real pain, and I've only once ever encountered a situation
    where it fixed my problems, but it's included in this list to help you if
    you get that stuck.


    This checklist definitely won't solve every problem; it's just intended to
    help you step through basic things you can try.

    Post to the MOTU-Mac list, hosted by Topica ( Explain your
    problem carefully, and describe your system in detail (type of computer,
    amount of RAM, programs used, audio and MIDI hardware involved). Make sure
    to describe the circumstances under which you're having problems, and list
    things you've already tried (this saves time).

    You can e-mail MOTU's tech support (, but be aware that
    they usually take a few days to get around to answering you.

    You can call MOTU's tech support phone line (617-576-3066) during business
    hours Monday through Friday. It's usually busy, so find a phone with
    automatic redial, and you can usually get through eventually and have a live
    person help you. Try and troubleshoot as much as possible before calling
    (i.e. use the steps above) to save yourself some long-distance time on the

    MOTU's web site ( has a large library of technotes, and so does
    the user-run Unicornation site ( Check both of them
    for tips and tricks also.


    In the most extreme case of problems that can't be solved, take a drive you
    can erase (I keep an extra partition on one of my hard drives that I don't
    use regularly), and reinitialize it using Apple's Drive Setup. Install a
    fresh copy of your system software from your system CD. If you're running
    system 9 or above, immediately run the Software Update control panel and
    update all your system software. Then install all the MOTU stuff, being
    careful to observe all the nitpicky warnings, like keeping AppleTalk and
    File Sharing off.

    If problems persist after this, there's a good chance you might have some
    kind of hardware defect.

    Hope that helps somebody!

    David Das -- Nashville, TN -- --
  4. chris lannon

    chris lannon Guest

    posted March 30, 2001 12:26 PM

    subspace says:                 

    It took me awhile to figure out, but once I did, it made mixing much easier. I thought I'd share it in case I'm not the only one who didn't know about this...
    Those little red peak indicators on the channel meters do not indicate clipping. They're simply telling you that if you assign that 32 bit signal to an output that converts back to 24 bit integer, the signal would clip. What the hell does that mean? Your individual channels can blink red all the time and as long as you reduce the master fader that they're assigned to and keep it out of the red, no clipping will occur. The only thing that can clip are the 24 bit physical outputs or a 16/24 bit integer recording to disk. As long as the signal stays in the 32 bit floating point program, you're safe.
    I used to re-adjust all my faders if I was lighting the channel clip thinking I was out of headroom. Now I'll put a trim plug on that channel and crank it up, that's why trim's meters go to +20. Just make sure you reduce the final output fader to keep it's clip light off when the signal exits the 32 bit realm for either monitoring or recording to disk.
  5. chris lannon

    chris lannon Guest

    posted March 17, 2001 05:18 PM

    kid says:                 

    I downloaded these plugins (Compressor Bank, Filter Bank) and tried them out with Free
    ProTools. Those of you who have not heard these plug ins yet should do yourselves a
    favor and sample them immediately. They sound amazing and most of all require very little CPU power. Now the problem. They are not available for MAS Digital Performer. I
    have emailed Mc DSP about this and was informed that they are tallying up requests for their products to decide which market to go after next. I urge every MAS user to contact MCDSP to request support for MAS. This to me is exactly the type of plug ins needed for DP. The Bomb Factory stuff seems rather interesting also but have heard it will require much horsepower to run. Anyway check them out and support our platform. The web site is
  6. chris lannon

    chris lannon Guest

    For dual macsters

Share This Page