I’m frustrated

Setup with Windows 7, Cubase 4 and Delta Audiophile 2496 hangs when closing the application

I used to have Cubase 4 and a Delta Audiophile 2496 in a perfectly working setup with Windows XP Home but after upgrading to Windows 7 Professional, Cubase always hangs indefinately when exiting. I have searched the net for days to find a solution but haven't managed to do so.

Facts:
-EXACT same setup worked with Windows XP
-Cubase does not hang if I disable or uninstall the Delta Audiophile 2496
-I have tried with all the Delta drivers available for Windows 7 (3) including the one I used to use in XP.
-Running the application in compatibility modes and as Administrator changes nothing
-Disabling antivirus software doesn't change things
-I have verified that IRQ's don't interfere
-I have disconnected all other devices that can be disconnected without causing the computer not to work and still no change.
-I have tried to place the Delta card in all available PCI slots.
-When inspecting the process, it seems that a dll named dmusic.dll get about 90% of the cpu when the program hangs but I don't know if that means that this is where the problem occurs. The computer becomes unresponsive and the CPU load stays on about 90% for Cubase which, however, never crashes, even if it stays like this forever (have tried at most about an hour or so). The error propagates in the exact same way throughout all of these configurations...

Symptoms:
No matter if I close the application with the red X or via the menu, the control panel disappears and then the program freezes. I usually try this by just opening the program and then closing it (not initializing a project) but the same happens even if I open a project first (no matter if I save or not save the project).

I know my setup is old but that is no reason to why it shouldn't work and I would be delighted, both out of curiosity and because I need the program to work properly, if anyone could help me.

Best regards,

