Subject:>>>>>>theBSofD<<<<<<

Posted by: fulani

Date:1/22/2003 3:02:59 AM

......PROCESS HAS LOCKED PAGES......



that's the message the beautiful BLUE SCREEN was telling me moments ago.

i was adding an audio track when it happened.

it also suggested that i "Disable BIOS memory options such as caching or shadowing."

also a bunch of 00000000076 , 0x82F7F5E0, k ind of n um b er s
and something about dumping physical memory to disk.


................
\\\\\\\\///////
////////\\\\\\.................




i want to make music. is it possible? i'm tired of troubleshooting .

surely there are people using this software who are having no problems.
enjoying being creative.



Perhaps i can bounce everything out of ACID into PTLE and mix it there.

has anyone done this or something similar?


i hope you are having a productive day.
peace

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: liquid

Date:1/22/2003 9:21:44 AM

Dude, I feel your pain. I'm so sick of having problmes with acid. What pisses me off the most is that I never used to have any problems with earlier versions (3.5). I used to think that acid was "the" best product because it was so stabble. I had been accustom to using logic and I had gotten used to it always crashing. And then I tried acid and it was stable......I loved it. And now it's worse than Logic. What I'm wondering is if I wouldn't be better off to just record a 16 bit bed track in acid, get all my loops in order, and then record vocals, guitar, bass etc... in Vegas or another program. Does anyone else here have any experience with Vegas? Is it stable?

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: stusy

Date:1/22/2003 10:10:34 AM

Prolly the ONLY reason I got acid was for the loop features and the midi stuff as a sideline; I was gettin most of that with sonar131, which I currently don't have installed right now...before I got CD5, I was usin vv3 for puttin it together, then SF6 and into Nero5 (which I only use for data now)...I also have NR2, so sonic foundry-wise, I'm pretty loaded up, maybe too much, but I think they have a high quality product, good tech support, good manuals, a pretty informed newsgroup like sonar's...so sue me if I'm overkill...! if there are problems with their prods I believe they know them and address those issues well, 'course, myself, I'd like to see more updates with what I've got and more faster, but hey, that's rock and roll...

Subject:forward motion

Reply by: fulani

Date:1/22/2003 3:02:52 PM

I'l have a look at Vegas.... also see about importing ACID into PTLE, (I'll have to bounce some tracks down in ACID first though. i'm already pushing 30+ tracks , with more vocals to be added still.)

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: Iacobus

Date:1/22/2003 3:17:30 PM

AFAIK, there was no ACID 3.5, only 3.0. There were builds such as 3.0g, but no 3.5...

Blue screens can be caused from anything. Don't overlook the possibility that it may be driver-related issues relating to hardware.

Vegas is a true multitracker app. It is not like ACID. Don't expect to loop like you do in ACID, just like you wouldn't expect to multitrack in ACID like you do in Vegas. Each was designed to complement the other just as Sound Forge complements them (with its digital audio editing capability).

HTH,
Iacobus

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: pwppch

Date:1/22/2003 3:27:10 PM

>>Blue screens can be caused from anything.

Blue screens can ONLY be caused by driver/kernel level code. If the driver/service is not implemented correctly, then an app can cause the driver to crash the system, but the driver/service is still the cause.

Peter

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: fulani

Date:1/22/2003 4:01:39 PM

Peter, can you offer some specifics on correcting this problem? thanks



liquid, you might want to browse this thread:

http://www.sonicfoundry.com/forums/ShowMessage.asp?MessageID=149986&Replies=21&Page=1

i'm beginning to understand that Vegas is the mulitrack app and ACID is for loop creation. duh.

Subject:RE: forward motion

Reply by: donkerce

Date:1/22/2003 4:33:04 PM

Hey, I always start with an ACID session, then render and import into ProTools.
That way, you can always go back, add loops, whatever and they'll still line up when you import the files into your ProTools session.
And vice-versa I suppose.
You could do your vocals on ProTools, bounce to disk JUST the vocal as a WAV,
and it should line up in ACID for your friends project.
I just upgraded from 2.0 to 4.0.
I don't seem to be having the problems a lot of people are,
but I'm also not recording audio into ACID.
Just doing loops.
Good luck.

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: Iacobus

