I’ve created three separate Mapping files, so that you can choose which banks you want to use. And more importantly, it is very easy to exchange one bank with another mapping. That way you can use a bank with your own mapping very easily.

Bank 1: Cue points

This is a very basic mapping taken from the defaults. Use Bank 1 to set and delete Hotcues. The picture shows the Dicer with cue point 1 and 3 set while 2, 4 and 5 are not set for the currently loaded track.

Bank 2: Pitch bend and loops

Basically this is the bank that I activate while I’m “in the mix”. It delivers pitch bend functionality and loop control. Button 1 and 2 are used to pitch bend the track and also indicate the phase meter. That means button 1 will get red when the track is too slow while button 2 indicates, that the track is too fast. The Loops are controlled by button 3, 4 and 5. Button 3 enables and disables the loop and the other two increase or decrease the loop size.

Bank 3: File browsing

This one is useful when the laptop is a bit too far away to easily reach the keyboard. Button 1 loads the currently selected track and the other four are used to navigate through the library in different ways.

Download

Novation Dicer Mappings (zipped)

Als ich angefangen habe meine Abschlussarbeit zu schreiben stand für mich fest: das wird mit LaTeX erledigt. Dies war natürlich nicht mein erster Kontakt mit LaTeX. Da ich leider keine (gute) Vorlage für meine Arbeit gefunden habe, ergaben sich dennoch einige Schwierigkeiten, die ich umschiffen musste. Das Resultat meiner Bemühungen war eine recht angenehm zu verwendende Projektstruktur, welche ich jetzt nochmals für diesen Post in generischer Form aufgearbeitet habe.

Einige grundlegende Empfehlungen vornweg:

• die Arbeit sollte (sinnvoll) in mehrere Dokumente und Verzeichnisse aufgeteilt sein
• alle Dokumente sollten versionsverwaltet sein
• wer kein Backup hat ist selber schuld! Am besten online (e-Mail) und offline (USB-Stick)

Als Basis für meine Arbeit (und damit auch für das Template) habe ich die KOMA-Script scrreprt-Klasse gewählt. Diese Klasse bietet sinnvolle Standards und kann einfach und sehr flexibel konfiguriert werden – habe es nicht bereut. Zur Lösung des ein oder anderen Problems kamen dann während des Schreibens immer wieder neue Pakete dazu. Die wichtigsten (nicht trivialen) seien hier kurz aufgeführt:

• listings zur Darstellung von Quelltext mit farblicher Syntaxhervorhebung
• da ich mit jurabib zum zitieren immer mal wieder merkwürdige Probleme hatte binauf natbib und germbib umgestiegen
• glossaries und nomencl für das Glossar- und Abkürzungsverzeichnis (da ich zu Faul war mit einem Paket mehrere Verzeichnisse anzulegen)
• PGF und TikZ für verschiedenste Diagramme

Hier also das Template sowie das daraus generierte Beispiel (PDF):

LaTeX Vorlage

Beispiel PDF

Inhalt und Struktur des Templates:

• Makefile: Konfigurationsdatei für make mit vier Optionen: pdf (führt nur pdflatex aus), all (führt alle Schritte aus), glo (nur Glossar) und clean (räumt Projektverzeichnis auf). Weitere Build-Ziele können leicht hinzugefügt werden
• dokument.tex: Hauptdokument: Von hier werden alle weiteren LaTeX-Dateien eingebunden. Für alle LaTeX Werkzeuge (pdflatex, etc.) ist dies die Quelldatei
• header.tex Alle benötigten Pakete werden hier eingebunden und konfiguriert
• kapitel1.tex, kapitel2.tex, kapitel3.tex und anhang.tex: LaTeX Dateien mit dem eigentlichen Inhalt der Arbeit. Diese werden in dokument.tex eingebunden.
• titlepage.tex: Enthält die Titelseite
• glossar.tex: Enthält das Glossar
• img/unilogo.png: Logo der Universität (wir auf Titelseite eingebunden)
• quellen.bib: Literaturangaben/Quellen im Bibtex-Format

Ich hoffe dem ein oder anderen bei technischen Umsetzung seiner Diplom-, Master-, Bachelor- oder Hausarbeit ein bisschen geholfen zu haben.

Right now I use WordPress with the following plug-ins/additions:

