Discuss Quantum Thunderbolt Interface Here
14 posts
Page 1 of 1
Has anyone had success recording into Studio One 4 with a Quantum and not used Low Z Monitoring? For being a fast interface I find there is stil too much latency to record without using Low Z.

MacBook Pro Retina, 13 inch Early 2015
2.7 ghz Intel Core i5
8 GB 1867 MHz DDR3
mac OS Sierra 10.12.6
Mac Pro late 2013
3.5 GHz 6-Core Intel Xeon E5
16GB 1866 MHz DDR3
Mojave
Presonus Quantum, Presonus Studio One Pro 4, Presonus Faderport, Presonus Digimax FS, Softube Console1MK II
User avatar
by MarkusHassold on Tue Aug 07, 2018 11:53 pm
Low-z only means using the lowest buffersize you have adjusted - without Low-z it uses the buffersize set for dropout-protection which can be very high.

So it doesn't make any sense not using Low-z when recording.

Presonus Firestudio Tube, Firestudio Project with Universal Control 1.7.6, Presonus Faderport, Bluetube DP, HP 4, Bluemax.....

Presonus Studio One Pro 4.1.1
Celemony Melodyne Studio 4.2
Softube Console1 MK II, Volume 2

- Mac Mini 6.2, (2014), internal SSD+HD, 2,3 GHz Core i7 quad, 16 GB RAM, MacOS 10.13.6 High Sierra
- iMac 27" 3,4 GHz Core i5 quad, 1TB Fusion-Drive, 8 GB RAM, MacOS 10.14.3 Mojave
External harddiscs (3.5" - 7200 rpm) USB 3.0.
User avatar
by adzord on Thu Aug 16, 2018 5:06 pm
Thanks for the reply,
The reason I ask, is that I am using Softube Console One and you cannot even have it on a track whether is enabled or not enabled and use low Z on the master bus when you enable record. I only use console one for mixing but its nice to have it all set up on a template.

MacBook Pro Retina, 13 inch Early 2015
2.7 ghz Intel Core i5
8 GB 1867 MHz DDR3
mac OS Sierra 10.12.6
Mac Pro late 2013
3.5 GHz 6-Core Intel Xeon E5
16GB 1866 MHz DDR3
Mojave
Presonus Quantum, Presonus Studio One Pro 4, Presonus Faderport, Presonus Digimax FS, Softube Console1MK II
User avatar
by Jim Roseberry on Fri Aug 17, 2018 8:07 am
The issue is that Console One plugins are latent (add additional latency).
That latency has to be compensated (whether the plugin is turned on/off), so you can immediately mute/unmute the track/bus.
If latency compensation wasn't enabled for plugins that are turned off, it would have to be calculated/applied after you hit the transport (causing sluggish response).

Best Regards,
Jim Roseberry
www.studiocat.com
jim@studiocat.com
User avatar
by Jessa on Sat Feb 02, 2019 8:38 am
Yup, no problem, monitoring through Slate plugs (except VTM) and Waves, reverbs / delays etc RTL 1.6ms @96k , 64 samples, dropout protection set to low , rock solid stability on Win 10 PC. I don't like monitoring with green Z at all, too many workarounds to make it play nice..:)
User avatar
by robertgray3 on Sat Feb 09, 2019 1:43 pm
Too much latency? Is that only when you use Console One? I'll run some tests but with the Quantum even the regular latency times (no green Z) are listed as much lower than the same buffers were on my last USB interfaces...

Mac OS X Mojave 10.14
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
User avatar
by Jim Roseberry on Fri Feb 15, 2019 9:10 am
Studio One uses a "Hybrid Buffering" technique.

If you have Dropout Protection set Maximum (2048 samples), the extra buffering significantly raises round-trip latency.
Using the Green Z button allows monitoring that particular track/s with normal latency (bypasses the dropout protection buffer for that track/s).

The larger Dropout Protection buffer allows more efficient CPU use (at the cost of additional latency).
The Green Z button allows you to monitor tracks without that additional buffer/latency.
This gives you the best of both worlds (more efficient CPU use... and the ability to work at low latency).

Studio One paired with Quantum is a great low-latency combination.
Studio One is one of the few DAW applications where you can effectively work at 96k using a 32-sample ASIO buffer size. That's 1ms total round-trip latency.
You can effectively play/monitor in realtime thru AmpSim plugins like Helix Native or the new TH-U with super tight timing (1ms total round-trip latency).
CPU use is pretty high with Helix Native... but the audio is glitch-free.
Without Hybrid Buffering, this would be much less practical...

Best Regards,
Jim Roseberry
www.studiocat.com
jim@studiocat.com
User avatar
by pauldormer1 on Wed Feb 20, 2019 3:55 pm
You seem rather knowledgeable Mr Roseberry :)

