[big / cats / code / f / fw / j / m / ma / o / w / z] [sc / scdev] [wiki / schism] [iichan (wakachan) / 2ch.us]
[Burichan] [Futaba] [Photon] [Transmission] [Wiiabu] - [Home]

Spam trap (leave blank):
Name
Link
Subject
Comment
File
  • Supported file types are: JPG, PNG, GIF, MP3, M4A, AAC, OGG, IT, S3M, XM, MOD, ZIP, TAR, GZ, BZ2, TGZ, MID
  • Maximum file size allowed is 20480 KB.
  • Images greater than 250x250 pixels will be thumbnailed.
  • Protect your name; use a tripcode.
  • Thread Index

No.4129   [Reply]

Hi everyone!

Everytime I use SchismTracker on Windows, my CPU fan is working the whole time, and the Task manager shows that it uses about 95% of my CPU. I have a Pentium III with 1Ghz and 512mb RAM, should be enough, I guess...
The strange thing is that it plays back modules without stuttering, it just seems to take every bit of CPU it can get...

Does someone know how to fix this? And is this a Windows-exclusive? What about Linux?

Thank you!!

5 replies omitted. [View entire thread]
No.4197

It only uses a constant 50% on mine, and I think if I had four processors instead of two it would only use 25%. It doesn't seem to matter what video mode I choose. This will become a greater problem once I start using schism more on my laptop and am concerned about battery life, but I also intend to run linux on my new laptop, so in that case, it won't be a problem. It would be nice to get it to use only the CPU it needs in windows. I imagine it's probably an SDL issue.

No.4198

http://www.nabble.com/CPU-usage-td15360412.html

some interesting info about SDL poll, wait, and delay events. Like I know anything :P

No.4236

Thank you for your replies! I'm glad that it seems to be a windows-only thing :)

How is the performance on Linux, then? Jarod T. Cabrera, how much CPU does Schism Tracker consume when it's idle and when you play a "normal" module on your 350mhz system?

Thank you!

No.4237

>>4236

So long as you have a good Xv support- that is, a graphics card/driver that supports an overlay at least 1280x400 (as indicated by the maximum XvImage size in xvinfo) and your alsa driver doesn't require any emulation, then it's usually using around 3% when playing (at least on my system).

No.4262

Any update on this?

It seems to be purely a Windows issue where schism constantly pegs the cpu usage; not to say it doesn't share with other apps just fine, but really causes a lot of unnecessary heat and battery usage. Other sdl apps don't seem to have this issue.



No.82   [Reply]

Very nice tracker! ;D thanks for the effort!!  

10 replies omitted. [View entire thread]
No.246

>>245

> it's strange because. only left alt + enter = fullscreen, not right alt + enter

Does right alt work for any other keys? It's probably that your keymap is set up so that right alt is actually AltGr or some other modifier.

No.269

Wonderfull tracker! Never been much into impulse tracker before, but now that you gave me the chance to run "it" on Linux I'm now completely sold. I now know what I missed using other trackers. :D

Thanks a million!

No.272

Hehe, just imagine what it's like with everything actually working :D

No.4260

this is amazing indeed :}}}}

No.4261

Schism tracker is amazing! THANK YOU FOR SCHISM TRACKER!!!



File: Test1.mid -(2 kb) 
2 kb No.4257   [Reply]

When exporting to MIDI, the bank settings don't appear to work. I know some of the MIDI stuff works already, but this function does not appear to work.

When played on Quicktime, the Saw Wave is supposed to sound like the one played at Program 82 (81 in Schism Tracker), and Bank Select MSB 1 (0 in Schism Tracker).

No.4258

Whoops, let me revise that:

When played on Quicktime, the Saw Wave is supposed to sound like the one played at Program 82 (81 in Schism Tracker), and Bank Select MSB 1 (1 in Schism Tracker?).

No.4259

Did you put something useful in the Bank Select in the MIDI output page?

Try something like:

Bc 00 a Bc 20 b

in the bank select field on the MIDI output configuration.



No.4249   [Reply]

posting is broken!

2 replies omitted. [View entire thread]
No.4252

>>4251
I bet you're using Firefox.

Apparently there's some problem between lighttpd and Firefox, and nobody wants to actually fix it. I don't know.

No.4253

(hint: click the refresh button)

No.4254

nothing happens here? :o

No.4255

>>4254
first post in june
>>4255
first post in july

whats with the 'report anonymous statistics to developers' in the autopackage installation?

what is send if chosen to?

No.4256

>>4255

I think it goes here:

http://autopackage.org/statistics/display.php?table=version&action=View&rid=250

which isn't that interesting, because I don't think anyone submits statistics.



No.4245   [Reply]

hi im in a right pickle, need todeliver my tune out to a netlabel, but whenever i diskwrite the wavefile, it comes out as 48khz. ive changed every config file i have to 44100 ssamplingrate but schism just doesnt listen to it. please help, what can i do
please.
i cant go to a mates mac (the studio keys are hundreds of kilometers away from where the studio is, currently) and diskwrite it as wave, i have no idea what to do. please help. surely there must be a way of getting a 44.1khz wavefile out of a tune!??!?!