• modified cleanr theme
• SyntaxHighlighter Evolved
• StatSurfer for some colorful diagrams
• Feed Statistics for even more data to look at
• Raven’s Antispam (hopefully enough for this small blog)

Beside the blog I’ve “installed” a Wiki and a online RSS reader. To cut a long story short: I use PmWiki with the SourceBlock plug-in (for syntax highlighting) for my personal Wiki and Tiny Tiny RSS to manage and read my news feeds.

While I normally try to avoid browser-based software, I must admit that I’m really impressed by Tiny Tiny RSS. It has completely replaced my desktop feed readers (Akregator and Liferea). And I really enjoy the fact that I don’t have to “sync” my feeds between different computers.

Now I just need a decent webmail software – something that can compete with the simplicity, power and speed of GMail…

Guess what... I got my diploma :-)

Big thanks to DjTuxeedo, who has tested my branch and found this really stupid mistake of me (probably happened during a merge) :)

• website: http://evosynth.rubyforge.org/
• project: http://rubyforge.org/projects/evosynth/
• git repositories: EvoSynth@Github and EvoSynth@Gitorious

EvoSynth is a framework (written in ruby) for rapid development and prototyping of evolutionary algorithms. It is designed with simplicity and productivity as main goals, so don’t expect it to compete with the performance of the established frameworks.

core features:

• classes for individuals, populations, algorithm profiles, genomes
• support for custom randomizer
• meta operators: proportional, sequential and conditional combined operators
• logging support with exporter to gnuplot, gruff and csv
• many predefined fitness functions

most common evolutionary algorithms:

• hillclimber (single individual and population based)
• standard genetic algorithm, steady state GA
• memetic algorithm
• evolution strategies (adaptive, selfadaptive and derandomized)
• local search (hillclimber, threshold acceptance, simulated annealing, great deluge, record-to-record travel)
• coevolutionary algorithms (round robin and balanced)

selection strategies:

• identity and random selection
• best selection
• n-stage tournament selection and tournament selection
• fitness proportional selection
• roulette wheel selection

mutations:

• identity
• one gene flipping, binary mutation, efficient binary mutation
• exchange mutation, inversion mutation, mixing mutation, shifting mutation
• uniform real mutation, gauss mutation, self-adaptive gauss mutation

recombinations:

• identity
• one-point-crossover, k-point-crossover, uniform crossover
• ordered recombination, partially mapped crossover, edge recombination
• arithmetic crossover
• global uniform crossover, global arithmetic crossover

installation and usage:

If you want to try EvoSynth, check the installation guide for instructions how to install it. Take a look at the examples and read the not yet complete rdoc documentation.

Now it is time to start hacking on new stuff. But during the next couple of days I will “port” my existing branches/patches to the xwax 0.7 codebase.

With this patch each record in your library will get five cue points (you can customize this number). The cue points are shown right beside the clocks. Each cue point got its own colour and will be displayed as coloured line in the overview and closeup-view.

I had to free some keys to control this functionality, so I introduced 2 modes: search and cue (call it library and dj mode if you want to). You can toggle between the two modes with the INSERT key.

key mapping

• toggle between search and cue mode: INSERT key

• deck one:
  • set/jump to cue points: 1, 2, 3, 4, 5
  • remove the cue points: CTRL + 1, 2, 3, 4, 5

• deck two:
  • set/jump to cue points: 6, 7, 8, 9, 0
  • remove the cue points: CTRL + 6, 7, 8, 9, 0

• deck three:
  • set/jump to cue points: q, w, e, r, t
  • remove the cue points: CTRL + q, w, e, r, t

How do you get it?

You can pull the 0.7+cue-points branch from my xwax repository @ githib. Github should also offer you a download button to get the source code.

Basically this patch provides a simple highlighting of played/loaded tracks in the record selector of xwax. You will see two new crates named “Played records” and “Loaded records” which are automatically managed by xwax (see screenshot below).

Once you load a record to a deck xwax will mark the record as “loaded”. You can continue to skip through your record list and each record you load, will be marked as “loaded”. A record gets marked as “played” when the previously loaded record was loaded to another deck.

You can toggle through the 3 states (not highlighted, loaded, played) with the DEL key.

How do you get it? You can pull the 0.7+playedtracks branch from my xwax repository @ githib. Github should also offer you a download button to get the source code.