Mod Archive Forums Mod Archive Forums
Advanced search  

News:

Please note: Your main modarchive.org account will not work here, you must create a forum account to post on the forums.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - supernoob5000

Pages: [1]
1

TL;DR: MilkyTracker isn't being recognized as a midi receiver by aconnect, but that's the only way I know of possibly getting midi input working. I'm just looking for some general guidance on how I can try to get midi input working from here.


My System Setup (If it helps)
I'm running Manjaro Linux with nothing special changed from the default audio setup as far as I'm aware. My MIDI input is going in through an audio interface, and that interface is also where the final audio is output to.


Long version:
Hi,
As the title says, I'm trying to get my midi keyboard to work in Linux. It works correctly with other software, but not in MilkyTracker for some reason. I'm also having trouble finding any useful information about how to resolve this, as neither the documentation nor Google seem to have any answers that I can find.

The docs only say
Quote
Enabled by default if available on the system. See the Linux readme for details.

I believe the readme they're referring to is this, but that only says
Quote
If available, MilkyTracker will detect Alsa and configure itself as a Midi receiver.  You can then link MilkyTracker up to a Midi sender in the normal manner.

I'm assuming the "normal manner" means using aconnect, though maybe they had something else in mind. I'm honestly not sure. Regardless, aconnect does not report MilkyTracker as a midi receiver.

Output of "aconnect -l" is
Code: [Select]
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 16: 'UMC404HD 192k' [type=kernel,card=0]
    0 'UMC404HD 192k MIDI 1'

This is unique to MilkyTracker. If I start any other program which accepts midi input -- for example, SchismTracker -- then the output of "aconnect -l" is
Code: [Select]
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 16: 'UMC404HD 192k' [type=kernel,card=0]
    0 'UMC404HD 192k MIDI 1'
client 128: 'Schism Tracker' [type=user,pid=17979]
    0 'Schism Tracker  '

So far, I've tried changing SDL_AUDIODRIVER to various settings including both "pulseaudio" and "alsa" and it seems to have no effect.

I've also tried searching previous posts on this forum and any other plausible place on the internet I could find, such as the MilkyTracker subreddit. So far, while I've found some questions on MIDI keyboard setup, nothing I've found offers a solution to my problem.

I'm at a complete loss at this point, so I'm hoping someone could please point me in the right direction. I'm new to MilkyTracker and I generally love the experience so far, but using a MIDI keyboard is vitally important for my creative workflow. I really don't want lack of MIDI keyboard support to be what turns me away from this otherwise awesome tracker.

Pages: [1]