If you're like me and decided to remove Windows XP or so completely in place with Linux, like Ubuntu and wanted to use the OS with Munt, and you downloaded and installed Munt for Linux that doesn't have an option for adding a new MIDI driver, you're in for a big surprise!
Here are the following items you need:
- A Retro Gaming PC with either an ISA Sound Card (ex: Sound Blaster AWE64) and SoftMPU provided by bjt42 or an MPU401 card (extremely hard to find), however, there is an MPU401 card by keropi for 110 euros plus PayPal fees.
- A Roland UM-ONE MKII USB MIDI Interface adapter
- Another external MIDI box, like a Roland SC-55 mkii or a MIDI female to female adapter
- An older computer running Linux (Requirements: Pentium 4 @ 1GHz, 1GB RAM)
- Either computer speakers with 2 inputs or a stereo computer speaker wire to connect between the headphone jack of the Linux box and the Line In (not microphone) on the Retro gaming PC
- Wine (Windows Executable program) and Munt for Windows
Plug in your Roland UM-ONE mkii USB MIDI adapter and plug in the MIDI-OUT into either the external MIDI box's MIDI-THRU or on the MIDI-OUT on the sound card (adapter must be purchased (Joystick to MIDI with Joystick bypass is required to use both the MIDI boxes (Munt and External MIDI) and a Joystick all at once)), then plug in your linux box into either the dual-input speakers or line-in on the Retro PC's sound card (sound must be set within MS-DOS prior to).
Step 5: Start up Munt for Windows, tick the boxes for which MIDI you want to use: MT-32 or CM-32L (Control and PCM ROMs must match the MIDI box you want to use), click on the following to uncheck under Options:
If you get music or messages in the Munt for Windows program, you're good to go. If not, check your speaker settings within Linux to see if it's either muted, low, and check your MS-DOS sound card program to see if the Line-in volume is too low or muted. Enjoy this tutorial. Post any questions if you have issues or if you're new to this.
Hmm, really, with ALSA mt32emu-qt cannot connect to another sequencer port, e.g. the hardware port as in this case. Though, the current version on GitHub should be able to connect to a raw MIDI port instead (including USB-MIDI devices). And the ALSA sequencer port client connection function can be implemented indeed. I'll add this as a feature request because such a setup sounds a bit too complicated ?
What exactly is the problem this is meant to address? Routing Munt from any ALSA MIDI port has never been a problem for me, except when the ALSA install was incomplete. Also, Munt is much more efficient when compiled natively with optimizations.
Perhaps, this is about having client connections to an ALSA sequencer port out of the box. Really, we have this function for Windows (just because of platform ugliness) but do not offer it for others.
I'm using an RME Fireface 400 audio interface with Cubase 8.5 pro.
I've tried an approx pcie firewire card, but I've had trouble with sound glitches, no playback of recorded audio tracks, bluescreens, reboots, etc...
I downloaded all the new drivers.
The problems exist also outside Cubase, when I try to use a stand-alone Guitar rig, or Amplitube software, even in youtube.
At first I thought that it had something to do with Windows 10, but now...
I guess it should be the approx pcie card's fault.
I've also noticed that it doesn't power up my Fireface 400 and I have to use the mains power.
Thanks ramses!
I don't really need firewire 800 ports and I've read in another topic, that it's best not to use combination cards.
But it seems that this EXSYS company makes approved products for what I need.
What about the card from delock I've mentioned?
Does anyone know about it?
Are Windows 10 one of the problems?
If I switch back to Windows 7, would everything run smoothly?
This would be an easier solution, than to sell Fireface 400 and buy a USB audio interface.
And I guess If I'll do so in the future, I would buy a USB3 audio interface.
The Delock 89121 is a pcie card and is windows 10 compatible, according to the manufacturers page, Fireface 400 is windows 10 compatible, according to RME, Cubase 8.5 is windows 10 compatible, according to Steinberg.
Hopefuly there should be no problem, or someone is lying about compatibility with windows 10...
We'll see.
If I were you I would try the Firewire cards with TI XIO2213B chip 1st, and then draw another decision. EXSYS cards are at least known to have a solid platine board = good manufacturiing quality. Dont know about Kalea, never heard of this company.
Beside that, the Fireface 400 is recognized by the system, and properly displayed in the device manager.
But the tray programs do not come up, DigiCheck reports error 4 (->F3: Fireface 400 is displayed/selected).
If you have the UCX try using USB, maybe it makes a difference.
This is BTW one of the reasons why I recommend people to spend the extra bucks for UCX.
Then you can choose what runs more stable on your PC.
Now with Windows 10 eventually one benefit more to have the choice between USB or FW.
I am still very curious whether it makes a difference to use Win7 in cases of Fw issues with 10.
In about 10 days from now I will be able to test the Fireface 400 through the EXSYS EX 16415 in Windows 10.
If it doesn't work, I'll try switching to Windows 7 and if that doesn't work either, it will mean that Windows 10 isn't the problem.
I have the suspicion that if Windows 10 was the problem then RME would not release firewire drivers for Windows 10 and they would be warning anybody with a firewire only audio interface not to upgrade to the new OS.
ok guys, I'm back with amazing results: after having installed the XI02213BZAY based chipset my system is running fine and stable. I can use all my FF800 bandwidth without any error.
I simply removed the "wrong" card and inserted the new one, started PC and..voil.. didn't even need to reinstall rme drivers.
The EXSYS EX 16415 has arrived.
I tested it and I have the same problems as with the approx.
When I record a guitar track in cubase 8.5 and try to overdub another guitar track, one of the two is not playing back and I hear odd sounds and glitches.
As I was recdording the second track, I was also hearing glitches and the recording stopped.
The waveforms of the recordings are visible, but the sound isn't there.
I uninstalled the RME drivers and installed them again, but nothing changed.
Do you have any ideas?
The RME Fireface 400 is working fine on my older computer(I7 920).
On my new computer I only did test recordings and everyone of them has the same problem.
I will try windows 7, but I suspect that this is not the problem.
The mainboard having an issue, seems more like it, but I guess that if I had hardware problems, I should also have blue screens.
Question:Would everything work fine if I had a Usb audio interface?
What do you think?
I did that already!
I thought that maybe one of my motherboards pcie slots, did not have enough power.
I tried both of my pcie slots.
Same problems.
I also have a big(red, just like the one my graphics card uses) pcie slot.
Should I try this also?
Is it compatible?
I've downloaded and installed my motherboards(gigabyte z170x gaming 3) audio and chipset drivers, with no better results.
Is there a chance that RME's drivers for windows 10 are not working good?
Could it be a software problem(Cubase 8.5)?
I will try the windows 7 installation tomorrow.
Well it doesn't work either...
Perhaps you know about other Z170 motherboards and firewire issues, because I read that many people have the same or similar problems, with Z170 motherboards from different manufacturers.
It doesn't seem to be a software problem to me.
Maybe a driver problem, from RME, or the motherboard.
I'm already very frustrated and tired, trying to find a (maybe non existing) solution to my problem.
If I decide to buy a Usb audio interface, wich one do you suggest?
UCX, 802, or wait for a UCX+, that will get rid of the firewire port for good and have a USB3 port?
UFX+ is an ovekill for me.
I don't want to record so many inputs at the same time and I don't want to pay so much for it.
But I see that it has newer preamps, converters and overall upgrades.
On the other hand, I don't want to buy something, that is already 4-5 years old and will soon be out of date, for some reason, like the FF400 I have now.
Buying a new interface was not in my program at all...
I'm very dissapointed with new technology and that kills my creativity as an artist!
Why don't you all build something that works well for a long time?
After all we want to make music, not fight with mysterious issues all the time.
There are certain things you need to know about Totalmix. The easiest way to work with it is the submix mode, so that you do not need to do the routing based on the matrix. This is much easier. You need to understand, that you select the Inputs and the Input Volume per output channel.
So you ensure you entered Submix mode.
You assign the 2 analog outputs with your Monitors to be you Main monitor.
Then you click in the lower right to the main monitor and now select, which channels you want to listen to and the volume.
Ramses I did my research, before I bought my new computer.
I didn't find anything wrong and nobody told me that it won't be good for music production.
I didn't have these problems in the past with my other computers.
After all it isn't fair that companies stopped supporting firewire, for all of us who have expensive professional firewire equipment and we paid a lot of money for them.
My musical instruments don't go out of date.
My mics don't go out of date.
My preamps don't go out of date.
They all work well for many decades!
That's money well spend.
I thought that it woud be the same at least for expensive audio interfaces.
If newer computers and software don't support them anymore, at least I'm expecting from the manufacturers to warn me and not say "everything works great with windows 10 and newer computers".
We musicians, or most of us, are not rich to throw away our hard earned equipment and buy new every few years.
Technology is supposed to be our friend and not our enemy.
So I suggest to audio equipment and computer manufacturers to at least be honest to us, because they are losing customers...