Today i decided it would be fun to poke around schism tracker some more. I got the source package from the schism tracker page. The mercurial snapshot.
I tried to run the ./configure thingie. It's not part of the package. I am too amateur to find out what to do next by myself.
I thought i could grab a new version before builds are made. I also thought i could check out if some bugs remain in the latest code.
I'm under mac os x. I compiled / installed SDL and all went well.
autoreconf -i will spit out a configure script. Shouldn't be much different on OS X than Linux once you have SDL installed, as long as you have sdl-config in your path. (Getting that might be a minor challenge – I don't remember how SDL works on OS X but I think it's kind of weird somehow)
hi storlek, we've been talking about this a bit on #schism, so here's a bit of a short paste:
9:46 <@distance> either way, is one or the other or both of those switches doable
19:46 <@Storlek> which switches? memory like a goldfish
19:47 <@distance> filter midi note input
19:47 <@distance> 19:29 <@Storlek> how about a switch to ignore midi input
19:47 <@Storlek> that, prolly not, because it seems really really complicated
19:47 <@Storlek> that, yes
19:47 <@distance> - when using midipattern trigger
19:48 <@distance> and switch: say: "when midi pattern trigger received, do you: A) start playback of pattern from
start of pattern B) start playback of pattern from row-cursor-is-on.19:48 <@Storlek> in other words "should midi sync start act like F6 or F7"
19:48 <@distance> exactly
19:48 <@Storlek> well, not exactly, since you can ALREADY switch between playing the song or pattern
preservation of thoughts against irc transience = +1
so basically this is to enhance the functionality of midi pattern trigger.
since its brilliant to be able to already use schism tracker to input notes from a midikeyboard, and have the pattern playback start on first pattern trigger - it is therefore suggested that two (2) switches are created for user usage:
first switch:
when receiving Midi Pattern Trigger - do you start from 1) first row of pattern or 2) row of pattern that cursor is on.
second switch:
when receiving Midi Pattern Trigger - yes/no on "do you filter all midi input?" -mode.
if these two are implemented, it's very easy to guess what i'm going to be asking for next.
I'm having some major issues with saving now, whenever i hit Ctrl+S to save, it outputs WAV over the original file. I could get around it at first by hitting F10 then saving over it again, but now it's giving me the error:
Unknown File Type: IT
which, as you can imagine, shocked me somewhat!
hope someone can help, im currently keeping Schism running so that i don't lose my changes!!
thanks
theGarbs
I noticed that CTRL+S does the same thing for me.
I decided to avoid using CTRL+S since it wiped out
a few of my songs. I now use F10 to save my mod updates.
fortunately, I had backed up those songs/wav's.
Shane.
Well obviously that shouldn't happen! I haven't heard problems from people about this stuff until recently so I guess it broke in the Feb. build, and all the file output code was torn out and rewritten so it shouldn't still be broken in the current source. If you're not using any of the stuff that was added in the February build you might be better off going back to the January one until I get a new one packaged.
I have no idea what might have been broken, but the file save and export code was a mess so I'm not fully surprised :P
OK, track 1, a version where I've done a version number switcharoo by giving them version 8.88 (OpenMPT, IIRC).
ok, it's refusing to load that because it has 257 entries in its orderlist...
And here's track 2, a conversion from dbm.gift or something like that. The samples are missing. For some weird reason, IT214v5 does the same, I'm not sure why. Maybe my converter's rooted. mikmod and vlc/libmodplug load it fine.
None of those samples have flag bit 1 ("sample has data") enabled. Neither modplug nor mikmod adhere to the spec there.
Thanks for that.
I believe I padded the orderlist before I saved it or something like that but it may have added the 255 after the 256th index, which I then dealt with in a hex editor.
Oh, and I should really remember to put that bit in in future.
Oh wait, one more and I'm pretty sure this isn't my fault.
Was just playing around and I stumbled across this corrupted thing.
To make matters even weirder, SussmansClock.it uses the same sample pack and apparently the same tracker, yet works a charm.
Also, it has 2 patterns, not 1 as the status text says.
I use 20100202.
That file is just plain broken. Probably truncated.
I added a lot of old stuff to the repo from ages past – the "old" cvs history from before the directory restructuring, and also merged in the sources to the old tarballs from before Schism Tracker was even tracked in a source control system. The old code has been added under branches "mesozoic" and "paleozoic", respectively. I also merged the first CVS commit with the old tarballs, but it's impossible to do the same with the schism/schism2 cvs transition since that would involve rebasing the entire repository and changing thousands of changesets.
What all that means is anyone tracking hg will now end up with a spare head for all the old stuff; don't be alarmed :)
Hi:
If a song changes speed/tempo (the Axxx Txxx commands),
then samples/instruments lose their volume, and or,
disappear completely.
I suspect that MODPLUG is where the bug is, because
other apps that use "modplug" do the same thing.
Could you please look into this for me, since I am
forced to use WinXP, and I have a whole mess of my
own drum tracks that rely on Impulse Tracker.
Most of my songs change speed/tempo a lot. Without a
bugfix, my future in music is dead.
Have any examples? I can't replicate this at all.
I'll try and bring an *.it mod that does this by Friday.
Thanks:
Shane.
Hello again:
Ok... Here's a backing track to one of my own songs.
Could someone please tell me why it does what I said
it does in Message 938? Notice that as you pass each
speed/tempo change, that samples/instruments drop in
volume or dissappear completely (eventually).
Thanks:
Shane.
There's nothing at all wrong with Schism Tracker's playback here. Your song is cutting the volume in a number of places, uses a bunch of Z00 filters, and has at least one channel muted.
Thanks Ashli.
I'll do what I can to correct this.
I noted that when I play some of my other mods,
that they play just fine, provided that I don't
change the speed/tempo...
Feedback was/is always appreciated. :-)
Take care:
Shane.
P.S. Schism Tracker really RULES! :-)
Well, if you do come across a scenario where something is being played incorrectly, try to reproduce it in a small test-file (i.e. not a full length song) and I'll look into it.
As for the filters, here's a Zxx-stripped version. Were you maybe using IT with non-filtered mixing or non-MMX drivers?
Thanks!
Thanks Ashli:
I stripped out all the Z00 commands by hand.
That was the source of my grief. Now the
MOD plays the way it was intended. Hooray!
I forgot that they were even in there.
I was using them as a memory aid (hard to explain).
I don't even use the midi portion of IT mods....
I REALLY APPRECIATE YOUR HELP/INSIGHT, THANKS! :-)
SCHISM TRACKER ABSOLUTELY RULES!!!!
Shane.
Hello:
Thanks for taking the time to strip out all those
Zxx commands.
Did you make a routine to do that?
I have 15yrs of my own mod work.
Schism Tracker has allowed me to "revive" them.
Thanks a million! :-)
Have a great one.
Shane.
changeset 2087: 5d12eaf07e3b
Why is the screenshot facility being removed?
This was very useful for taking screenshots of schismtracker in fullscreen mode.
It never worked – it always wrote "error writing screenshot: no such file or directory", or "success".
It wasn't a useful feature anyway even if it did work, because you can take a screenshot perfectly fine with whatever existing method your operating system provides.
The .png writer was highly redundant considering libpng exists everywhere, so there's not much use for reinventing the wheel.
The keyboard handler for it was a horribly nasty hack.
On top of that, what is the burning need to take screenshots of the tracker, that it needs to be directly integrated with it? Write more music.
That said, if you can rationally disprove those statements, I might consider adding a proper screenshot mechanism, but I seriously doubt its usefulness.
> It never worked
Yes it did.
> It wasn't a useful feature anyway even if it did work, because you can take a screenshot perfectly fine with whatever existing method your operating system provides
Except when the keyboard is grabbed. Or when you run it without a desktop environment (framebuffer on z2 zipit).
Sorry, I should be more specific. It never worked for me.
It's trivially simple to ungrab the keyboard, and there most certainly are screen-grabbing programs that run on a framebuffer. Indeed, a few of the early screenshots on this page were captured from a framebuffer, because for a time I wasn't even using X11.
I'm entirely unconvinced that such functionality is at all useful enough to be built in.
To hit the point home, here's a screenshot I grabbed, from the framebuffer on my laptop, of Schism Tracker failing to make a screenshot.
I got the latest mercurial and had to construct version.h myself. Also, you forgot to update the automake thingy or something to use its.c instead of its.cc.
-GM
P.S. I got it working eventually... and me.png.it is STILL not using the IT behaviour (compatible Gxx ? don't switch samples, just change volume : if the C5 speeds don't match, DON'T CONVERT (i'm looking at you, modplug >:/ )). Don't forget ßainor.it, too, as mikmod would play it IT-like if the loader wasn't so fragile (it conks out normally due to a few things, mostly the Ux modplug extension).
version.h added, thanks for the heads up lol.
As for automake: it doesn't deal so well with changing file extensions apparently. I usually make distclean and reconfigure if it's insisting on looking for nonexistent files.
yes, I have not bothered with further subtleties of the Gxx effect yet. It does a lot of things wrong. That's still a low priority, considering how many players get that effect wrong in so many profound ways.
(Ux modplug extensions?)
I sure don't care about modplug extensions working, I wish they'd die entirely. But I'd sure love to see Gxx at least work as well as it does in ST3.
Try playing satellite one by purple motion on a current build, it's completely unplayable.
>>926
Just tried it, sounds fine to me. In fact, I played it six times, the full song and then with different channels soloed.
Also ST3 is full of stupid bugs, and I wouldn't be surprised if one of those bugs was related to portamento. Does it sound "wrong" in Impulse Tracker as well? I don't know if I ever listened to Satellite One in ST3, so maybe I have just been hearing it wrong for many years :P
Anyway, if you have any sort of bug to report, a testcase with preferably one channel and a very simple pattern is most helpful.
I'll look at all of the pitch handling code today.
I'm sorry I didn't provide more specific info. My copy from Jan 14 plays the song wrong from the very first second, you would notice it immediately. Building with today's code plays just fine, though. Perfectly, even.
Great job as always!
(sorry about the tone of my last post, reading it now it sounds a lot shittier than I intended)
Happens. shrug
I don't even know what might have been broken... and then fixed again, I guess
http://schismtracker.org/hg/rev/eb3ebf65161e
This behavior was observed in registered copies of IT.EXE (the same copy that has shift-chording in the pattern editor)
Did implementing this IT.EXE bug bother anyone?
That seems like awfully specific behavior for a bug... but then again, I also can't come up with any reason why it might have been deliberately implemented. I can't think of any reasonable purpose that particular combination of actions might serve. Either way, it makes it pretty hard to enter a chord with a G# in it.
This probably doesn't matter at all...
But looking over the code I noticed here that it says "Farnadole" instead of "Farandole".
http://schismtracker.org/hg/rev/8cbdadd80681
1.139+ strcpy(song->tracker_id, "Farnadole Composer");
Not like it matters, who uses this psycho format, anyway?
Hahaha, I am the master of the tpyo!
Fixed, thanks.
(And yeah... I actually had to search for .far files to test the loader, because I have one of them.)
This file is broken. On one of the instruments (strings - e.wav), "carry" is on. This instrument only ever plays once on each channel, so you just get one chord.
Well, then turn it off!
Seems that xmplay and xmp both reset the envelope and retrigger the note when it hits the note off, I don't get why but I'll try to investigate that later. For the time being I checked in a patch to make the envelope reset when a note is triggered and there's nothing playing, which I'm not sure how I managed to not ever notice before since it only makes total sense that you'd want new notes to start with the envelope not at the end :P