I just tried a new version of schism in a while and it crashes with the following the crashreporter :
I am using the build provided on the schism page (july 12th build)
**********
Host Name: Mistigris
Date/Time: 2009-07-16 16:34:28.475 -0400
OS Version: 10.4.11 (Build 8S2167)
Report Version: 4
Command: schismtracker
Path: /Users/xonox/Desktop/schismtracker-20090712-macosx/Schism Tracker.app/Contents/MacOS/schismtracker
Parent: WindowServer [61]
Version: 20090712 (20090712)
PID: 392
Thread: Unknown
Link (dyld) error:
Symbol not found: _pages
Referenced from: /Users/xonox/Desktop/schismtracker-20090712-macosx/Schism Tracker.app/Contents/MacOS/schismtracker
Expected in: /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
I compiled from source and it worked. I then discovered some bugs.
Keyjazz doesn't work well with instruments outputing midi. It works in my old version of schism.
>>4578
Hm. Strange.
I have no idea what might be wrong there. Not having an OS X testing environment (or even a real OS X build environment) makes that really hard to test.
Are you using PPC or Intel?
I had no clue how the midi keyjazz worked, so I made some random guesses. Not surprised that it's dysfunctional. My midi keyboard just does input – no synth stuff on it or anything – so I'm not sure how to test that either. I guess I could set up a second schism instance somehow?
midi clueless
I am using Intel. It does work fine when i compile it myself.
I could test on my powermac g4, but it only has 10.2 running on it.
MIDI keyjazz only outputs one note in like 10-20 notes i press. It is very erratic but used to work perfectly. I dream of the day schism will have complete midi support.
To test out midi... Which OS are you using ? I'm fairly used to deal with midi gear and midi setups. Not a lot under these OSes but i find out a bit of info and try to help. I unfortunately can't seem to understand the schism tracker code since i haven't used the C language in a long time and never used it very much...
But i'll do my best to help when i can.
If you can set up something like an internal midi bus, i could provide you with a csound orchestra to test midi.
Under Mac OS X you can create virtual midi connections that lets you connect together midi software. I did it under linux 10 years ago with something like a FIFO file and some really crude tracker code i wrote back when i had lots of spare time.
So if you can get 2 pieces of software to connect via an internal midi connection.
Under windows i think you can set up something like that using MIDI Yoke (http://www.midiox.com/).
Then you could use another piece of software that monitors midi (MIDI OX does it, i think).
I could write a csound orchestra that prints out incoming midi data in the console if you are using linux and can't find something that monitors midi data.
Let me know if you need anything or have questions.
Linux with Alsa. I know that my midi keyboard works because aseqdump is printing out lots of midi events when I press keys or fiddle with the knobs, but schism just flat out refuses to listen to it. (It says there was some nonspecific error opening the midi port if I try to use alsa midi with it, OSS opens the device just fine but does nothing at all.)
I'm aware there's apparently some way to get schism to talk to itself via midi but I have no idea how that is supposed to work, and if I try loading two instances only one of them will function. I tried to feed schism's midi-out data into qsynth but I don't understand qsynth's gui and it has virtually no documentation...
argh
Do you want me to make some real time midi orchestra with csound ? The only changes you would have to do to the csound file would be to pick a midi port and a different audio output than what i use.
I have exactly zero knowledge of csound, so that might not be too helpful...
Yes, i didn't expect you to have knowledge about it.
But it's pretty much the only midi / audio package i can code on. Hence why i offered to code up small things to test midi. Running a csound file is pretty much like compiling something using gcc, except there's way less options.
I don't know which linux software can work with midi right now... There's some midi sequencers like Rosegarden, perhaps you could try it out to see if your midi setup is allright under linux...
Maybe plusminus could suggest something. He's got linux and he's got midi knowledge. And he's a good guy.
>>4603
Sorry, the only thing I really know about MIDI and Linux is that SDL's MIDI synthesizer is cracked out to hell. Which doesn't even really affect what you're doing, I think.
I'll try getting my old synth hooked up to my computer via MIDI sometime this week, but it's not something I've done in ages. I can't even remember whether I got it working with Linux or not.
Hey Storlek what soundcard do you have?
>>4605
For the desktop: ALi M5455 (Realtek ALC658D) on the motherboard, and a CMedia CMI8768 PCI (it's trash, but I use it for the spdif in).
My laptop (Eee 901) has a HDA Intel card (Realtek ALC269) built in, it's also crap.
They all "work" in that they make the speakers do things...
I don't think the sound card matters tho, since it's a usb device...? As far as midi goes, I know that:
When I plug the keyboard in, and start timidity in daemon mode and then run qsynth and click on a bunch of buttons at random because the gui SUCKS, eventually, I somehow end up at the point where pressing notes makes it produce sound... with a ton of latency. And when I run aseqdump and bang at the keyboard I get a flood of text in the xterm... with no latency, but also no audio. Presumably the way ahead is by copying large parts of aseqdump's code into isysev. (Of course, actually hooking isysev into schism instead of just having it sit there and not do anything would also help, but that's kind of hairy.)
I am not planning on doing any midi at all with SDL, because it seems like it'd be a lot of no fun.