So why is Presonus dodging this question? Simple question, what is the true RTL using a utility like Oblique? Not the near zero latency using the monitoring software, but the true RTL through the DAW.
Why does every reviewer, at least from what I have seen, avoid the real RTL numbers?
Ask and you will be attacked. See FB for examples. See GS for more.
It seems the corporate line is to try and direct the thread toward toward the near zero latency provided by the software.
That is all well and good for those recording and monitoring real instruments but id DOES NOTHING for those ITB using VSTI.
So come on Presonus, pony up the numbers.
RME has for their Babyface Pro.
MOTU does for their AVB line.
Lynx does for their new cards.
So why doesn't Presonus?
No dog in this fight but not sure what you're askng. Are you asking for the total delay (throughput) of the hardware itself from input to output? The round trip latency otherwise will be based on the buffer size in whatever software you use and I also suppose how well the driver and your system can run at really low latency.
Not sure what Oblique is exactly but why not just ask someone with a 192 to do it for you? If you do, post it back so we all know.
I can give you the numbers that ASIO reports here for various buffer sizes but I'm running USB2 so they may not be best case, no idea really.
Hey Lawrence! Nice to see you again... RTL.. Total MEASURED round trip latency at various sample rates and buffer sizes.
So for example, under Windows what are you getting at 44.1k and 64 samples? 128 samples? etc... This is what people who are in the box, playing VSTi are interested in as it determines the "delay" factor... So for example, I get around 4.9ms RTL using a MOTU Ultralite AVB. Playing say Ivory, balls out, all options on, has zero clicks and pops and no lag. Even at 128 samples same thing, no lag. So where does the Studio192 fit in terms of RTL? Is it 5ms or 10ms? HUGE difference for those ITB. Not so much for those recording real instruments and using the zero latency mixer which all cards offer (TotalMix under RME for example).
Ok, here's what i see in the ASIO device panel...
"Minimum Latency" setting in the 192 control panel...
44.1: 5.6 ms (2.8 ms in & out)
48k: 2.67 / 2.67
88.2: 2.63 / 2.63
96k: 2.5 / 2.5
176.4: 2.5 / 2.5
192: 2.5 / 2.5
So it looks like 5ms is the lowest RTL. Whether you can run issue free at those lowest buffer settings with the virtual instrument projects you typically do on your system, no idea, you'd have to try it to see I suppose.
Hope that helps.
Thank you for taking the time to post the numbers Lawrence. So the next step would be to get some feedback on how well heavy VSTi usage works with the Studio 192 and at the lowest buffer settings.
Anyone else who is running ITB with VSTi or guitar amp simulators etc care to offer their experience with latency?
Lawrence wrotekeys88 wroteThank you for taking the time to post the numbers Lawrence.
According to TAFKAT on GS, there is more to it than that unfortunately..
Yeah. His comments seem to align with the numbers I posted.
Anyway, if a person is really interested in maybe using the device, order one from a reputable dealer (Sweetwater maybe) and test it for yourself. If it doesn't meet your expectations for low latency performance with VI's, return it.
Sometimes you just have to find out for yourself.
If you already own an AVB device that performs exceptionally well at low latency with VI's, and have no pressing need for the 192's more obvious strengths (live tracking, mixing live signals, hardware dsp, etc, etc), not sure what the appeal or potential value of it would be.
There are some standardized tests out there though. Why deal with the hassle of merch returns if you can get a reliable test result and make an informed decision before ordering?
Someone over there will run those tests soon anyway.
I think what is happening is that all manufacturers are pushing their "zero latency" monitoring via hardware and that is what is confusing some people. I haven't seen any top tier company that does not offer this via their software. MOTU, RME , Presonus all have this ability as well as the ability to add the built in processing (Reverb+compression, usually) to these zero latency mixes.
And this is extremely important to people working OTB and recording real instruments.
From what I have seen the Studio 192 raises the bar even further with the Z function and Fatchannel and integration with Studio One which unlike other cards does not require the extra software mixing.
This is great!
However, for those people working in the box or using say guitar amp sims, VSTi and so forth the true RTL is EXTREMELY important.
In fact it's really what separates the men from the boys.
If you look at RME or MOTU and some others they have extremely low RTL numbers and are not afraid to offer them up when asked. Even Audient who have the fine interfaces freely speak of these numbers. And all of course with the caveat that the system does and will play a role in this even using standard tools like the Centrance tool.
Presonus OTH seems silent.
Several people asked on their FB page responding to a review of the box and that person obviously had no idea what he was talking about because he kept referring back to the zero latency monitoring even after the differences were pointed out.
In another thread a Presonus employee posted a very nice review and was asked the same questions. I haven't seen a response yet so shoot me if I am paranoid but something doesn't seem right here and my suspicion is poor performance at the lowest latencies.
Like others I am anticipating Tafkat's testing because he does a standardized benchmark using the same system so the numbers are directly comparable.
This box looks killer to me and many other users however if the RTL sucks, the box just lost a good portion of its market, EDM folks in particular.
I would like for users who are actually producing ITB recordings to post their experiences with low latency and what is realistically usable.
Very true. Hardware monitoring is nothing new by any stretch, the 192 pushes it a little with the Studio One integration though... but yeah, hardware direct monitoring is nothing new. The remote mic pre controls and phantom power and hardware dsp integration and all that is not all that typical though, for people who want that kind of integration with S1 anyway, for the dsp bits.
But yeah, I do agree with the general idea that the device seems to be more targeted towards live work, maybe not so much VI production, but it will be good to know how it performs doing that for most anyway.
I never really run latency that low for VI's so my input there would be of less than zero value. I'll lurk and read the feedback on all that like the rest.
I think one of the reasons it is hard to pin down numbers for latency is it depends much more heavily on your CPU and drives with USB than it does with Firewire. USB 3 is certainly more than fast enough. However any input that comes from USB has to go through the CPU before it can get to the memory. Where Firewiere can read and write to RAM directly. This bypassing the CPU is a big advantage. However as fast as computers are today, I suspect a modern computer that wasn't bogged down with a lot of junk running all the time would do pretty well. But if you have older hardware that worked fine with Firewire, I wouldn't be surprised if it the latency via USB was a problem. I certainly wouldn't use this on a machine that didn't come with USB 3 ports if latency was a big issue.
There is a known issue with the current Studio 192 driver reporting its own input and output
latency only rather than the total system latency. The resolution for this issue is currently in
beta testing and will be released as soon as it is ready for public release. This issue has caused
some users to inquire about what comprises the total system latency of the Studio 192.
The PreSonus Studio 192 features a world-class DSP engine that runs up to 16 instances of
Studio One 3’s Fat Channel plugin. This plugin includes a switchable gate/expander, look-ahead
compressor, four-band parametric EQ, and variable limiter. Like other audio interfaces with an
extremely powerful onboard DSP and top-quality ADC/DAC converters, the round-trip system
latency is higher than simpler designs without DSP or only basic DSP mixing. This is due to the
internal buffers required for the DSP engine to provide both stable, ultra-low latency
While the USB driver latency is comparable to other audio devices, when coupled with the
Studio 192’s internal conversion and DSP buffering times, the resulting overall round-trip
system latency is higher than basic I/O devices, however the total system latency of the Studio
192 is on par with other devices with similar plugin processing, high-quality audio converters,
and high simultaneous input and output configurations.
This DSP engine has been optimized to provide 2 ms of round trip latency from inputs through
the Fat Channel plugin processing to any of the physical outputs while using UC Surface or
Studio One. This configuration also supports recording the input signal pre- or post-Fat Channel
plugin processing to your favorite DAW application, plus up to sixteen stereo monitor mixes
(nine in UC Surface), two additional two stereo mix busses for the onboard reverb and delay
For Studio One 3 users, the DSP engine is an integrated part of their mixing and recording
environment. The proprietary hybrid Fat Channel plugin’s flexible design allows users to record
and monitor through the same Fat Channel processing with a sonically seamless transition. This
solves the infamous ‘punch-in’ problem where the audio jumps between playback and
recording as the processing is added and removed. This functionality has previously only been
available in a few high-end professional interfaces and provides optimized mixing and
monitoring within the Studio One 3 environment.
Studio 192 is apparently a Class Compliant USB audio device. As such it relies on OS drivers. I'm a Mac user working with OS X 10.11. My Firestudio units work perfectly every time (TCAT Dice II drivers) while my little Audiobox iOne (class compliant) isn't completely reliable (sometimes it looses connection or isn't recognized after boot or restart).
A hybrid Studio 192 (Firewire/USB) would have been great... but I understand that Thunderbolt / USB 3 are the new trend.
From a user point of view a Thunderbolt/USB3 audio device basically brings us back 15 years back when PCI cards (and after that FW) from Echo, Digidesign, EMU, etc where just as powerful and stable... So, other than keep changing cables and protocols ... everything is pretty much unchanged.
Studio 192 is apparently a Class Compliant USB audio device. As such it relies on OS drivers.
I'm not really the well versed computer tech guy like some of you guys (so my impressions of this might be incorrect) but I thought "class compliant" only meant that it will or can operate without a proprietary driver or an ASIO driver, not that it only ever uses the OS driver. It has an ASIO driver.
I mean, for example, a class compliant device will (or should) work with an iPad, where you can't install any of your mfg drivers.
Since Presonus wont address this issue and are banning members who ask for this information I WONT be getting this box
Great job MODS!!!
shanabit wroteSince Presonus wont address this issue and are banning members who ask for this information I WONT be getting this box
Well the 192 just took a bonking in Sound on Sound. Poor software and huge latency issues. I am still running an 1818vsl and you know how we got treated with the VSL boxes. Abandoned and they never got it all working right.
Users browsing this forum: No registered users and 2 guests