Jump to content

simon

Members
  • Posts

    2,711
  • Joined

  • Days Won

    7

Posts posted by simon

  1. looks like those who invested in the FL/UVI Power Bundle from earlier this year get zilch.

    These never got added to your UVI account, you just got iLok licences - I emailed support at the time and they said weren't added to your account "by design" for "technical reasons"

    Meaning they won't qualify for upgrades either I suspect ?

     

    • Sad 2
  2. looks like SSL are now forcing you to use their download manager !  has anyone got a direct link ?

    EDIT

    found it - under the "support" part of their website - annoying !

    • Thanks 1
  3. 9 minutes ago, Fwrend said:

    I have no errors listed in the log files.  

    that's very interesting - are you on windows and running plugin  v1.7 ? and which version of BBCSO (pro/core/discover) ?

    on Windows the BBCSO plugin logs are in the folder c:\users\<username>\appdata\roaming\com.spitfireaudio\

    Each time the plugin is initialised it generates a new log (.txt file) with a day/date in the file name.

  4. 1 minute ago, Fwrend said:

    I think that's what did it for me after a lot of trial and error.  Thanks!  The plugin now shows as 1.7 when opening inside the DAW and the plugin doesn't show in the list inside SA installer.  No piano for me.

    do you get the errors in the log file as per that VI forum post ?   - I see another post from a couple of days ago on the SpitfireAudio forum saying something similar.    I suspect something is broken under the hood.

  5. 2 minutes ago, Keni said:

    Actually, I don't think so... The problem turns out to be that Cake's plugin manager has the old common file path for the plugin's location instead of the new foldered location. I fixed mine brute force copying the vst3 dll to the common vst3 folder... Then Cake loads it fine, but next update I'll have to fix it again etc... so I will probably go the long route and do a reset, followed by a Plugin manager Re-Scan All Plugins (How I hate doing this!) So that it scans for the new location...

    that's a slightly different issue - The VI thread mentions that the old v1.5 VST3 plugin might not get overwritten as the v1.7 VST3 plugin gets relocated to a new subfolder. 

     

  6. 2 hours ago, locrian said:

    Did the update break it?

    updating the various contents to 1.7 but leaving the plugin at 1.5 broke it for me.  I'm not given an option to update that to 1,7

  7. 6 minutes ago, locrian said:

    the latest update may cause the plugin and preset/sample files to become 'out-of-sync'.

    FYI - my BBCSO Pro is currently broken after the update (windows 10 - Nuendo 11/12)

  8. 18 minutes ago, iNate said:

    "still maintain[ed], bug fixed, etc"

    it's really not being actively maintained and as I say, no code updates for 2 years - but obviously you are welcome to your opinion.

     

  9. 13 hours ago, iNate said:

    eLCC is still maintain, bug fixed, etc

    not really - the last Mac bug fix was in 2021.

    7 hours ago, Marina said:

    so it kind of looks more than coincidence that an eLCC update appears on the very same day of the SL 10 release.

    it was a coincidence.  The eLCC update is actually a couple of days old.

    There are very frequent updates to eLCC and this is the 4th this year.  They are all basically database updates, the licensing code doesn't change.   Looks like this last database change was to amend the status of licences that have been upgraded to SAM.

    • Like 1
  10. 2 minutes ago, cclarry said:

    Hmmmm..even the release notes say that it was released today, but I only installed the Kontakt 
    update.  Maybe NA installed them both at the same time....what do I know...I'm old

    look at the date stamps on the .exe files ?

    • Like 1
  11. 55 minutes ago, cclarry said:

    Well I'm not a Beta Tester... and I already had that version installed so I have no idea how that's possible!

    very odd ? - I'd checked this morning (UK) and there were no updates,  both appeared for me a couple of hours ago.

     

    • Like 1
  12. 6 minutes ago, locrian said:

    Does "Zoom Scaling" mean I can now use my mouse wheel to increase the GUI to any arbitray size?

    looks like you can pick: 50 - 75 - 100 (etc) %  - it's not arbitrary and it's the entire GUI, you can't just zoom the instrument window.

    • Like 1
  13. 18 minutes ago, Brian Lawler said:

    NO, it is not your machine.  Others have posted about the loooong load times for Kontak7, but not nearly as many as I would have expected, so there are at least some of us.  Kontakt 7 (empty) takes at least 25 seconds to load for me, regardless of DAW.  Kontakt 6 loads in less than 2 seconds.  Subsequent loads of 7 after the first one are fast, so it must have something to do with the file parsing that doesn't happen from cache.   I followed some suggested changes like clearing out some XML files and excepting Kontakt folders from AV scans, but no improvement.

    I think it's possible that it has something to do with windows defender - seems to spend a lot of time scanning when loading up and I see a lot of defender CPU usage.

    And yes, always quicker on 2nd load (like v6) - again because defender has already scanned (I think)

    • Like 1
  14. 40 minutes ago, lawajava said:

    It’s probably just my machine. I have some support requests in to NI (and they have been responding back which is nice).  It takes an abnormally long time for me to load Kontakt 7.  Didn’t happen before. Kontakt 6 opens instantly.  Again, maybe something particular to my machine and not a general problem for others.

    takes much longer on my (windows 10) system too.

  15. 12 minutes ago, David Jameson said:

    I will take that bet. Any amount you like!

    well that bet is gonna cost me around $150 so v4.5.9 needs to have an amazing feature to justify that...and I'm still not giving you a cent - PA customers should get that for free as WE'VE PAID FOR IT !  As you've said "it was your mistake" !

    to be honest I'd rather you posted explaining why you are asking your customers to pay twice ?

    and why you are charging a $15 admin fee - what's the justification for that ?  We can buy plugins cheaper than your 'admin fee'.

    it's already been pointed out that you've known about PA's pricing for SEVERAL YEARS.

     

     

     

    • Like 1
×
×
  • Create New...