Freddie H

Hi Bub!
 
To Rap it up, as long you continue to use x32bit and XP32 you will have problems...
Upgrade to a new computer that can handle all the task with Windows 7 x64bit and SONAR X1 x64.  
 
Best Regards
Freddie

Freddie ... you have no clue what you are talking about on so many levels, which is the main reason I usually skip over your posts.

First: I have run X1 on Windows XP and never saw Guitar Rig Pro 4 spike like this.

Second: I'm running Windows 7 x64 on an Intel i5 W/4GB RAM. I'm running Sonar X1C x86 and X64 as well as Sonar 8.5.3 x86 and x64.

Which reminds me ... I didn't try it in Sonar 8.5.3, so I just did and here's what happened ...

8.5.3 x86 reports 38% CPU usage with 1 track and Guitar Rig Pro.
8.5.3 x64 reports 30% CPU usage with 1 track and Guitar Rig Pro. It spikes to 86% when I first turn on Input Echo.

I use Guitar Rig all the time and I can tell you it never used this much of my system resources until I installed X1C.

I gotta say guys, I am really pissed off right now and should probably just shut this ****ing thing down and get away from it.

I cannot believe installing X1C has done this to my system and affected Guitar Rig and Sonar 8.5.

Unbelievable, absolutely unbelievable.

I gotta go ...

Sonar X1c Producer 64bit, one track, GuitarRig 4 32bit, works as aspected. The same results as with Samplitude 11.21 Pro.

Freddie H

Bub

Freddie H

Hi Bub!

To Rap it up, as long you continue to use x32bit and XP32 you will have problems...
Upgrade to a new computer that can handle all the task with Windows 7 x64bit and SONAR X1 x64.  

Best Regards
Freddie

Freddie ... you have no clue what you are talking about on so many levels, which is the main reason I usually skip over your posts.

First: I have run X1 on Windows XP and never saw Guitar Rig Pro 4 spike like this.

Second: I'm running Windows 7 x64 on an Intel i5 W/4GB RAM. I'm running Sonar X1C x86 and X64 as well as Sonar 8.5.3 x86 and x64.

Which reminds me ... I didn't try it in Sonar 8.5.3, so I just did and here's what happened ...

8.5.3 x86 reports 38% CPU usage with 1 track and Guitar Rig Pro.
8.5.3 x64 reports 30% CPU usage with 1 track and Guitar Rig Pro. It spikes to 86% when I first turn on Input Echo.

I use Guitar Rig all the time and I can tell you it never used this much of my system resources until I installed X1C.

I gotta say guys, I am really pissed off right now and should probably just shut this ****ing thing down and get away from it.

I cannot believe installing X1C has done this to my system and affected Guitar Rig and Sonar 8.5.

Unbelievable, absolutely unbelievable.

I gotta go ...

Okay great ! You need more RAM 8-16 GB....

If you can't understand the fact that Guitar Rig 4 worked on 3 ~ 5% CPU Usage before X1C and uses 40% after X1C on an i5 Win7x64 w/4GB RAM ... you got bigger problems than anyone here can help you with.

Seek a professional Freddie.

Brandon Ryan [Cakewalk]

It's hard for us all to go "Yeah they need to fix this crap when none of us see the same behavior. So let's all just try to stay calm and determine what this anomaly stems from. We all might learn something.

I understand Brandon, but when I got a guy coming on here telling me an i5 Quad Core with 4GB of RAM isn't enough to run 1 track and 1 effect ... give me a freaking break.

I'm going to do a system restore and go back to X1B.

I'll be back later to let you know the results.

Personally, I think it has something to do with the .Net 2010 redistributable X1C installed on my system when I updated.

I'll do the restore now and report back shortly.

Thank you.

Bub

Bub

Personally, I think it has something to do with the .Net 2010 redistributable X1C installed on my system when I updated.

You don't already have this installed on your system? I believe this is just C/C++ shared libraries that many (I mean many) applications utilize. So it seems strange to me that you don't already have this on your machine unless the machine is very new.

JonD

digitalboy

....
 
Then when I try and run the SINGLE loop track with a single FX inserted - MixControl Pro - the CPU meters go crazy and spike out again... 
  
 

This plug-in is a beta release.  Do I have to point out why it's a bad choice for testing with X1C?
 

I understand that...But it was also going crazy with the Mix Control Pro diasabled...
 
I used MCP because I had it "in my hand" - having just DL'd it and I was always a fan of the original....
 
As soon as I hit the global FX defeat button,the spikes on the CPU meter calm down...
 
BUT THERE ARE NO FX INSERTED !   Explain that please...
 
This computer is a dedicated DAW with no internet or wireless etc,but like I said in an earlier post,I am going to build a couple of new monsters and see what Sonar X1c has to say about that...
 
Ohhh - and before anyone says anything more about Windows XP...This is Win 7 Pro x64 with 8 GB of RAM and lots of the good fruit...
 

