I am getting a blue screen during the process of opening an existing project that I haven't been in since last year. All of my other projects open just fine. I'm wondering if it could be a plugin or something. Is there a way to disable plugins during the time you are opening the project? to maybe get around what the problem is and at least open the project with just the raw tracks?
For the longer term, this must mean that my PC has some memory or something that is going bad. Because I have not changed anything at all (no updates, etc.) since I was working on this project last year.
Any help is much appreciated. Thanks.
Hey Jay, I feel your concern. I've not experienced this. Turning off some plugs can be done in your Systems/Effects/VST
Try the support forums for this one too and then get back to us with any solutions so we can pass it on as well.
JayTerrance, post: 448918, member: 49019 wrote: I am getting a blue screen during the process of opening an existing project that I haven't been in since last year. All of my other projects open just fine. I'm wondering if it could be a plugin or something. Is there a way to disable plugins during the time you are opening the project? to maybe get around what the problem is and at least open the project with just the raw tracks?
Yeah, this a new one on me too, Jay.
I've had Samp almost three years now, and I can open older files with no problems, or perhaps I should say, at least I haven't encountered any problems... yet... ( knock wood)
Generally, if there's a plug-in or VSTi that's associated with that project file; that's either run out its trial period, or is having difficulty loading for other reasons, you'll get a message from Samp during start-up giving you the choice to continue loading and ignore the plug in question, or to activate or repair the plug/sample.
Then again, we don't even know for sure if it is the fault of a particular plug or VSTi ... That's a valid thing to consider, but it could be that this particular project file just became corrupted some how, or is missing data, and Samp doesn't know what to do with it.
JayTerrance, post: 448918, member: 49019 wrote: For the longer term, this must mean that my PC has some memory or something that is going bad. Because I have not changed anything at all (no updates, etc.) since I was working on this project last year.
Well, we don't know that for sure either, Jay.
It's certainly possible, as it is with most all computers eventually, but I wouldn't run out and spend a bunch of money on a new system until we figure out why all your other Samp files are loading fine - but this file in particular does not.
audiokid, post: 448921, member: 1 wrote: Try the support forums for this one too and then get back to us with any solutions so we can pass it on as well.
I'd strongly echo Chris's suggestion, and post this query on the Samplitude forum.
I would also do a search for YouTube videos on the subject, look for Samp instructional vids from a very knowledgeable guy named "Kraznet".
He's incredibly knowledgeable on all things Samp/Sequoia.
As a side note: Have you ever optimized your version of Windows for audio production? Marco (pcrecord ) has a link to a great video on the subject, with step by step instructions on how to get the most out of your audio production with Windows..
(Let me see if I can find it...)
Here ya go.... I copied these from one of Marco's posts:
Donny - Thanks for those Optimizing tips. I will give that a try first.
I just keep thinking it is probably something with my PC because of the Blue Screen Error. Especially when no one else has gotten this issue. A slowly failing piece of hardware? A drive that is badly fragmented? hmm - but that shouldn't produce a blue screen.
All of my VST's are up-to-date.
JayTerrance, post: 448954, member: 49019 wrote: I just keep thinking it is probably something with my PC because of the Blue Screen Error. Especially when no one else has gotten this issue
I'm not saying it's not possible that you have an actual computer problem somewhere, Jay ... it very well may be that you do.
But ... the fact that all your other Samp files are opening fine, except for just that one, kinda points us in the direction of there being something wrong with the file itself; maybe it got corrupted somehow, I'm not saying I know for sure.
It could be a directory thing - like it can't find the audio associated with the file? Have you done any recent organizing or house-cleaning on your PC? Maybe moved something somewhere, to a directory that's different from what Samp is looking for?
I'm just thinking out loud here, pal.
The thing is... if you are able to open other Samp files, and Samp boots normally, then I doubt it's because something is wrong with your computer, or at least, if there is, that's not what's causing this problem.
If you were having this same thing happen when you tried to open any Samp project file, then I'd say that your Samp program was corrupted - which would mean you'd need to wipe the program itself and reinstall it.
But from what you've described, other Samp project files are opening with no issues... right?
I'd still echo (audiokid ) Chris's advice, and take this problem over to the Samplitude Forum... Like yourself and Chris, I'm a Samp user, and I love to help others with Samplitude stuff when I feel I can be of assistance ( you should keep using it...we're all gonna have gang jackets made, hang out on the corner in front of the drug store, and let our hair grow... :cool: ) ...but because what you've described has never happened to me before, I have no helpful advice to offer, other than suggesting that you talk to some other very smart Magix users, or, that maybe you should file a support ticket with Magix.
The few times I've done this, they've always been very good about getting back to me.
It's not like Avid's "Bermuda Triangle", where you file a support ticket and it disappears of the radar screen, or if they do decide to get back to you, it might be in two weeks - maybe LOL; and then, before they assist you, they want to know what support "subscription plan" you have... o_O
Let us know what you find out. ;)
After a long few weeks of getting info from various sources and the Samplitude forum (and here), I was finally able to get into my problem projects! I didn't get too much help from the Samplitude forum, so I went to Jim Roseberry who I purchased my DAW from a few years back (since a BSOD usually equates to hardware in my simple mind). Jim was extremely helpful and timely with first helping me diagnose if it was my hard drive (No); then he helped me thru testing my memory sticks (No); then he mentioned about some things with the VST's and possibly copying them out of their location. His thoughts spurred me to think of the preset VST options in Samplitude. So I went in and started to change those presets to various ones and by changing to the preset of ASIO VST I was able to open up the problem projects!
HOW and IF that preset was ever changed I do not know, but I feel good about getting those projects back. And the maker of my DAW - Jim Roseberry - gave excellent service years after.
I was actually very close with AudioKid's suggestion above of the System/Effects/VST but I just didn't follow it through to changing the presets back a few weeks ago when AudioKid mentioned this.
So big thanks to Jim Roseberry (and AudioKid) for their help on this one. A big "Thank You" to Donny who provided a ton of information to me right from the get-go on this too.
I'm glad you and Jim Roseberry were able to fix the problem.
Jim has a well-deserved reputation for building great audio production computers. I remember following him years ago on one of the old Cakewalk forums, and I personally know 6 people who have had him build lean and mean turn-key systems for them - and every single one of those people were over-the-top satisfied with his work.
You couldn't have chosen a better guy to build your production computer for you. ;)
Keep us in the loop with your Samplitude journey. While somewhat deep and complex, I think you will discover many new things about it over time that will make you happy that you chose it. I know that I felt that way.
Oh... and keep those YouTube Samplitude instructional vids from Martin ("Kraznet") close by; you will find them to be priceless as you develop questions and want to learn new things. You may want to consider subscribing to his YT channel, as this makes it a little easier to find specific topics covered.
While I'm pretty familiar with the program after using it for 2 years, there are still things about it, certain features that I discover that I want to know more about, and so I still turn to his Samp vids from time to time. ;)
Happy to hear that your issues were solved!
JayTerrance, post: 450079, member: 49019 wrote: I was actually very close with AudioKid's suggestion above of the System/Effects/VST but I just didn't follow it through to changing the presets back a few weeks ago when AudioKid mentioned this.