[ddots-l] Re: BFD nightmare continues
- From: "Damon Fibraio" <dfibraio@xxxxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Sun, 30 Sep 2007 00:48:09 -0400
George, the errors just said something like unhandled exception and gave
some hex values or something. The error has modified itself a bit, see my
post in reply to Phil's.
--
Damon Fibraio
screen names -- aol: dfibraio...msn dfibraio@xxxxxxxxxxxx skype: dfibraio
web sites: personal music site: http://www.keyboardguy.com. band:
http://www.queenoftheryche.com. Internet Radio station:
http://www.nhbradio.com
Internet radio show every Wednesday night from 8 to 11 pm eastern
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of George Bell
Sent: Saturday, September 29, 2007 6:18 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: BFD nightmare continues
Hi Damon,
If you are getting "crashes" it is essential to try and see if an error
message is occurring and what it says. If this is not appearing in screen
at the time, then in will often appear in the Event Logs on your system.
Go to control Panel, and select Administrative Tools. You will find Event
Viewer in there, so open it up.
The dialog view is very much like Windows Explorer, with folders such as
Application, Security, etc. down the left pane, and individual items, or
more correctly in this case, Events, down the right.
These events will be dated and time stamped, and double clicking on them
will produce a more detailed dialog. If you examine these logs immediately
after a crash, you may be able to pinpoint one or more events which occurred
at that time.
Now this is a rather technical area, but contain messages like the following
for example. "Volume Shadow Copy Service error: Unexpected error querying
for the IVssWriterCallback interface. hr = 0x80070005. This is often caused
by incorrect security settings in either the writer or requestor process.".
Such a message may not mean much to you, but it gives us something to go
hunting round the web for.
In an ideal world, if you can force a crash to occur, you can then first
clear all the logs by right clicking on each folder, and selecting "Clear"
(No need to save them at this point. Then force the crash, and go
immediately back and look at the logs.
If you do get error logs, then right click on the folder containing the
errors and save the log to a file. Send me the file or files off list to
<mailto:George@xxxxxxxxxxxxxxxxxxx> George@xxxxxxxxxxxxxxxxxxx , and I'll
see if I can establish what the problem might be.
George.
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Damon Fibraio
Sent: 29 September 2007 17:55
To: midimag@xxxxxxxxxxx; ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] BFD nightmare continues
OK, I'll toss this out to anybody who has experience with soft synths and
maybe I can figure out why this is happening. The scenario is as follows: My
DAW is currently an aMD Athlon xp 3000plus processor with 2gb of ddr400 Ram.
My hard drives are all eide ata100 or 133 drives, the primary is a 250, the
secondary is a 400 and the third one is a 200. I forget how they are chained
on the ide bus, though, maybe I can jockey that around a bit. I am running
windows xp sp2, sonar 6.21 producer edition, JAWS 8.0.2173 and the latest
caketalking. I have dimension pro, which works fine, Native Instruments b4
2, which also works fine and the latest version of BFD, which is not doing
so well. I had issues with audio dropouts while playing the BFD drums, even
when using bfd stereo in standalone mode. I also started having crashes
occur when Sonar would load my project that contained the BFD all plugin
with a kit inserted. The procedure would go, load project, wait a few
seconds while BFD loaded all its kit pieces, then an unhandled exception
would occur in BFD which would also take out Sonar. What I thought my
mistake was was that when I installed BFD, I put all the data on the c:
drive with the OS. I tried moving the data to my e: drive, which isn't doing
anything, really, just storing music. So, my c: drive is my OS, my d: drive
is my audio streaming drive for audio tracks in Sonar, and now my e: drive
would be streaming the BFD samples. The dropout issues seems to have
improved, but the crash still occurs. So, I uninstalled BFD completely and
removed any and all bfd related folders. I then scanned my system for
spyware, defragged all three drives after doing disk cleanup on all of the,
and reinstalled BFD the way I had it before, i.e. data going to e: drive.
The crash didn't occur until I loaded a particular kit, I forget which one.
BFD is updated with all the patches I could find on the web site. My
questions are: Is my computer not powerful enough to handle this synth? I
can't imagine why it wouldn't be. I am running the audio through the tascam
fw1884, latency slider seems to be best at 50 percent. My Motif xs7 is the
midi controller running through USB to the computer. I am at a loss and
don't know what to do. I know my computer is a little lacking in the power
department and I have full intention of updating to a better system as money
lets me, but for now, I really want to get these drums to work, and I can't
figure out why I am getting crashes. I believe the kit I am loading is the
Pearl kit, but would have to double check. Any ideas from you soft synth
experts?
--
Damon Fibraio
screen names -- aol: dfibraio...msn dfibraio@xxxxxxxxxxxx skype: dfibraio
web sites: personal music site: http://www.keyboardguy.com. band:
http://www.queenoftheryche.com. Internet Radio station:
http://www.nhbradio.com
Internet radio show every Wednesday night from 8 to 11 pm eastern
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.488 / Virus Database: 269.13.33/1036 - Release Date: 28/09/2007
15:40
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.488 / Virus Database: 269.13.33/1036 - Release Date: 28/09/2007
15:40
Other related posts:
