PreSonus Forums

steve if you are on windows download it (right click 'save link as') ... then right click pdf file and "open with" a browser... Edge, Internet Explorer etc... it opens with both Google Chrome and Windows Edge fine here. cheers

So, I've decided to track some guitars today to test out these features.

I have a saved FX chain that I have used in the past and like and I've loaded it into a track. My "Z" is green on my output folder and when I put the track into record and monitor, the Inserts all go green, so looking good. Only, I swear it's processing the whole effects chain twice - sounds terrible! If I look at the performance monitor, I see the plug ins listed as Monitoring FX, so all good there, and I also see them listed again as Inserts on the track, but if I disable them there, I lose them completely (in both areas).
If I turn off the green "Z" in the output and try the old fashioned way, it sound normal, the way I would expect - aside for the latency now introduced by dropout protection.

Any ideas?

Cheers, Tim

Only plug-ins 3 ms or less can be heard on the green Z path. Look at the performance monitor and see if they're doubling. They should be but you should only be able to hear one of the two.
If they are greater than 3 ms and you can only hear them on a bus but with the delay.

Thanks for the reply!

I've attached a screenshot of the mixer and performance meter. Cheers

Ah, I think I might have a clue.
My FX chain has splitter tools in it, however, the track was set to mono as it only has the single input, I get the feeling it was processing the two amps in series...

Thanks for the booklet JPettit. Trying to get my head around this. Now, whilst I seem to be able to have the track running at high latency (many plugins etc., a few virtual instruments), and I'm also able to play a VST synth (via Kontakt) at low latency whilst this is happening (ergo, the new feature must be working!?), I cannot choose "use native low latency monitoring" - it is greyed out, as the attachment will show.
If I choose the "enable low latency monitoring for instruments" - which is available, the clicks/pops return.

From what I've read, the native low latency is the better option.... but unavailable for some reason? I'm likely to be missing the obvious.

(i7 4770K, Windows 10 64 bit, Focusrite Clarett 8 Pre via thunderbolt for PC... )

Thanks. This is very helpful.

Jeff's excellent handbook document is the link at the top of this thread and yes, I can open it fine. Try again?

Skip

Speranza wrote1) I cannot choose "use native low latency monitoring" - it is greyed out, as the attachment will show.
2) If I choose the "enable low latency monitoring for instruments" - which is available, the clicks/pops return.

(i7 4770K, Windows 10 64 bit, Focusrite Clarett 8 Pre via thunderbolt for PC... )

1) First clarification. the second option is for people with hardware low latency to NOT use blue Z but use Green Z. It is not available to people who do not have hardware monitoring via Presonus 192 or Quantum series or an ASIO 2 DM driver.
But then I look at you interface and I would think a TB interface would have ASIO DM drivers? I know RME does. To save you time though Green Z trumps them all.

2) This is the opposite behavior expected. We (you and/or the community) would have to start with a test song with the same Kontakt and samples and work up to a point we could replicate it.

jpettit wrote

Speranza wrote1) I cannot choose "use native low latency monitoring" - it is greyed out, as the attachment will show.
2) If I choose the "enable low latency monitoring for instruments" - which is available, the clicks/pops return.

(i7 4770K, Windows 10 64 bit, Focusrite Clarett 8 Pre via thunderbolt for PC... )

1) First clarification. the second option is for people with hardware low latency to NOT use blue Z but use Green Z. It is not available to people who do not have hardware monitoring via Presonus 192 or Quantum series or an ASIO 2 DM driver.
But then I look at you interface and I would think a TB interface would have ASIO DM drivers? I know RME does. To save you time though Green Z trumps them all.

2) This is the opposite behavior expected. We (you and/or the community) would have to start with a test song with the same Kontakt and samples and work up to a point we could replicate it.

Jeff, thanks for the reply.

So it's greyed out because I haven't the necessary hardware i.e. Presonus Quantum/192 etc.

As for point 2, I'm even more confused....

Speranza wrote

jpettit wrote

Speranza wrote1) I cannot choose "use native low latency monitoring" - it is greyed out, as the attachment will show.
2) If I choose the "enable low latency monitoring for instruments" - which is available, the clicks/pops return.

(i7 4770K, Windows 10 64 bit, Focusrite Clarett 8 Pre via thunderbolt for PC... )

1) First clarification. the second option is for people with hardware low latency to NOT use blue Z but use Green Z. It is not available to people who do not have hardware monitoring via Presonus 192 or Quantum series or an ASIO 2 DM driver.
But then I look at you interface and I would think a TB interface would have ASIO DM drivers? I know RME does. To save you time though Green Z trumps them all.

2) This is the opposite behavior expected. We (you and/or the community) would have to start with a test song with the same Kontakt and samples and work up to a point we could replicate it.

Jeff, thanks for the reply.

So it's greyed out because I haven't the necessary hardware i.e. Presonus Quantum/192 etc.

As for point 2, I'm even more confused....

2) If I choose the "enable low latency monitoring for instruments" - which is available, the clicks/pops return

Enabling LLM should NOT cause pops and clicks
Need to get to the bottom of it by starting a new song and adding complexity until the wrong behavior starts.

I'll have to try it when I've more time to test that. Currently in between projects.

What is odd is that the feature is working. I can play a VST instrument at low latency, and the Green Z is lit. It's on maximum drop out protection, and the buffer setting I've chosen on the Focusrite Control Panel is 64 samples (equating to 3.23ms latency according to S1). Thanks for responding here.

Perhaps I shouldn't look a gift horse in the mouth. It's working, so for now, I'll leave it as is and try to get to the bottom of it another time....

Good read on the booklet.
Should prove useful for future needs.
Nice, Jeff.

No issues.

Enjoying three five.

Thanks for trying to help guys, much appreciated.

Tried a fw times downloading again but no joy. I've looked into it further and for some reason my tablet is downloading/seeing the file as a video file, not a pdf file!
Jay ... I don't have the facility to right click and 'open as' cos I'm away from home and only have my tablet with me. It'll wait till I get back to France with my 'brand spanking new' PC - hoping for good things loading S1-3.5 onto a virgin machine (but not naive enough to expect plain sailing) wish me luck......

Regards

tshadgett wroteAh, I think I might have a clue.
My FX chain has splitter tools in it, however, the track was set to mono as it only has the single input, I get the feeling it was processing the two amps in series...

Yes splitters and analysis tools are not supported. (listed in the handbook)

I was even able to open it in iBooks on my iPad.

Steve Carter wroteHi Jeff...

Once again a big thanks for all of your help and efforts. But... unable to open the pdf handbook in your link (tried multiple times)! Is it just me?

Regards....

jpettit wroteHardware monitoring is slightly better than the low latency monitoring
? Do you have both blue and green Zs or are you talking about your direct monitor knob on the device?
The HUGE advantage to Green Z all your VSTs <= 3ms are available during monitoring

I will move post now.

To clarify, I mean yes I have both and that the blue Z is a few ms less than the green Z.
I always use the physical monitor button on the interface when tracking though.

Just a matter if you want to hear the voice/instrument processed and reverb to help the performance.
BTW you should be see a 30% drop across the board on marginal CPU songs.

jpettit wroteJust a matter if you want to hear the voice/instrument processed and reverb to help the performance.

I need more than processing / reverb to help my performance; more like a miracle

jpettit wroteDo you think the key to this is 64 vs 32 bit Process Precision?

It's tough to tell without more information. That's why I'm asking if anyone else can replicate the issue.