What happened to schismtracker.org? (Page 5 of 7)

OK so it builds on RPi2 B+ with Raspbian Jessie \o/
From the /doc/Building on Linux
installed these:   
build-essential automake autoconf autoconf-archive libx11-dev libxext-dev libxv-dev libxxf86vm-dev libsdl1.2-dev libasound2-dev mercurial libtool

But  libxxf86misc-dev isn't in the Debian respo. So it didn't get installed.

I also went through the list of deps for this SchismTracker package:
https://packages.debian.org/stable/sound/schism
They were all up to date on my system.

Then ran
mkdir -p build && cd build && ../configure && make
../configure seemed to finish but make failed with:
...
make  all-am
make[1]: Entering directory '/home/pi/schismtracker/build'
/bin/bash: schism/.dirstamp: Permission denied
Makefile:861: recipe for target 'schism/.dirstamp' failed
make[1]: *** [schism/.dirstamp] Error 1
make[1]: Leaving directory '/home/pi/schismtracker/build'
Makefile:765: recipe for target 'all' failed
make: *** [all] Error 2

So tried changing permissions:
pi@raspberrypi:~ $ sudo chmod a+rw /home/pi/schismtracker
This didn't help. But then tried just 'sudo make' and this created a bin

Most of it works fine, in QjackCtl are the Midi In and Out ports; but had to go into .schism/.config and add:
[Audio]
...
  driver=alsa:default
to get sound out. So this loads the driver and plays great, but I can't have Jack open. I tried
  driver=alsa:dmix and just alsa but these didn't work. I'm not real sure if the dmix applies to Deb or I should be using some other argument.
Anyway, I still have to check out midi sync into other apps without Jack, but it's working very well at this point. I'll copy the bin to my dropbox if anyone needs it.
Yogi

Just a little follow up after some testing with MidiOx.
I'm using the current release Win32 20160913 with s3m Mods sending into Midi Ox's Midi Sync Transport detecting the Tempo.
On this setup there is a minor difference between the Mod's labled Tempo and the detected Tempo. Mods displaying Tempo 80 are detected at 81; and mods labeled as 125 are detected as Tempo of 128.
The difference is probably due to Midi Ox's detection Looks good!

One thing that I don't understand is the Midi Output Configuration page. The init values were:
start=FF
stop=FC
tick=
So I changed these to:
start=FA
stop=FC
tick=F8
At one point I wanted to see the Start/Stop message behaviour better, so I reset the tick field to blank. But ticks continued to be sent. Then also blanked the Start field but Start messages also are sent regardless of the values on the Midi Configure Page. Am I misunderstanding the use of this page? It does update the config file and I have tried re-starting Schism. Or does it describe how/what the tracker responds to?
It's not really an issue for me but just trying to understand,
Yogi

Last edited by yogi (Sep 17, 2016 7:34 pm)

Oh yes, Midi ox is the tool to filter. 'Broken' or not, very happy to have it sending midi clock The other workaround is to set the Midi out port to disable

I'm not sure if it has impact but with these tests I had the Midi Mode set to  "IT semantics". But just a little bit ago I set it to "tracker semantics". I don't really know what the differences are but I noticed that with the latter setting, when I stop the mod, this is being send out:

 
.... Tracker running   
  19843009  1  --    248   ---   ---   --  ---  Timing Clock  