I wonder, if you are a Mac user, could you recommend bitrate / kHz / buffer settings for the rather common combo of Quantum (2) + late 2013 Mac (base model) ?
User avatar
by Jim Roseberry on Wed Feb 27, 2019 1:26 pm
pauldormer1 wroteYou seem rather knowledgeable Mr Roseberry :)

I wonder, if you are a Mac user, could you recommend bitrate / kHz / buffer settings for the rather common combo of Quantum (2) + late 2013 Mac (base model) ?


Hi Paul,

There's not a "one side fits all" answer. ;)
Each scenario is different.

The Quantum/2 can go down to a 16-sample ASIO buffer size.
No current machine is going to be able to effectively work at that setting.
To effectively work at the 32-sample ASIO buffer size (especially with higher sample-rates), it takes a fast recent-make machine.

Given your machine, I'd say 64-128 sample ASIO buffer size would be a reasonable starting point.

Regarding sample-rate, I do think the sound-stage is a little more 3D at higher sample-rates.
That said, I think there are numerous other factors that play a larger role in the ultimate quality of a recording. Mics/position/instrument/performance/arrangement/song/room/etc all play a larger factor than the sample-rate.
Some folks get hung-up on sample-rate. I had one local guy tell me, "No professional would work at anything other than 96k." Ironically, this person hasn't released anything professionally.
My wife is on the local classic-rock station's morning show. They do everything at 44.1k.
No record has been (or not been) purchased solely based on the sample-rate used to record it.
There are situations where 44.1k is more practical (large/dense projects).
If working with video, 48k is more practical.
If you're recording an acoustic guitar player who simultaneously sings... and you want to capture as much detail as possible, working at higher sample-rates isn't a bad idea (the overall project load isn't very high).

Best Regards,
Jim Roseberry
www.studiocat.com
jim@studiocat.com
User avatar
by jpettit on Wed Feb 27, 2019 2:22 pm
Quantum set to 16 buffers 48k
Image

That is about 1.5 feet between the mic and your speaker for recording general tracks and 5 feet if you need to punch into an existing track.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by pauldormer1 on Sat Mar 02, 2019 9:11 am
Thanks chaps!

Yes I think audio-wise the bitrate is more important (although I'm interested in recording some hi res sounds of nature to slow down! Hear what are above our ears). I have tended to stick with 44.1Khz, just for compatibility and familiarities sake really. I was under the impression though that increasing sample rate leads to slightly less latency?

I think you are right 64 samples, I've had a few clicks at 32 when running a lot of processing... I'll try working around these settings, and jpetit that seems a fairly decent there. Why may I ask tho, is LLM not OK for punch ins?
User avatar
by jpettit on Sat Mar 02, 2019 10:27 am
Please read the low latency handbook found in the FAQ section of the forum.
One side affect of LLM is that you cannot hear the existing track prior to a punch in when in that mode.
The handbook explains 3 to 4 work arounds the simplest one of which is just to not use LLM in that situation.

Yes increasing sample rate decreases latency.

It’s all really a matter of what works for you.

For most people anything under 10 ms RTL is sufficient.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by pauldormer1 on Sat Mar 02, 2019 10:40 am
Will read the handbook. Apologies asking a redundant question!

I find under 10ms decent, but the low latency is clearly a draw for the Quantum range. In DI guitar / Mic performance, I want to get as close to hardware feel as possible! I notice a disconnect even at low ms.
User avatar
by Skip Jones on Sat Mar 02, 2019 12:32 pm
jpettit1 is da man!

:reading:

Skip

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Windows 10 X 64 : AMD Phenom II X 4 945, ATI Radeon 5450 / 512 RAM - 8GB RAM / 1T SATA, Mac Mini (Late 2014), Faderport and Faderport 8, Yamaha S-08 Synth, Fishman TriplePlay Guitar MIDI, Logidy Controller, assorted PreSonus Gear

14 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 2 guests