As in the heading. This driver has appeared it seems over night and is preventing GP from loading the correct Focusrite
driver.
This might help:
I found that the Magix driver was installed with Sony Sound Forge. I have uninstalled it as I rarely used it. But, how it came to rule over my Focusrite driver quite suddenly, I can not figure out.
Hey, thanks for that.
Did that work? Is everything back to normal?
Well, in the end, I had to load an image saved in late October to get things back to normal. And that was just before your answer arrived. Any ideas as to why Magix would suddenly rear up and take control? It was even pushing the Focusrite driver out and putting itself in as I changed rack spaces. My two hour gig in the Main Street of the nearby town just didn’t happen. I was furious as I packed up and crawled home in great embarrassment without a note being played. And of course, no pay either.
This has been a disastrous day for me. Is it possible to send a script or message of some sort whenever GP is booted up that will correctly set the necessary details for the Focusrite software? Anything that will help avoid this shocker happening again.
Was this something you recently installed? If so, once you have your gigging system working, avoid installing anything new or making other changes. You never know what unexpected impacts even a seemingly insignificant change could have.
If you like to test new things, then having a separate computer would be a good option, in order to keep your working gigging system protected.
Stop installing new stuff, stop upgrading on a machine that is critical for live performance. Keep a backup machine with an identical configuration.
For what it’s worth, while I’m one of the GP developers and I have to make sure that GP itself will run on recent machines with recent updates, etc. the actual laptop I use for live performance with my bands is a 7 year old machine running an OS that is also 7 years old and hasn’t been updated. And before I got that one (second hand refurbished), I was using machines from 2012
I’ve probably only updated a few plugins on that machine over that whole time period after testing them extensively first. Other than that, those machines don’t even connect to the internet.
Hi Al,
Maybe you can repurpose your old Surface Pro for applications that you don’t use for live gigs? Other than that, I agree with @dhj that you should do everything you can to freeze your configuration of the performance machine including disabling software updates or loading other applications. If you need to update your Gig Files, give your self 3-4 days to test prior to a performance. I’m so sorry your performance went bad but I don’t think we can blame it on Gig Performer. I feel your pain though.
Steve
My SP9 I’ve only had maybe three months, and it was new when I got it. I haven’t been installing new stuff and I only update plugins when I get a notification. I am not going to install the stuff I don’t use much from now on.
Don’t even do that without a lot of care and plenty of time to revert. You cannot assume that plugin updates will be flawless
I don’t have a second machine. My SP9 is solely used for gigging with Gip Performer. All the internet stuff I do, is carried out using iPads.
After a good night’s sleep, I feel better. I really appreciate the positive comments from all you guys. I’m doing something that I know several posters don’t agree with, and that is, a fresh rebuild of my Surface Pro 9. Whilst Win 11 is a great OS that does run well on my SP9, the build I was using at the crash time was probably a year old (and had been updated) and was based around an image that was taken from my SP8. So I do feel that a new, fresh build is a good thing in this case.
Well I guess somewhere along the line, you installed this. Are you using it for anything?
Steve
Only when I have a sound file I want to trigger at a certain time within GP, but needs editing first. I think I’ll just use Audacity for that purpose from now on. Sound Forge won’t be installed in future. Strangely enough, its been sitting there unused for three months without a peep. Why its Magix driver decided to play up and shoot me down suddenly is hard to understand.
Maybe it has an automatic updater that runs periodically. Do you ever connect your Surface Pro to the internet? Some programs do this. For instance Corel Video Studio has a background process that periodically shows “specials”. It if very annoying and hard to turn off. Also McAfee seems to do automatic updates in the background. None of these are part of the Windows update process but have their own background tasks that do this stuff. You would either need to de-install apps that do this or never hook them up to the internet so that they don’t do updates.
Steve
I only use Windows Defender.
So now that we know that Sony Sound Forge misbehaves, it would probably be a good idea to either find a different program to accomplish what it does or run it on a different system, do your editing and the move the Audacity sound file to your Surface Pro.
If you want to continue using the same program, I would suggest talking to the software manufacturer about fixing their problem.
Steve
If you’re going to do that, don’t forget to deregister/deactivate plugins and applications with a license, for example your iLok if you have that, PA plugins, GP itself (although the GP helpdesk is, to my experience, very helpful), etcetera.