Introducing Portal

[Kim]

@Rom

Portal can be seen as a virtual audio loopback, so if you are using 128 samples in the system parameters, the effects after Portal are using 2 x 128 samples, so you add some latency…

Yes, this is right, I got some flangering in some setups. But with a setup that avoids that flangering it is not hearabel to me. I am a guitar and mandoline player. May be with synths it is hearable. to me… and to be honest I cannot imagine that anyone can hear it.

[Teuvosick]

I measured exactly 5,0 ms of latency

[oeSmash]

Oh hey this just gave me an idea to maybe run RM pro into the recorder plugin, where I don’t care about extra latency while playing… I can still have my normal chain going out with the usual latency… Still haven’t worked portal into any of my stuff… maybe I’m still too used to CPU tetris…

[rogeriocouto]

Hey @falkTX

How cool to see you use one of my PBs as an example for such an interesting plugin.
I have not been able to keep up with the forum lately, and when I saw this plugin, my fingers started to itch.

All the best for you guys!!!

[malfunction54]

I was just noticing a few days ago that you had not posted in a while @rogeriocouto !

[Aurex]

Veramente utile. Non ho trovato altri modi per ottimizzare la CPU.
E quel bel gateway di Portal funziona. Evita i glitches finali del processore.
Grazie…

[Kopplog]

congrats!
this was a crucial piece to develop in terms of regarding CPU economics.
I´m impressed - you saved my preset

[Kopplog]

Any idea how the Portal works on a ModDuoX-ProductionModel?
Experiences anyone?

[dreamer]

The same as on all the other models …

[khz]

@ignis32

Meanwhile, MDX has 2 more cores than Dwarf, is it theoretically possible to have more portals there? Not like I feel very limited at the moment, just curious.

With the plugins that can buffered this is possible. IMHO

Plugin Updates (Official Store)

IR loader cabsim updated to 1.0-20 Neural Amp Modeler updated to 1.0-11 Minor CPU optimizations to these 2 plugins.

MOD - Convolution Loader

We just pushed an update to this IR loader plugin to support a “buffered” approach to reverb, by means of a new parameter in the advanced settings of the plugin. It is off by default in order to keep compatibility with existing pedalboards. As you might know, this reverb plugin uses background threads as a “2nd stage” of processing (so 1st part of the reverb is processed in realtime, rest is processed in the background). What this new parameter/option does is offload this realtime processing …

[Carlos_Galvez]

I guess I’m late for the party, but I just want to say that I LOVE “PORTAL” Plugin!!! I was running a heavy pedalboard at 256 frames with 92% CPU Load… Now with Portal, the same pedalboard at 256 frames is just 49% CPU Load!!! … and at 128 frames is just 72% !!!

I don’t know who was the developer of the Portal plugin but I just want to say THANKS!!! and by the way, thanks to Hugo Sanchez, he told me about Portal! Now I love even more my ModDwarf!!

[LievenDV]

Yeah I saw your post on the Fb page as well.

Can’t spread enough love for this plugin!
I put it on every pedalboard.

Thos those who don’t understand it, just TRY it

• Load one of your heavier pedalboards
• Check the cpu load
• stick a portal somewhere after you drives/dist section and before your time based plugins.
• read the cpu load again.

Your favourite board just got some extra processor power to spare!

[toferyu]

Hey thanks for clarifying
When you say

@LievenDV

• stick a portal somewhere after you drives/dist section and before your time based plugins.

Such as delay or reverb ?

[gianfranco]

@toferyu

Such as delay or reverb ?

Exactly. I put an example above.

@gianfranco

But I can split the wet part like this:

Now the CPU load is still manageable, there is not perceptible added latency as the dry signal does not use the Portal, and the wet chain, which is much less sensitive to latency in this case, is diverted to another core.

[toferyu]

Perfect !
Thanks

[Jandalf]

But if you don’t have a direct connection bypassing the portal - for example as it is in the board of @Carlos_Galvez - then the added latency will also affect the plugins that are before the portal, right?

[funkypou]

You’re right. If the signal that goes through the Portal has no parallel direct path to the output, it will be affected by extra latency. If it has a parallel path, the same signal is sent to 2 places :

• the direct path : no extra latency.
• the Portal path : extra latency.

If you want to keep a very low latency, this parallel kind of use is interesting but it’s limited by 2 factors regarding the plugins that come after the Portal :

• the fact that latency is not important for them (eg : reverb, delay).
• their ability to achieve the desired tone when mixed in parallel (it’s OK for a reverb or a delay but would be weird for a distortion and inefficient for tremolo).

[LievenDV]

To be honest, We play a genre of music that is quite fast and I haven’t noticed the latency (and I don’t even use a parallel non-portal signal)

[Boi_Social]

This quick explanation should be added to the plugin description

[Anderson_cezar_gomes]

How to instal this plugin? I cannot find it on plugin store. Can you help me please?