[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.548   [Reply]

No, unfortunately. But I have made differently.

In xkb.c :

#ifdef HAVE_X11_EXTENSIONS_XKB_H
#include <X11/XKBlib.h>
#endif
....
....
#ifdef HAVE_X11_EXTENSIONS_XKB_H
static XkbDescPtr us_kb_map;
#endif

and next step:

Comment too long. Click here to view the full text.

5 replies and 1 file omitted. [View entire thread]
… No.554

>>553
Whoops, should've been four spaces in there... HTML ate them. Foiled again!

… No.555

>>548 I understand well enough. Added to CVS.

I'll update the builds later today; when they update, please download and let us know if they will compile cleanly for you.

… No.556

Compilation has passed successfully! Thanks! Also I corrected symbolical references:
INSTALL
/usr/share/automake-1.9/INSTALL -> /usr/local/share/automake-1.4/INSTALL
(Strange. In automake 1.9 it was not possible to find INSTALL it was necessary to use the old version)

config.guess
/usr/share/automake-1.9/config.guess -> /usr/local/share/automake-1.9/config.guess

..etc (config.sub, depcomp, install-sh, missing) add "../local/.."

… No.558

Those files really shouldn't be links anyway. That's a debianism.

… No.560

>>558

I modified autogen.sh to copy instead of symlink. That should help.


No.557   [Reply]

If you do not object, I can translate the documentation on Russian.

… No.559

Go for it! Preferably, put it on the wiki, under the Schism: namespace. It might even prompt us to bother finishing the task of wikifying the English docs :P


No.536   [Reply]

I try to compile CVS ver. on FreeBSD 6.3

  1. Has corrected symbolical references to utilities automake (INSTALL, install-sh, etc) as they did not work in my system.
  2. A mistake at compilation:

code:
.....deps/xkb.Tpo -c -o xkb.o test -f 'sys/x11/xkb.c' || echo './'sys/x11/xkb.c
sys/x11/xkb.c: In function `_key_info_setup':
sys/x11/xkb.c:91: error: `us_kb_map' undeclared (first use in this function)
sys/x11/xkb.c:91: error: (Each undeclared identifier is reported only once
sys/x11/xkb.c:91: error: for each function it appears in.)
sys/x11/xkb.c: In function `key_scancode_lookup':
sys/x11/xkb.c:143: error: `us_kb_map' undeclared (first use in this function)
*** Error code 1

2 replies and 1 file omitted. [View entire thread]
… No.541

>>540

conftest.c:79:32: X11/extensions/XKB.h: No such file or directory

Is there an XKB.h on your system? Can you run locate -i xkb.h and perhaps do some digging?

Without xkb support, FreeBSD users with non-US or non-qwerty keyboards/layouts will have great difficulty using schismtracker...

… No.544

>>541
Schism certainly doesn't work with a dvorak keyboard, are you saying it would be worse without xkb?

… No.545

>>Can you run locate -i xkb.h and perhaps do some digging?

Yes:
===========
[nau@buddha ~]locate -i xkb.h
/usr/local/include/X11/extensions/XKB.h
============

>>will have great difficulty using >>schismtracker...

All hotkeys which has had time to check up work, in the pattern editor too all is good.

Comment too long. Click here to view the full text.

… No.546

>>545 Ah I see it's in /usr/local/ I'll see about fixing this up later...

… No.547

>>545

If you run configure as:

./configure --x-includes=/usr/local/include

does it build correctly?


No.533   [Reply]
  1. At start of the program (parameters standard, it is used SDL), loading on CPU> 80 %! The Configuration of mine PC: Celeron 2.7/2Gb/GeForce PCI 6600/Sound onboard (HD Realtek 5.1)/Win XP SP2.
… No.534

2. At end of the program the established parameters (a palette, system preferences, etc) are not kept. At following start of the program I see adjustments by default. Win XP, Schism - CVS latest bild ver.

… No.542

>>534

You have to push the save/settings button in order for your preferences to be saved.

… No.543

>>533

You didn't mention if you tried any other video drivers (Ctrl-F1), or if you were in fullscreen, or if you used any programs like ASIO4ALL.


No.535   [Reply]

DUMB engine (http://dumb.sourceforge.net/) was created w/the purpose of sounding as close to impulse tracker as possible. if the license doesn't conflict maybe try that instead of modplug engine?

… No.537

Dumb is actually a worse choice than Modplug, as Modplug is mostly intended to be a player library, but also is used for a tracker; Dumb is just a player, so it would likely require extensive modifications beyond the magnitude of those initially needed to fit Modplug into the program.

We've made a large number of changes to Modplug's engine with the purpose of improving IT compatibility, and Schism plays IT files significantly better than Modplug or Mikmod. Also, a while back some work was put into a replacement engine written specifically for Schism Tracker:
http://schismtracker.cvs.sourceforge.net/schismtracker/pm/
The main goals for pm are to be bug-compatible with IT playback, efficient, and written cleanly (i.e. no hacks). In theory when pm is working right, it should be possible to drop the whole Modplug directory from the source, cut out all Modplug references, and replace them with code in pm.
Unfortunately it's been sitting there for a long time and hasn't had much attention since it was first committed to cvs, so I don't think it's altogether likely that it's going to be replacing Modplug any time soon :(

… No.538

DUMB may have been created with the purpose of sounding close to Impulse Tracker, it doesn't succeed very well; the hacked up modplug in schism sounds more like Impulse Tracker than DUMB does.

DUMB is also not under active development.


No.530   [Reply]

Schism hangs when there is a large file in the directory it's started from... It's a problem because I've got a large slackware drive image in my home directory. Can't it be optimised?

… No.531

There is something wrong with your computer. Schism mmap()s all the files, but it doesn't touch all the pages. I have several large disk images in my home directory and schism has no problems.

Try using strace -p to find out what schism is doing on your system.

… No.532

>>530
What OS are you using?


No.529   [Reply]

hi i think it would be great to have an automatic multibatchdiskwrite that diskwrites all 64 channels of the song to songname_chn01.wav songname_chn02.wav songname_chn03.wav ... songname_chn64.wav
this would be exemplary.


No.524   [Reply]

hi. on win32 version the track length calculation is completely utterly broken.
build is 9th may
the results are like 444994594534:4350495:43535404350 its dcompletely hopeless :(
please fix

… No.525

This isn't happening to me; I'm running schismtracker.exe under wine.

Can you upload the errant module?

… No.526

>>525

EVERY SINGLE MODULE I LOAD, BE IT .S3M, .IT OR .MOD SHOWS THIS PROBLEM. THE MODULES HAVE BEEN MADE WITH SCHISMTRACKER, SCREAMTRACKER, FASTTRACKER AND THEY ALL GIVE COMPLETELY FUCKED UP TRACKLENGTHS ON WIN32, NOT ON LINUX.
THEREFORE IT IS OF NO CONSEQUENCE WHICH SONG I GIVE TO YOU WHEN EVERY SINGLE SONG BUGS.

NEVERMIND, DONT FIX IT.

… No.527
File: 12128814761018751.jpg -(53 kb, 750x600)  53 kb, 750x600
… No.528

Fixed in CVS.

Windows sucks.

Film at 11.


File: jeffm3.it -(10 kb) 
10 kb No.521   [Reply]
… No.522
File: jeffm3_it.mid -(10 kb)  10 kb
… No.523
File: jeffm3_schism.mid -(14 kb)  14 kb

No.501   [Reply]

As has been stated a couple times here and there, Schism Tracker would be greatly benefit from a scripting language. This would make the following much easier to implement, more robust, or otherwise generally much better:

General considerations, roughly in order of most important to least:

  1. How widely supported is the language? If it only runs on Linux, it's not much use.
  2. How hard is it to use within C code? Adding a thousand lines of code just to move data structures back and forth nullifies most of the benefits of moving the code away from C.
  3. How fast is it? Considering the target here is a media application, a language that can't keep up with itself sucking lots of processor time isn't very useful.

Comment too long. Click here to view the full text.

7 replies omitted. [View entire thread]
… No.516

>>513

What point?

> The trouble is that you can't easily tell just by looking at (f x) how to interpret it.

This point?

I was saying that I think Amit's thesis is mistaken. Non-programmers don't interpret (hence many of JavaScript's problems), they just copy what they like and fudge it about a bit. Python programmers seem very upset when Lisp programmers not only tell them that they don't interpret it either, but that you don't have to worry about it either.

Lisp isn't a good language for dealing with the smallest, most indivisible things, but for dealing with big-picture stuff.

Comment too long. Click here to view the full text.

… No.517

>>516

> Lisp seems to be optimized for writing code; Python seems to be optimized for reading it.

> there is no answer that will be right for everyone

and

> I have a bias towards the people who view these things as tradeoffs and a bias against the people who say there's only one right answer and everyone else is stupid or clueless. This has sadly pushed me away from Lisp, the Mac, and other systems that I think are really good but have fanatical communities.

… No.518

>>517

> > Lisp seems to be optimized for writing code; Python seems to be optimized for reading it.

I disagree.

I think that if you're used to reading Java, C, or Lua, it's probably easier for you to read python than lisp. This has to do with the fact they form their data-model of code similarly, not because their syntax is similar.

Likewise, if you're used to reading forth, reading postscript or factor is a small step.

However, I think that if you don't know how to read any of these- that is, if you're a nonprogrammer, then lisp is probably easiest simply because there is simply less of it to read.

Comment too long. Click here to view the full text.

… No.519

By the way, I think the console should be much more line/oriented though. Especially by default. It would be a great place to put configuration and commands that don't have any ui (or even if they do!)

That is, even we did use lisp, it should work more like zwei or autocad's console and feel more like basic for entry, than like lisp.

… No.520

I was thinking we could extend the status line with Ctrl-D for inputting the more esoteric commands – Schism's M-x key, so to speak. The console log was originally intended to be where Impulse Tracker's fancy file saving status output went – such as the S3M warnings and so forth. That it turned into a generic debug log was purely accidental. In any case, I think keeping the input separated would be a good idea; that way you don't have to switch screens to enter commands, which has several advantages, not the least of which is you can manipulate the GUI in-context.

> I think that if you're used to reading Java, C, or Lua,

Or English, to some extent. Generally speaking, natural language isn't list-based.

and, I certainly don't think the other person in this thread is stupid; just a bit smug, and biased toward parentheses and cudders ;)


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

- matsuba + wakaba + futaba -