No.4246

>>4245

ctrl-f11 says 44100hz 16bit stereo
then if i diskwrite the tune to wavefile with shift-f10,
it hard-defaults to 48khz. i cant transcode from 48khz to 44.1khz because itll start sounding really fucking muddy. what can i do PLEASE

No.4247

Edit your config file. It presently says:

[Diskwriter]
rate=48000
No.4248

An old version defaulted to that. Edit your config file.



No.4238   [Reply]

Helo! I had to replace my cpu/mobo, and my older debian didn't manage to boot up correctly on this "new" dual processor system (2x p3 650 muhaha).
So I installed a clear stable debian etch. I noticed that I cant install schism, the c library comes with etch is too old, so I dist-upgraded to testing version lenny. Okay, now autopackage installs schism fine, but when I set any midi port to output, and try to send an event out, schism stops, and says this:
schismtracker: ../schism/midi-core.c:776: midi_send_buffer: Assertion `((unsigned)pos) < ((unsigned)qlen)' failed.
any suggestions what to do? is this my systems fault?

No.4239

oh sorry... I had the same problem before, I try to increase buffer size, once it worked

No.4240

erm... okay it doesnt stop now but still not at a stable tempo :\

No.4243

How are you testing a stable tempo? Are you using arecordmidi or timidity or some real midi gear?

No.4244

just connecting another pc and listening to the sotsynth running on. Its conspicouos enough. If I send events from a midi keyboard to the same stuff, that works fine. (and it worked fine with another midi tracker)



No.4241   [Reply]

that's all I am saying

No.4242

renoise fucked up me... I didn't like the way to sort/manage patterns. But if i cant make schism's midi out work fine, I'll have to use renoise or other stuff (last enter festival ["festival"] i used cheese or what, I was almost the end of my music when I realized that there's only about 27 patterns to use, sorry, beta or wtf...)



No.4230   [Reply]

-To add latency (miliseconds) for each midi ouput.
-That could select a different midi ouput for each instrument.

No.4231
File: 1207207068518548.jpg -(198 kb, 806x625)  198 kb, 806x625
No.4232
File: 12072071243814249.jpg -(196 kb, 806x625)  196 kb, 806x625
No.4233

The file formats won't save site-specific information; It reduces shareability and interchange.

We could add latency to each output (however) fairly easily. I don't presently save selected output configuration because I wasn't aware it was stable enough to do so, so we'd probably want to do that first. Are there any reports of the MIDI page freezing users?

But why do you want to select hardware connections per instrument? Is it just because there aren't enough midi channels?

Or are you trying to connect to "midi devices" that are too stupid to select the channels/programs they want (like VSTs)?

No.4234

The idea is works with an instruments Vst and devices midi simultaneously (KORG, YAMAHA, etc.).

The problem that I have is with the synchronization midi and audio, since the audio of the Schism tracker has one small latency with regard to a device midi, because of it it of the latency.

No.4235

>>4234

Your KORG or YAMAHA synth should be able to select on specific channels. If you're using VSTs, you might be able to use an extra level of indirection in the meantime.

If we add it to the instruments: you wouldn't be able to save it and would have to re-enter the bindings every time you load a module. That is, until a schism-tracker module format shows up...

However I agree we need to add latency to the midi devices and will work on adding that soon...



File: schism-midi-export.zip -(4 kb) 
4 kb No.4229   [Reply]

MIDI file export has improved somewhat with today's build. It's still got some issues, but it's producing some pretty good results so far.



File: 1205014330661361.jpg -(56 kb, 400x300) 
56 kb, 400x300 No.4200   [Reply]

Look what have we done in Skale Tracker using small vst libs. It is a musicdisk with a shell only 7 Mb size.
Why don't add some simple build-in effects into Schism? Reverb, delay, chorus, EQ and compressor would be very useful.

6 replies omitted. [View entire thread]
No.4208

agree with esaruoho.
first get midi working. If midi works better, you can use any midi-capable thing to do what you want. if you want to use samples with effects, you can use a sampler with any effect. but you are still welcome to use native synths or any external sound device.dot.

No.4224

>>4208

yeah, unfortunately at least on my win32, even sending one midinote per row, the notes are not sent stably.. they are sent, but it is more like a shuffle gone awry, theres no way for me to place notes so that they are sent in an even way so that they continuously stay in rhythm.
hence why i cant use schism for anything:)

No.4226

same thing for me... even win or linux, shuffle. Once it was explained its becouse sample handling or what.

No.4227

Actually, the sound effects could be the real composing tool, not just "postprocessing". For example, composing an electronic music, it would be quite strange to track an arpeggio without delays and leave the delays "for postprocessing". So, the basic effects are strongly needed things on the composing stage.

No.4228

MIDI output is fine on Linux/ALSA. If it isn't on your system try adjusting your audio buffersize making it bigger or smaller. Having too large a buffer means schism requires a more sensitive and more accurate timer. MIDI output on MacOSX should be about the same.

MIDI output on Unix/OSS is probably never going to work unless you're running nice -19 or something.

MIDI output on Windows is another story...



[]
Previous [0] [1] [2] [3] [4] [5] [6] [7] [8] [9]