CC 2014 H.264 + audio (w/ GPU and Multiprocessing)

15" Late 2013 rMBP, 750m, 2.3 i7, 16GB
I so understand why Adobe took the H.264 codec out of CC 2014 and has directed us to AME. I'm not complaining about that. Todd Kopriva has a good write-up here: http://blogs.adobe.com/aftereffects/2014/06/adobe-media-encoder-h-264-mpeg-2-wmv-after-eff ects.html
In his Method #1 he describes using a QT PNG and watch folder in AME to take advantage of the GPU and Multiprocessing capabilities of AE – however this does not allow a video file to be exported with audio.
"The fastest way to create videos in these formats using Adobe Media Encoder with After Effects is to use the After Effects render queue to export a losslessly encoded master file (e.g., using the PNG video codec in a QuickTime .mov container file) to a watch folder that Adobe Media Encoder monitors. You can assign encoding presets to a watch folder in Adobe Media Encoder so that it automatically encodes using whichever settings you have specified. One advantage of using this method is that it uses After Effects performance features for rendering (such as GPU acceleration and multiprocessing where applicable) and Adobe Media Encoder performance features for encoding (such as parallel encoding). The disadvantage of using this method is that it occupies the main After Effects application for the entire rendering operation, during which time you can’t use After Effects for anything else."
Any idea what the best (and most efficient) route is to get my videos exported as H.264's with audio? Just exporting to AME is rather slow since it doesn't do multiprocessing....
Thanks for the input!

Todd's suggested work flow is a very good one. Render to a lossless file (which uses multi-processing, GPU acceleration, etc.) and then use the Adobe Media Encoder to make your final deliverable. That's the workflow I've had since Adobe introduced the Adobe Media Encoder. I have never used AE to create a final deliverable because it sucked at h.264 encoding.
Now, Todd suggests rendering your lossless file to a watch folder so that AME picks up and encodes your deliverable automatically after the intermediate file finishes rendering from AE. I've not used the watch folder method because I have different requirements for different projects, but it works for a lot of people.

