It is currently Mon Jan 30, 2023 3:46 am


Arturia Minifuse 4 has a MIDI problem?

Connecting Hauptwerk to MIDI organs, sequencers, ...
  • Author
  • Message
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 11:06 am

I bought a hoped for replacement for my M-Audio 410.
The newly released Aurturia Minifuse 4 was highly rated.
With only 4 channels it was minimal for organs but the price was in my range.

It took a long time to get through their validation procedures which I thought peculiar for a hardware device.
Then figuring out how to get 4 independent ASIO channels instead of 2 stereo channels took more time.

Its MIDI functionality is partially working:
1) MIDI-OX sees the organ console.
2) Hauptwerk hangs when I click General_Settings/ MIDI_ports.
The escape key releases the hang but there is no MIDI.

Any hope to making this device work or should I try to return it?
Offline
User avatar

mdyde

Moderator

  • Posts: 14630
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 11:16 am

Hello John,

I have no experience myself with that device, but my thoughts would be:

- Are you sure that the "General settings | MIDI ports" screen actually hangs, as opposed merely to being slow to open?

- If it does actually hang, does "Engine | Advanced ... | Stop audio/MIDI" also hang? (I would expect so, since Hauptwerk tries to stop the MIDI drivers when opening the "General settings | MIDI ports" screen, and likewise with "General settings | Audio device ...", and with the general/organ preferences screens.)

- After it has hung (and whilst it is still hung), try looking at the last line in:

<your-OS-user-home-directory>\Hauptwerk\HauptwerkUserData\Config0-Logs\HauptwerkLog.html

Probably it will be a "... INF:3834 Stopping MIDI IN port ..." line. If so then it will be that particular MIDI port/driver that's hanging.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 11:42 am

Yes, hangs for minutes

No, Engine stop just shuts down the loaded organ.

Here is log after MIDI, then esc, then STOP.
I see it's trying to stop the FW 410 which is no longer hooked up.
When I first ran HW after removing the 410 it asked for interface advice and I said delete/remove all prior devices.
Perhaps that didn't completely work.
I can try to reinstall the 410 and get it back online. Will take a while and a a few reboots.
Unless there is an easier option to edit HW config files.

2022-05-27-19-36-54: INF:3828 Stopping MIDI.

2022-05-27-19-36-54: INF:3825 Stopping MIDI IN port 'FW 410 MIDI'. (Driver pri: 13[128:0]. Engine pri: 15[128:2]. Buff: floods: 0, peak usage: 0 pct, total traffic: 0.0 KB. Event perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: event latency: '1.0 / 1.0 / 1.0 / 2 / 2 / 0 / 0 / 0 / 0 / 0', processing time: '0.1 / 0.1 / 0.1 / 2 / 2 / 0 / 0 / 0 / 0 / 0', processing overrun: '0.0 / 0.0 / 0.0 / 1 / 1 / 0 / 0 / 0 / 0 / 0')

2022-05-27-19-36-54: INF:3826 MIDI stopped.

