jaketanner
Senior Member
Excusing the bad melody and accompaniment, the Flute sounds boxy to my ears.
what mic position did you use?
Excusing the bad melody and accompaniment, the Flute sounds boxy to my ears.
I think this sounds pretty good. I think it is a matter of learning to program to the libraries' strengths. And remember they need to take breaths. I always forget that part......Here's a quick run with a tighter legato with the mics put as far up front as I could (by tinkering) with a fairly tight legato. I really like the way the Bass Clarinet turned out. Light CSS to go with it.
I think this sounds pretty good. I think it is a matter of learning to program to the libraries' strengths. And remember they need to take breaths. I always forget that part......
Here's a quick run with a tighter legato with the mics put as far up front as I could (by tinkering) with a fairly tight legato. I really like the way the Bass Clarinet turned out. Light CSS to go with it.
1. Bass Clarinet
[AUDIOPLUS=https://vi-control.net/community/attachments/spitfire-bass-clarinet-mp3.19901/][/AUDIOPLUS]
2. Bassoon
[AUDIOPLUS=https://vi-control.net/community/attachments/spitfire-bassoon-mp3.19902/][/AUDIOPLUS]
3. Flute
[AUDIOPLUS=https://vi-control.net/community/attachments/spitfire-flute-mp3.19903/][/AUDIOPLUS]
No disrespect to anything you did, but I actually don't think this sounds good at all. It sounds incredibly MIDI-ish and flat, and those tree mics are just wrong.
Core / T1 mics...what mic position did you use?
Core / T1 mics...
I didnt use any modulation or expression. Didnt want to put that much time into a quick demo
I suspect this might be the kind of thing that drives developers crazy. People throwing up "demos" of a library without the slightest attention to factors that directly impact the overall impression of it. I'm sure you just did it to show the "tone" or the tree mic or whatever but a lot of things contribute to the overall impression of the "sound" of a library and the reality is that almost any library will sound bad, synthy and flat (to varying degrees) if you don't even bother to ride dynamics.
IMHO, if you're going to take the time to record a "quick demo" the least you could do is ride the modwheel even a little while you're doing it.
Just for the record....someone here asked me for a demo. Just because someone asks for a demo doesnt mean im going to spend an entire afternoon on it.
People throwing up "demos" of a library without the slightest attention to factors that directly impact the overall impression of it.
I would argue the exact opposite way and say it is even more valid since it shows what users could expect right out of the box. Why would a user only be allowed to 'demonstrate' something, if it works well right out of the box but not if it needs work?I suspect this might be the kind of thing that drives developers crazy. People throwing up "demos" of a library without the slightest attention to factors that directly impact the overall impression of it. I'm sure you just did it to show the "tone" or the tree mic or whatever but a lot of things contribute to the overall impression of the "sound" of a library and the reality is that almost any library will sound bad, synthy and flat (to varying degrees) if you don't even bother to ride dynamics.
IMHO, if you're going to take the time to record a "quick demo" the least you could do is ride the modwheel even a little while you're doing it.
I would argue the exact opposite way and say it is even more valid since it shows what users could expect right out of the box. Why would a user only be allowed to 'demonstrate' something, if it works well right out of the box but not if it needs work?