cjbrett22
New Member
Yeah I've had loads of issues, was in contact with support yesterday who suggested a reinstall. Did that but still having the same problems. Haven't heard back from them yet so will see.
Spitfire - Hans Zimmer Strings 24 Hours Left! ENDING Tuesday 5th June 23:59 BST
- Thread starter Spitfire Team
- Start date
Yeah I've had loads of issues, was in contact with support yesterday who suggested a reinstall. Did that but still having the same problems. Haven't heard back from them yet so will see.
SpitfireSupport
Customer Experience
Hi there,
We're actually up to date with all open support cases today so you should have received a response to anything you've sent in. Whatever issues you may find you're having, we'll be happy to help.
Luke
VinRice
... i am a robot ... viruses have no effect ...
Except that an $800 specialist string library is pretty self-selecting and if the UX testing groups were not in that sub-set of individuals for whom this is a likely purchase then the results are not particularly helpful. I'm sure there is a Grand Plan to introduce more accessible libraries but in this case the concept of the collapse button, which nobody will ever use ever; the Big Knob, which adds another completely unnecessary level of abstraction; and the constant scrolling and paging required when so much UI space in unused, just seems perverse.
JohnG
Senior Member
Hi there -- your post made me wonder if you've discovered the slider in the upper right, which really helped me with balance.
Kind regards,
John
Dale Turner
Member
The "knob" and "scrolling" to grab an articulation is so fast and painless, it doesn't bother me at all. Perplexed over how peeved some peeps are!
I saw on Daniel James' live vid that the close mics (l, c and r) did have a page break between them.... That'd be a bother, I understand. The rest though....?
I saw on Daniel James' live vid that the close mics (l, c and r) did have a page break between them.... That'd be a bother, I understand. The rest though....?
VinRice
... i am a robot ... viruses have no effect ...
Except it resets to unity every time a new art. is selected
It seems I had replied to the sales email and it went to do-not-reply ID. Have sent it to Support now.
OP
OP
Spitfire Team
Senior Member
VinRice
... i am a robot ... viruses have no effect ...
I'm peeved because I care. I love Spitfire and I have paid to 'license' pretty much their entire output and this library sounds excellent, and far more flexible than I had anticipated. I was also a designer in a previous career. The interface looks beautiful and probably cost an insane amount of money, but that's not the primary concern of the CORE user base, and I can't help feeling that an attack of 'expensive designer bollocks' has added unnecessary levels of abstraction and user interactions. The paging of mic signals should indeed be more logical - an easy fix.
Garry
Senior Member
(also just posted same request on YouTube):
Amazing as always Christian. You're no doubt aware of the debate on VI-C, and this was a very convincing demonstrations of the fast shorts. However, I have a challenge: I don't have the musical skill you have to get the juice you get out of this library and few will, so the question is, would HZS sound the same in my/our hands. So here's the challenge: would you be prepared to release the midi data for this, so that I can use it with my current (Spitfire) libraries, and compare what I get with, for example, Albion One/Tundra, compared to what I hear in your demo here using HZS? If HZS is truly worth the considerable price tag, then without it (given my lack of mic positions, lack of 344 players, and specific articulations) I should hear that my version is far inferior to yours. I hope you see this as a reasonable request: it is something done by some of your competitors (particularly those who shall remain nameless, but make twitter rants about marketing!), and is consistent with the Spitfire transparency. It could really make the difference of the library shine, and help your customer base make a meaningful comparison. What'd ya say?
Amazing as always Christian. You're no doubt aware of the debate on VI-C, and this was a very convincing demonstrations of the fast shorts. However, I have a challenge: I don't have the musical skill you have to get the juice you get out of this library and few will, so the question is, would HZS sound the same in my/our hands. So here's the challenge: would you be prepared to release the midi data for this, so that I can use it with my current (Spitfire) libraries, and compare what I get with, for example, Albion One/Tundra, compared to what I hear in your demo here using HZS? If HZS is truly worth the considerable price tag, then without it (given my lack of mic positions, lack of 344 players, and specific articulations) I should hear that my version is far inferior to yours. I hope you see this as a reasonable request: it is something done by some of your competitors (particularly those who shall remain nameless, but make twitter rants about marketing!), and is consistent with the Spitfire transparency. It could really make the difference of the library shine, and help your customer base make a meaningful comparison. What'd ya say?
Last edited:
fiestared
Vintage -but- not obsolete
I use an iMac late 2013 with 32 GB of ram, intel 3.5 GHZ i7, the lib is on a SSD, and I must say I have no prob at all with drop out, spike, or else, I was a bit afraid by this, but it's cpu friendly for me. The sound is... HUGE, wide, clear and airy, I think we'll have to learn how to musically use this lib, "no more full hands of notes", for me it will be the release point of my tracks, a kind of cherry on the cake. I feel ok with the interface, my only small prob is I would prefer to have all the mics together(maybe in a floating window), for the mics, I prefer the non "advanced" and use the close and far slider, very useful and easy. After one hour of pleasure, I've got the feeling, I'll have to learn a lot to use this "baby" as it deserves, this is probably where our friends at Spitfire will have to help us...
Garry
Senior Member
Christian's midi file from his demo would go a long way to helping you learn this library, no? I hope he'll agree to my request/challenge...
Garry
Senior Member
Additional suggestion: if there are restrictions that would prevent releasing this one, how about any/all of those already on the website by you, Paul and Oliver as demos? I can think of no better way to get to understand this library than having the Logic file, or failing that, the midi file, that would enable us to see in a very practical way, how you guys caress this library into getting the sounds you do.
lucky909091
Senior Member
I have a (small) clue what has happened to you - and to me, too.
I have a very fast PC with endless power, too.
When I load more than 3 mics and play harmony chords with the longs, I also get these issues, clicks and pops.
When I press 6-10 notes at the same time, the "CPU" and the "Disk" signal in the GUI show something over 80 %. The indicators gets red.
Sometimes the "CPU"-signal even goes to 90 and over, sometimes it is the "Disk" signal that overloads.
Because I know my PC very well, I assume that this is an issue generated by the harddisc, where I saved the library.
I will change the storage location to an internal SSD and will see what happens.
Perhaps this will solve the issue...
Last edited:
My samples are on a brand new Crucial MX500 2TB SSD... Let's see if it helps you
It seems this issue is prominent on Windows 10 PC because Mac users seem to be fine
christianhenson
Senior Member
Yes, or get in touch with service. CPU / Ram / Drive problems have never been an issue with alpha and beta versions of this library. It is leaner than being sampler based so should reflect on your systems thus.
As mentioned in my video above this lib has a slightly steeper learning curve than other 'out of the box' style libs, it is a pro piece of kit. So it has taken me a good couple of weeks to really draw the best out. What disappoints me about the sweeping statements being made is that with it only being 24 hours old and at least an 8 hour DL is this fair enough time to draw a well considered conclusion about the lib? Particularly the really trolly ones about this being some kind of cynical marketing stunt. Cos that is what Spitfire has always been about for the last 10 years?? Paul and Christian ripping off and pulling fast ones on our friends, colleagues and heroes?
We've had some really foul comments here which is sad because we have amassed a team of over 40 individuals to deliver 6 years work, 2 years production, our biggest budget by far, and 6 months of intense UX research and design with UsTwo. Is it going to be perfect, of course not which is why it is on discount, and which is why I'm loving the brilliant and constructive feedback that we're getting.
Did we release it with a bug? Yes, the legato thing, and we're a bit red faced about it but it crept into the release version without us knowing, and it will be fixed in the best way that doesn't cause too much of a headache for you all. But again this is why we release v1.0s with a discount, to get your feedback, iron out the creases and work with you to get you what you need.
I also want to take this op to thank the dozens of amazing emails of support and congrats we've received from people from all over, including some of my childhood heroes. Its these words of encouragement that really buoy our hard working team.
Thanks as always for everyone's support here.
I'll check with Paul re. MIDI files, don't see why this would be a problem and its a great suggestionm. I don't think the MIDI programming in the video above is anything special. Maybe the only thing you missed is when playing it in I tend to wind the tightness knob way in so it is synth-style responsive before dialling it back, and adjusting the pre-delay accordingly. This is when I carefully address the mic mixes too. Thats the workflow I've established by really putting this bad boy through its paces.
CH x
As mentioned in my video above this lib has a slightly steeper learning curve than other 'out of the box' style libs, it is a pro piece of kit. So it has taken me a good couple of weeks to really draw the best out. What disappoints me about the sweeping statements being made is that with it only being 24 hours old and at least an 8 hour DL is this fair enough time to draw a well considered conclusion about the lib? Particularly the really trolly ones about this being some kind of cynical marketing stunt. Cos that is what Spitfire has always been about for the last 10 years?? Paul and Christian ripping off and pulling fast ones on our friends, colleagues and heroes?
We've had some really foul comments here which is sad because we have amassed a team of over 40 individuals to deliver 6 years work, 2 years production, our biggest budget by far, and 6 months of intense UX research and design with UsTwo. Is it going to be perfect, of course not which is why it is on discount, and which is why I'm loving the brilliant and constructive feedback that we're getting.
Did we release it with a bug? Yes, the legato thing, and we're a bit red faced about it but it crept into the release version without us knowing, and it will be fixed in the best way that doesn't cause too much of a headache for you all. But again this is why we release v1.0s with a discount, to get your feedback, iron out the creases and work with you to get you what you need.
I also want to take this op to thank the dozens of amazing emails of support and congrats we've received from people from all over, including some of my childhood heroes. Its these words of encouragement that really buoy our hard working team.
Thanks as always for everyone's support here.
I'll check with Paul re. MIDI files, don't see why this would be a problem and its a great suggestionm. I don't think the MIDI programming in the video above is anything special. Maybe the only thing you missed is when playing it in I tend to wind the tightness knob way in so it is synth-style responsive before dialling it back, and adjusting the pre-delay accordingly. This is when I carefully address the mic mixes too. Thats the workflow I've established by really putting this bad boy through its paces.
CH x
lucky909091
Senior Member
Garry
Senior Member
Thanks Christian. I am a huge Spitfire fan, and made the suggestion out of all sincerity, and only because I feel your company is equally sincere. I have defended you and Spitfire many times here on VI-C. Since you gave my request credibility, please allow me to refine: if the MIDI file is all that can be released, that itself would be great, but if you release the Logic file, that would help even more, because we can then get a much better hands on sense of how you use this library, and because you are (quite rightly) encouraging people to reserve judgement until they have more fully understood its capabilities, which require a different approach than with other libraries, then any resources Spitfire can provide in this regard, will be of great mutual benefit.
Thank you for considering this - thoroughly appreciate the transparency of Spitfire, and the community you're building - which isn't always appreciated by all, but it truly is by some of us who get great pleasure from your products.
fretti
Senior Member
I have the same problem on mac (but I can't blame the engine or anything else, as my computer isn't the greatest), but for me it helped a lot to change the settings for "Preload Size" and "Stream Buffer Size" in the audio tab (if you haven't tried that already?).
