What's new

New Spitfire library with Bleeding Fingers & James Everingham

You can load Fractured Strings into a third party plugin that supports its own tempo, something like Unify. Then you can delink that plugin from the host tempo and set the tempo you want. If you haven't done so already, you might try changing the quality on the render and see if any of the modes give you a quality that you are satisfied with.
this is indeed a better solution (once you find the right tempo)!
 
You can load Fractured Strings into a third party plugin that supports its own tempo, something like Unify. Then you can delink that plugin from the host tempo and set the tempo you want. If you haven't done so already, you might try changing the quality on the render and see if any of the modes give you a quality that you are satisfied with.
Ah yes! I’ll try it :)
 
a quick update

1. Spitfire has not even replied to my ticket submission yet :emoji_unamused:
2. Unfortunately I have found a case in which even the "Mid Stretch Quality" trick does not work. When I play a Ab1, A1 or Bb1 note, all arps sound fine except for the Major Wide one which sounds a semitone down. This is also the case if I set Quality to Low. ouch! (btw this confirms that they have sampled every minor 3rd)
 
Last edited:
Hey everyone! Just bought Fractured Strings during Flash Sale and I love it. It’s a very niche library but adds realism to your tracks.
However, one thing that really annoys me is that some articulations are tempo synced and others are not. I haven’t found any way to turn off that tempo sync feature, maybe some of you have? I composed a track in slow tempo (about 60bpm) and the tempo synced articulations are not really useable due to the weird time stretching effect… just doesn’t sound good at all in that case. So I want to turn it off. Any clue how?
Somewhere was written that it’s not possible but I hope that’s not true 😅
Another thing to try is writing in "double tempo", e.g. you can write a track in 60 bpm with project tempo set to 120 bpm. You just have to account for this mentally, e.g. a 1/4 note @ 60 bpm is a 1/2 note @ 120 bpm. 1 bar @ 60 bpm is 2 bars @ 120 bpm, and so on.

This should get you closer to the original bpm of the recordings, thereby reducing time-stretching artifacts for tempo-synched articulations.

I got into making music through electronica and hip hop, and there's quite a few genres that - consciously or not - use this to great effect. For example UK drill: The hats are written in ≈ 140 bpm, whereas kick & snare are written @ 70 bpm. I think this creates interesting rhythmic interplay, which can also be used in more "classical" styles.

Of course, you can get the same effect by doubling grid resolution, e.g. setting to 32nd steps @ 60 bpm. But at least for me, it's way harder to program this way. Not an end-all, be-all solution, but rather just a different way to think about underlying metric structures.
 
a quick update

1. Spitfire has not even replied to my ticket submission yet :emoji_unamused:
2. Unfortunately I have found a case in which even the "Mid Stretch Quality" trick does not work. When I play a Ab1, A1 or Bb1 note, all arps sound fine except for the Major Wide one which sounds a semitone down. This is also the case if I set Quality to Low. ouch! (btw this confirms that they have sampled every minor 3rd)
I got a response, but it was then escalated to the technical team. Evidently, the technical team is "quite busy at the moment, so give them some time to get back to you!"
 
I finally got a response too

"we are aware of it and it is currently being addressed for the next up"

so let's hope :emoji_fingers_crossed:
 
I got a response, but it was then escalated to the technical team. Evidently, the technical team is "quite busy at the moment, so give them some time to get back to you!"
I've been hearing this from Spitfire for a few years now. It is disappointing. 😟
 
I've been hearing this from Spitfire for a few years now. It is disappointing. 😟
I also haven't yet heard from the technical team. It does seem like the size of the technical team might need to be increased. They are servicing a lot of products now and the updates for each product are coming less frequently than they used to. (Contrary to what others have said, SF still updates many older libraries, but once upon a time we got one about every year; that schedule no longer seems to apply, and things that in the past would have been dealt with quickly, like the issues with AR-2 solo strings, are now languishing unresolved for over a year.)
 
I also haven't yet heard from the technical team. It does seem like the size of the technical team might need to be increased. They are servicing a lot of products now and the updates for each product are coming less frequently than they used to. (Contrary to what others have said, SF still updates many older libraries, but once upon a time we got one about every year; that schedule no longer seems to apply, and things that in the past would have been dealt with quickly, like the issues with AR-2 solo strings, are now languishing unresolved for over a year.)
Starting with, and since the pandemic began, a lot of companies have struggled to keep a full team, so Spitfire is far from alone in having "longer than normal wait times." That said, there has been no corresponding slowdown in product releases, which suggest their priorities are not what I would prefer.
 
Starting with, and since the pandemic began, a lot of companies have struggled to keep a full team, so Spitfire is far from alone in having "longer than normal wait times." That said, there has been no corresponding slowdown in product releases, which suggest their priorities are not what I would prefer.
Well, they likely need the revenue from new products to keep the lights on and everyone employed, so I understand why that might get more attention in the short term, especially in crisis times like pandemics. But it's not good if they can't rebalance things in the long term, and they still seem to be trending in the wrong direction with respect to maintenance. Ever slower maintenance updates does seem to be an industry-wide problem.
 
Top Bottom