Gig Performer vs. Kushview Element

[gentleclockdivider]

Don't rule out cantabile
The free versions is pretty future rich , and now there is a handy 'modular/connect with wires' view option

Still stereo only though.

What do you mean still stereo , as inputs to plugins ?
This depends on the plugin , you just got to make them visible .
Audio in/out , afaik depends on your interface .

[mgw38]

Don't rule out cantabile
The free versions is pretty future rich , and now there is a handy 'modular/connect with wires' view option

Still stereo only though.

What do you mean still stereo , as inputs to plugins ?
This depends on the plugin , you just got to make them visible .
Audio in/out , afaik depends on your interface .

I don’t see any mention of multichannel audio support in their documentation.

[msimsek]

I mainly use Element for playing guitar with amp sims. It is much easier than opening and using a DAW, I really don't need to use a DAW just to use amp sims to play. And when I want to record something, I could easily load Element as a vst and use the presets I made while just playing. I have made hundreds of presets for different amp sims and it is quite easy to switch between them using the folder explorer in the side bar.

It is a great tool for me. You can see what I mean here:

[jackoo]

Yes, and I'm sure GP is very well capable of the same.
I'm too lazy to pick up the demo; maybe will do

I would be interested how it does the transitions from one setup to another. Does it load everything in RAM when loading the program? Does it turn off the audio processing for the setups which are not in use, to free up the CPU, ... stuff like that.

I am assuming it doesn't load dlls and samples when changing the setup, or the transition would not be seamless...

[msimsek]

The biggest difference Element has is that you can also load Element as an AU, VST, VST3 or AAX plugin. As far as I know you can't do that with Gig Performer. But I might be wrong.

[deskew]

I am assuming it doesn't load dlls and samples when changing the setup, or the transition would not be seamless...

Mistrust those assumptions


https://gigperformer.com/docs/GP4UserMa ... ading.html

I'm too lazy to pick up the demo

The demo (it's actually 100% fully functional) is there so that one doesn't actually have to make assumptions

[deskew]

The biggest difference Element has is that you can also load Element as an AU, VST, VST3 or AAX plugin. As far as I know you can't do that with Gig Performer. But I might be wrong.

You are not wrong --- this was a deliberate decision on our part - our vision is that GP is part of the musician's instrument, intended to be completely separate from the recording process. Think of using GP in the same way as you would think about your physical effects pedals or your amplifier, etc. They are part of your sound, that you can adjust in real time as you play. They have nothing to do with the recording process.

If your focus is the DAW, you don't need 90% of what Gig Performer offers. There are various articles on the blog section of our website that discuss this philosophy. That said, it is quite feasible to run your DAW and Gig Performer at the same time so that you can record your performance. Again, there are several articles on our forums that explain how to do this.

[jackoo]

I am assuming it doesn't load dlls and samples when changing the setup, or the transition would not be seamless...

Mistrust those assumptions


https://gigperformer.com/docs/GP4UserMa ... ading.html

I'm too lazy to pick up the demo

The demo (it's actually 100% fully functional) is there so that one doesn't actually have to make assumptions

well now you're talking!
This is actual info, and very juicy! Predictive loading sounds very cool!
I'll do my research!
Thanks a lot for the link for the manual!

[deskew]

To be honest, predictive loading is a minor feature in the scheme of things, either to help with situations where a user doesn't have enough RAM or if one wants to have quick access to hundreds or thousands of completely separate topologies available --- wedding bands, for example.

[jackoo]

well, maybe you have in mind one setup per musician - as in musician plays one instrument

For me, a setup means one musician playing all the instruments in the track (live, or guided by input chords)
A setup for one song could easily have 15GB, 20 synths, samplers, 40 effects... occupying 50% of CPU just standing idle.

The trouble is to switch perfectly between these kind of "setups" or "pages".
E.g. one page for a single track / song could look like this:


There is no sequencer on the page, no recording device (well actually in the image there is something recording midi, but it wasn't there from the beginning)...
This is for me one instrument to play live - completely separated from the recording process.

Switching these on the fly? Minor feature? I don't think so.

[deskew]

well, maybe you have in mind one setup per musician - as in musician plays one instrument

Not at all. For example, in one of my bands, a Pink Floyd tribute band, I have about 30 songs. Most of them have completely different topologies and some might even have multiple topologies for different parts of the same song. For example, one song might just have an acoustic piano and an organ (e.g, Great Gig in the Sky). Another song (Money) has a sampler for the money sounds, a Rhodes for the main verses and a Sax plugin for the solo. Then you get something like Sheep which has plugins for Rhodes, Hammond, Strings, ARP Odyssey, Synthi and a few more that I don't remember off the top of my head)

Each of those will be a completely different collection of inter-routed plugins (topology - what you think of as setup perhaps) and widgets and you can switch from one to another on the fly --- even in the middle of a beat, with no glitches. Those are examples of major features.

https://i.imgur.com/v1Ahybh.mp4

Normally, all of this would be loaded into RAM. However, if you are short of RAM, the predictive loading mechanism can be used and if you're following a setlist, then it will even let you switch without delays. In the context of everything else Gig Performer does, predictive loading is a minor feature. I don't even use it myself as I have a machine with 16Gb RAM and that seems to be plenty for what I do.