Mac OSX Bug Report
BUG: When I tried to put the program into full screen, the window went away and stopped responding, if you force stop the program and restart it, then it will try to go into fullscreen and then it will not have any windows displayed and it will be frozen. If you go to the window bar the rainbow pinwheel beachball, whatever you want to call it, comes up and you can't click on any of the drop-down menus. Deleting and reinstalling the program doesn't help.
Please help, email me at gmorr3@sbcglobal.net
Mac OSX Bug Report
BUG: When I tried to put the program into full screen, the window went away and stopped responding, if you force stop the program and restart it, then it will try to go into fullscreen and then it will not have any windows displayed and it will be frozen. If you go to the window bar the rainbow pinwheel beachball, whatever you want to call it, comes up and you can't click on any of the drop-down menus. Deleting and reinstalling the program doesn't help.
Please help, email me at gmorr3@sbcglobal.net
When loading a file, schism seems to think that blank instrument slots before the highest numbered instrument aren't really blank. Any time you load a sample in instrument mode and select "Create new instrument", and the corresponding instrument slot isn't the highest numbered instrument, the instrument will get created after the highest numbered one.
I don't feel like I'm being very clear, so as an example here's a file with samples and instruments in slots 01 and 20. Loading a sample in slot 02-19 will create an instrument in slot 21. This will hold true even if you delete the instrument in slot 20 and save/reload the file (well actually it goes in slot 20 since that one got deleted properly).
Mac OSX Bug Report
BUG: When it tried to put the program into full screen, the window went away and stopped responding, if you force stop the program and restart it, then it will try to go into fullscreen and then it will not have any windows displayed and it will be frozen. If you go to the window bar the rainbow pinwheel beachball, whatever you want to call it, comes up and you can't click on any of the drop-down menus. Deleting and reinstalling the program doesn't help.
Please help, email me at gmorr3@sbcglobal.net
I remember what was apparently 2 years ago, rendering my piece for 8bitcollective's "chinese whimpers" (chinese whispers vol 2), and noticing that the bass clicks quite horribly.
IT 2.12's diskwriter introduced a simple anticlick. My implementation of it is as follows:
Getting rid of these clicks in Schism Tracker can actually be achieved by much easier means than implementing a completely new anti-click mechanism.
Instead of setting the channel length to 0, you should set the fadeout volume to 0 and enable the CHN_FADEOUT flag. It has the same effect (i.e. volume commands can't "pick up" a note after it has been cut), but it avoids the clicks.
Hey GreaseMonkey, where did you get the stats on IT 2.12's volume ramping and anticlick? I tried Googling it but couldn't find nothing.. :-/
Mac OSX Bug Report
BUG: When it tried to put the program into full screen, the window went away and stopped responding, if you force stop the program and restart it, then it will try to go into fullscreen and then it will not have any windows displayed and it will be frozen. If you go to the window bar the rainbow pinwheel beachball, whatever you want to call it, comes up and you can't click on any of the drop-down menus. Deleting and reinstalling the program doesn't help.
Please help, email me at gmorr3@sbcglobal.net
In http://inai.de/scdev/ , you will find an S3M file, and how schismtracker-20120105 and the XMP player render it to WAV (encoded to ogg for small downloads).
Playback the S3M with schismtracker and set channel 1 to solo mode. In order 2+ (pattern 4), you will notice that schismtracker does sort of "glottal stops" when the instrument is invoked anew. XMP does not seem to do this, but which implementation is right?
In fact, this is a MOD file, renamed to S3M. SchismTracker seems to use a wrong period to frequency conversion table. I don't remember the gory details, but it has something to do with PAL vs NTSC timing.
Mac OSX Bug Report
BUG: When it tried to put the program into full screen, the window went away and stopped responding, if you force stop the program and restart it, then it will try to go into fullscreen and then it will not have any windows displayed and it will be frozen. If you go to the window bar the rainbow pinwheel beachball, whatever you want to call it, comes up and you can't click on any of the drop-down menus. Deleting and reinstalling the program doesn't help.
Please help, email me at gmorr3@sbcglobal.net
Finally, this bug shall be fixed.
On Schism Tracker 20120105 built Jan 19 2013 11:14:14.
Compiled using the following commands:
./configure
make
make check
make install
In song "Panic by Future Crew". Downloaded from scene.org.
In order 5/53 pattern #6 at channel 7.
A very high frequency beep occurs.
But when I play this song on a mod decoder (some kind of lib), the beep sound is gone.
Confirming that the s3m sounds quite different in ST3 or IT from Schism.
In IT the (Amiga) F80 slides cause the note frequency to quickly go past the point where IT just cuts the note off instead. Schism doesn't seem to have a point like this, so you get some crazy aliased noise instead.
I recently got into this in Psycle and after looking into the problem, I found that it is documented:
This is from Impulse Tracker doc:
Fxx Pitch Slide up
FFx Fine Pitch slide up
FEx Extra fine pitch slide up Operates in the same manner as the Exx commands, but
slides the pitch up. If the pitch gets 'too high', then
the channel is turned off."Too high" means that the (amiga) period goes below 1. (Since a period 0 has no meaning and periods are integer values in these trackers). I am unsure what the effect is with linear slides, but the same logic might apply.
With linear slides, Impulse Tracker continues pitch slides into infinity (well, probably until it wraps around or maybe there is an insanely high limit), but with Amiga slides it should indeed stop.
Mac OSX Bug Report
BUG: When it tried to put the program into full screen, the window went away and stopped responding, if you force stop the program and restart it, then it will try to go into fullscreen and then it will not have any windows displayed and it will be frozen. If you go to the window bar the rainbow pinwheel beachball, whatever you want to call it, comes up and you can't click on any of the drop-down menus. Deleting and reinstalling the program doesn't help.
Please help, email me at gmorr3@sbcglobal.net
Hello,
Some channels (percussion) are not played.
At first, I thought this is bug #1551
http://schismtracker.org/scdev/res/1551.html
But I cannot apply the patch posted and so I cannot confirm this is the same bug.
I did hg bisect:
$ hg bisect -g
The first bad revision is:
changeset: 2871:cf8f327d96d2
user: Storlek <storlek@rigelseven.com>
Sorry. Ignore 1715. This IS bug 1551. I finaly were able to apply the patch.
Mac OSX Bug Report
BUG: When it tried to put the program into full screen, the window went away and stopped responding, if you force stop the program and restart it, then it will try to go into fullscreen and then it will not have any windows displayed and it will be frozen. If you go to the window bar the rainbow pinwheel beachball, whatever you want to call it, comes up and you can't click on any of the drop-down menus. Deleting and reinstalling the program doesn't help.
Please help, email me at gmorr3@sbcglobal.net
You are probably very well aware of this, but since there are actually applications out there that can write IT-compressed stereo samples now (munch.py and OpenMPT), it should be pointed out that Schism Tracker only loads the left channel of such samples.
Here's a minor bug: if multichannel playback is enabled (F3/F4, Alt-N), entering an instrument or sample name will increase the playback channel whenever a key that would play a note is pressed, even though no note actually plays.
Confirmed. Strange!
CTRL-PgUp (Move to top of pattern) has no effect. PgUp (on its own) and CTRL-PgDn work as expected.
Version 20120105 running on Windows 7
German keyboard layout (tried with US int., no change)
I can be reached at #schism on FreeNode for further tests/information.
Page up/down keys work perfectly with all combinations of control/alt/shift on my computer, and I'm running the same version. Only difference is I have a US keyboard.
I swear I've heard this same bug before somewhere, but I can't for my life remember how it was resolved.
