Working with Vince Fusca History
I ran into this while setting up a new session for a film scoring project. Vince Fusca History is a collection of orchestral sample libraries and virtual instruments, primarily focused on cinematic strings and hybrid orchestration sounds. If you're looking to use it in a DAW, here's how it actually works in practice. The library is built around Kontakt, so the first thing you need is Native Instruments Kontakt Player or the full version of Kontakt. The samples are organized by instrument family — violins, cellos, basses, brass sections, plus some solo voice elements that can be layered in for texture. Installation is straightforward: download the archive, extract it to your samples folder, and launch Kontakt. From there you browse to the library folder and load the main script file. One thing that trips people up is the keyswitch layout. The default keyswitches are color-coded in the manual, but if you've ever rearranged your MIDI controller mapping, you can easily lose track of which key triggers legato versus spiccato. I had this happen mid-session when my controller was remapped to bank B instead of bank A. The workaround was pulling up the on-screen keyboard in Kontakt, hitting each keyswitch one at a time while watching the display update, and writing down the current mapping before remapping anything else going forward.
The velocity layers are reasonably deep — I counted eight distinct layers in the string samples, which means you can push for some dynamic realism if you're actually using aftertouch or expression pedal automation. That said, the expression pedal implementation assumes you have a continuous CC11 source. If you're working from a MIDI keyboard without one, you'll be manually automating volume curves in your DAW, which is fine but adds about twenty minutes to your setup time per patch. Another detail most people overlook: the library uses round robins across its sustained patches, but the short articulations — staccato, marcato, pizzicato — have fewer round robin variants. If you're writing rapid repeated notes in those articulations, the artificial repetition becomes obvious within four to six bars. My fix was layering a second instance of the same patch an octave apart with slightly detuned oscillators, which masked the pattern without sounding like a deliberate effect. The brass section has a notable limitation. The fortissimo layers cut off abruptly above fortissimo without a true climax zone. For cues that need to push past ff, you have to layer the brass library with something else. I ended up combining it with a smaller chamber brass sample set and crossfading between them in the arrangement, which gives you a usable range from pp to roughly fff before things start sounding thin.
There are no included mixer templates or preset patches beyond the factory defaults, so you're building your signal chain from scratch. You'll want reverb on the string section — a hall verb with a decay around 2.2 seconds tends to sit well — and a light bus compressor to glue the groups together. The solo elements benefit from a plate reverb at about 15% wet mix to keep them present without pushing them too far forward. If you need the download, the official source is through the vendor's website. Make sure you're running Kontakt 5.7 or later; older versions had issues with the library's script files and could crash on certain articulation switches. I encountered one crash when loading the full ensemble patch with 32 voices active on an older build. Upgrading resolved it immediately. The system requirements are modest compared to some larger orchestral libraries. You should have at least 16 GB of RAM free, though 32 GB is more comfortable if you're running multiple articulations simultaneously. CPU usage scales with voice count, so a dual-core processor from a few years back will struggle with full ensemble patches, but a modern quad-core handles typical session sizes without breaking a sweat.
Get the Full Details
