1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

A Komplete disaster in Cubase...

Discussion in 'Computer Technology and Setup' started by mdf25, Apr 8, 2010.

Thread Status:
Not open for further replies.
  1. mdf25

    mdf25 Forum Member

    Messages:
    154
    Hi all, having a few problems in getting Cubase to try and recognise some of my VST2 plugins on OS 10.5... This is really weird as it has only just recently happened. Here is what happened:

    I downloaded a load of free VST FX for OSX, and tested them all out. Everything worked fine apart from BlockFish (compressor freebie which got deleted as soon as i found the bug, superb sound it gave out when it was working though) and I had this huge long list of plugins that I downloaded.
    I then thought hey, I have way too many plugs for them to be left in this really long list down one column, so I went into the VST folder and made separate folders for things like Dynamics. Reverb etc and put all corresponding plugins back there. For the NI ones, I made a folder called Multi FX (there are FX versions of the full plugins like Kore2 FX and Absynth4 FX)
    I then went to start up cubase to see the plugins in their new areas, and it worked fine but several NI plugins were not there anymore, they were Absynth4 FX, Absynth4 Surround, KoreFX, Kore Player FX, Kore2 FX, FM8 FX, Pro53 FX, Reaktor5 Surround and Reaktor5 FX. Weirdly enough, B4 II FX and Guitar Rig 3 were still showing fine, and all the NI instruments like Kontakt and Massive, and all instrument versions of FM8 and Kore etc were still showing properly.

    I then looked around for a solution to my VST problem, and found that there exists a blacklist where potentially faulty plugins get recorded and are hidden from view even if they are present in your designated VST directory. I quit Cubase and deleted the blacklist as recommended by Steinberg on their support area, and started cubase up again. No luck.
    Next I tried putting the NI FX back in the place where they had been put originally and deleted the blacklist and all the VST info files. I then went back to open Cubase. Still nothing, and the blacklist had reappeared with the same plugins.
    So I then tried reinstalling all of the faulty plugins and leaving them where they were (deleting the blacklist and all VST info again, and removing all plugins and everything else) and did a reboot. Still nothing happened, and all the same plugins were still showing. I also had opened every last one in standalone first as recommended by NI before moving to Cubase.

    Is there any way that you can stop Cubase from blacklisting? I find it funny that Cubase lets faulty plugins like Blockfish through, which crashed it, and stops plugins like Absynth and others which have never had a problem running in cubase. I don't think it was anything to do with Blockfish, as i tried it once before with the same results but this disappearing act of the good plugins didn't happen, and thought it was because I downloaded an earlier version which wasn't compatible on Intel based Macs. I reckon it's a bug in the blacklisting... I am going to check for any viruses that might be messing with it. but on a mac chances are its very low... Has anybody got any suggestions as to what I can do? I would reinstall everything but that would take me 3 days solid (Komplete 5 took a day to just install it with all its sample content and to get all the kore drivers and guitar rig controller working) and it would be so frustrating if i do all that just to find that nothing changes. I hope steinberg makes some sort of 'trusted listing' which allows you to manually go through the plugins tick which ones you know to be working properly, and let cubase evaluate stuff like the freebies for bugs and glitches, as I find the plugin manager leaves the user with no options at all other than to refresh the plugin list which does not let you see the blacklisted plugins... Does this mean that when I get my Waves bundle, that the same thing would happen with this too? I really hope not as it may put me off cubase quite a lot, but not a lot of other DAWs have the features that Cubase does like VariAudio and would mean forking out even more cash to get a stable system which does the same things that cubase could (meaning I would have to get Melodyne or Waves Tune to compensate for the loss of variaudio and all of Cubase's extensive warp features, not to mention having to lose a lot of projects I am working on) and also put my trust in another DAW manufacturer... Which I don't want to do as Cubase is what I have been using for years and I have found it to be very good up to now.

    Im wondering though If I could use my older verson of Cubase AI4 and try and rewire that into cubase 5 if it doesnt have the blacklist issue like cubase 5 does... That way I could still use it and have the benefits of all the plugins and all the cubase features... And the best part is I wouldnt have to buy two licences for NI stuff as its all being used on one computer. Would this be a good workaround or would I be better off trying out rewiring Logic or Reason through it instead (after learning it and all that stuff as well...) so that I could also get the benefits of that DAW? I would rather stick with cubase but if its what works... Does anyone have any recommendations or solutions to my dilema? Maybe cubase 5.5 will sort the issue though. I know komplete is not the problem because it has been working well up to now.
     
  2. Kostekandreev

    Kostekandreev New Member

    Messages:
    19
    hm... I can onle say that my Cubase 4.5.2
    see 64 bit NI plugins as 32
    so I just gave it up cause I had no time for reinstalling - I had a few days before fliyng across ocean to work on next CD
    so I just use 32 bit version of Cubase - works
    actually it should be mentioned on Steinberg forum, cause of their crappy VST bridge...
    and tricky assinging multuple audiotracks to same input... or... ok I do not know much about variaudio cause I use Melodyne...
    but
    I really would like to have simple installer for NI updates where all dll files would be updated.. and there would be no need to check everything in standalone mode
    and after that just wonder why it still does not work like it should... :)
     
  3. procrastinator

    procrastinator NI Product Owner

    Messages:
    1,392
    Are the missing plugins listed in the VST 2.x Plugin Information List ? If yes maybe klicking on "update plugin info" could help.
     
  4. madkeys

    madkeys NI Product Owner

    Messages:
    17
    I changed my internal HD in my Macbook Pro for a bigger 640GB one which I then partitioned into two equal 320GB drives. I attempted to install komplete 5. However I then discovered that my DVD drive was faulty. I replaced faulty DVD drive with new one. Now my Komplete is Inkomplete (s'cuse the pun). Although my new DVD drive is fine with all other DVD/CD's it still spits out my Komplete 5 disc A.
    I'm running Snow Leopard and Cubase 4.5 on a 2.4GHZ Macbook Pro 'pre' Unibody with 6GB RAM. I do want to upgrade to Komplete 6 but initially would like to get Komplete 5 fully functioning.
    What are my options ? should I uninstall everything ? There is still the concern about the DVD not being recognised.
    Does the team think I might be best to upgrade to Cubase 5 ?
    http://www.timhinkley.com
    tim@timhinkley.com
     
  5. ew

    ew Moderator Moderator

    Messages:
    21,328
  6. madkeys

    madkeys NI Product Owner

    Messages:
    17
    sorry where did I cross post ?
     
  7. ew

    ew Moderator Moderator

    Messages:
    21,328
    In the thread I linked to. I'll quote from the forum rules:
    You asked your question in this thread, and started a new thread asking exactly the same thing.

    ew
     
  8. madkeys

    madkeys NI Product Owner

    Messages:
    17
    I'm very sorry, I didn't realise. Now can we get my komplete 5 installed please ?
     
Thread Status:
Not open for further replies.