Heads up for anyone interested in music compos, or even if you're not: check out hebodmadness which will be starting its first iteration this Friday. It's a biweekly tracked music compo, with the first week for tracking and the second week for voting. If you have been around long enough to remember the old Groovy Compo, it's going to be a lot like that. Check it out, it will be awesome.
Hey cush! Got some votes?
Also mandrasigma, but I don't think he watches this board/thread.
Results of this one might not be so pretty, which is a shame since the songs were good.
i voted....
but not with the right file.. :(
which you could've told me, i suppose.. :P
Aha! So that's where the unmarked votepack came from. Fixing results.
... I did tell you... now. :)
I don't usually look at the vote files until right before I calculate them, to help keep my own unbiased.
It wasn't just blank..
it was the 06 comp blank one. :D
I look forward to seeing if i've retained my least consistant title..
DAMN!.. MOST consistent...
My only comment is that I've have quite a bit of least consistents... more than anyone else has gotten.
Get any entries this week? Sorry if my pack drove people away :P
If you're extending it I'll make the effort to submit something.
I just loaded an S3M with AdLib samples into Schism Tracker and was wondered: it shows AdLib parameters! It excite me very much. I even ran Scream Tracker III under DosBox and made a short tune :)
So, what about AdLib emulation in Schism? May be it wouldn't be too hard (there is open source adplug project)?
It can drive the Scene to made some cool S3M tunes. Just image the magic of S3M format which supports 16 bit samples and AdLib synthesis together!
Already done, try pressing play ;)
Wow, it works!!!
But wait a minute. It looks like AdLib's volume is too quite (I tested on the S3M which uses AdLib and digital samples at the same time).
I tested S3M on the real hardware. It was Synergy ViperMAX sound card which has GUS and AdLib chips on it's board. Actually, the volume balance between PCM and FM is exactly as DosBox emulator has. So, you can use Scream Tracker 3 under DosBox for test.
Now Schism plays FM approximately 2.6 times quietly then original.
Guys, please fix the AdLib volume!
Here is the test tune:
http://www.youtube.com/watch?v=-lFNYJ7B820
www.thesands.ru/rotagila.s3m
...without noting down and adding temp values to the orderlist then removing them.
It would be so nice if ctrl+O on the sample list would render current pattern to the selected sample slot. (maybe ask "replace sample? yes/no" if there's already a sample there)
on todo list, something like that will implemented eventually.
btw: does ANYONE actually use that pattern linking thing?
I've used it.
You can use it as a pattern sequencer.
If you create all your separate musical parts individually in a pattern i.e. drums in pattern 1, bass in 2, chorus lead in 3, verse lead in 4.
Then you can chop and change parts together quickly.
Plus it means you can layer several effects on at the same time.
eg Pitch envelope AND filter envelope.
It's so hot right now.. :)
I use it all the time, usually with long patterns at high tempos and Oxx effects to get a nice flanging going on.
Pattern linking sounds like an interesting feature - could someone explain how to use it or point me to the appropriate documentation? Thanks.
>>4694
F11, F1:
Ctrl-B Link (diskwriter) this pattern to the current sample
Ctrl-O Copy (diskwriter) this pattern to the current sampleCtrl-O is super useful,
Ctrl-B I never use.
I like to use the link because that way when I update the pattern, it automatically updates the sample.
Ctrl+O is useful for creating samples from basic waveforms, or octave doubled samples, etc. with effects applied to them, then you can apply more effects when you use those new samples in new patterns.
Ctrl+B i don't use very often, because the mixing volume is inconsistent with the rest of the pattern. (at least this was the case a few months ago)
hiya, i just installed the newest build of schism on my mac osx.
so here's a few questions.
2) is it possible to arm, and un-arm, a midi-input-channel? i'd like to be able to slap in a few notes from my korg nanopad while pattern-follow is on, then when the general pattern is playing, i'd like to be able to just toggle the midi device off.. how?
3) have muted channels ALWAYS played midi-notes? can this be toggled off, so that i could, instead of arming/unarming a mididevice, just slap myself onto track#5 which is muted and play stuff into my other sequencer, an
4) is it feasible that schismtracker would have a simple "start playback of song when midi clock START has been received via a midi input"? all that actual sync stuff is fine, sure, but just start-playback-on-start-midiclock would be wonnerful!
Fn-DeleteCtrl-backslash as the global arm.IT generating MIDI events for muted channels. Can anyone verify?Ctrl-Z)
drooooollllllllllllllllllllllll...................... :D
Write me a geometry manager and consider it done ;)
oh, not as exciting, but here's one i gimped up @ 800x600
For awhile I've been thinking of ways to automate certain repetitive tasks when composing, but I never really got into being able to read/write .it files enough to do anything useful.
But, what about being able to save a song as a plain text file? And in turn being able to import a modified text file? Sample data would obviously be obliterated but anything else should be exportable without doing anything too crazy.
IIRC modplug could copy pattern data as plaintext, which could be in turn pasted into a text editor. So hopefully this idea isn't so crazy..
What OS are you using?
Schism can copy its pattern data in the very same format as modplug, but it's really clumsy and fails half the time.
I tried suggesting a way to handle pattern load/save like with FT2's .xp pattern file format, but people seemed to not have liked that idea for some reason. Nice to see someone else think the same way as me.
If you've got the X headers (not just the SDL headers) schism will include X11 clipboard support.
>>4436 Both behaviors are implemented.
I suppose the ITEXE behavior can be had without forcing classic mode by adding an option; I presume you suggest the ITEXE behavior be the default?
>>4437
I suggest the "new" behavior be removed. It doesn't do what people expect.
Auto's been removed.
Also added extension detection.
Idea:
It'd be convenient if, when typing a filename to save, schism inspected the filename and temporarily switched the filetype button to reflect the file extension – unless a button was explicitly clicked on. That is to say, pressing F10 and entering asdf.s3m would result in an implicit pressing of the S3M filetype button; altering the filename somehow to have an .it extension would re-press the IT button, but, selecting the S3M button explicitly and typing asdf.it would still save an s3m file.
Switching away from the page would undo any explicitly set filetype and re-enable the auto type selector.
This way, it's visually clear what is going to be saved, there's no guesswork, no extra button clicks needed, and if someone wants to save something as the "wrong" file type for some odd reason, it's still entirely possible.
>>4666
No it isn't. There was no visual indicator at all of what type of file was being saved before it was saved, and the auto button seemed to backfire more often than it worked properly.
Loading an S3M and saving as blah.it seemed to sometimes save S3M data, and on at least one instance it managed to overwrite an .it file with a diskwritten .wav somehow.
With this behavior (which I also think should be fully optional) you would be able to see exactly what will happen when you press enter.
I personally suggest replacing the rather useless and misleading:
> Opening /wherever/is/file.0 for writing
> Starting up diskwriter
> Diskwriter completed successfullywith something like:
> Saving to /wherever/is/file.it Format: Impulse Tracker
> (maybe some other useful info like file size, number of patterns, samples, instruments, etc...)This way you'd know what format was saved, to what file, AND you wouldn't think you've accidentally started the diskwriter and exported the module to a .wav file.
>>4667 The one about the .wav writing occurred when the save and export pages were linked, not because of Auto. I've never experienced the rest of those problems, the way >>4665 describes it is how it was supposed to work, except for the visual indicator.
Perhaps a good visual indicator would be in the status text flash area:
It could be reused when in non-auto mode to complain if the extension doesn't match the type and the extension is known to the saver:
(tldr warning, proceeding to wax philosophical here)
I think what you're suggesting is using the status text in a way that degrades its purpose. Impulse Tracker usually only writes informative, but non-essential text there, to supply feedback for actions performed that were (potentially) outside the scope of what's visible onscreen, but which could potentially affect future behavior. Hence the messages for multichannel playback, cursor centralize (a bit over 50% of the time on a 64-row pattern, that option won't actually adjust anything), playback tracing, locking/unlocking the orderlist, etc. etc. etc.
Not that it's perfect; IMO there are a few cases where a dialog box would perhaps be clearer (e.g. when sample save fails for some reason, or if a song can't be loaded), and there's a couple instances where it doesn't say anything at all when it probably should, but these are the exception, not the rule. Then again, Jeffrey Lim didn't publish a human interface guideline document, so maybe there is a deeper connection than is superficially obvious. Nevertheless, in this case I think the status is a bad choice, because (a) we have the means to indicate it in a manner that's more consistent with the rest of the interface that's visually present at the time the song is being saved (i.e. the filetype buttons), and (b) warnings really shouldn't be blinked like that to begin with.
I agree with >>4669 in that the text displayed on the save page is entirely unhelpful. Visual separation from the rest of the text on the log page would be great – make it not all gray, add some extra space around it, maybe even reset the scroll position so the old text is scrolled offscreen. (Of course you could still get to it with pageup or whatever, but no one really looks at that page anyway. It's not exactly Terry Pratchett quality.) Information about the file – the file format; number of patterns, samples, instruments, etc.; warnings for anything extra that had to be done to pigeonhole the song data in; and so forth – would be nice to have, but at least having the actual song name and not just blah.0. (Also: possibly indicate if an existing file was overwritten or backed up?)
>>4671 I think having the buttons automatically toggle like that would be surprising.
>Information about the file – the file format; number of patterns, samples, instruments, etc.; warnings for anything extra that had to be done to pigeonhole the song data in;
That'd be dandy; schism already prints warnings for chopped features. Or at least it did.
> but at least having the actual song name and not just blah.0
The writer opens a temporary file, writes to it, fsyncs, then renames it over the original. blah.0 was simply the temporary name- nobody is likely to be interested in it unless opening the temporary file fails.
Several ppl seemed to agree with this. Especially with the new resonant filter code, this feature would be GREATLY useful in creating kickass samples :D :D :D
I think i just posted it on the wrong board —>
... btw sorry for doubleposting / cross-posting this :eek:
Random wave for tremolo/vibrato/panswing should be channel-independent, but it seems like a single LFO is being used for the whole track.
Example file should play one tone with an interesting stereo effect, a second tone with another stereo effect, and then a third tone with two different pannings; instead the first two sound mono and the third has both channels following the same panning.
> some very weird Vxx behavior
You're right about this. MandraSigma's compo tune goes silent at about 1:40, when he starts doing VFF/V00 stuff. :|
>>4567
Actually, that's fully correct. IT ignores values above V80.
http://eval.sovietrussia.org/wiki/Player_abuse_tests#Global_volume
>>4568
Oh right :P
Arpeggio bug breaks some chiptunes.
... .. .. J37
C-5 01 .. J00
... .. .. J00
etc. J00
In a pattern with the above, the arpeggio is ignored the first time the pattern is played. When the pattern is played twice in a row the arpeggio will take effect the second time around.
Bug seems to be introduced not long ago.
Just tested with several old versions, that seems to have existed since the dawn of mankind.
I noticed it recently as well; it's been fixed as of this commit. I'll probably do builds this weekend.
In case you weren't aware (you probably were) Ixy is broken in current hg snapshot, and more broken in 05 August 2009 build. Currently it seems to be ignoring the y value entirely.
OTOH I am literally thrilled to see you tracked down the */8 numkey input bug!
... Wait what, more broken? How that happen, it un possible :(
>>4653
Sorry, my bad. Aapparently I did something dumb trying to apply a patch? Anyhow a clean hg clone seems OK.
I guess it would be worthwhile for me to actually learn how to use hg properly.
haha. then crisis averted, i guess :)
I was messing with Schism's filters, with a couple pointers from madbrain and coda, and added a bunch more resonance to them – check out current hg if you're interested. It isn't IT-exact (reduz reverse-engineered Impulse's filters for ChibiTracker, so it's supposedly the same... but still, I think they sound noticeably different), but I figure, even different Impulse Tracker drivers handle them differently, esp. the hardware mixed ones; so as long as they have some "punch" to them, I think that's enough :)
Also, slightly related, I added a small hack to ignore Zxx effects for IT files that claim to have been written by IT < 2.14. This fixes >>1589 (which was fixed once, very incorrectly, by completely ignoring all filters in sample mode). Hopefully it won't break anything.
... all right i must admit that was very rambly and not altogether coherent
>I was messing with Schism's filters, with a couple pointers from madbrain and coda, and added a bunch more resonance to them – check out current hg if you're interested.
Interesting. They sound almost too strong to me, though maybe I just haven't heard IT in awhile. They do sound nice, though.
>Also, slightly related, I added a small hack to ignore Zxx effects for IT files that claim to have been written by IT < 2.14.
I could very well be wrong, but did some older (but still post-IT2.14 and still filter-capable) versions of modplug save files as IT 2.00?
I did tweak the resonance out perhaps more than IT does.
As for the file version, you're probably thinking of the 'compatible with' field – the one that it would make sense to check, and yes MPT wrote 0x0200 in that field at least up to 1.16. OpenMPT stuffs 0x0888 there, but I think even still in "compatibility mode" it puts 0x0200.
What I'm checking is the created with field, which MPT has written 0x0217 for as far back as I know. I don't remember when Modplug got filter support, but I would hope that it also started writing 0x0214+ then.
Plus, it'd be interesting to look for changes in its file saving code to fingerprint file versions. :)
... new name, must be thursday
All right, I just tracked down MPT 1.00 alpha 5, and coerced it to save an IT file (after much hassle; it kept giving me strange errors about invalid characters in the filename) – it writes 0x0214/0x0200. So I think it should be fine. I don't even think the old MPT versions played filters; I'll play with it more some other time.
And the GUI is hilarious. I remember it really sucking back then, but wow. :D (And the pattern editor has no cursor advance either, you have to keep pressing the down arrow after everything you insert.) Although in many respects, I think I would kind of prefer this to what it's become, if I had to choose between the two. Much more straightforward, none of that superfluous stuff that it has now. Almost inspiring me to take another shot at making a toolkit-based tracker. (last time I tried that might've been around 1999)
>>4616
Haha, that's really got the Excel 95 look going for it.
As far as fields and whatnot I have no idea which I was talking about, I just remember IT listing some old mods as "Impulse Tracker 2.00" or something. Schism seems to be listing most of them as "Compressed Impulse Tracker" for whatever reason.. in any case it doesn't really matter.
> I did tweak the resonance out perhaps more than IT does.
Playing with it some more, I'm sure it is stronger now in schism than IT. You can hear resonance quite clearly even at Z81 and even sometimes at Z80. I really like the sound of it actually, but compatibility-wise I think it makes filtered samples a lot more emphasized than they should be.
Tried not to laugh at that screenshot, but... gotta agree about the ms excel/office comment :D
> You can hear resonance quite clearly even at Z81 and even sometimes at Z80.
Z80 (set resonance to zero) simply acts a lowpass filter. Good for echo channels to sound more natual ...... just put a S91 Z80 Zxx where xx is around 70, you'll see what i mean. and if you put a third pass echo, set it to Z60, etc etc.... (:
This is due to the fact that most materials (like walls) tend to absorb high frequency more, because of their shorter wavelength. Pretty much the same thing happens with light and atmospheric gases, causing the beauty of sunsets.
in theory yeah, it should be a lowpass, but is it causing resonance? if so probably should take a closer look at the resonance table and see if i can make it, er, not do that :)
>>4641
On 28 July 09 build, there is definitely resonance at Z80. A filter sweep over a sine wave gives an increase in volume prior to decrease. Non-resonant filter on a sine wave should just reduce volume from the cutoff point (as it is in July 12 build).