CPU issue in GigPerformer

[npudar]

I see.

Extra work or some ‘extra miles’ are never a problem for me, but there are several issues with these lists.

1. Forgotten
Although initially interested in these lists, such as this Zero-latency plugins list, people seem to forget about them and do not post in them any more.

2. Possibly inaccurate
The list can be misleading: plugin updates can (say) either increase CPU cycles and add latency or the other way round - can be optimized and/or reduce additional latency.

[Hermon]

When I was writing my post, I had already thought of your answers and I knew it wouldn’t really be relevant.
So I think this thread “CPU issue in GigPerformer” is the best place to continue talking about it and posting opinions, even if it’s quickly forgotten.

[npudar]

I think that this thread is not the best thread for this talk
(the title suggests that there is a CPU issue in Gig Performer itself)

Feel free to create a new thread, say, ‘CPU intensive plugins’ and share your observations. I suppose that there are some usual suspects such as Diva.

[Musichandyman_Oscar]

@DaveBoulden

By all means use it to find the sound you want, but once you do, find which engines (i.e. which individual Arturia plugin) provides the sound and use that directly.

Thx!. But the problem is I think you then would need to buy that spesific plugin, or own the V collection.

Also, I own the Stage-73 plugin, and it seems to add around 17% CPU usage by itself. Not so much off a problem when you use it by itself, but when you use it with other CPU heavy stuff it can add up. I bought Lounge Lizard a few days ago, and intend to use that plugin in place of the Arturia Stage-73.

[Hermon]

I’ve created a topic, but as I’m not used to or fluent in English, please let me know if there are any clumsinesses or clarifications to be added.

CPU intensive plugins

Following this post, some answers have been given and it may be interesting to know which plugins are greedy in cpu cycles and if this is the case for all users.

[dhj]

Not sure why we couldn’t just change the title of this topic!

[Wick]

I don’t think this problem is so easily culpable on outboard apps. I feel the problem is totally gig performer based. Mine’s (5.04) fine until I open another app. Then, suddenly, CPU ceilings out. Kill either app and wait a minute or three? Finally, usage drops back to “reasonable”. Very frustrating as I use YouTube and Truefire with Gig Performer all the time. It’s become impossible…

[dhj]

@Wick

Mine’s (5.04)

There is no such version. Do you mean 5.0.40?

@Wick

Then, suddenly, CPU ceilings out

The regular CPU or GP’s Audio Thread CPU?

@Wick

until I open another app

OK - I don’t know what platform you’re running and you haven’t indicated what audio interface you’re using, how much RAM you have, what audio drivers you’re using, etc. but if you’re on Windows, then I would immediately be skeptical of the audio drivers. GP is just a normal application, it’s not doing anything strange or unofficial in terms of its communication with the operating system. Assuming your other app is also trying to use the audio interface, then the most likely issue is the audio interface driver not properly handling multiple applications communicating with it.

[Frank1119]

@dhj

Assuming your other app is also trying to use the audio interface, then the most likely issue is the audio interface driver not properly handling multiple applications communicating with it.

Assuming @Wick is using Windows: maybe it helps to set the Windows audio (on one side) and the ASIO driver used by GP (on the other side) to the same sample rate.

[dhj]

I didn’t even think of that - some other app trying to use a different sample rate