digitalboy

JonD

digitalboy

....
 
Then when I try and run the SINGLE loop track with a single FX inserted - MixControl Pro - the CPU meters go crazy and spike out again... 
  
 

This plug-in is a beta release.  Do I have to point out why it's a bad choice for testing with X1C?
 

I understand that...But it was also going crazy with the Mix Control Pro diasabled...
 
I used MCP because I had it "in my hand" - having just DL'd it and I was always a fan of the original....
 
As soon as I hit the global FX defeat button,the spikes on the CPU meter calm down...
 
BUT THERE ARE NO FX INSERTED !   Explain that please...
 
This computer is a dedicated DAW with no internet or wireless etc,but like I said in an earlier post,I am going to build a couple of new monsters and see what Sonar X1c has to say about that...
 
Ohhh - and before anyone says anything more about Windows XP...This is Win 7 Pro x64 with 8 GB of RAM and lots of the good fruit...
 

When you say there are NO FX INSERTED is this on a saved project with the deleted and defeated FX or are you leaving Sonar open after deleting the FX and still seeing the spikes at that point?   If the latter is the case that would definitely point at the FX not closing properly when deleted.  In other words it is showing it is removed from the project but it actually is still using resources until the project closes. 
If so the FX developers may not have tested it in Sonar and may not be aware of the problem.  If it is still in Beta phase it may be valuable to them to advise them of the problem so they can address it.

Jonbouy


I have Windows 7, 64 bit installed on my i7 based machine.

Despite this Freddie is still incredibly glitchy. (Not that it REALLY matters.)

Anyone else seeing this behaviour?
 

Is Freddie glitchy or is it Sonar ?  Freddie does matter really  
 
Yes - We see all sorts of behaviour around these parts....
 
OK...I may have identified the cause of the problem...
 
I think the problem on this machine may be related to the Intel Turbo Boost Utility...

I have deleted this program and the craziness in the spikes have disappeared...... 

The CPU meters are still a little irrational with no activity,but calm down when the FX defeat is engaged...
 
And to the guys who were targeting the BETA of MCP,it was occurring with ALL plugins... 
 
So I have put the safety on the shotgun and I will keep you all posted... 
   
Thanks for your patience,myriad of suggestions and support...Much appreciated
 
I'm still looking foward to building those new DAWs though  
 
BTW Ryan...Has that problem with the digital noise when automating PX64 been fixed yet ?
 
 

lorneyb2

digitalboy

JonD

digitalboy

....

Then when I try and run the SINGLE loop track with a single FX inserted - MixControl Pro - the CPU meters go crazy and spike out again... 
 

This plug-in is a beta release.  Do I have to point out why it's a bad choice for testing with X1C?

I understand that...But it was also going crazy with the Mix Control Pro diasabled...

I used MCP because I had it "in my hand" - having just DL'd it and I was always a fan of the original....

As soon as I hit the global FX defeat button,the spikes on the CPU meter calm down...

BUT THERE ARE NO FX INSERTED !   Explain that please...

This computer is a dedicated DAW with no internet or wireless etc,but like I said in an earlier post,I am going to build a couple of new monsters and see what Sonar X1c has to say about that...

Ohhh - and before anyone says anything more about Windows XP...This is Win 7 Pro x64 with 8 GB of RAM and lots of the good fruit...

When you say there are NO FX INSERTED is this on a saved project with the deleted and defeated FX or are you leaving Sonar open after deleting the FX and still seeing the spikes at that point?   If the latter is the case that would definitely point at the FX not closing properly when deleted.  In other words it is showing it is removed from the project but it actually is still using resources until the project closes. 
If so the FX developers may not have tested it in Sonar and may not be aware of the problem.  If it is still in Beta phase it may be valuable to them to advise them of the problem so they can address it.

Exactly my point.  There simply is no way to know that the beta plug is behaving correctly - even when you've removed it (As lorneyb2 implied - Did it really get removed?).
 
What happens if you try the same thing  with another plug?  Better yet, grab three others from different developers and go through the same process (making sure to close the project after each one).  What happens?  
 

Brandon Ryan [Cakewalk]

Thanks for investigating further Bub. Will be intersting to see what it ends up being.

Sorry I didn't report back sooner. My ISP went down right after I made the post saying I would do the system restore and report back.

I did the system restore and X1B Build 242 is showing the same results now.

Here's what I'm seeing.

I load X1b Build 242 and 8.5.3 and create a 1 track project. Each version was opened then closed so they weren't running at the same time.

I load Guitar Rig as a VST and turn on Input Echo.

Guitar Rig's CPU meter reports 68% usage .... X1 looks roughly 30% across 3 cores ... 8.5.3 reports 38% CPU usage ... Windows Task Manager reports 20% CPU usage.

Any suggestions before I wipe my HDD and start from scratch?

