yeah so like you know multichannel diskwrite so thingy yeah. i think this one goes best like this:
<distance> yay so like multichannel diskwrite automatic batch great woo
<distance> i'd currently pay a total of 33eur for it since thats all i have
<Storlek> dude
<Storlek> where did you get the idea that if you pay, i'll write it
<Storlek> yes, it'd be a nice feature to have but i'm just not the most apt person to write it :)
<distance> whered you get the idea i didnt just say that to 7 people on this channel at large?
<Storlek> i'd say best results would be attained from putting it on the board and cross linking to the post on the todo page in the wiki
<Storlek> and if you really want to pay for it, i can arrange a code bounty
<tarzeau> anyone going to http://www.fosdem.org/ ?
<Storlek> i'm going there right now
<Storlek> and now, i'm closing the window
<tarzeau> aha

• errordeveloper (n=errordev@78-86-1-110.zone2.bethere.co.uk) has joined #Schism

<distance> i cant concentrate enough to do it
<distance> it'd just get another smarmy answer from someone going YEAH WOTCH MEAN MAN YEAH LIKE DRAW US A DIAGRAM MAN YEAH YEAH SHUT UP
<Storlek> what.
<Storlek> sure, if you just post a message that says "i want multichannel disk write" and nothing else, you will get a "what are you talking about" response
<Storlek> because other people are not you
<Storlek> just a bit more detail is extremely helpful
<Storlek> "I want a multichannel diskwriter, such that it would be possible to press a key, give a directory name such as "output", and it would output a separate file for each channel in the song that isn't muted, writing e.g. channel 4's output to "output/04.wav"
<Storlek> "this could be done with the standard F10 screen by adding a button labeled "Multi"
<Storlek> "and if possible it would be nice to have a bit more information about the progress than the standard disk write, like an overall progress bar, list of each file written, and an animated chicken"

i think he summed it up perfec. this would be ridiculously amazing. i could literally take schismtracker wavefiles and punch them into logic at a studio im doin vocational training on, run them via preamps and try and filter them otherwise, and thus rpocess them at a go. it'd be freakin amazing.
!! totaly amazing.
others could get into doing loops or mixing with abletn live, and then theres the protools/audiomulch lot.

thisd be a really rather important thing!!! to suss out. its never been done before in impulsetracker format, itd be a MAJOR IMPROVEMENT (!!!)
*pure gold

If anyone is interested in a code bounty for this functionality, post a clean diff -u patch to this thread along with contact information.

... a couple more details:

• The bounty amount will be $50 USD, paid via PayPal.
• Bounty will be awarded to the first person who posts a clean patch with code deemed acceptable by the dev team. (And yes, this is quite subjective.)

I'd do it, but I can't figure out how to compile schism

>>355
It's the same as any other GNU/FSF app. Make sure you have SDL installed and:

./configure
make

Although for development I recommend:

./configure --enable-ludicrous-mode

Unless you're using Windows, in which case... get Linux? *shrug*

The whole 'diskwriter' interface was so not designed to write multiple files ... can't see any way to do this without going around the interface, but that will make it harder for the patch to get accepted :(

>>357
Hah. That's one of the reasons why nobody's done this yet.

Really, if the patch works and isn't absolutely hideous (i.e. mallocing huge chunks of stuff and not cleaning up, looks like something right from the IOCCC, etc.) we'll probably take it.

>>357

ever since save module/wav/etc were split to shift-f10 (wav+mid), F10 (s3m it etc), Shift-f10 has a very good place for multichannel diskwrite. its just another button, and what that button will do is, during the process of diskwriting, solo one channel, write that, solo next channel and write that. it might get a bit more complex when one would also have to take into consideration the effect of Wxx and so on, on other channels. obviously even if only one channel is "playing" (solo'd for recording purposes), Axx, Txx and Wxx effects should still be read from the other channels, and be in full effect. there are probably some other effects that go into this, but all it really is, is an automated method of solo-ing whilst diskwriting, so we end up with
module-chan01.wav
...
module-chan64.wav

in theory one parameter that would be good to have would be the limitation of diskwriting channel amounts, by inputting one number (i.e., shift-f10 multibatch diskwrite user saying "please only write up until channel 37" -> chan01.wav - chan37.wav and thats it.

i guess someone here might see the possibility of just diskwriting everything at one go instead of sequentially (but automated), but i wouldnt know how much that complexifies things.

Why not just write whatever channels aren't muted and leave it up to the user to set everything up with F11 beforehand? Not much sense writing a bunch of muted channels.

Also I think there's a way to get at the mixdown of each channel in succession while modplug is playing, and a tricky way to multi-diskwrite would be to fopen() all the active channels and stuff the file pointers in an array, then in the playback loop, run through each channel, grab its mixdown buffer, and feed it to the corresponding file. I don't think the filesystem would be too happy with having 64 open files simultaneously being fed some 50-100 megs of data apiece, but the only alternative I can think of is to go through all the active channels, internally solo each one, and render it to disk one at a time, and that's just icky because it'd have to essentially play the entire song 64 times.

>>363

it could - and should - allow for very nicely just running through the whole song one track at a time. a couple of minutes of that and it'd be done, and it'd save a lot of, muting and diskwriting.
it can be automated, and it will be wicked to be able to do that!

>>363

one other alternative would be to have "any key" in F11 in such a way that one could set wav01.wav to be for instance the first 5 channels, by hand - and then set wav02 to be channels6-10 or just do a cyclical number on it. then to diskwrite what has been tagged

>>365
Channel grouping? Erk.

>>366
just hardwriting all channels individually would b perfect

This is done. Current builds have a multichannel diskwriter. The UI is a bit funky, but it works, and is only marginally slower than the regular diskwriter.

It works like this:

Shift-F10, and enter the name of a directory.

Instead of an error message, schism will say "Multi-out?" and if you say yes, schism will dump all the wav files in there- one per channel.

NNA is kept on the same channel as its master.

Thank you! It works really well! I can now easily import it all back into ardour. One enhancement i'd like to see is that channels which use no panning be exported as mono files. I think it is already the case when exporting a song without using multi channel diskwrite.

Keep it up! Schism tracker is always getting better!

>>564

excellent work! we thank thee. now lets have me try it out and see what hapens! thank you:)

Multi-out now tries to downmix as many of the wav files to mono as possible.

Changing the panning, stereo samples, envelopes, etc will all prevent a file from being mono.

Seems it exports as mono when panning is not hard left or hard right. Hope you don't suffer too much from that lousy test song...