If you're extending it I'll make the effort to submit something.

I don't usually look at the vote files until right before I calculate them, to help keep my own unbiased.

but not with the right file.. :(

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.

No-one.. It was hypothetical...

>>4730

Well there you go... :P

>(Note that sample packs are saved as compressed IT files; if you re-save as uncompressed IT, that's roughly the upper limit.)

Like i said, i don't care. but someone might.

i'm not asking for the entry to be disqualified, i was just pointing out that it "broke the rules:

But, pointing out the rules for those that didn't read them :)

> Maximum entry size is 1 MB (1048576 bytes) or the total size in bytes of the raw data within the samplepack, whichever is larger.

Regardless of how it was saved, if it's over that size I think that means it's too big.

Though it seems that the only reason it's so big is because it's got duplicates of the samples instead of mapping the different instruments to the same samples. I dunno about anyone else, but I would let that one go.

cough 1 mb limit cough

>>4719
Mulitple songs by the same person allowed? Interesting. I'm not complaining, it's just unusual.

Lucky you got "some proper time to compose"

^_^

But I had to borrow work's netbook for the evening and I came up with a nice idea on the bus. :D

I was just thinking yesterday that an orchestral sample pack would be a great challenge.

This is even better.

Oh yeah... I hate you.

:)

Also LOL sample pack. Not as bad as your all cymbals idea from way back at least ;)

I suppose 1/5th is ok... :P

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)

I like to use the link because that way when I update the pattern, it automatically updates the sample.

he's already made short music :)

"Can we have a sonmg that's under 50 minutes, this time,please."

:P

I suppose, as long as it's derived from the same data.

Ctrl-B            Link (diskwriter) this pattern to the current sample
Ctrl-O            Copy (diskwriter) this pattern to the current sample

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.. :)

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)

puts feet up

:0

jesus...

Interested to see how I go..

It's not very "sceney", if you catch my drift..

1. what is insert? on a laptop keyboard, in f2 pattern editor? i.e. currently i can use "." to delete a note on cursor, but cannot actually do an insert. how would i find this, please?

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!

Comment too long; full version here.

If you've got the X headers (not just the SDL headers) schism will include X11 clipboard support.

>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.

Perhaps a good visual indicator would be in the status text flash area:

• Will save in IT format
• Will save in S3M format

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:

• Warning: Will be saving in S3M format
• Warning: Will be saving in IT format

> Opening /wherever/is/file.0 for writing
> Starting up diskwriter
> Diskwriter completed successfully

with 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.

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.

That was very similar to the behavior of the "AUTO" button that >>4437 described, that was removed at >>4441

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.

Apparantley there were six entries... half the number than what I usually see. Oh well, that's OK. ^_^

>>4662
Well the point (for me) is to get patterns in some kind of text-based, somewhat-human-readable format. But actually it would be a big plus to be able to do that with individual patterns.

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.

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..

I think i just posted it on the wrong board —>

http://sovietrussia.org/scdev/res/714.html

... looks like it's gonna be for next bi-week =)

I guess it would be worthwhile for me to actually learn how to use hg properly.

>if you're also doing individual entries

That's the part I was curious about. Thanks.