Date:1/22/2003 6:33:15 PM

Thanks for that clarification, Peter!

Standing corrected,
Iacobus

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: msorrels

Date:1/23/2003 12:33:57 AM

Not sure it has anything to do with your problem, but I was getting blue screends with PROCESS HAS LOCKED PAGES turned out it was the Oxygen 8 Midiman keyboard USB drivers. I switched the keyboard to us the MIDI in/out and now no more blue screens. What was horrible about it was it didn't happen when you hit a key. It would happen after using the keyboard for a short while.

Since a blue screen can only happen with a device driver, you need to figure out which device driver is going bad. Odds are it's a music/sound/midi device driver.

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: fulani

Date:1/23/2003 2:17:04 AM

i'm using a Midisport 2x2 USB which connects the pc to a synth and a VS 1680. but neither of this are in use when i get the crash.

msorrels said "I switched the keyboard to us the MIDI in/out and now no more blue screens."

could you explain please?
"switched the keyboard to us the MIDI in/out"

as opposed to what?
what paricular preference are you refering to?

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: msorrels

Date:1/23/2003 3:01:04 AM

The Oxygen8 has a USB port and a MIDI in/out port. So you can hook it to a computer via the USB or via a MIDI connection(if your computer already has a MIDI port). Since the problem/bug was in the Oxygen8 USB drivers (Midiman seems to make the worse drivers for USB devices I've ever seen) by switching to using my DMX 6Fire's MIDI input I was able to uninstall the Oxygen8 USB drivers and solve my crashing problems. Of course that means I have to power the keyboard with a power supply, but less blue screening is better.

My blue screening never would happen just while I was using the keyboard, only after a bit of use. Sometimes I would use the keyboard for a bit, then quit, an hour or so later it would blue screen. If it happened when I pressed a key it would have been much easier to track down. The only common thing I could find is that the blue screen always happened after I used the USB keyboard(sometimes soon, sometimes a little while). The message is the same one you reported. Microsoft's knowledge base says it's due to a device driver not handling memory correctly.

I'd be willing to bet your having the same kind of problem I was having. I suspect Midiman USB drivers all share certain core things. In this case it seems to be the core thing called not working. I didn't bother trying to get them to help me, their tech support is well known at not being very helpful. In this case the only thing that will help is a new version of the drivers, written correctly. With the MIDI connection I don't have to run any of their poorly written drivers and as a result my computer stopped blue screening, 100%.

Of course that doesn't help you much, since the Midisport is your MIDI connection. At least you have an idea of what is not working. Perhaps you can get Midiman to fix the drivers. Or find another MIDI interface by another company.

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: fulani

Date:1/23/2003 4:14:20 AM

would the midisport driver be involved in the crash if I was not using the keyboard or USB?
It's hooked up, but not in use.

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: michelp

Date:1/23/2003 11:00:59 AM

Hello Iacobus,

I am looking at ACID vs Vegas and truly, aside from the video supprt in Vegas, I fail to see the difference between the two...

Is Vegas really better to record audio? Audio can be recorded in ACID too (although you cannot monitor through ACID!). Did they really improve this part in Vegas? Seems to me more like a video oriented app instead of audio.

I really like the simplicity of using ACID, I wonder if I should get Vegas for "real" audio recording...

You obviously have experience with both apps, thanks for any input!

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: liquid

Date:1/23/2003 2:07:43 PM

I use acid to do loops, and then I use it as a multitracker. Is this bad? I don't like switching programs. How do I get my acid project into vegas, keeping the track positions and the overall mix the way I want it to be? Is there a way to easily switch between programs?

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: Iacobus

Date:1/23/2003 2:47:48 PM

What some users don't know is that ACID complements Vegas and vice versa; they're meant to be modular with each other. Sound Forge complements both even further with its digital audio editing capability. Each product serves a specific purpose.

Vegas is a true multitracking app, allowing multiple inputs for recording on separate, independent tracks. Think of it as a software version of a hardware multitrack recorder. (Remember those cassette 4-track recorders that still are being sold?). ACID does not do this but can playback multiple disk-based tracks. However, ACID is limited in this regard as it was not entirely designed to playback a load of these types of tracks. You can usually get away with 4-5 disk-based tracks, more if you have a well-configured system.

ACID is a true looping app, unique in its paradigm, as it will allow you to stretch a loop to a specific key and/or tempo (when the loop is ACIDized, of course) when your project changes key and/or tempo. Vegas does not do this, at least not in the way that ACID does it. You must do it manually and even then you have some calculating to do, as well as being able to do it only at the event level.

If you like to work with audio in a "what you hear is what you get" way, Vegas may be more your speed. If you want some looping capability too, ACID will be indispensable. I'd recommend Sound Forge in any case whether you have Vegas and/or ACID, just to have the capability to enhance and master your projects with the tools/functions available only in that app.

HTH,
Iacobus

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: fulani

Date:1/23/2003 3:00:04 PM

"Not sure it has anything to do with your problem, but I was getting blue screends with PROCESS HAS LOCKED PAGES turned out it was the Oxygen 8 Midiman keyboard USB drivers. I switched the keyboard to us the MIDI in/out and now no more blue screens."


could my midisport driver be involved in the crashing even if I am not using the keyboard or USB when the crash occurs?
It's hooked up, but not in use.

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: michelp

Date:1/23/2003 3:24:25 PM

You are right sorry,

Like it was stated in other replies, BSOD is caused by very low level code. Could be related to video or audio and lately, quite a few USB drivers. If you have tweaked the BIOS, try to "Load default BIOS settings", sometimes this will bring back a failing computer...

What Windows version are you on? Did you get all the SP and latest drivers? Does this happen only in ACID or also in other music apps?

Do you see a pattern? Are you able to re-create the problem? Important if you want to know if this is a functional problem (driver version) instead of hardware problem (over-heating, incompatible chip set or failing memory...).

Unfortunately, there is no easy way to pinpoint a hardware problem. Do what "techies" do, simply go through the process of systematicaly trying different hardware (video cards, memory, network card, etc). No wonder it takes weeks to get a computer fixed!

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: msorrels

Date:1/23/2003 5:01:35 PM

Are you doing anything with MIDI at all? If the answer is yes, I'd say the midisport is involved. Uninstall the midisport driver(just unpluging it may not be enough, you have to remove the driver) and use the computer like you have been doing, if it doesn't blue screen you know it's the driver.

A blue screen can only happen by a bad driver. Application software cannot make a blue screen occur by itself(it has to use a driver). Applications can load dymanic drivers(but that's rare). But usually blue screens mean some hardware driver you have has a major flaw. So start narrowing down the hardware drivers you have. Use the control panel to remove them. By and large most core Microsoft drivers aren't going to be the problem(IDE drivers, etc). So start with the 3rd party stuff. So your sound card, your midi interface, your video card, your video capture card, your etc.

It's unlikely that it's something other than the midisport though, since I know the Midiman USB drivers have the problem like what your describing. It wouldn't surprise me in the slightest if that same problem exists on all Midiman USB products. I'm sure it's not 100% common either. Could have something to do with my motherboard, or maybe my OS, or perhaps something else. Doesn't really matter to me anymore, I have a working solution using just the MIDI output on the keyboard.

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: fulani

Date:1/24/2003 5:57:29 AM

i'm using the midi/synth only when running Reason. Not when running ACID. That being the case, could the midi drivers still cause a problem ?

Subject:RE: >>>>>>theBSofD<<<<<<

Reply by: dkistner

Date:1/25/2003 7:59:02 AM

I have this vague suspicion that sometimes the midi driver-type problems are actually due to programs not releasing midi ports when they should. I don't really understand how to ensure that they do, however. Does anyone know? Like, for example, sometimes I'll get errors in Acid saying a certain midi port is not available when I've closed the other program that was using it. How to make sure this doesn't happen?