Elias
2 people have
this problem
+1
Reply
  • Hello Elias,

    Thanks for posting and for the thorough troubleshooting!

    -What is the brand/type/speed of processor in the computer? (ex, Intel Core Duo 2.4GHz)
    -How much RAM is installed?
    -Windows 7 running 32 or 64 bit?
    -If you reboot your computer, wait for it to completely boot, then monitor the CPU and memory loads before opening any applications, does any process take the majority of the CPU or memory load? Can you calculate how much memory remains before opening any programs?

    The dmusic.dll, to my knowledge, is a DirectX / Microsoft driver. It should not be involved in Windows communicating with your Delta drivers. The fact that it, or any single process for that matter, hangs onto 90% of your CPU is not normal under any circumstance. I'm not really familiar with supporting that; it might be a better question for Microsoft.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I’m thankful
    Hi Dan!

    Thanks for your input...

    -CPU Intel Pentium 4, 2,8 GHZ
    -2,50 GB of RAM is installed
    -Windows 7 Professional 32-bit (clean install)
    -If I reboot the computer, there is the regular startup CPU usage which tends to spike from time to time but then, the system stays at a steady ~100% free CPU capacity and about 1,2 GB free RAM. This is true both when having the Audiophile enabled and disabled. After starting Cubase , I have about 400 MB of free RAM and a fluctuating free CPU capacity of about 60-80% (Cubase consumes 20%-40%). All the Cubase threads seem calm and then when I close the application, a thread WITHIN the Cubase process which was initiated in dmusic.dll, soars to using 75% of the CPU where it stays. There is still free RAM but the total CPU usage in the system amounts to 100% where about 90%+ goes to Cubase (75% to the dmusic thread, 15% to one of the main threads and a few other small percentages). If I actively kill this thread, the remaining threads in the application exit like they should and the program closes fine. Now, the thing here is that when the Audiophile is disabled, this thread doesn't exist within the Cubase process whereas as soon as the Audiophile is enabled in the system, this thread is present. The thread has started by the time the application has loaded and has a call stack that looks the same right after start-up and when it starts to consume a lot of CPU (I can provide more details if needed). Now, considering that this thread seems to be the culprit, this might be more of a question for a Cubase expert perhaps but if you have any ideas... let me know about them :)

    Best regards,

    Elias
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Hi,
    How is cubase connecting to the Delta card, what driver, ASIO, WDM DirectX?
    See if the others make a difference, if available.

    What sound device is Windows set to use as default audio device? Can you make sure it's not using the Delta card for normal sound out and communications.

    It does seem strange.

    Having a poke around the URL from Steinberg, I found some docs pertaining to the update 4.5.2. Have you installed the update?
    ftp://ftp.steinberg.net/Download/Cubase_Studio_4/4.5.2.274/Cubase_4.5.2_VH_Issues&Solutions.pdf
    And the patch files are here - select the 32bit msp one.
    ftp://ftp.steinberg.net/Download/Cubase_Studio_4/4.5.2.274/PC/

    Have you checked which plugins are loaded? Can you move them to another folder to make Cubase not see them, and then see it that fixes it. Sounds strange but there could be a plugin being loaded in memory that has become incompatible somehow. The VST plugins will likely be in one of these places:
    C:\program files\steinberg\vst
    C:\program files\common files\steinberg\vst

    Or if you know the exact file name of one of your plugins you could search for that in windows start menu, for example Voxengo Gliss EQ - "glisseq.dll"

    I've had a search around the 'net but haven't really found anything too helpful, just other people having similar issues with different M-Audio cards, and also different hardware from other manufacturers too!

    I gave up on Cubase VST5 a long time ago. I moved to Reaper and it's been faultless comparably. Not particularly relevant information, but it may be worth considering a different DAW if you can't get it fixed.

    Kind regards
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Oh, have you checked the Windows Event Viewer to see what is in there?
    It'll probably say the same dll that you identified anyway, but sometimes something else maybe the culprit.

    If Cubase can use the ASIO driver for devices, would you mind installing ASIO4ALL? It's a small program that acts as a KernelStream intermediate between ASIO/KS/WASAPI output of software and the hardware device configured in it's control panel.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I’m happy
    Thank you Chris!

    First of all, I have a built-in sound card and a PCI sound card (the Audiophile) and the computer uses an ASIO driver to connect to the Audiophile. I checked all the documents you posted and nothing made me wiser, also, the link is not to Cubase but to Cubase Studio but yes, I have updated my Cubase with the equivalent updates on the Cubase side.

    Also, I tried to move plugins but nothing changed. FInally, I also have ASIO4ALL installed and there is no difference as to whether this is installed, used or not at all installed.

    However, you told me to make sure that Cubase didn't use any of the resources of the Delta card to see whether it still caused freezing on exit or not and this is where I found the solution.

    When the Delta card is enabled in the computer, Cubase automatically adds it under Device Setup->Midi->Midi Port Setup where the Delta card contributes with two input entries where the Device column says DirectMusic and WIndows MIDI. When trying to render these connections inactive (by unchecking 'In All inputs') the computer freezes when trying to disable the inbound connection with device name DirectMusic.

    Apparently, the previously described thread within Cubase (dmusic.dll) hangs immediately when Cubase starts but this doesn't show until I either try to exit the program OR until I try to modify the inbound MIDI connection with device name DirectMusic (this makes sense since dmusic.dll is handling DirectMusic stuff in Windows). Now, if I uncheck the box, the computer hangs as usual, but if I first (or later) manually kill the dmusic.dll thread, the unchecking of the box works fine and now all of a sudden Cubase works like usual; it closes fine, it starts fine and closes fine again and the dmusic.dll thread is never present, even though the Delta card is enabled and used by Cubase (this of course while the inbound DirectMusic MIDI connection is disabled).

    This applies BOTH to Cubase 4 and Cubase 7.5 in a Windows 7 32-bit Professional environment.

    My problem is solved but I would still be delighted to hear more about why this problem exists and if there's something wrong with a driver or something. I ended up using the newest Delta Audiophile 2496 driver (6.0.8) but I believe the result would have been the same with any of them.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited