Hi there,
I have some questions about sound process and which one is responsible for it.
Midi Notes read by VST instrument, then the instrument processes the sound and the host monitor it, right? If it is right, that means the host is not responsible for the quality of the sound of that instrument, it is just a monitor.
Then I record this sound and the result is wave file. Here which part is responsible for this file? The host? Or the host just calling some method in the OS? I mean where the code exist to build the wav file (or whatever format) inside the host? Or inside the OS?
Thanks in advance
Sound process
-
- KVRAF
- 9150 posts since 7 Oct, 2005
-
- KVRAF
- 6937 posts since 4 Jun, 2004 from Utrecht, Holland
The dataflow is as follows in general:
* You put midi notes and CC info in the host.
* The host sends this info to VSTi plugins
* The VSTi's produce audio (WAV) data in 32bits precision
* The host sends this audio data to further VST effects you may have on the track. VST plugins can only produce 32bits audio (WAV) data.
* The host sums all audio data of all tracks on the master bus. You may have further VST effects on the master bus, so it still is 32bits.
With final results of the master bus anything further can be done:
- Optional dithering for nice rounding to 16bits
- Send (through ASIO driver) to a soundcard
- Write to a WAV, AIFF or MP3 file. Most host developers use existing library routines for this, but writing your own method can be done also. I believe when writing 24 or 32bits WAV files there is absolutely nothing "lost" in audio quality.
At the final point you are totally in control, since you can set options on the project or output file which control bit depth and sample frequency. So the one responsible for the final quality is you
* You put midi notes and CC info in the host.
* The host sends this info to VSTi plugins
* The VSTi's produce audio (WAV) data in 32bits precision
* The host sends this audio data to further VST effects you may have on the track. VST plugins can only produce 32bits audio (WAV) data.
* The host sums all audio data of all tracks on the master bus. You may have further VST effects on the master bus, so it still is 32bits.
With final results of the master bus anything further can be done:
- Optional dithering for nice rounding to 16bits
- Send (through ASIO driver) to a soundcard
- Write to a WAV, AIFF or MP3 file. Most host developers use existing library routines for this, but writing your own method can be done also. I believe when writing 24 or 32bits WAV files there is absolutely nothing "lost" in audio quality.
At the final point you are totally in control, since you can set options on the project or output file which control bit depth and sample frequency. So the one responsible for the final quality is you
My MusicCalc is temporary offline.
We are the KVR collective. Resistance is futile. You will be assimilated.
We are the KVR collective. Resistance is futile. You will be assimilated.
-
- KVRAF
- Topic Starter
- 9150 posts since 7 Oct, 2005
Thanks a lot C00kie for your explanation.
Now regarding the final stage. Is this existing library considered a standard way in rendering to WAV (for example)? I mean is rendering to WAV or AIFF is like saving midi notes in format 0 or 1? Is it host independent process?
Now regarding the final stage. Is this existing library considered a standard way in rendering to WAV (for example)? I mean is rendering to WAV or AIFF is like saving midi notes in format 0 or 1? Is it host independent process?
Using: Cubase Pro 15, Bitwig 5, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- 6937 posts since 4 Jun, 2004 from Utrecht, Holland
Yep, the 0 and 1's in WAV/AIFF files are totally host-independant. Some hosts may some additional info (e.g. Acid can put beat markers in loops) but the raw file format can't be tempered with.
This is why I don't believe in debates like "Host A sounds different from Host B" and "Exported WAV sounds different than played in host, need a recorder VST"
There is no other explanation than it's in the head of the perceiver.
This is why I don't believe in debates like "Host A sounds different from Host B" and "Exported WAV sounds different than played in host, need a recorder VST"
There is no other explanation than it's in the head of the perceiver.
My MusicCalc is temporary offline.
We are the KVR collective. Resistance is futile. You will be assimilated.
We are the KVR collective. Resistance is futile. You will be assimilated.
-
- KVRAF
- Topic Starter
- 9150 posts since 7 Oct, 2005
You already knew what conclusion I wanted
I think this conclusion is logical, because if Host A sounds different than Host B and Host C (supposing all have the same setup), while Host B and Host C sounds similar, that means Host A is altering the standard way to render to that format, something like the difference between the monitors used for mixing and the monitors used in any home stereo. The later colors the sound while the first supposed to be neutral. Of course I don't think that any host is trying to not be neutral because how can we get what we hear!
Thanks C00kie for making that clear for me
I think this conclusion is logical, because if Host A sounds different than Host B and Host C (supposing all have the same setup), while Host B and Host C sounds similar, that means Host A is altering the standard way to render to that format, something like the difference between the monitors used for mixing and the monitors used in any home stereo. The later colors the sound while the first supposed to be neutral. Of course I don't think that any host is trying to not be neutral because how can we get what we hear!
Thanks C00kie for making that clear for me
Using: Cubase Pro 15, Bitwig 5, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.