2022-05-27-19-36-56: INF:2509 Stopped audio and MIDI. Peak levels since last started: audio: -71.6 dB (>=0 dB indicates clipping), polyphony as pct of limit: 0.1, estimated audio CPU load during first 10 seconds: 0.0 pct, thereafter: 163.1 pct. Ran at real-time priority (Windows only)?: N. Extra time allowed when audio started (Windows only): 0.0 s. Sample rate: 48000 Hz. Mixer preset: 1. Num active stereo reverbs: 0, Max active reverb length: 0.00 s. Expected buffer latency: 1024 frames, actual max buffer latency: 1024 frames (21.3 ms), max single buffer latency allowed for: 1536 frames (32.0 ms).
[Priorities: audio engines: 15[128:15], audio recorders: 15[128:15], mixer convolver FIR preparation/buffer allocator: 13[128:0], convolver engines: --, MIDI player: --, MIDI recorder: 15[128:2], GUI rendering: 13[128:0], default user events: 14[128:1].]
[Event buffer stats: (size in K-events, num floods, peak frac full pct, total traffic in K-events): GUI rendering: (64.0, 0, 0.00, 3.7), high-pri events: (8.0, 0, 0.00, 0.0), default user events: (8.0, 0, 0.00, 0.3).] [Background models:
relay models: (priority: 15[128:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.0 / 0.1 / 618.3 / 118883 / 118864 / 3 / 2 / 2 / 0 / 12, waiting stats: 0.2 / 2.3 / 616.6 / 118883 / 98315 / 19037 / 534 / 46 / 776 / 175, interval stats: 0.2 / 2.4 / 618.6 / 118883 / 58473 / 58861 / 538 / 49 / 775 / 187),
trem model: (priority: 15[128:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.0 / 0.0 / 18.2 / 118883 / 118882 / 0 / 0 / 1 / 0 / 0, waiting stats: 0.1 / 2.4 / 618.6 / 118883 / 73863 / 43473 / 537 / 48 / 775 / 187, interval stats: 0.1 / 2.4 / 618.6 / 118883 / 57885 / 59447 / 540 / 49 / 775 / 187),
wind supply model: (priority: 15[128:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.1 / 0.2 / 618.4 / 118883 / 118861 / 2 / 0 / 2 / 3 / 15, waiting stats: 0.1 / 2.2 / 94.8 / 118883 / 112986 / 4319 / 565 / 69 / 771 / 173, interval stats: 0.2 / 2.4 / 647.4 / 118883 / 57573 / 59689 / 582 / 78 / 773 / 188),
pipework: (priority: 15[128:2], model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.0 / 0.0 / 0.4 / 118883 / 118883 / 0 / 0 / 0 / 0 / 0, waiting stats: 0.2 / 2.4 / 620.3 / 118883 / 100670 / 16480 / 684 / 85 / 777 / 187, interval stats: 0.2 / 2.4 / 620.3 / 118883 / 59189 / 57951 / 691 / 88 / 777 / 187),
master: (model perf stats: min ms/avg ms/max ms/total num/num 0-1.9ms/num 2-4.9ms/num 5-9.9ms/num 10-19.9ms/num 20-49.9ms/num >=50ms: processing stats: 0.2 / 0.6 / 618.6 / 118883 / 117442 / 334 / 174 / 29 / 733 / 171, waiting stats: 0.0 / 1.8 / 73.2 / 118883 / 116038 / 2440 / 332 / 15 / 42 / 16, interval stats: 1.7 / 2.4 / 618.6 / 118883 / 56220 / 61113 / 539 / 49 / 775 / 187).]
Voice generator background model event stats: total num event blocks: 118190, num event queue underflowed blocks: 2868 (2.43 pct), mean block length for non-underflowed blocks: 2.4 ms.
Voice generator note-on events stats: total num processed: 23, mean time waited before events: 536 frames (11.2 ms).

2022-05-27-19-36-58: INF:0403 Hauptwerk has finished shutting down.
Offline
User avatar

mdyde

Moderator

  • Posts: 14630
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 12:20 pm

Hello John,

Please try:

- Use "Organ | Unload ..." if an organ is loaded.

- On the "General settings | General preferences" screen check that the "Load organ when Hauptwerk starts" setting is set to "No organ loaded" for now. OK the screen.

- Exit Hauptwerk.

- Reboot the computer for good measure.

- Re-launch Hauptwerk.

- Now try opening the "General settings | MIDI ports" screen.

Can you get it to open?

If so, on *both* the "MIDI IN ports" and "MIDI OUT ports" tabs, untick any ticked entries in any columns that represent MIDI ports from your FireWire 410 then OK the screen, the exit and re-launch Hauptwerk for good measure.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 12:56 pm

Nothing changed. Hang and log entries same as before.
Offline
User avatar

mdyde

Moderator

  • Posts: 14630
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 1:27 pm

Hello John,

Do you mean you can't get the "General settings | MIDI ports" screen to open at all?

How about if, after re-launching Hauptwerk with no organ loaded, you use "Engine | Advanced ... | Stop audio/MIDI" first?
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 1:45 pm

"General settings | MIDI ports" Small window opens "please wait", then quickly goes away, after that any key click gets ding sound, HW is hung until Esc key.

"Engine | Advanced ... | Stop audio/MIDI" Brief window opens (too brief to see what it says) then can load organ but no MIDI as above.
Offline
User avatar

mdyde

Moderator

  • Posts: 14630
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 1:54 pm

After launching Hauptwerk with no organ loaded, if you use "Engine | Advanced ... | Stop audio/MIDI" (and don't the load an organ or do anything else), can you then open the"General settings | MIDI ports" screen?
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 2:10 pm

No, a brief windows ("please wait") appears and then hangs.
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 2:10 pm

I can take a video of the various actions if you want.
Offline
User avatar

mdyde

Moderator

  • Posts: 14630
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 2:33 pm

Hello John,

Since Hauptwerk is still trying to start/stop the "FW 410 MIDI" MIDI IN port, it must be that case that the driver is still actually reporting the device as being present. Presumably the driver *shouldn't* be reporting it as present, given that you no longer have your FireWire 410 connected to the computer. When Hauptwerk prompted you previously about a missing device, probably it was the FireWire 410's audio driver that had disappeared, as opposed to its MIDI port (given that the MIDI driver is evidently incorrectly still reporting the MIDI port as being present).

I suspect that's a bug in the FireWire 410's driver, or at least an incompatibility between it and the operating system you're using. (I believe M-Audio don't have officially-supported drivers for Windows 10, for example.)

Perhaps if you actually uninstall the driver completely (when Hauptwerk isn't running), and then reboot, that will fully get rid of the driver, in which case when you then launch Hauptwerk it will prompt you that the FW 410 MIDI port now appears to be missing, and asking whether to clear settings that relate to it. Choose that option to clear its settings if so.

Alternatively, you could try temporarily re-attaching the FireWire 410 (when Hauptwerk isn't running), then launching Hauptwerk, just so that you can (hopefully) open the "General settings | MIDI ports" screen to untick all columns (on both the IN and OUT ports tabs) that relate to it. You could then OK the screen, exit Hauptwerk, disconnect the device, and (ideally also) uninstall its driver.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 2:40 pm

Yes, I did uninstall the 410 driver. Maybe, because of its general incompatibility with WIn 10 it may not have succeeded.
I will reinstall and repeat the uninstall but it will take some time since I also must reinstall the Firewire card.
I will continue this dialogue another day (time off for new years).
Thanks for the kind assistance so far and Happy New Year!.
Offline
User avatar

mdyde

Moderator

  • Posts: 14630
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Arturia Minifuse 4 has a MIDI problem?

PostSat Dec 31, 2022 3:26 pm

Thanks, John. You're very welcome.

Alternatively, and unsupported (I'm not promising this will work, and try at your own risk; back up first!) you could conceivably edit Hauptwerk's main Config.Config_Hauptwerk_xml file when Hauptwerk isn't running, to delete any XML tags of the following format:

<portnam>FW 410 MIDI</portnam>

... which refer to the FireWire 410. Don't delete the rest of the line, though -- just the 'portnam' tags themselves, including their contents. They will be within the "EnabledMIDIInputPort" and/or "EnabledMIDIOutputPort" XML tables. That should be equivalent to unticking the entries on the MIDI ports screen.

A very happy New Year to you too.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

jrball

Member

  • Posts: 193
  • Joined: Fri Feb 06, 2004 2:07 pm
  • Location: Virginia, US

Re: Arturia Minifuse 4 has a MIDI problem?

PostSun Jan 01, 2023 11:02 am

Martin,
Cache(s) mod didn't work to clear MIDI hangs.
I reinstalled HW7 and all seems well now.
I ignored unavailable settings on the complaint screen, then it asked for MIDI details and correctly offered Minifuse choices.
Both Audio and MIDI are now working with the Minifuse 4 interface.

I much appreciate your kind tutoring through this.
John
Offline
User avatar

mdyde

Moderator

  • Posts: 14630
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Arturia Minifuse 4 has a MIDI problem?

PostSun Jan 01, 2023 11:41 am

Thanks, John, You're very welcome. Glad to hear you have it working now.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.

Return to Audio / MIDI interfacing

Who is online

Users browsing this forum: No registered users and 1 guest