Pro Tools 11

Anyone else get this when they click the download link?

This webpage is not available

Tried again later and it was fixed. Thanks man.

Although Slate was on track to release VTM last week too, then go figure...a delay. I take his timelines with a grain of salt at this point. They won't be here until they arrive.

Is the Low Latency Input Buffer available on Native systems? And does that mean that I should be able to just set my buffers as low as they can go and not worry about recording with direct monitoring? I'm a little confused how this would help me. I wouldn't have to put the Tritone Mutetone on the channel I'm recording, because the latency wouldn't be there...but that's the only step it would save, right? I just wouldn't have to deal with the Maestro software (Apogee) anymore...right? Would anything I put on the inserts record? I don't think so, right?

if you have apollo console your daw buffers are irrelevant ; you should be able to just leave them high for mixing and do your tracking through console with or without ua plugs ?

From page 421 of the manual:

Host-based Pro Tools systems use the host processor
in your computer for all audio processing, playback,
and recording, so there is always a small
amount of latency in the system. For example,
there may be some audible delay between the incoming
signal and outgoing signal when monitoring
recording through Pro Tools.
With Pro Tools, latency occurs as follows:
• All Pro Tools systems can have Virtual Instrument
plug-in MIDI-to-audio latency (such as
when playing a virtual instrument live and monitoring
the instrument’s output).
• Pro Tools systems have input-to-output monitoring
latency on any record-armed tracks or
Auxiliary Inputs with live inputs.
• Pro Tools|HDX systems have monitoring latency
on tracks that have one or more host-based
plug-ins.
The latency amount is related to the H/W Buffer
Size setting—the larger the buffer size, the greater
the latency. You can reduce the amount of monitoring
latency by reducing the H/W Buffer Size setting.
However, even at the smallest buffer size,
there is still some latency.
In addition, reducing the buffer size limits the
number of simultaneous audio tracks you can record
without encountering performance errors.
While there may be times when you want a larger
buffer size, such as when you have higher track
counts with more plug-ins, you will generally want
the smallest possible buffer size when latency is
present during recording and monitoring.
If you are monitoring the recording source with an
external mixer before it is routed to Pro Tools, you
will not hear any latency.

I think that's just referring to Low Latency Monitoring with the old 10 and below. Supposedly, 11 has two separate buffers for input and output, thus allowing really small buffers while tracking...This might actually answer it - from the avid site...

Get ultra-low latency with a dedicated input buffer

With dedicated low-latency input and playback buffers , you can monitor record inputs on native systems with ultra-low latency—without sacrificing plug-in performance. Even with large, plug-in-heavy sessions, you get the responsiveness you need to record your best performance.

Look about halfway down...
www.avid.com/US/products/Pro-Tools-Software#Features

To clarify, I have to deal with PT's Low Latency setting when tracking midi drums via an Alesis DM10 kit and BFD3. For audio, I monitor through the Apollo Console.

no probs; we are all learning

I use ssd4 and yamaha drums, do you know that in your daw you can send the drums to console's virtual channels ( 4 mono or 2 stereo) and use ua plugs like any other signal for low latency real time recording ?

I create a session in console called drums and I bounce a stereo sub mix of my session with no drums and load that into a new session, put in a click track and then you can play your electric drums in real time, so I have 1 stereo drum track( recording the midi), the click track and the stereo sub mix( no plugs).

When I complete the midi drums, I export the midi file to the original session and import it.  I always put 2 bars of click to tempo at the head so the file lines up perfectly and then you can just mix with what ever plugs you want and/or convert it to audio as well.

The whole point of  apollo console tracking is to fix the latency delay problem before it even starts and you can save your console sessions by name and/or function with templates and plugs preloaded and there is the console recall plug which you load into your daw session which inks the daw with the console.

Console didn't get a lot of lov at first and it is a little hard to get your head around, but it is more versatile  than people give it credit for and with the improved routing functions more useful too.

how  are  our mutual friend jack and johnie doing anyway ?

I agree with your approach to developing a spiritual appreciation for spirits :it is best not to be come culturally ethnocentric !

It's kind of a drag waiting for some manufacturers to catch up with the 64 bit format. But performance-wise it's been great. Offline bounce was long overdue. I was able to track at 32samples for VI's before with 10, but it's definitely more stable now. LLM works the same as it did before. I have noticed though that while having a track record enabled, the playback is not totally in synch. I'm in time while recording in LLM mode but I have to take the track out of record to listen back without my audio sounding like its been bumped forward 20 milliseconds or so. Maybe theres something I'm not understanding yet about the new split input/output buffer. Larger faders make the old ones seem ridiculous now!

Really dug into a project today...Running Stylus, Superior Drums 2 (with huge, hungry kit) and Addictive Keys at 64 samples...no problems whatsoever. Now THIS, I could get used to. So much so, that I'm gonna give up all the plugs that don't work and use 11 for tracking. AND it's rock solid.