search

BN701 / MultiArp

Another step on the Great Midi Adventure! A place to try out several midi sequencer ideas I've had over the years and maybe build a little platform I can use for live improv.
GNU General Public License v3.0
1 stars 0 forks source link

Pattern Menu doesn't work #2

Open mxmilkiib opened 6 years ago

mxmilkiib commented 6 years ago

Command e and I get: silver_2018-01-06-04 01 19 Up and down arrows still change the red background pattern number.

ncurses 6.0+20170902-3, tried in urxvt and xterm

BN701 commented 6 years ago

Hmm ... apart from missing some background highlight in the pattern list and panel to the right, that's what it should look like. Here's mine: image Which terminal were you using when you took the screen capture? Mine is xfce4-terminal, which is just the default with Ubuntu Studio, can you run that?

By the way, have you tried hooking up some midi sources and destinations? I use the ALSA panel in QjackCtl, though you don't actually need to start Jack. Guess I should write a quick start guide at some point soon, too :)

mxmilkiib commented 6 years ago

The terminals I tried were rxvt-unicode aka urxvt (lightweight terminal) and xterm (classic "midweight").

So I installed xfce4-terminal but I get the same no edit menu selection.

(Aside: what was buggy for me there was that pressing backspace inserted a ^? character. echo $TERM in xfce4-terminal was "xterm-256color". So I did export TERM=rxvt-unicode-256color, which is what urxvt is using, and backspace worked again. This is because I have xterm.*backarrowKey: false set in my .Xresources, though nothing similar set for urxvt)

So I installed gnome-terminal, the main heavyweight VTE terminal, and the menu/visual DID work.

Hmm.

I haven't tried routing yet. So far I've been reading, trying out and summarising the docs.

Edit: I've checked basic midi recording and output and it works. I used a2jmidid, Carla (and Patchage), jack-keyboard and a random synth.

BN701 commented 6 years ago

I tried xterm and xrvt and got even less than you: one or two lines of grey text and but mostly black-on-black.

Next step was to try and debug - gdb inside Codeblocks - but this gave me colours and most of the text I see with xfce4-terminal. In fact, apart from the ridiculously tiny font, it looked just the first screen grab you sent me.

I decided to try and fix the fonts next. When I looked, I found i didn't have a .Xresources file so I downloaded this one: That at least gave me something I could read and it also gave me all the highlighting ... but only for xterm and only when debugging in Codeblocks. Running MultiArp from within Codeblocks without gbd, or running from gdb outside of Codeblocks, or just running standalone is still only working in xfce4-terminal.

I have to admit I find all this terminal config stuff fairly impenetrable and besides, I shouldn't expect users to have to mess around with it anyway just to run a specific app. I need my app - any app - to work out of the box on as many platforms as possible. I think I'll go back and look at the way I'm setting up colours with ncurses and start by turning them all off. It was all a bit trial and error, anyway.

Thanks for your help. Do you think you'll get on to making some music at some point?

B

mxmilkiib commented 6 years ago

An .Xresources isn't required but it can help. One has to load the .Xresource settings on boot. Modern DEs just have sensible defaults or their own configuration system. If one is running a more bespoke system, there's a bit more dotfile config management.

You can generate your own .Xresources colour theme if you wish here.

Possibly an ncurses toolkit like CPPurses might assist?

I'm at the phase of working out a MIDI routing system, making music comes soon :)