pouët.net

I love to connect nodes in unusal ways. Gopher, that´s what your synth is made for !! ;)
It´s not that easy to create interesting sounds but you´ll get used to it.
Here are some shots at digital waveguide synthesis i tried lately:
https://soundcloud.com/virgill/64klang2-physical-modeling-test

Gopher: Man that looks like some crazy shit that I want to have a go on at some point.

The big benefit of the DAW / Plugin approach is you have the overall picture of the arrangement, named, labels, colour coded, grouped etc. all in one place. It's really bloody handy when trying to get the arrangement done and more over adding dynamics to the track by editing parts.

However, I can't really comment on the other approach as I've never tried any other scene synth to make a tune (only ever used Gargaj and Ferris's setups). I've tried a small selection of them in the past but they all seem to fall over in Cubase! I'd be interested to know how well 64klang2 works with Cubase, does look quite interesting. (hint hint.. ianhoffmanuk at gmail.com )

there's some 64k synths around working under linux? or all are win32 only? :3

@rez: this is where you go pro-active and offer to port ;)

Alternatively, there are VST bridges for Windows plugins. Which could for example be used inside Renoise on Linux.

@hoffman: it works perfectly with cubase :)

Hoffman: true. the overall picture of your arrangement might be better if you go the traditional way. But then again it is just a matter of a good usability design and ui concept in the plugin itself to provide a similar or even better experience.in that aspect theres probably still a lot to do in 64klang2 :)
Ill send you a link somewhen this weekend.

That flute sound towards the third quarter of the track. Great work, dude!

gopher & virgill : Cheers :)

Virgill: o_O Massively impressive sounds!

I agree with ton - a single multitimbral VSTi is OK.

@rez try TuneFish for Linux.

What torus/freezedream said. That's some serious Korg Prophecy/Z1 level stuff there. :)

Sounds awesome indeed!

+1 for sick sounds ^^

It sounds superb!!! The 64k category should be revived/resurected, if only so we can listen to this sound/music quality. Damn...!

Thx, ppl :) For those who didn´t knew it... this is also done with 64klang2:
https://soundcloud.com/virgill/computers-are-gay
beware! vocoders!

@gopher: I would like to try 64klang2 too. Any download link? :P

This is my current tracker-based non-fixed-pipeline/free-programmable synth:

https://www.youtube.com/watch?v=VhZCCJ20lAw

I'll maybe release it in some months together with two playback source code variants in C and Pascal, after I've implemented some missing parts from my ideas todo-list, for example the still missing noise-part-processing of my sinusoid-based WRS (WaveReSynthesizer) stuff.

The synthtracker generates a .h C header with the track pattern data as byte array together with microsoft-linker-compatible .obj COFF files with my internal x86 assembler, which contains the generated native x86 code of the AULAN synth instruments and AULAN global audio code part of a soundtrack. (AULAN is my own Pascal+Basic+C-style-mixed programming language, which you can see in the YT-video also.)

I'm using it in my 64ks since fr-minus-017: coderpr0n and even in my 8k fr-067: Outer worlds.

I hear your vocoder and raise you my incomprehensible vocoder:

https://soundcloud.com/simon-ley/synthfest-vocoder-test

(speech is done using Windows SAPI)

@Bero: nice stuff!

bero: Bravo! your tracker looks really powerful! I have two questions - can you play the instruments with the keyboard to enter notes? Secondly, how do you create the instruments? If it's through code then a lot of musicians will be rather alienated. Some form of GUI for instrument editing is essential these days - this isn't the 1980s. :p

freezedream: what I wrote already to xTr1m on youtube to his video comment:

"There is no GUI for this yet, but this is a good idea. The GUI concept for this should be well thought out, otherwise it will be an for-the-most-peoples-unusable GUI, I think."

ie a useful GUI concept for visual AULAN instrument code editing must be found first.

And CreamTracker has no MIDI keyboard input support yet, but I could quickly copy&paste the MIDI keyboard input code from BeRoTracker or Picatune2 into CreamTracker, if needed.

red: incomprehensible but nice sounding! Have you used the so called Bark-frequencies ? That might improve the speech comprehension.

Voiced/unvoiced detection is also a must.