Thursday, February 1, 2007
Wednesday, January 31, 2007
Minor New Release
Due to a little wiring error, "Semitone" and "Fine" knobs for Oscilliator 2 did not work. This has been fixed in this minor release.
You can download it here:
http://rapidshare.com/files/14258951/Disease.v0.51b.zip
Disease has been downloaded 494 times at the time of writing. Strange, the word does not get spread so quick. And, according to statistics, this site has received 300~ views. 494 downloads, 300 views. How?
You can download it here:
http://rapidshare.com/files/14258951/Disease.v0.51b.zip
Disease has been downloaded 494 times at the time of writing. Strange, the word does not get spread so quick. And, according to statistics, this site has received 300~ views. 494 downloads, 300 views. How?
Monday, January 29, 2007
First Release of Disease
Here is the first release of Disease (v0.5 Beta):
http://rapidshare.com/files/13976610/Disease_v0.5b.rar
http://rapidshare.com/files/13976610/Disease_v0.5b.rar
First Beta Release
I have completed LFO section of Disease. First release is about to come.
Missing List:
1. LFO unit still lacks Tempo Sync. That feature will be added on future releases.
2. Patches.
3. There may be some problems in snapshots, I have not encountered one so far.
4. I do not know if it can be automated efficiently in sequencers and hosts.
5. Pulse Width modulation.
6. Still a CPU hog.
I have also got a chance to examine a low quality hypersaw sound, sampled from a video. It is different than what Disease produces right now. The character of that synth is because of its filter module. Disease hypersaw is much brighter as I have analyzed.
I still need information. I think I will get assistance when the word gets spread with first release.
This is what Disease looks like now.

http://img247.imageshack.us/img247/6321/diseasev05bxl0.jpg
Missing List:
1. LFO unit still lacks Tempo Sync. That feature will be added on future releases.
2. Patches.
3. There may be some problems in snapshots, I have not encountered one so far.
4. I do not know if it can be automated efficiently in sequencers and hosts.
5. Pulse Width modulation.
6. Still a CPU hog.
I have also got a chance to examine a low quality hypersaw sound, sampled from a video. It is different than what Disease produces right now. The character of that synth is because of its filter module. Disease hypersaw is much brighter as I have analyzed.
I still need information. I think I will get assistance when the word gets spread with first release.
This is what Disease looks like now.

