Subject:post crash hanging in task manager

Posted by: martin7

Date:7/10/2008 5:02:08 AM

I've been getting crashes which seem to revolve around midi issues. I have a novation remote compact with automap running and a mackie control (going into a midisport 2X2). When I check taskmanager post crash the acid process is still there and won't be terminated. Rebooting is the only answer so far. Any ideas?
M7

Subject:RE: post crash hanging in task manager

Reply by: DKeenum

Date:7/10/2008 3:29:12 PM

Are you thinking that the crashes are related to the novation or the mackie? Have you tried repoducing the crashes with those two unplugged?

Subject:RE: post crash hanging in task manager

Reply by: pwppch

Date:7/10/2008 7:24:15 PM

We have seen this after crashes with with the MIDISport drivers not releasing cleanly. We have reported this to MAudio. Do you know what version of the MIDISport drivers you are using?

Of course the crash is something I would like to know more about. Can you provide some details?

Peter

Subject:RE: post crash hanging in task manager

Reply by: martin7

Date:7/11/2008 6:14:01 AM

MA_CMIDI_V32_4.3.00 is the driver I'm using (the latest 32 bit). for the midisport, I've found that when trying to add the mackie (on the midisport) under preferences I can cause a crash when I right click 'configure', causing acid to hang. This, in turn, causes acid to hang as a process in taskmanager and requires a reboot. I can, of course, reload Acid without rebooting but i end up with two instances of acid in the task manager and furthermore, once inside the 2nd instance of Acid, 'external control' is not listed under options and the mackie is not found when I attempt to scan in external control under preferences. So, I just reboot and this clears the system.
I'm now running the MCU through the midi port in the Novation, so far so good.


' Have you tried repoducing the crashes with those two unplugged?' -
It doesn't seem to happen when both unplugged. I will try again with each alone and report back.

thanks for getting back,
m7

Subject:RE: post crash hanging in task manager

Reply by: pwppch

Date:7/11/2008 9:55:48 AM

I have verified that the MIDI Sport drivers hang and never release upon a crash. This is a driver bug that we notified MAudio about. 2+ years ago. (There are other non crash related scenarios that can also cause the MIDI Sport drivers to hang and force a reboot.)

Do you have an alternative MIDI device to try using other than the MIDI Sport to see if the hang goes away?

The reason that the second instance of ACID does not see the external control is because only one instance of ACID can access. Since the other instance is running, the second instance will never see and access external control.

Again, the crash is of more concern, but I am not clear on what you are doing in detail to cause the crash. If you could provide me a step by step procedure - the more specific details - the better.

Peter

Subject:RE: post crash hanging in task manager

Reply by: martin7

Date:7/12/2008 9:30:23 AM

Thanks for getting back, Peter.

I'm running the MCu through the midi port in my Novation Compact to see if the problem persists. So far so good.

Until I get another midi interface, I'm currently only running a micro korg through the midisport, so we'll see.

Asfar as details of the crash the most obvious is the one I listed in my previous post.
1- Run the MCU into the midisport. The midisport appears as harware in the midi tab.(preferences)
2-Select /Add Mackie control in the available devices - external control tab (preferences)
2- right click the MCU in the active control devices list
3- click 'Configure' in the list.
this, more often than not, causes Acid to freeze - In task manager Acid is listed as not responding. So I end up rebooting.

I hope that's clear. While I have you 'on the line' can I ask you another midi related question? I'm running BFD as a soft synth. When I record another softssynth like NI FM7 or even play a casio digital piano, (which has it's own usb port,) the drum patterns from BFD appear as midi notes along with the notes I'm actually playing/recording. This also happens when running Guru as a soft synth. It's obviously some routing issue but I'm scratching my head as to stop this cross over happening. Can you help me?

Thanks again for everything.
m7

Subject:RE: post crash hanging in task manager

Reply by: pwppch

Date:7/12/2008 10:45:53 AM

Thanks for the details.

This sounds like the driver problem with the MIDISport we have identified.

The MIDI Sport drivers don't like how we talk to the MIDI MME Streaming API. We have discussed this and provided specific repros of this problem to MAudio since we first discovered the problem in ACID 4. Typically you will not have this problem if you use the MIDISport for sequencing rather than external control.

This is also why the driver hangs the instance of ACID when a problem occurs. It is "stuck" inside of its own infinte loop and refuses any attempts to "cancel" the driver. (If you wait a REALLY long time, the driver will eventually be killed off by the OS, but this can be a VERY long time.)

We have a solution for this particular problem that we believe will end this problem with the MIDI Sport once and for all. It will be part of the next release of ACID. Sorry, but there will be no update fix for ACID 6.

Please let me know if see the same problem with any other MIDI interface.

WRT your other problem:

I am not clear exactly what you are describing. Are you saying that the MIDI that BFD is playing is getting recorded to a new track?

Again, the more details on how your project is setup and routed would be helpful.

Thanks
Peter

Subject:RE: post crash hanging in task manager

Reply by: martin7

Date:7/12/2008 12:40:40 PM

Your description of the problem does indeed chime with my experience. Although it's annoying there is a certain satisfaction
in understanding the problem!

Regarding my routing issue, the set up in this particular project is as follows - (Then the problem)

first my midi set up in preferences-
devices available for track playback (enabled)
REmote Compact: port 1 - Reserved by device (mackie control v 2.10)
Remote Compact: port 2
Remote compact: port 3
Out A USB midisport 2X2
out B Usb midisport 2X2
MK USB out 1 (this runs from my casio px-200 digital piano)

devices available for MIDI input:
REmote Compact: port 2 - Reserved by device (mackie control v 2.10)
Remote Compact: port 1
Remote compact: port 3
Out A USB midisport 2X2
out B Usb midisport 2X2
MK USB out 1
All marked 'AUTO' in 'MIDI THRU TO'

Auto MIDI input routing is checked

there are -
7 audio tracks
4 midi tracks

2 soft synths ( 1 - BFD) ((2 - TRILOGY)
midi track 1 - Midi input Auto - midi channel all - output=soft synth 2 trilogy
midi track 2 - Midi input Auto - midi channel all - output=soft synth 1 BFD
midi track 3 - Midi input usb midisport - midi channel 4 - output= usb midisport midi cahnnel 4
midi track 4 - Midi input MKusb in 1 - midi channel 5 - output= MKusb in 1 - midi channel 5 (casio)

When I record midi (using either the remote compact or the casio) onto any of the tracks excepting the BFD track, extra midi notes
are recorded which correspond to the midi rythmns being played by the BFD soft synth. I end up with these midi notes
in addition to the ones I recorded. I've had the same experience in another project using Guru as soft synth.
In other words, the drum mid patterns are leaking into other midi tracks during recording. I'm sure it's an obvious thing but I just can't find the leak.
M7