MTU.Community


Go Back   MTU.Community > Microstudio Software & Burners > Microstudio Help

Microstudio Help Post Microstudio questions, tips and suggestions here.

Reply
 
Thread Tools Display Modes
  #1  
Old February 13th, 2003, 07:47 PM
Rich LePage Rich LePage is offline
Blocked From MTU.Community
 
Join Date: Nov 2000
Location: NYC Area
Posts: 110
Mstudio 2.4 crash problems when ripping audio

Just installed this version on a machine that had not had M/studio previously, so no chance things were corrupted by a prior version.

The test situation: Rip all audio from 8 CDs in a set (audio only, these are not CDG disks), one CD at a time, ripping all to WAV files in separate directory for each CD. The CDs in this test were made with MicroCD and Microeditor. The thought was that by ripping the audio tracks this way, it would be easier to re-edit a new compilation using Microeditor than to have to go into the actual Medit project files themselves to delete and re-sequence some of the material, since the Medit project mix files are extremely dense and complex for this long project.

Machine: Athlon 1.4gig, Abit KT7A Raid m/board, Win98SE, variety of drives (all Maxtor 7200rpm), 512 RAM, Yam CRW2100E firmware 1.0N. All appropriate ASPI and Direct X updates have been installed, most all other non-browser Windows patches have been installed also (machine does not go online by design).
No other rip/burn software installed on machine except MicroCD.
Also Microeditor 5.4 installed and a Tekram SCSI controller which is used to connect external tape backup drives when needed.
(none connected during this test)
Only other software installed is Veritas/Stomp Backup My PC (formerly Backup Exec), Cool Edit Pro 2.0, and Waves Waveconvert Pro. All standard Microeditor Windows tweaks done, all other stuff such as no auto-insert notify and DMA enabled plus sync data transfer enabled also done. Drives in
test were not running from the HPT Raid controller, all were running from the main pri/sec IDE controllers.

M/studio settings: all default settings from install, plus Jitter=on,
Speed=auto-select.

I got the same result twice during two separate attempts on the 8 CD set, but at different points in the process. After first try I deliberately erased all copied WAV files, cold re-booted, and tried again. The crash in the first attempt was during CD 4, in the second attempt in CD 7. The discs are OK, proven by the fact of rebooting and doing just those discs with identical settings, which worked. But I thought this was something you would want to know about.

M/studio caused crash with message that errors were at
Kernel32.DLL 0177:bff7d76b

This also crashed Win to a blue screen with message
fatal exception at 0177:BFF9DFFF

Otherwise, M/studio worked fine. I was NOT closing the progam and re-starting it between CDs. The idea was to open the program once, and be able to rip all the audio from the 8 CD set.
Reason behind this: see below.
After each CD had imported, the destination folder was changed,
the read tracks command re-invoked, and the autonaming changed. For each CD, the autonaming was set to
CD(x)-Trk(xx via auto-increment)

Reason for trying to do it this way:
M/studio does not seem to retain the user settings under the "drives" pull down, such as speed select, jitter, etc.
Is there perhaps a way to do that-- like we do with an INI file in Medit? It does seem to remember the chosen destination folder and some other settings, though. That's why it not remembering the other settings seemed strange, and somewhat of a handicap.

It thus seemed easier and more logical to try and do each CD one at a time with M/Studio open the whole time, though as noted, that didn't work out either time I tried it.

Other notes:
During each track's import, the cursor will hover over the Terminate button, which is active anyway. Was this by design? If so, why? It seems all to easy to inadvertently abort and terminate with the pointer hovering there. An inadvertent click or whatever, and you've been "terminated". And even if you move the pointer, on the next track's import, it will jump right back there again. (most of the CDs in my test set had 40 to 60 tracks on them each)

Also, if you try to move the import window, the program will allow that, but since it is re-invoked again on the next track's import,
it will then jump right back where it defaults to. I'd consider modifying that too if it's not too difficult. You cannot scroll through the main window at all while importing is going on because the import window seems to be persistently active, rather than being able to be in the background. That may be a big deal to change, if so, no problem-- but the pointer thing probably should be changed if not too hard to do that.

That's all the notes for the moment. Hope they help.
Other than what I've noted here, it seems to work quite well
though. I'll test some more and report anything else, though it will be audio-only testing.
Reply With Quote
  #2  
Old February 14th, 2003, 01:41 PM
MTUSUPPORT MTUSUPPORT is offline
Moderator
 
Join Date: Nov 2000
Location: Raleigh, NC
Posts: 5,253
Rich,
Please try upgrading the ASPI drivers to the Adaptec drivers stated in Solution #2 of this post: http://forum.mtu.com/showthread.php?threadid=493

Then let me know if this still occurs.
__________________
Bryan, MTU
Reply With Quote
  #3  
Old February 14th, 2003, 02:32 PM
Rich LePage Rich LePage is offline
Blocked From MTU.Community
 
Join Date: Nov 2000
Location: NYC Area
Posts: 110
I'll try it and let you know, Bryan. Thx.
Reply With Quote
  #4  
Old February 14th, 2003, 05:59 PM
Rich LePage Rich LePage is offline
Blocked From MTU.Community
 
Join Date: Nov 2000
Location: NYC Area
Posts: 110
Bravo, Bryan,

It works using the ASPI drivers from Adaptec, while it didn't using the ones installed by M/studio. I think you should still consider changing the terminate mouse stickiness and other stuff I mentioned, however.

But indeed, I was able to rip the entire 8 CD set with no crashes
after installing the Win 98 APSI stuff from Adaptec.

Good work!

Rich
Reply With Quote
  #5  
Old February 16th, 2003, 07:33 PM
MTUSUPPORT MTUSUPPORT is offline
Moderator
 
Join Date: Nov 2000
Location: Raleigh, NC
Posts: 5,253
Glad to know this. Now I know which engineer to go to to fix this problem. This means the problem lies within the ASPI driver.

Thanks for the help as always Rich.
__________________
Bryan, MTU
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On


All times are GMT -4. The time now is 08:04 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2009 - 2024, Jelsoft Enterprises Ltd.
The contents of this forum are copyrighted by Micro Technology Unlimited, 2000-2008. Use of any material from these Forums is prohibited without written agreement from MTU.