Native Instruments - Komplete 15

[bulevardi]

thanks a lot! seems to be on the right way then, im sorry, only if you got time! is Guitar Rig 7 also faster ? i tend to use the old versions too cause GR6 is so annoyingly slow...

On my setup it's slow.
And it slows down in time too, after 30 minutes continuously changing presets to try out stuff, it starts to freeze or crash.

However, I'm not using it natively, as NI doesn't have a Linux version.
I run the Windows version on my Linux OS (via Wine / Yabridge), and I guess that workaround does slow it down.
Wished I could avoid anything that's Windows related, thát makes stuff sluggish.

[Caine123]

thanks a lot! seems to be on the right way then, im sorry, only if you got time! is Guitar Rig 7 also faster ? i tend to use the old versions too cause GR6 is so annoyingly slow...

On my setup it's slow.
And it slows down in time too, after 30 minutes continuously changing presets to try out stuff, it starts to freeze or crash.

However, I'm not using it natively, as NI doesn't have a Linux version.
I run the Windows version on my Linux OS (via Wine / Yabridge), and I guess that workaround does slow it down.
Wished I could avoid anything that's Windows related, thát makes stuff sluggish.

thanks, hmmm doesnt sound optimized so far. it is just bad how they never fixed K7 and sell you now faster loading times for a paid upgrade price....

maybe Guitar Rig 8 will be faster and you are stuck with v7 then until you upgrade. what a bad company.

[mcbpete]

Maybe email NI and ask if Guitar Rig was influenced by Amplitube

[bulevardi]

thanks, hmmm doesnt sound optimized so far. it is just bad how they never fixed K7 and sell you now faster loading times for a paid upgrade price....

maybe Guitar Rig 8 will be faster and you are stuck with v7 then until you upgrade. what a bad company.

Hmm, still not clearly sure if the problem is Guitar Rig in my personal case.
I tested some stuff here and because I'm running GR in a Yabridge environment, that causes the slowing down here.

I explained my case here:
viewtopic.php?p=8970520#p8970520

Aside that, Guitar Rig is a heavy weight program.

[digitalboytn]

Guitar Rig is a heavy weight program.

The new ICM models in GR7 balance out what started in GR6 perfectly...

If anyone can't make great sounding guitar tracks with GR7,they should put away their geetar and take up crochet or knitting instead

[bulevardi]

Hmm, still not clearly sure if the problem is Guitar Rig in my personal case.
I tested some stuff here and because I'm running GR in a Yabridge environment, that causes the slowing down here.

Just to give an example 'cause I was testing again: one Guitar Rig instance in only one track.
(it's in the yabridge wrapper)

It starts at 800MB RAM when loading, and then quickly builts up while you're using it.
After a while it gets sluggish and after half an hour it eats my RAM: 8,5 Gb !

yabridgeswells.jpg

You can imagine...

[Caine123]

Hmm, still not clearly sure if the problem is Guitar Rig in my personal case.
I tested some stuff here and because I'm running GR in a Yabridge environment, that causes the slowing down here.

Just to give an example 'cause I was testing again: one Guitar Rig instance in only one track.
(it's in the yabridge wrapper)

It starts at 800MB RAM when loading, and then quickly builts up while you're using it.
After a while it gets sluggish and after half an hour it eats my RAM: 8,5 Gb !
yabridgeswells.jpg

You can imagine...

wow, then we need to wait until GR8 i guess for a fix

[_leras]

Hmm, still not clearly sure if the problem is Guitar Rig in my personal case.
I tested some stuff here and because I'm running GR in a Yabridge environment, that causes the slowing down here.

Just to give an example 'cause I was testing again: one Guitar Rig instance in only one track.
(it's in the yabridge wrapper)

It starts at 800MB RAM when loading, and then quickly builts up while you're using it.
After a while it gets sluggish and after half an hour it eats my RAM: 8,5 Gb !
yabridgeswells.jpg

You can imagine...

That's a Yabridge plug in wrapper problem.

Show the same problem in windows and then you would have a point.

This type of misinformation is a waste of everyone's time.

[_leras]

However, I'm not using it natively, as NI doesn't have a Linux version.

I run the Windows version on my Linux OS (via Wine / Yabridge), and I guess that workaround does slow it down.

Wished I could avoid anything that's Windows related, thát makes stuff sluggish.

Just use windows it works great for music.

Blaming NI because your hodgepodge unsupported workaround for unsupported Linux is really wack...

[bulevardi]

That's a Yabridge plug in wrapper problem.

Show the same problem in windows and then you would have a point.

This type of misinformation is a waste of everyone's time.

I guess the problem is not Yabridge slowing it down.
I don't have the problem in Yabridge with other VST's I tested.

I was thinking about testing it on Windows to compare, but due to blue screen of death I didn't get to that point, yet.

I read on reddit that CPU usage is really excessive for Windows users aswel.
So I guess it's not Yabridge. (haven't done a test with LinVST yet...)
https://www.reddit.com/r/NativeInstrume ... _problems/

I suppose I'll record track by track and use the Freeze-track function in Reaper each time. That's not really productive but anyway.

Meanwhile I'll look for alternative guitar amp plugins and try to resell GR later.

Just use windows it works great for music.

If you don't get a BSOD... Windows failed for me tons of times (that started 10 years ago), that's just the reason why I HAD to switch to another OS.
Can't even reïnstall with the original recovery dvd's.

Working on Linux is way stable and lightweight.
When I compare, it's way more productive for me to make music.
Feel free to test it, it's free.

Blaming NI because your hodgepodge unsupported workaround for unsupported Linux is really wack...

Well then, if they'd support it it wouldn't be a problem, innit...

I'm aware that it's not distributed for Linux users.
However, it works perfectly. There are plenty of other linux users who use NI plugins through virtual environments.

If a native Linux installer would be available aside Windows and Mac, that would really be awesome.
Most prominent plugin companies that take their customers serious do that. (Such as U-HE)

The Linux world is currently quite booming with a lot of creative producers. There's a lot of audio stuff made for this market in the past 10 years. It's time for NI to add their (strong) mark to it too.
NI would really benefit from this. And lots of Linux users are willing to pay for quality, if it runs natively and stable on their system, without having the need for virtual environments.

Aswel, many people who are now still using Windows, can then finally use their beloved NI-plugins under Linux and make the switch to be independent from the OS.

[Vocalpoint Studios]

I'm aware that it's not distributed for Linux users. However, it works perfectly. There are plenty of other linux users who use NI plugins through virtual environments.

Whether it works (or not) is besides the point.

If you are actually "aware" this is not supported - what are you doing asking for weird workarounds or support of any kind? There are none.

Use a supported baseline system and I am sure lots of folks can help you out. But please don't try to "360" the conversation into your own personal promo crusade as to why you think Linux is "booming".

If it was booming in the DAW market- it would be supported by NI and millions of NI users would be using their plugins on it.

VP

[BJ]

Windows has been great for music since Windows 7. Are blue screens still a thing? I haven't had one for 20 years. What kind of system are you running?

[Vocalpoint Studios]

Windows has been great for music since Windows 7. Are blue screens still a thing? I haven't had one for 20 years. What kind of system are you running?

Exactly.

Takes a LOT to generate a blue screen and the (very) rare sighting of one is 100% hardware/driver related. I think I had one back in 2008 and that was it.

VP

[audiojunkie]

I'm aware that it's not distributed for Linux users. However, it works perfectly. There are plenty of other linux users who use NI plugins through virtual environments.

Whether it works (or not) is besides the point.

If you are actually "aware" this is not supported - what are you doing asking for weird workarounds or support of any kind? There are none.

Use a supported baseline system and I am sure lots of folks can help you out. But please don't try to "360" the conversation into your own personal promo crusade as to why you think Linux is "booming".

If it was booming in the DAW market- it would be supported by NI and millions of NI users would be using their plugins on it.

VP

I don't disagree with you, but I also believe that there is nothing wrong with "asking", in my opinion. Expecting support where none was promised would be wrong.

I do hope that some developers, little by little, will become more "Linux Friendly" over time. It would be cool if they would be willing to post instructions on how Linux users are successfully using their Windows software through WINE and yabridge in their support section--if a volunteer offered the instructions.

The developer could do that, while being very clear that the software is not supported on linux. That, to me, seems like a question that there is no harm in asking. It's not something that I would "expect" developers to do, but it would be a nice gesture that comes with very little risk.

The word "booming" is a relative thing. Yes, Linux has nowhere near the number of users. However, comparatively, people are starting to flock to Linux in droves. Some try it and don't like it and go back to their previous OS. Many stay. Either way, Linux is getting better and better and is a perfectly valid system for audio work--even if the native Linux software isn't as plentiful as the Windows native software.

[audiojunkie]

Windows has been great for music since Windows 7. Are blue screens still a thing? I haven't had one for 20 years. What kind of system are you running?

It's been great for much longer than that. Some of us have been using it since Windows 3.1. I started using Linux for audio about 5 years ago, and I have no desire to go back. That said, there is nothing wrong with using Windows or MacOs. They are all valid for audio work these days. It comes down to personal preference, as to what a person uses.