Similar Messages

  • PP CC 2014 plays video fine from .mts files, but the audio is glitchy and jumpy.

    Premiere Pro CC 2014
    OSX 10.9.5
    I have imported .MTS files from one Canon C100 into PP through the Media Browser. I kept the file structure intact from the camera when copying. When I play a file in the source or program monitor the video plays back perfectly; however, the audio is glitchy and jumpy. It will skip time, jumping forward and backward seemingly randomly. If I open the same clip in Quicktime 10, it plays back 100% normal. I have restarted, reimported, and even transcoded the files to Pro Res 422 using Media Encoder CC 14. Nothing fixed it. The audio glitches the same way in the transcoded Pro Res Files.
    This is only the first of three cards of media. In total I have 120 .mts files in three separate AVCHD folders from a three camera C100 shoot. This leads to another issue I know I will run into. There will be three .mts files named "001," three named "002," etc. I have solved this issue in the past simply by transcoding, but that again failed to work for me thus far. So if I must stick with the .mts files, does anyone know a workflow for using multiple .mts files with the same name in one project/timeline?
    Thanks

    I find it hard to believe that this fixes the root of the problem as the same files playback fine in CS6. CS6 and CC 2014 should be referencing the same codec library on my system, right? If this is the case, then there is something wrong with how CC14 is decompressing the footage with the codecs that are working fine in CS6.
    To further this point. I imported the same files into CS6. CS6 played them back fine, so I saved the session and opened it up in CC14. CC14 converted the project file and all media loaded and plays back normal now.
    So if this is a codec issue, it would not have been solved by opening the files first in CS6. It also would not be solved as so many others report by moving the files and relinking to the new folder. It seems to me to be an import issue that is solely in CC14, not CC or CS6.

  • On a Mac, in Adobe Photoshop CC 2014, when adding audio to an edit, i get the message "Could not complete your request, because Dynamiclink is not available". When performing the exact same operation in Adobe Photoshop CC, i can add audio in the same way,

    On a Mac, in Adobe Photoshop CC 2014, when adding audio to an edit, i get the message "Could not complete your request, because Dynamiclink is not available".
    When performing the exact same operation in Adobe Photoshop CC, i can add audio in the same way, no error message. Any ideas to solve this, anyone? Would be greatly appreciated.

    I tried to update and it keeps telling me to get the Application Manager. And this is what happens
    Adobe Application Manager failed and it told me to download the Adobe Support Advisor.
    Adobe Support Advisor told me that there was an issue:" cpsid_82829s1: "A restart is pending," bootstrapper error has occurred. "Token Number: 40-87772-063201122012
    I followed the instructions it gave me to correct this issue:
    If you receive the error "Installer has detected that a machine restart is pending. It is recommended that you quit the installer, restart try again," do the following:
    #Restart the computer and try the installation again.
    #If the installation fails, delete the InProgress registry key: 
    Disclaimer: This procedure involves editing the Windows registry. Adobe doesn't provide support for editing the registry, which contains critical system and application information. Make sure to back up the registry before editing it. For more information about the registry, see Windows registry information for advanced users on the Microsoft support site, or contact Microsoft. 
    Launch Windows Registry Editor.
    (Windows XP) Choose Start > Run, type regedit in the Open text box and click OK.
    (Windows Vista/ Windows 7) Choose Start, type regedit in the Search box, and press Enter.
    Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
    Delete the InProgress key.
    I was not able to find the "InProgress" key.

  • Premiere pro cc 2014 problems with audio

    I have edited some sequences in premiere using sony xdcam ex clips. The clips where recorded as 1080 50i. I have edited it in the same sequence properties as premiere sugested it. All there is fine and audio is playing well. The problem strats when i change the sequence properties and select it at 1080 60i or 29p. The audio is distorted and it sounds like robotic, sometimes audio is muted on audio transitions. When i revert the properties back to 50i then all is fine.
    Anyone else experience the same problems?

    Sometimes i must add some clips that are recorded on canon 6d on 29.97p. and this clips look choppy and jerky on 50i sequence. But on 60i sequence both 50i and 29.97p look good. On premiere cc i cann change sequence properties without any problems with audio, only on cc 2014 that audio problem exist.

  • The latest Premier Pro CC 2014 update forced me to convert and create version of my project while guaranteeing that the project would not be altered; however, the timelines are not the up to date versions I had.

    The latest Premier Pro CC 2014 update forced me to convert and create version of my project while guaranteeing that the project would not be altered; however, the timelines/sequences are not the up to date versions I had. I saved different version of this project for various purposes, but they were all named differently(i.e joe and mary wedding, joe and mary wedding 2, joe and mary wedding 3, joe and mary wedding 3.1).  I do not know if they just pulled the timelines from the earliest version, eradicated the data entirely, or something else.
    Since the program prompts me to create and save a new version for the updated premier, I still have the previous projects, but cannot open them.  I imagine they are unchanged, but cannot be sure.
    Thoughts? Is it possible to uninstall an update re-install it later?
    Please advise.
    Thank you.
    Brian

    Also...
    Add to right click menu of timelines an entry for "go to next keyframe" and "go to last keyframe" a la After Effects, we should also be able to assign a kb shortcut to this.
    There are buttons on either side of the create keyframe button to advance forward or backward in the effects control panel or timeline.
    You can also advance forward or backward in the effects control window by holding shift while dragging the playhead.
    Allow copy/paste of selection of audio/video effects, not just one at a time. Sure we can copy/paste attributes but since we can also copy/paste effects it would only make sense to allow to copy/paste a selection of effects.
    I guess I don't get this one. If I have 5 effects on a clip, I can simply command-click on the ones I want to copy over to the other clip.

  • Export to ME to H.264 Audio Out of Sync

    HELP!!!!!! Adobe Premiere Pro CS3, 3.2 version Windows XP. For sometime now I have had to go back into Premiere and shift the audio forward so it is many frame ahead of the video when viewing in program monitor so that when the project is exported to Media Encoder CS3 and then to H.264 for streaming on Vimeo the audio will be in sync with the video. I spend hours and hours editing the project so it plays perfectly in Premeire and then have to spend hours exporting to test to see if the video is going to play in sync with the audio. But NO!!!!!
    I have seen many, I mean Many of posts all over the net about the audio sync problems and how Abode just ignores the problem. WHAT UP with THAT????  Come on guys!!! You take our money and sell us a product that doesn't work?? At least you can fix the bug and or tell us how to create a work around!!! COME ON! I guess I should have bought FCP instead. NAB is coming up, a perfect time to corner the Adobe clan with a video camera and get their answer to fixing the problem. Once I do, I'll post it online... but then again, the Audio may be out of sync??? Unless they give me the magic fairy dust to sprinkle on my computer to make CS3 export properly. (I hear that this problem still exists in CS4, CS4 and even CS6!!!)  HELP!!!!! I need to be able to export into Media Encoder and output to H.264 perfectly each time!!!!

    Thanks Jeff. I'll add a bit more detailed information.
    OS Windows XP SP3
    Adobe premiere Pro CS3 (latest updates installed 3.2)
    Footage: from DVX1000 FireWire capture either through Premiere Pro or On Location. Footage specs are 48kHz stereo audio, video either 16:9 or standard 4:3 ratio.
    In the past I have been mixing a stereo signal from a mixing console directly into the camera, so that no I porting of audio from other sources are necessary. This recent project I sent a stereo signal to the camera as a reference point and then recorded 4 tracks separately on a DAW and then mixed and imported the audio tracks into Premiere and sync the imported stereo track with the captured audio from the camera.
    Editing process: Locked main video with new imported tracks from DAW. Longest complete section is 3 minutes. Imported video b roll for out takes and cross dissolved from one video track to another. Then once completed, exported to Media Encoder.
    Media Encoder Settings:
    4:3 ratio DV Footage 720w x 480h Input and output
    Format H.264
    Range Entire Sequence
    Preset. Custom
    NTSC 720x480, 30 fps, progressive
    ACC (ACC+ version 1 and 2, each tried separately) 48khz
    VBR, 2 pass, target 100.09, Max 100.00 (Mbps)
    Filters. Non
    Video
    NTSC
    720
    480
    30 fops
    Standard 4:3
    Profile Main
    level 5.1
    VBR, 2 Pass
    Target bitrate 100 Mbps
    Maximum Bitrate 100 Mbps
    Advanced settings
    Set key frame distance checked
    Key frames distance 30
    Audio
    ACC
    Audio codec ACC, ACC+ Version 1, ACC + Version 2
    Frequency 48 kHz
    Audio quality HIGH
    Bitrate Kbps 48
    Advanced settings
    Precedence. BITRATE
    Mulitplexing. MP4
    Stream Compatibility Standard
    Others
    None
    Results: audio on h.264 is always out of sync, 14 frames ahead of the video
    Has this always been happening? YES. I have reinstalled this CS 3 on two different computers with freshly installed OS win XP with SP3. Always the same results. 
    Comment: Surely there has to be a preset for H.264 to output perfectly to YouTube or Vimeo with out all the beta testing and re-editing. Is there another software available to convert to?  The export to movie function seems to work perfectly. It's just when exporting to Media Encoder. This leads me to believe that the problem is inherent to Media Encoder. If I have to buy a software converter from QuickTime movie to h.264 so be it but, you would think this should not be the case.

  • Does the new Mac Pro(Later 2014) had an Audio-In port?

    I want to convert a cassette tapes in digital files using my new Mac Pro(Later 2014). Does it have an Audio-in port and where it is located?

    The new Mac pro has:
    Combined optical digital audio output/analog line out minijack
    Headphone minijack with headset support
    HDMI port supports multichannel audio output
    Built-in speaker
    If you want digital audio in:
    MacPro (late 2013): Digital audio in - how?

  • FAQ: What features use the GPU and how do I troubleshoot GPU issues?

    Photoshop CS6 GPU FAQ
    Introduction
    This document provides a quick reference guide to video card usage in Photoshop.  Some features require a compatible video card to work; if the video card or its driver is defective or unsupported, those features will not work at all.  Other features use the video card for acceleration and if the card or driver is defective those features will run more slowly.
    Mercury Graphics Engine
    The Mercury Graphics Engine (MGE) represents features that use video card, or GPU, acceleration. In Photoshop CS6, this new engine delivers near-instant results when editing with key tools such as Liquify, Warp, Lighting Effects and the Oil Paint filter. The new MGE delivers unprecedented responsiveness for a fluid feel as you work.
    MGE is new to Photoshop CS6, and uses both the OpenGL and OpenCL frameworks. It does not use the proprietary CUDA framework from nVidia.
    In order to use MGE, you must have a supported video card and updated driver. If you do not have a supported card, performance will be degraded. In most cases the acceleration is lost and the feature runs in the normal CPU mode. However, there are some features that will not work without a supported video card.
    GPU features added in Photoshop CS6
    Adaptive Wide Angle Filter (compatible video card required)
    Liquify (accelerated by compatible video card with 512MB VRAM, GPU mode unavailable on Windows XP)
    Oil Paint (compatible video card required)
    Warp and Puppet Warp (accelerated by compatible video card, GPU mode unavailable on Windows XP)
    Field Blur, Iris Blur, and Tilt/Shift (accelerated by compatible video
    card supporting OpenCL, GPU mode unavailable on Windows XP)
    Lighting Effects Gallery (compatible video card required with 512MB
    VRAM, unavailable on Windows XP)
    New 3D enhancements (3D features in Photoshop require a compatible video card with 512MB VRAM, unavailable on Windows XP):
    Draggable Shadows
    Ground plane reflections
    Roughness
    On-canvas UI controls
    Ground plane
    Liqht widgets on edge of canvas
    IBL (image based light) controller
    * Note that all 3D features are unavailable on Windows XP in Photoshop CS6
    GPU features added in previous versions of Photoshop
    Scrubby Zoom. See Zoom continuously
    Heads Up Display (HUD) color picker. See Choose a color while painting
    Color sampling ring. Choose colors with the Eyedropper tool
    Brush dynamic resize and hardness control. See Resize or change hardness of cursors by dragging
    Bristle Brush tip previews. Bristle tip shape options
    Rule of thirds crop grid overlay. Crop images
    Zoom enhancements. Smooth display at all zoom levels and temporary zoom. See Zoom continuouslyTemporarily zoom an image
    Animated transitions for one-stop zoom.
    Flick-panning.
    Rotate the canvas. Use the Rotate View tool
    View nonsquare pixel images. Adjust pixel aspect ratio
    Pixel grid. Hide the pixel grid
    Adobe Color Engine (ACE).
    Draw Brush tip cursors. Resize or change hardness of cursors by dragging
    Adobe Bridge GPU features
    Preview panel
    Full-screen preview
    Review mode
    See Preview and compare images in Adobe Bridge CS6 Help for information on all of these features.
    GPU/OpenGL preferences in Photoshop CS6
    The advantages of using a compatible video card (GPU) with Photoshop are that you can experience better performance and more features.   Problems can occur if you have an older video card with limited VRAM or if you use other programs at the same time as Photoshop that use the GPU.
    Choose Edit > Preferences (Windows) or Photoshop > Preferences (Mac OS).
    In the Performance panel, make sure Use Graphics Processor is selected in GPU Settings.
    Click Advanced Settings and specify the following options:
    Mode > Basic
    Mode > Normal
    Mode > Advanced Provides the benefits of Normal mode as well as newer OpenGL advances that can result in improved performance.
    Use Graphics Processor to Accelerate Computation
    Use OpenCL Uses the GPU to accelerate the new blur filters (Field Blur, Iris Blur, and Tilt-Shift) – OpenCL will only be available on newer GPUs that support OpenCL v1.1 or higher
    Anti-Alias Guides And Paths Allows the GPU hardware to smooth the edges of drawn guides and paths.
    30 Bit Display (Windows only) Allows Photoshop to display 30 bit data directly to screen on video cards that support it
    Quick GPU Troubleshooting Steps
    You can experience problems such as artifacts, errors, and crashes if there are incompatibilities between Photoshop and the display components that access the GPU.
    If you experience crashes, incorrectly rendered windows or objects, redraw issues, or performance issues while running Photoshop, first determine whether OpenGL is causing the problem.
    Turn off OpenGL.
    Choose Edit > Preferences (Windows) or Photoshop > Preferences (Mac OS).
    In the Performance panel, uncheck Use Graphics Processor. Click OK.
    Restart Photoshop, and perform the same function.
    If the problem recurs while OpenGL Drawing is disabled, OpenGL is not the cause. For additional troubleshooting, see Troubleshoot system errors and freezes | Adobe software on Windows (cpsid_82252) or Troubleshoot system errors and freezes | Adobe software on Mac OS 10.x (cpsid_82414).
    If the problem resolves, proceed with the rest of the troubleshooting steps to fix OpenGL.
    Make sure that you're using the latest update of Photoshop.Updates fix bugs and issues.
    Update the display driver.Updated display drivers can fix many issues, such as crashing, incorrectly rendered objects, and performance problems. Determine what video card you have and go directly to the manufacturer's website (nVidia or ATI/AMD) and download the latest driver. (Note: Simply doing a Windows Update is does not guarantee you are using the latest driver. You must go directly to the nVideo or ATI/AMD websites to get the absolute latest driver.) After you update your driver, turn on Use Graphics Processor in Photoshop preferences.
    Reset preferences.
    Resetting preferences returns OpenGL settings to their default status. Reset Photoshop preferences by pressing and holding Shift+Ctrl+Alt (Windows) or Shift+Option+Command (Mac OS) immediately after you start Photoshop.
    Click Yes when asked if you want to delete the Adobe Photoshop Settings File.
    Retry the function that caused the problem.
    Change the OpenGL mode to Basic.
    Setting the OpenGL mode to Basic uses the least amount of GPU memory and the most basic GPU feature set.
    Close all documents.
    Choose Edit > Preferences (Windows) or Photoshop > Preferences (Mac OS)
    In the Performance panel, click the GPU Settings Advanced Settings button.
    Choose Mode > Basic
    Restart Photoshop.
    If this solution resolves the problem, switch to Normal mode. See if the issue recurs. If the issue recurs, return to Basic mode.
    Note:  If you’re changing GPU preferences to troubleshoot a problem, re-launch Photoshop after each change.
    If you are using more than one video adapter, remove the additional cards.
    Multiple video adapters can cause problems with GPU accelerated or enabled features in Photoshop. It's best to connect two (or more) monitors into one video adapter. If you have to use more than one video adapter, make sure that they are the same make and model. Otherwise, crashes and other problems can occur in Photoshop.
    Note: Using two video adapters does not enhance Photoshop's performance.
    Check your Cache Levels setting.
    If you've set your Cache Levels to 1 in Photoshop preferences, you can experience performance issues with GPU features. Reset Cache Levels to the default setting, which is 4.
    Choose Edit > Preferences > Performance (Windows) or Photoshop > Preferences (Mac OS)
    In the Performance panel, choose Cache Levels > 4.
    The GPU Sniffer
    To help guard against Photoshop crashes related to bad GPU hardware or drivers, Photoshop employs a small program called the GPU Sniffer. Every time Photoshop is launched, Photoshop launches the sniffer. The sniffer runs rudimentary tests of the GPU and reports the results to Photoshop. If the sniffer crashes or reports a failure status to Photoshop, Photoshop will not use the GPU. The Use Graphics Hardware checkbox in the Performance panel of the Preferences will be unchecked and disabled.
    The first time the sniffer fails, Photoshop will display a dialog indicating that it has detected a problem with the GPU. On subsequent launches the dialog will not appear unless the Photoshop preferences are reset.
    If the user corrects the problem, either by replacing the video card or by updating the driver, then the sniffer will pass on the next launch and the Use Graphics Hardware checkbox will be enabled and returned to its previous state (enabled or disabled).
    Tested video cards for Photoshop CS6
    Adobe tested the following video cards before the release of Photoshop CS6. This document lists the video card by series. While the minimum amount of VRAM supported on video cards for Photoshop CS6 is 256MB, some features require 512MB of VRAM to be enabled.
    Note: Adobe tested laptop and desktop versions of the following cards. Be sure to download the latest driver for your specific model. (Laptop and desktop versions have slightly different names.)
    nVidia GeForce 8000, 9000, 100, 200, 300, 400, 500 series 
    nVidia Quadro 400, 600, 2000, 4000 (Mac & Win), CX, 5000, 6000
    AMD/ATI Radeon 2000, 3000, 4000, 5000, 6000, 7000 series
    AMD/ATI FirePro 3800, 4800, 5800, 7800, 8800, 9800, 3900, 4900, 5900, 7900
    Intel Intel HD Graphics, Intel HD Graphics P3000, Intel HD Graphics P4000
    Note: ATI X1000 series and nVidia 7000 series cards are no longer being tested and are not officially supported in CS6 – some basic GL functionality may be available for both these cards.
    Note: 3Dand some Open GL features are disabled on Windows XP, as stated on : http://labs.adobe.com/technologies/photoshopcs6/

    I've had several timeout since the pings were started. Got a some response times > 1ms (nothing greater than 7 or 8ms), but no timeouts.

  • No Audio during Log and Capture

    Hello, I have FCP 6.0 and am unable to hear my audio during log and capture. I have this problem on all 5 G5 Macs that I have, and have tried different editing docks and cables. I have used FCP for more than 5 years and have never had this problem. iMovie has audio during capture, so I am convinced that there is a pre-set in FCP that I don't have checked properly, but I've been over them many times and still have no answer. I searched past forums and didn't really find anything helpful to me.
    My pre-sets are set to DV NTSC 48kHz and the playback pre-sets are set to default. I can hear audio of my clips after I log and capture, but I still need to hear audio during importing. I'm more confused than anything. If anybody has had this problem before or any suggestions for me, I'm all ears.
    Thanks.
    John

    ... as Bogie says.
    However... this is a non-feature that dates back to slower CPU days... yet, still with all the different formats and such I (ME!!) I believe it's still good practice to leave it off.
    Devoting as much CPU work to the capture process lessens the chance for something to go wrong. You can easily monitor the audio directly out of the deck as needed.
    Sure -- octo cores need 30 apps open just to get your money's worth and I'm sure you won't have any issues using an 8th of one to send audio thru itself while the other 7 and 7/8ths are used for capture... but who wants to risk it?
    Not me... I'm to old to change my ways.
    Blast you FCP v1.2.5 on a beige G3 with 7gig and 15gig hard drive -- you taught me well.
    CaptM

  • A quick primer on audio drivers, devices, and latency

    This information has come from Durin, Adobe staffer:
    Hi everyone,
    A  common question that comes up in these forums over and over has to do  with recording latency, audio drivers, and device formats.  I'm going to  provide a brief overview of the different types of devices, how they  interface with the computer and Audition, and steps to maximize  performance and minimize the latency inherent in computer audio.
    First, a few definitions:
    Monitoring: listening to existing audio while simultaneously recording new audio.
    Sample: The value of each individual bit of audio digitized by the audio  device.  Typically, the audio device measures the incoming signal 44,100  or 48,000 times every second.
    Buffer Size: The  "bucket" where samples are placed before being passed to the  destination.  An audio application will collect a buffers-worth of  samples before feeding it to the audio device for playback.  An audio  device will collect a buffers-worth of samples before feeding it to the  audio device when recording.  Buffers are typically measured in Samples  (command values being 64, 128, 512, 1024, 2048...) or milliseconds which  is simply a calculation based on the device sample rate and buffer  size.
    Latency: The time span that occurs between  providing an input signal into an audio device (through a microphone,  keyboard, guitar input, etc) and when each buffers-worth of that signal  is provided to the audio application.  It also refers to the other  direction, where the output audio signal is sent from the audio  application to the audio device for playback.  When recording while  monitoring, the overall perceived latency can often be double the device  buffer size.
    ASIO, MME, CoreAudio: These are audio driver models, which simply specify the manner in which an audio application and audio device communicate.  Apple Mac systems use CoreAudio almost exclusively which provides for low buffer sizes and the ability  to mix and match different devices (called an Aggregate Device.)  MME  and ASIO are mostly Windows-exclusive driver models, and provide  different methods of communicating between application and device.  MME drivers allow the operating system itself to act as a go-between and  are generally slower as they rely upon higher buffer sizes and have to  pass through multiple processes on the computer before being sent to the  audio device.  ASIO drivers provide an audio  application direct communication with the hardware, bypassing the  operating system.  This allows for much lower latency while being  limited in an applications ability to access multiple devices  simultaneously, or share a device channel with another application.
    Dropouts: Missing  audio data as a result of being unable to process an audio stream fast  enough to keep up with the buffer size.  Generally, dropouts occur when  an audio application cannot process effects and mix tracks together  quickly enough to fill the device buffer, or when the audio device is  trying to send audio data to the application more quickly than it can  handle it.  (Remember when Lucy and Ethel were working at the chocolate  factory and the machine sped up to the point where they were dropping  chocolates all over the place?  Pretend the chocolates were samples,  Lucy and Ethel were the audio application, and the chocolate machine is  the audio device/driver, and you'll have a pretty good visualization of  how this works.)
    Typically, latency is not a problem if  you're simply playing back existing audio (you might experience a very  slight delay between pressing PLAY and when audio is heard through your  speakers) or recording to disk without monitoring existing audio tracks  since precise timing is not crucial in these conditions.  However, when  trying to play along with a drum track, or sing a harmony to an existing  track, or overdub narration to a video, latency becomes a factor since  our ears are far more sensitive to timing issues than our other senses.   If a bass guitar track is not precisely aligned with the drums, it  quickly sounds sloppy.  Therefore, we need to attempt to reduce latency  as much as possible for these situations.  If we simply set our Buffer  Size parameter as low as it will go, we're likely to experience dropouts  - especially if we have some tracks configured with audio effects which  require additional processing and contribute their own latency to the  chain.  Dropouts are annoying but not destructive during playback, but  if dropouts occur on the recording stream, it means you're losing data  and your recording will never sound right - the data is simply lost.   Obviously, this is not good.
    Latency under 40ms is  generally considered within the range of reasonable for recording.  Some  folks can hear even this and it affects their ability to play, but most  people find this unnoticeable or tolerable.  We can calculate our  approximate desired buffer size with this formula:
    (Sample per second / 1000) * Desired Latency
    So,  if we are recording at 44,100 Hz and we are aiming for 20ms latency:   44100 / 1000 * 20 = 882 samples.  Most audio devices do not allow  arbitrary buffer sizes but offer an array of choices, so we would select  the closest option.  The device I'm using right now offers 512 and 1024  samples as the closest available buffer sizes, so I would select 512  first and see how this performs.  If my session has a lot of tracks  and/or several effects, I might need to bump this up to 1024 if I  experience dropouts.
    Now that we hopefully have a pretty  firm understanding of what constitutes latency and under what  circumstances it is undesirable, let's take a look at how we can reduce  it for our needs.  You may find that you continue to experience dropouts  at a buffer size of 1024 but that raising it to larger options  introduces too much latency for your needs.  So we need to determine  what we can do to reduce our overhead in order to have quality playback  and recording at this buffer size.
    Effects: A  common cause of playback latency is the use of effects.  As your audio  stream passes through an effect, it takes time for the computer to  perform the calculations to modify that signal.  Each effect in a chain  introduces its own amount of latency before the chunk of audio even  reaches the point where the audio application passes it to the audio  device and starts to fill up the buffer.  Audition and other DAWs  attempt to address this through "latency compensation" routines which  introduce a bit more latency when you first press play as they process  several seconds of audio ahead of time before beginning to stream those  chunks to the audio driver.  In some cases, however, the effects may be  so intensive that the CPU simply isn't processing the math fast enough.   With Audition, you can "freeze" or pre-render these tracks by clicking  the small lightning bolt button visible in the Effects Rack with that  track selected.  This performs a background render of that track, which  automatically updates if you make any changes to the track or effect  parameters, so that instead of calculating all those changes on-the-fly,  it simply needs to stream back a plain old audio file which requires  much fewer system resources.  You may also choose to disable certain  effects, or temporarily replace them with alternatives which may not  sound exactly like what you want for your final mix, but which  adequately simulate the desired effect for the purpose of recording.   (You might replace the CPU-intensive Full Reverb effect with the  lightweight Studio Reverb effect, for example.  Full Reverb effect is  mathematically far more accurate and realistic, but Studio Reverb can  provide that quick "body" you might want when monitoring vocals, for  example.)  You can also just disable the effects for a track or clip  while recording, and turn them on later.
    Device and Driver Options: Different  devices may have wildly different performance at the same buffer size  and with the same session.  Audio devices designed primarily for gaming  are less likely to perform well at low buffer sizes as those designed  for music production, for example.  Even if the hardware performs the  same, the driver mode may be a source of latency.  ASIO is almost always  faster than MME, though many device manufacturers do not supply an ASIO  driver.  The use of third-party, device-agnostic drivers, such as  ASIO4ALL (www.asio4all.com) allow you to wrap an MME-only device inside a  faux-ASIO shell.  The audio application believes it's speaking to an  ASIO driver, and ASIO4ALL has been streamlined to work more quickly with  the MME device, or even to allow you to use different inputs and  outputs on separate devices which ASIO would otherwise prevent.
    We  also now see more USB microphone devices which are input-only audio  devices that generally use a generic Windows driver and, with a few  exceptions, rarely offer native ASIO support.  USB microphones generally  require a higher buffer size as they are primarily designed for  recording in cases where monitoring is unimportant.  When attempting to  record via a USB microphone and monitor via a separate audio device,  you're more likely to run into issues where the two devices are not  synchronized or drift apart after some time.  (The ugly secret of many  device manufacturers is that they rarely operate at EXACTLY the sample  rate specified.  The difference between 44,100 and 44,118 Hz is  negligible when listening to audio, but when trying to precisely  synchronize to a track recorded AT 44,100, the difference adds up over  time and what sounded in sync for the first minute will be wildly  off-beat several minutes later.)  You are almost always going to have  better sync and performance with a standard microphone connected to the  same device you're using for playback, and for serious recording, this  is the best practice.  If USB microphones are your only option, then I  would recommend making certain you purchase a high-quality one and have  an equally high-quality playback device.  Attempt to match the buffer  sizes and sample rates as closely as possible, and consider using a  higher buffer size and correcting the latency post-recording.  (One  method of doing this is to have a click or clap at the beginning of your  session and make sure this is recorded by your USB microphone.  After  you finish your recording, you can visually line up the click in the  recorded track with the click in the original track by moving your clip  backwards in the timeline.  This is not the most efficient method, but  this alignment is the reason you see the clapboards in behind-the-scenes  filmmaking footage.)
    Other Hardware: Other  hardware in your computer plays a role in the ability to feed or store  audio data quickly.  CPUs are so fast, and with multiple cores, capable  of spreading the load so often the bottleneck for good performance -  especially at high sample rates - tends to be your hard drive or storage  media.  It is highly recommended that you configure your temporary  files location, and session/recording location, to a physical drive that  is NOT the same as you have your operating system installed.  Audition  and other DAWs have absolutely no control over what Windows or OS X may  decide to do at any given time and if your antivirus software or system  file indexer decides it's time to start churning away at your hard drive  at the same time that you're recording your magnum opus, you raise the  likelihood of losing some of that performance.  (In fact, it's a good  idea to disable all non-essential applications and internet connections  while recording to reduce the likelihood of external interference.)  If  you're going to be recording multiple tracks at once, it's a good idea  to purchase the fastest hard drive your budget allows.  Most cheap  drives spin around 5400 rpm, which is fine for general use cases but  does not allow for the fast read, write, and seek operations the drive  needs to do when recording and playing back from multiple files  simultaneously.  7200 RPM drives perform much better, and even faster  options are available.  While fragmentation is less of a problem on OS X  systems, you'll want to frequently defragment your drive on Windows  frequently - this process realigns all the blocks of your files so  they're grouped together.  As you write and delete files, pieces of each  tend to get placed in the first location that has room.  This ends up  creating lots of gaps or splitting files up all over the disk.  The act  of reading or writing to these spread out areas cause the operation to  take significantly longer than it needs to and can contribute to  glitches in playback or loss of data when recording.

    There is one point in the above that needed a little clarification, relating to USB mics:
    _durin_ wrote:
     If  USB microphones are your only option, then I would recommend making  certain you purchase a high-quality one and have an equally high-quality  playback device.
    If you are going to spend that much, then you'd be better off putting a little more money into an  external device with a proper mic pre, and a little less money by not  bothering with a USB mic at all, and just getting a 'normal' condensor  mic. It's true to say that over the years, the USB mic class of  recording device has caused more trouble than any other, regardless.
    You  should also be aware that if you find a USB mic offering ASIO support,  then unless it's got a headphone socket on it as well then you aren't  going to be able to monitor what you record if you use it in its native  ASIO mode. This is because your computer can only cope with one ASIO device in the system - that's all the spec allows. What you can do with most ASIO hardware though is share multiple streams (if the  device has multiple inputs and outputs) between different software.
    Seriously, USB mics are more trouble than they're worth.

  • Having problems connecting iMac(late 2006) running 10.7.5 to a Samsung Flat Screen TV using separate audio/speaker cable and HDMI standard cable, mini-DVI to HDMI video converter.  TV displays generic Apple galaxy background and "some" windows (e.g. scree

    Not sure that I have selected the correct forum.  Hope my questions are clearly stated.
    Having problems connecting iMac(late 2006) running 10.7.5 to a Samsung Flat Screen TV using separate audio/speaker cable and HDMI standard cable, mini-DVI to HDMI video converter.  TV displays generic Apple galaxy background and "some" windows (e.g. screen resolution choices).   It does not show Mail or Safari menus.  System preferences'  display "gathered" the Samsung and chose its resolution.  I did not find a way to select the Samsung as my display.
    In addition to having old hardware, we have Verizon FIOS providing internet and TV access.  Is there any way to make this work for us?  We would like to stream video (Netflix) and view shows from the Web.  Do we need Apple TV to do this?  Or is it not possible with our old iMac?  My husband thinks that our Airport could be a factor. 
    Thank you

    Lately, I have been seeing a lot of posts with users trying to use their Macs/iMacs to mirror their streaming video from their Macs to an HDTV.
    There are, actually, many alternatives to choose from than just from a Mac.
    You need to have or invest in a WiFi capable router for all of these examples.
    Apple TV only integrates with WiFi and newer Mac hardware. So, if you want to have total integrated experience, if you have a 2011 Mac or newer, you might as well pay the $100 for the AppleTV box.
    If you have a older Mac, like I have noticed many users do, then you have other options.
    If you want to elimate long cable clutter and having your Mac at the mercy of your TV all of the time,  you can still use the AppleTV box independently or purchase cheaper alternative media streaming boxes from Roku, Sony, Boxee or any number of electronics manufacturers that now have media streaming boxes and media streaming capability built into DVD/Blu-ray players.
    These eliminate long cable clutter by being close to the HDTV where shorter, less expensive cables can be used.
    Another alternative for iPad users is to use an iPad with the USB/HDMI video adapter and use your iPad as the streaming box. This ties up your iPad in much the same way as it does with your Mac, but again the iPad can be close to the TV and use minimal cables to the TV.
    Another alternative to is to use a combination of an iPad and your Mac to stream content that is only available to stream online from a computer. In this case, you can use a desktop remote app on your iPad and Mac. A good and cheap Desktop Remote app is Splashtop Remote. This allows you to completely connect your iPad remotely, over Wifi, to your iMac desktop. The app streams both video and sound to the iPad which is still connected to your HDTV. The resultant stream video picture will be smaller than the size of your HDTV, but it will still be plenty large enough to watch. Again, if you own a iPad and an Intel Mac, this method also allows minimal cabling to the TV.

  • Adding Menue Audio Track selection and soubtitles on/off

    Hi,
    with some help from replies to other questions I managed to get a working DVD/BR with cool 2.0 / 5.1 sound and subtitles.
    But for now I do have to select the audio track manually and also I do have to enable subtitles from the DVD/BR players menu.
    So I wanted to add a DVD/BR menu where you can choose the audio track which should be played and to switch on and of subtitles.
    I edited a nice PS PSD File with some buttons and they show up in Encore and I can do some "encore" editig like moving tham arrond or link to some other elements.
    My question: How do I get e.g. the Button "2.0 Stereo" to select the stereo track and the button "5.1 Surround" to select the 5.1 track. An other button should switch on/off the right subtitle
    Than I'd like to have a button which starts the video with the selected audio and if selected subtitle on.
    At the end of the movie I like to be back in the menu.
    I bet thats simple
    I thought to create different timelines and add the audio/video/subtitle, but that i have a lot of timelines in all sort of combinations; e.g. video ON, 5.1 sound ON, subtitle OFF ..... video ON, 2.0 sound ON, subtitle ON etc ....
    Thansk for any suggestion . and BIG thanks. Götz

    Thanks for your posting, but there is the higlight  Layer.
    I opend the menue in photoshot once more and enabled the layers.
    For me a button has the following different states:
    Normal, no highlight,just "plain" text. e.g. "English Subtitle". in that state, the Subtitle is NOT selected/enabled.
    Mouse Over, the highlight shows up, so you can see where you are with your mouse. e.g. "English Subtitle √"
    Mouse left click, the highlight "sticks" to the menue item and when moving the mouse avay it is still highlighted, e.g.  "English Subtitle √"
    So I'd liked to indicate which audio track is enabled/selected and if subtitles are off or on.
    I thought, the highlight button states are markend with (=1) & (=3) ....
    BTW. in encore menue edit mode, if I click the show selected/activated Subpicture Highlight, the right layer shows up (with my √-symbol)
    But in preview mode or on a burned dvd this did not work
    Regards . Götz

  • Audio cut out and midi miss sync

    Lately I have been getting audio cut out, and the missing, 'error while trying to sync audio and midi'.
    I thought it was that I had too many instances of virtual instruments. So I mixed the song down. Imported that into a NEW song, with only one audio track, and then proceeded to try to do an organ overdub...Well Logic still drops out and gives me the message, even though there is NO midi information in this file...
    Then I noticed that even AIF or mp3 files, didn't play properly from the desktop preview mode. They stop too. Activity monitor doesn't seem to be showing anything overworking..
    Disk Warrior fixed some volume errors,
    Anyone have any ideas to try?

    I'm using a motu828. I disconnected the firewire connection, and ran audio from the headphone jack to the motu, and VOILA, no problems... Last year, I went thru two motu units, not really sure if they are the issue.
    I think it might be LOGIC's firewire circuitry. Apple techs couldn't find the issue, I had the G5 motherboard replaced. Another factor was I had 3 Lacie firewire drives (2 firewire 800, 1 400) I have had 4 Lacie drives die on me in the last 3 years. They are the only firewire drives I have, so I don't know if the fault lies with them, or the again Apples firewire circuitry, stressing the drives out???
    I also put a firewire 800 card in my system.
    I have now switched to an external ESATA raid setup. No more firewire drives. So far so good. Since I had the whole motherboard replaced, I don't know what that means in terms of MOTU connected via firewire..
    For now, I'm running audio out of headphone jack, using all virtual instruments, so I know it will sound better when I get firewire audio up and running, but I got tired of it cutting out every 3 - 30 minutes. I'm thinking about the apogee duet unit. But again if it's connected via firewire, I don't know where that leaves me..
    My G5 is three and half years old, perhaps it's tired and wants to be retired....
    The dark part of me wonders, if Apple computers don't start crapping out after three years of heavy use, or is it that technology, software, updates, push the hardware beyond it's capacity after a few years.

  • HT5287 If DVD Movies, Audio CD's and even burning CD and DVD's are not supported, what is the point of DVD & CD Sharing then? Wouldn't it just be better to remote in or use a thumb drive if it's only able to be used for data transfer?

    If DVD Movies, Audio CD's and even burning CD and DVD's are not supported, what is the point of DVD & CD Sharing then? Wouldn't it just be better to remote in or use a thumb drive if it's only able to be used for data transfer?
    Or am I missing the bigger picture?

    As long as you have a Superdrive or an external burner/drive, burning, watching, installing, etc. from CD or DVD will work just fine. And so will sharing.

  • I have iTunes version 10.7.0.21 for Windows 7.  It was working fine untill recently.  Now when I play a T.V. show the audio cuts in and out, the video pauses intermittenly and also intermittenly fast forwards.  What is causing this and how do I fix it?

    I'm having problems with video play back in itunes 10.7.0.21 for windows 7.  Video was playing fine, but now I'm having audio issues.  Audio cuts in and out.  Also video pauses and fast forwards.  Does anyone know what would cause this all the suddenly?  More importantly does anyone know how to fix this?

    All sorted now. Thread can be closed!

Maybe you are looking for