.... Tracker stopped        
  19843056  1  --    176   120     0    1  ---  CC: All Sound Off     
  19843088  1  --    176   123     0    1  ---  CC: All Notes Off     
  19843119  1  --    176   121     0    1  ---  CC: Reset Cntrl       
  19843197  1  --    176     7   127    1  ---  CC: Volume            
  19843228  1  --    176   101     0    1  ---  CC: RPN MSB           
  19843275  1  --    176   100     0    1  ---  CC: RPN LSB           
  19843306  1  --    176     6    12    1  ---  CC: Data Entry MSB    
  19843338  1  --    176    38     1    1  ---  CC: Data Entry LSB    
  19843400  1  --    176   101   129    1  ---  CC: RPN MSB           
  19843431  1  --    176   100   128    1  ---  CC: RPN LSB           
  19843463  1  --    177   120     0    2  ---  CC: All Sound Off     
 ....same for all channels
  19855916  1  --    190   101   129   15  ---  CC: RPN MSB           
  19855963  1  --    190   100   128   15  ---  CC: RPN LSB           
  19855994  1  --    191   120     0   16  ---  CC: All Sound Off     
  19856025  1  --    191   123     0   16  ---  CC: All Notes Off     
  19856056  1  --    191   121     0   16  ---  CC: Reset Cntrl       
  19856135  1  --    191     7   127   16  ---  CC: Volume            
  19856197  1  --    191   101     0   16  ---  CC: RPN MSB           
  19856228  1  --    191   100     0   16  ---  CC: RPN LSB           
  19856233  1  --    191     6    12   16  ---  CC: Data Entry MSB    
  19856233  1  --    191    38     1   16  ---  CC: Data Entry LSB    
  19856233  1  --    191   101   129   16  ---  CC: RPN MSB           
  19856233  1  --    191   100   128   16  ---  CC: RPN LSB           
  19856233  1  --    252   ---   ---   --  ---  Stop    

It appears to me a more complete shutdown of all midi channels. Interesting feature.
Yogi

I don't have a Win toolchain (VS?) installed but do have the RPi setup (linux Deb Jessie). And I wish I could find a Linux 'MidiOx', the best I can do is set the midi out on the Pi to an interface and cable to another interface on the PC with MidiOx.

If you can do Win build that would be more direct, but I was going to do the Linux-to-Win setup anyways to test the RPi build. Will rebuild the RPi Schism in the AM at any rate
Yogi

got so excited with you guys keeping this great software alive I just did this track last night

\o/ Great Work! Now totally configurable This is such a great patch to Schism (also really digging the OPL2 emu), Thank You So Much. It really opens up many possibilities for integrating drum machines and sequencers. Very excited! 

  As to the Win toolchain, I'm kind of halfway there. ATM have msys and GCC (arm-none-eabi 4.7) for Midibox.org builds, so will have to see if I can have the two side by side. May be with separate SET PATH= commands. And sorry, last night opened a 'pull request' not knowing what I was doing, I'm such a git-hub n00b.

  Had looked at Mididings, about a month ago (when I first started setting up the Pi) but once I figured out QjackCtl, kind of thought that was enough. A lot of what MidiOx does, routing wise, is seamless in ALSA so even QjackCtl isn't needed very much. Till now, hadn't needed the more in depth monitoring features of M.Ox on the Pi but will try out Mididings (I think it has an armhf build in the repo) because really do need a solid midi monitor.

@PULSLOOPER, A++ and thanks for the MOD file

Well, off to re-build on the Pi. Thanks again,
Yogi

Also the 20160918 branch runs well on Pi, even subbed FA for MIDI tick. Spit out lots of Start messages HAHA. This was Pi to PC/MidiOx end-to-end test Another minor OT detail, Schism  does run with QjackCtl, just can't run the Jack server (which makes sense).

As to Note on/off, no don't see any traffic. But to me, thought it would be something like a 'instrument' set to a Channel to be used on a track. With the entry '9c n v'; this looks to me like hardcoded 9=high nibble of status, Note message, and  c=variable for low nibble, the Channel. With n and v variables to complete the message. So I thought either a placeholder for function or some way to send notes from a track.

Just did some simple tests, changing the Note On to 91 01 01, to see if it would send these absolute values but no. Then changed the 'Embed MIDI data' to On but no change. Much of the Midi Screen I don't understand, kind of 'poking at it with a stick to see if it does something'

It would be a wet dream if this works Being able to track an external synth along with samples would be the Holy Grail
Yogi