For some reason the IT does stretch on my screen somewhat. I was using this version off pouet - http://www.pouet.net/prod.php?which=13366
Maybe it doesn't have the patch 3? I better look around and make sure I have the right version.

Reason is I might be writing a co-op with someone who uses Schism, and if I end up using old IT I need to make sure we can trade the file back and forth :)

The schismtracker.exe file is linked to missing export SHELL32.DLL:SHGetFolderPathW

Same error with Sunvox too :(

I wonder if it would be possible to download a newer version of the shell32.dll and put it in the Schism path?

Oh well, at least Impulse Tracker works so it's not really that much of a problem. :) Now to setup all that emm386.exe stuff, since I got about 20 "out of memory" errors when trying to load CHRIS31B.IT :P

Also, Are files saved with Schism backwards compatible with the actual Impulse Tracker program?

Thanks!

schism is open source software, so it can never be "no longer developed", but merely dormant. at least one patch was posted on >>>/scdev/ just days ago, which at some point will get merged into the repository - when I have a day off that I'm not already putting toward catching up on accumulated days of lost sleep, out of town for some other obligation, or visiting family which I rarely see.

those other comments in that article do hurt slightly... :/

When I become a billionaire I'm hiring a team of coders to work on Schism! I swear!

Is it true?!?! :(

But, it would be nice if full screen mode worked. For now I will just maximize the window.

As far as I know, I'm using 16-bit samples, but I'll check again. I'll have the opportunity to test Schismtracker on a friend's computer soon (also a Mac) to see whether it's related to my machine.

Any other ideas why this could be happening?

There is at least one circumstance that may make the sample not load... one of them would be that the sample is 24 or 32 bits, where Schism Tracker perhaps may only take 16 bits

I'm unable to load .Wav samples on OSX 10.5.8. (Using some samples from Mad Tracker and other sources). I can select the sample in the window, but I can't actually load it, much less create an instrument.

I've read through a couple other threads on this topic, but it seems that this was a bug that was considered fixed for most other users. Could this be a persistent bug related to my build? Is there something else I should try?

Forgive me if I'm asking a dumb question. I'm new to tracking, but I've spent several hours tooling around in the interface and reading manuals so I don't think I'm doing anything egregiously wrong.

Thanks so much,

Try deleting your config file? %APPDATA%\Schism Tracker\config.ini in Windows.

If that doesn't work then I have no idea.

I was running a 2010 build, and just now noticed there's a newer 20120115 build or something about a year old for Mac OS X. So I got that, same problem. So now I'm forced to run it in windows mode...

Anyone got any ideas how to resolve this? Also why no updates in a year? :(

In pattern mode, selecting a block and pressing Ctrl-K will vary the effect value, if the cursor is on a row with a panning (Xxx) effect, and only for panning effects in the block.

Otherwise it seems to do nothing?

The cursor being on a panning effect seems suspect...

palette_cur=...FFFeeessskkkVVVhhhNNNHHHZZZmmmPPPccczzzFFFBBB

It feels somehow wrong at first too, but I got used to it. Also it's good as a starting template, I think: just add a bit of color here and there and voilà!

• Complexity: Trivial
• Priority: Normal
• Screen: Sample List
• Status: Accepted

I'd do it, but I can't figure out how to compile Schism on Mac OS X 10.7.5 yet.. :( Or under Windows 8 :(.. haha..

p.s. setting up what program is called could be done via some simple text/ini/config file I guess... :)

Looks like you do not need this patch anyway:

$ cd schismtracker/
$ patch -p1 < dw-crash.patch
patching file effects.c
Reversed (or previously applied) patch detected!  Assume -R? [n] n
Apply anyway? [n] n
Skipping patch.
1 out of 1 hunk ignored

cd some_dir
patch -p 0 < /path/to/patchfile.patch
cd main_source_dir
./configure
make

and then make install or whatever. (You can actually just do ./configure && make && make check && make install and it will do its thing as long as no errors occur.)

The key is that you might have to cd into a different directory and/or use a different number for p.

For example if you look at the patch to fix volume envelopes from http://schismtracker.org/scdev/res/1551.html#1567 you see the first two lines read
--- sndmix.c 2012-04-13 01:26:58.733534622 +0400

Comment too long; full version here.

I just do this on compilation:
./configure
make
make check
sudo make install

I installed the latest version of schism tracker.

Also see these threads: http://schismtracker.org/sc/res/5924.html and http://schismtracker.org/sc/res/5703.html

>>5813 Schism without X is a bit flaky. Try editing ~/.schism/config and changing the video driver (under the [Video] section) to different values of yuv / sdl / opengl to see if that does anything.

>>5955 Edit ~/.schism/config and try changing the buffer size. If that doesn't work, try adding the line driver=alsa:default:0 under the [Audio] section. (Does Raspberry Pi use ALSA?) the audio driver accepts a bunch of arcane entries, I'm not sure what other options to try.

>>5956 what happens if you select in terminal? or just execute it?

>>5957 Nothing happens at all? No error messages or anything? Which schismtracker version are you using?

anyone have any ideas - would it be because I'm runny the wheezy version of Debian possibly?

> It would be MUCH easier if it mentions what part
> is altered. Like "Font color", "background editor" etc.,

Ultimately, i'd simply have a separate color for everything, even different fields on the pattern editor. That's one of the reasons i like 12-channels view (and 10-ch) a lot :D

Remember, we're sort of "emulating" IT's 80x50 vga textmode, but we're not limited to it - and we have already gone beyond 80x50 textmode limitations before (for ex. envelope drawings on inst. list)

(and yeah, IT's original default colors sucked ass.... that bright cyan-blue if anyone remembers)

> what part is altered

That's actually documented. ........ somewhere

I do not remember where, but there's a list somewhere of which color does what, I swear.

You can try schismtracker -a waveout, but that driver is incredibly laggy on my system to the point of being practically useless, and I don't think it even honors the buffer size settings. I don't think SDL supports anything else, either.

Can you work around it? What is it you want to do from running two Schism Tracker instances?

Guess i updated aptitude a little late.

Thanks for Schism, and the tracks bundled with the Pi version are very good! Especially "Secretly Wishing" and "Get that Goblin!!!"

EJ

thanks for your efforts and answers!

Yes, that must be it.
If i can find the toolchain for Raspbian, i'll give it a go.

I'll tell the MagPi mag about this, there is going to be another article on Schism.

Thanks!

> this may be a soft float build and would therefore not work on Raspbian, which is a hard float abi

If you can, you might want to try building it yourself - not sure how much effort that entails, though. (It shouldn't take much tweaking, if any.)

the RasPi flavour of the tracker gives a "bus error" on RaspBian and Occidentalis, haven't tried other distros.

I got the tracker from a link in the MagPi online magazine:
http://goo.gl/aw1eA

It's only a drop-boox URL.
Who built this instance i don't know, i contacted the MagPi mag but they do not seem to be involved.

Anyone know more about this?

>>5910 timestamps would be nice though.

<THIS IS A HINT>
It would be MUCH easier if it mentions what part is altered. Like "Font color", "background editor" etc.,
</THIS IS A HINT>

<THIS IS A FACT>
I have tracked since 1996, and tried palleting since Bob Ross made the Happy Tree theme, which never made it to any version of Impulse Tracker. Jeffrey Lim disliked it only becuase Australia is one big desert. NO TREES. Since then I tried reinventing the theme. GODDAMNIT BOB ROSS TOOK THIS PALLETTE CONFIGURATION INTO THE GRAVE
</THIS IS A FACT>

>Schism uses some of the colors for different places simultaneously (Like, for background here, for text there and for highlighting over there), and it makes very hard to tune palette for something pleasing.

This has been my problem literally every time I try a user-defined palette. I have not ever succeeded in making one I like, despite trying about once a year since 1997.

Schism uses some of the colors for different places simultaneously (Like, for background here, for text there and for highlighting over there), and it makes very hard to tune palette for something pleasing.

This insight came about partly from playing around with sc's board look styles. I was using the default(?) of Headline for a while but recently I've switched to Mercury, which I think is a little nicer (and not too anime).

Anyone got any favourites?

Also I wouldn't worry about breaking up the old thread.

In the meantime here's a link to a temp votepack that has all the entries and some basic vote instructions, though you are encouraged to wait for the full posting including source files, author descriptions, etc., which should be up Wednesday(?).

http://compo.quikphix.org/bonus1/hcbonus1_tmp.zip (31 M)

Exception raised when the relational integrity of the database is affected, e.g. a foreign key check fails, duplicate key, etc.

Duplicate entry '25-1' for key 1

(I tried posting two more tests, and it changed to 25-2 and 25-3 subsequently)

The neat advantage of this is that with the config of the new board, the links for "last 50 posts" etc. actually work, which is nice for a big long thread like that one. I could also break the thread into multiple pieces, but I'm not sure where to split it. Each new round?