It was a Windows System Restore. I checked and it took me back to the previous version of the 2010 redistributable but I may be barking up the wrong tree with that. I'm just trying to brainstorm to think of what could have happened?

I did the 32bit X1C update first and it went flawlessly, but it crashed giving me a grooveplayer.dll error when I did the 64bit update. I ran the update as an administrator both times as well. So it could be something to do with that crash as well.

One tweak I made prior to even installing X1 was I did the core parking 'hack'. I wonder if there's something in the X1C Update that doesn't play well with that?

I have a drive image I can go back to, but is there anything you can suggest to check before I do that?

bapu

Bristol_Jonesey


With that setup it'll run like a dream.

Hell - it runs perfectly well on my XP32 machine!!

Jonesy,


How can you say that? Freddie says that's impossible!! 

YES, With my projects it is. You couldn't even OPEN it and start it in x32bit!
X32bit work fine as long you stay with one guitar, one Drum and 6 tracks of Vocals...

Freddie H

bapu

Bristol_Jonesey


With that setup it'll run like a dream.

Hell - it runs perfectly well on my XP32 machine!!

Jonesy,


How can you say that? Freddie says that's impossible!! 

YES, With my projects it is. You couldn't even OPEN it and start it in x32bit!
X32bit work fine as long you stay with one guitar, one Drum and 6 tracks of Vocals...

I don't want to start a flaming war, but I ran a lengthy session last night on one of my projects which contained an awful lot more than one guitar and one drum!

I threw everything I could at it - multiple Pro Channels, extensive automation, numerous plugs, live synths, live V-Vocal clips, switching rapidly between screensets, I basically tried everything to get it to crash.

It didn't.

Freddie H

Okay great ! You need more RAM 8-16 GB....

Plase stop with this. You're giving your self a bad reputation as somebody who doesn't really know how computers work.

Freddie H

Bub

Freddie H

Bub

Freddie H

Hi Bub!

To Rap it up, as long you continue to use x32bit and XP32 you will have problems...
Upgrade to a new computer that can handle all the task with Windows 7 x64bit and SONAR X1 x64.  

Best Regards
Freddie

Freddie ... you have no clue what you are talking about on so many levels, which is the main reason I usually skip over your posts.

First: I have run X1 on Windows XP and never saw Guitar Rig Pro 4 spike like this.

Second: I'm running Windows 7 x64 on an Intel i5 W/4GB RAM. I'm running Sonar X1C x86 and X64 as well as Sonar 8.5.3 x86 and x64.

Which reminds me ... I didn't try it in Sonar 8.5.3, so I just did and here's what happened ...

8.5.3 x86 reports 38% CPU usage with 1 track and Guitar Rig Pro.
8.5.3 x64 reports 30% CPU usage with 1 track and Guitar Rig Pro. It spikes to 86% when I first turn on Input Echo.

I use Guitar Rig all the time and I can tell you it never used this much of my system resources until I installed X1C.

I gotta say guys, I am really pissed off right now and should probably just shut this ****ing thing down and get away from it.

I cannot believe installing X1C has done this to my system and affected Guitar Rig and Sonar 8.5.

Unbelievable, absolutely unbelievable.

I gotta go ...

Okay great ! You need more RAM 8-16 GB....

If you can't understand the fact that Guitar Rig 4 worked on 3 ~ 5% CPU Usage before X1C and uses 40% after X1C on an i5 Win7x64 w/4GB RAM ... you got bigger problems than anyone here can help you with.

Seek a professional Freddie.

Bub!
 
You state almost everyday in this FORUM you have varoius problems with your Setup and X1. Today its Guitar RIG, tomorrow something else.
I'm telling you, you need more RAM then 4GB in Windows 7 and SONAR X1 to work right. I think you should "seek a professional" system manager or one that can help you with your computer. Its obvious it must be s-hit behind the wheels.
 
 
Best Regards
Freddie

Every single problem I have had with X1 has been a bug with the software .... the only problem I had with my system was bad RAM and that was fixed months ago.

If I was running in to white screens of death or blue screens of death, I would look at my sound card drivers, if I was getting constant sonarpdr.exe crashes, I would look at my RAM. Every single problem I have had since day one of X1's release has been a confirmed bug, but even with all the bugs, I've never run in to a situation where I could load 1 track with 1 effect. That's just not right.

So Freddie, I know you are doing this just to be annoying ... but you really are hurting nobody but yourself. And you are spreading misinformation that quite frankly, I'm shocked the admin are allowing to continue ....

@Jim ... Hi Jim, I use Acronis True Image. I recommend it all the time here on the forums and I do have an image to go back to, I mentioned it in another post in this thread. Thanks for the tip though, it should be a requirement of everyone to have a drive imaging program ... and actually Windows 7 has one built in. It's not a nice as ATI but it does work.

Anyhoo ... I'm waiting to hear back from Brandon to see what he has to say before I do a restore from an image.