lsc
/
intro-synths
mirror of https://gitlab.com/PoroCYon/4klang-linux.git
2
0
Fork 0
Code Issues 0 Releases 0 Wiki Activity
4klang, Clinkster, Oidos and V2 on Linux template code
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
24 Commits
1 Branch
2.3 MiB
 
 
 
 
 
 
Branch: master
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'master'
${ noResults }
 ZIP  TAR.GZ
PoroCYon 6aad3109cc fix nasm include paths 2 years ago
4klang fix nasm include paths 2 years ago
clinkster [clinkster] _WIN32 -> _MSC_VER 2 years ago
oidos fix nasm include paths 2 years ago
v2 [v2] C++ backend stuff, enable ronan w/ asm backend 2 years ago
.gitattributes add clinkster source (doesn't seem to have a public git repo) 2 years ago
.gitignore add clinkster player code 2 years ago
.gitmodules [v2] option to use the asm or C++ (with patches) backend 2 years ago
LICENSE README and LICENSE stuff 2 years ago
README.md add clinkster player code 2 years ago

README.md

Linux templates for PC intro synths

Small template code to get 4klang, Clinkster, Oidos and V2 running on Linux :)

Quickly hacked together by PoroCYon.

Hugs to Alkama and noby for providing 4klang test tracks! And greets to Punqtured for publishing the .xrns files too in Tiny Sound Planet.

How to use

Requirements

  • A C compiler, make, sed, awk
  • nasm or yasm
  • Python 2, for the converters used in Clinkster and Oidos.

Usage

4klang

  1. Put the exported 4klang files in the mus folder (4klang.asm, 4klang.inc and 4klang.h).
  2. Run make
  3. Run bin/runner

Clinkster

  1. Put the .xrns files in the mus folder.
  2. Run make
  3. Run bin/play-<songname> | aplay

Oidos

  1. Put the .xrns files in the mus folder.
  2. Run make
  3. Run bin/play-<songname> | aplay

V2

  1. Put the exported .v2m files in the mus folder.
  2. Run make
  3. Run bin/lplayer-<songname> | aplay -c2 -r44100 -fFLOAT_LE

License

WTFPL.

The code under the clinkster/Clinkster directory and all code in the git submodules, are all published under their respective licenses.