Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
Quote:
Originally Posted by Lunar Ladder
I wouldn't use the feature myself. Personally, I don't feel the need to do this automatically, and I very seldom use high latency stuff while I actually perform/record. Still, my own needs aren't the needs of everyone , and I can see how this could be nifty in a different workflow, so I was commenting on some misleading remarks and simply misunderstandings that were taking away from what the OP actually proposed.
Gotcha. And I guess it makes sense. Depends more on the individual`s mindset and workflow than anything else.
ReaPack/mpl_Toggle bypass all project FX with latency (PDC) higher than X samples
Hi,
Is this something where you can put your own value? I just updated it but I could not find it.
I can only find as lowest latency 256 and I think 128 is really needed.
If you could...
can anyone tell me if there is a similar function to low latency mode, where all the plugins with high latency gets bypassed in order to be able to record new synths (or audio) part?
This is just for future reference. VST's have progressed to the 3rd level in so that latency is no longer a problem. Reaper can use these 3 generation VST's. For what it's worth Reaper can NUGE (N on the keybord) 1 millisecond at a time left or right.
This is just for future reference. VST's have progressed to the 3rd level in so that latency is no longer a problem. Reaper can use these 3 generation VST's. For what it's worth Reaper can NUGE (N on the keybord) 1 millisecond at a time left or right.
I guess we're talking about 2 different latency. I'm referring to the one for recording, kind of creating a direct monitoring for people like me, that don't use as a main audio card, one that has it.
I guess we're talking about 2 different latency. I'm referring to the one for recording, kind of creating a direct monitoring for people like me, that don't use as a main audio card, one that has it.
It sounds like you have the monitor (software switch on the track) turned on. Try turning it off. Enjoy Andrew
This is just for future reference. VST's have progressed to the 3rd level in so that latency is no longer a problem. Reaper can use these 3 generation VST's. For what it's worth Reaper can NUGE (N on the keybord) 1 millisecond at a time left or right.
You're talking about PDC, rather than bypassing plugins that introduce latency for overdubbing.
The Logic implementation is very simple and neat - a speedometer button on the transport that bypasses all plugins that introduce latency beyond the audio buffer amount.
bypasses all plugins that introduce latency beyond the audio buffer amount.
Weird. What should the two values "an individual plugin's PDC" and "buffer size" have to do with each other ? (Apart from that both contribute to the sum latency.)
Weird. What should the two values "an individual plugin's PDC" and "buffer size" have to do with each other ? (Apart from that both contribute to the sum latency.)
-Michael
It could well be me not understanding how it works.
I'd always presumed that latency was a matter of thresholds, rather than being additive. ie. if a plugin introduces less latency than the audio buffer, the total system latency is unchanged, or if I have 100 plugins with 30 samples of latency, I still only have 30 samples of latency added.
Are you saying that if I have a buffer of 256 samples, and I instantiate a plugin with 32 samples of latency, I now have a total latency of 288 samples?
It could well be me not understanding how it works.
I'd always presumed that latency was a matter of thresholds, rather than being additive. ie. if a plugin introduces less latency than the audio buffer, the total system latency is unchanged, or if I have 100 plugins with 30 samples of latency, I still only have 30 samples of latency added.
Are you saying that if I have a buffer of 256 samples, and I instantiate a plugin with 32 samples of latency, I now have a total latency of 288 samples?
I think you are actually right. But I'm not a tech expert of the matter.
I only know that with some other softwares you push a button and you're done.
I only know that with some other softwares you push a button and you're done.
The good news is that you can do the same in REAPER!
You need ReaPack to have the script mentioned by mpl, but once you have that you can bind it to a toolbar button and have the same functionality as Logic, minus being able to differentiate between virtual instruments and audio tracks... because REAPER doesn't make that distinction.
I don't have time to watch this video, but hopefully it includes binding scripts to toolbar buttons. If not, you'll have to do some googling:
You can also bind it to MIDI/OSC control.
I added 64 and 128 samples to metapackage.
Quote:
Originally Posted by Judders
Are you saying that if I have a buffer of 256 samples, and I instantiate a plugin with 32 samples of latency, I now have a total latency of 288 samples?
I remember (can be wrong) it quanized to the power of two so
Try recording without listening to what you are recording and just the per-recorded stuff in playback mode. If you can't do that then I'd check my hook up.
ReaPack/mpl_Toggle bypass all project FX with latency (PDC) higher than X samples
Hi MPL,
I've been using your feature with some degree of success.
There are 2 main problems. In order to make sure the latency feature is on, I need to open a window plugin that gets bypassed, that by toggling I can be sure where I am. This is actually not too much of a problem even because you can definitely hear the difference.
The second matter is way more important. While recording I had a crash...and the toggling was gone. Same if you close the session exhausted from recording and forget to toggle back. You will loose all the positions.
It could well be me not understanding how it works.
I'd always presumed that latency was a matter of thresholds, rather than being additive. ie. if a plugin introduces less latency than the audio buffer, the total system latency is unchanged
Correct.
Quote:
Originally Posted by Judders
or if I have 100 plugins with 30 samples of latency, I still only have 30 samples of latency added.
Only if you have 1 plugin per track (on 100 tracks).
Are you saying that if I have a buffer of 256 samples, and I instantiate a plugin with 32 samples of latency, I now have a total latency of 288 samples?
, and I can see how this could be nifty in a different workflow, so I was commenting on some misleading remarks and simply misunderstandings that were taking away from what the OP actually proposed.
Linear Mode