http://img247.imageshack.us/img247/6321/diseasev05bxl0.jpg
Wednesday, January 17, 2007
Demos
Here are some demos of what Disease can do in its current stage.
http://d.turboupload.com/d/1438575/demo1.mp3.html
http://d.turboupload.com/d/1438583/demo2.mp3.html
http://d.turboupload.com/d/1438575/demo1.mp3.html
http://d.turboupload.com/d/1438583/demo2.mp3.html
First Steps
I have begun searching for samples of hypersaw and supersaw oscilliators. People will not suddenly hear about and help this project; I have to spread the information.
I have not come to any samples so far, but from what I have learned, there is something that has been made like Disease in the past. Some user at somewhere mentioned it, and I am searching for the user that has the file.
Apart from that, if the research of synthesizing a hypersaw does not yield any result, then Disease may use a different approach to situation: Rendering hypersaw oscilliators to 10 or so wave files, differing in detune, then using them in a looped sampler that will be used as an oscilliator - like wavetable synthesis. This will be more CPU friendly compared to running 3x 9-saw oscilliators.
I have not come to any samples so far, but from what I have learned, there is something that has been made like Disease in the past. Some user at somewhere mentioned it, and I am searching for the user that has the file.
Apart from that, if the research of synthesizing a hypersaw does not yield any result, then Disease may use a different approach to situation: Rendering hypersaw oscilliators to 10 or so wave files, differing in detune, then using them in a looped sampler that will be used as an oscilliator - like wavetable synthesis. This will be more CPU friendly compared to running 3x 9-saw oscilliators.
Friday, January 12, 2007
Hello World.
Let me introduce myself. I am a man with a scientist's mind. That is all you need to know, because what I will do must stay as anonymous.
I have a mission.
To produce electronic dance music, you have to invest a good amount of cash on hardware equipment. No matter good software is, it uses too much CPU to emulate analogue sounds that hardware create. And those which don't emulate hardware sound too crisp and thin for good productions.
This may not be a problem for those who are into drum and bass and that kind of out-of-boundaries music. But people who try to make dance, trance and their subgenres are limited, and required spending lots of cash on overpriced hardware.
Then, here comes the paradox:
To make professional music, you need good hardware; to get good hardware, you need money.
To earn money, you need to make professional music; you make professional music, you need good hardware. -The Scientist
There are many analogue emulated plugins out there. But there are no emulations for the famous (and infamous) hypersaw and supersaw (except Superwave bundle).
My mission is to provide you with these typical sounds.
The closest way to get to result is using Native Instruments' Reaktor. I am building up an instrument named, Disease. It will only include what you need to get for good hypersaw/supersaw leads.
I was planning to open up this blog earlier, but some problems occured while registration process, so it was delayed.
This means, some parts of the instrument, Disease, is completed.
I am going to approach this from a point of view of a scientist. I will collect information, form a hypothesis and make experiments.
I need support for this project. Searching the world wide web did not help sometimes, like finding a raw hypersaw or supersaw oscilliator output. That is strange, noone posted any raw demos of hypersaw and supersaw oscilliators.
What I need is here:
1. Raw hypersaw output. Not detuned, slightly detuned, and standardly detuned. This will be used for examination and for an alternative.
2. Raw supersaw output. Not detuned, slightly detuned, and standardly detuned.
3. Technical information that you can share.
4. Hints of original research. Ex-Access employees, ex-Roland employees... All are welcome. Anonymously and freedom of speech is the key to success.
Now, onto the basic information we have.
1. Hypersaw uses only 1 voice for 9 saws.
2. There is some rumor about comb filtering in supersaw sound. (I have tried this, but I couldn't use the filter efficiently. Need more info and a better algorithm)
3. DSP chips are as not powerful as our CPUs. So, to achieve nearly 80 voices, there may be a dirty trick going on. This supports the second data.
This data pool will grow with the bits of information you share. Then I will form a hypothesis and work on that.
I hope I can aid the community.
I have a mission.
To produce electronic dance music, you have to invest a good amount of cash on hardware equipment. No matter good software is, it uses too much CPU to emulate analogue sounds that hardware create. And those which don't emulate hardware sound too crisp and thin for good productions.
This may not be a problem for those who are into drum and bass and that kind of out-of-boundaries music. But people who try to make dance, trance and their subgenres are limited, and required spending lots of cash on overpriced hardware.
Then, here comes the paradox:
To make professional music, you need good hardware; to get good hardware, you need money.
To earn money, you need to make professional music; you make professional music, you need good hardware. -The Scientist
There are many analogue emulated plugins out there. But there are no emulations for the famous (and infamous) hypersaw and supersaw (except Superwave bundle).
My mission is to provide you with these typical sounds.
The closest way to get to result is using Native Instruments' Reaktor. I am building up an instrument named, Disease. It will only include what you need to get for good hypersaw/supersaw leads.
I was planning to open up this blog earlier, but some problems occured while registration process, so it was delayed.
This means, some parts of the instrument, Disease, is completed.
I am going to approach this from a point of view of a scientist. I will collect information, form a hypothesis and make experiments.
I need support for this project. Searching the world wide web did not help sometimes, like finding a raw hypersaw or supersaw oscilliator output. That is strange, noone posted any raw demos of hypersaw and supersaw oscilliators.
What I need is here:
1. Raw hypersaw output. Not detuned, slightly detuned, and standardly detuned. This will be used for examination and for an alternative.
2. Raw supersaw output. Not detuned, slightly detuned, and standardly detuned.
3. Technical information that you can share.
4. Hints of original research. Ex-Access employees, ex-Roland employees... All are welcome. Anonymously and freedom of speech is the key to success.
Now, onto the basic information we have.
1. Hypersaw uses only 1 voice for 9 saws.
2. There is some rumor about comb filtering in supersaw sound. (I have tried this, but I couldn't use the filter efficiently. Need more info and a better algorithm)
3. DSP chips are as not powerful as our CPUs. So, to achieve nearly 80 voices, there may be a dirty trick going on. This supports the second data.
This data pool will grow with the bits of information you share. Then I will form a hypothesis and work on that.
I hope I can aid the community.
Subscribe to:
Posts (Atom)