[Answered] Producer Expanded and vst scanning

Author
Post
Essentials Only Full Version
silvercn
Max Output Level: -66 dBFS
  • Total Posts : 1238
  • Joined: 2007/12/04 12:14:24
  • Location: Midland, Texas
  • Status: offline
2011/10/07 19:06:44 (permalink)

[Answered] Producer Expanded and vst scanning

So that my program (32bit) loads up fast, I have the vst scanner turned off at this time.  When I download Expanded am I going to have to put scanner back on the first time I open the program after the upgrade - or will that not matter?
 
Thanks !
post edited by Willy Jones [Cakewalk] - 2011/10/08 10:17:22

Charles 
https://cnsacoustic.squarespace.com
https://www.reverbnation.com/charlessilverman


Charles S.
#1

6 Replies Related Threads
    garrigus
    Max Output Level: 0 dBFS
    • Total Posts : 8599
    • Joined: 2003/11/05 17:23:21
    • Location: www.garrigus.com
    • Status: offline
    Re:Producer Expanded and vst scanning 2011/10/07 19:22:05 (permalink)
    If you also purchase the PC4K, then yes, you'll need to scan after installing that. But you don't need to scan after installed X1 Expanded itself.

    You can do a manual scan from the Preferences dialog without having to put the auto scanning back on.

    Scott

    --
    Scott R. Garrigus - http://garrigus.com
    * Author of the Cakewalk Sonar and Sony Sound Forge Power book series: http://garrigus.com/?PowerBooks
    * Author of the Cakewalk Sonar ProAudioTutor video tutorial series: http://garrigus.com/?ProAudioTutor
    * Publisher of the DigiFreq free music technology newsletter: http://digifreq.com/?DigiFreq
    * Publisher of the NewTechReview free consumer technology newsletter: http://newtechreview.com/?NewTechReview

    #2
    silvercn
    Max Output Level: -66 dBFS
    • Total Posts : 1238
    • Joined: 2007/12/04 12:14:24
    • Location: Midland, Texas
    • Status: offline
    Re:Producer Expanded and vst scanning 2011/10/07 21:37:58 (permalink)
    Thanks Scott... !

    Charles 
    https://cnsacoustic.squarespace.com
    https://www.reverbnation.com/charlessilverman


    Charles S.
    #3
    Brandon Ryan [Roland]
    Max Output Level: -40.5 dBFS
    • Total Posts : 3458
    • Joined: 2003/11/06 03:29:12
    • Location: Los Angeles, CA
    • Status: offline
    Re:Producer Expanded and vst scanning 2011/10/08 02:39:17 (permalink)
    And I would experiment with just leaving the "scan on startup" on permanently.

    "The sky above the port was the color of television, tuned to a dead channel." WG

    SONAR Platinum | VS-700 | A-800 PRO | PCAL i7 with SSD running Windows 8 x64 | Samsung 27" LCD @ 1920x1080 | Blue Sky monitors with BMC | All kinds of other stuff
    #4
    gcolbert
    Max Output Level: -67 dBFS
    • Total Posts : 1176
    • Joined: 2010/11/13 18:34:06
    • Location: Windsor Mill, MD
    • Status: offline
    Re:Producer Expanded and vst scanning 2011/10/08 08:22:22 (permalink)
    I think there may be some enhancements in X1e that affect the performance of the VST scan.  The Scan-On-Startup seems to be much faster now in my system.  You may want to consider just keeping it on in X1e
     
     
    Glen
    #5
    silvercn
    Max Output Level: -66 dBFS
    • Total Posts : 1238
    • Joined: 2007/12/04 12:14:24
    • Location: Midland, Texas
    • Status: offline
    Re:Producer Expanded and vst scanning 2011/10/08 10:42:20 (permalink)
    Will try putting scan back on for a whileand see. Unless I had to scan after putting in a new vst, it was nice and quick to have it off. I need to thin my vsts down anyway, I have way too many collected anyway!!

    Charles 
    https://cnsacoustic.squarespace.com
    https://www.reverbnation.com/charlessilverman


    Charles S.
    #6
    Grumbleweed_
    Max Output Level: -72 dBFS
    • Total Posts : 915
    • Joined: 2007/11/01 09:13:58
    • Location: Southampton, England
    • Status: offline
    Re:Producer Expanded and vst scanning 2011/10/09 15:16:27 (permalink)
    garrigus
    If you also purchase the PC4K, then yes, you'll need to scan after installing that.
    But you don't need to scan after installed X1 Expanded itself.
    I have to disagree with this. When I did the 64 bit version X1 did a mini scan and it all worked. Installing the 32 bit version left me with no Saturation Knob (painful, I know). I thought it was broken but a rescan was suggested and all was well. 
     
    I would suggest a scan is required no matter what version is installed.
     
    Grum.

    Grumbleweed on Soundcloud
    Grumbleweed on Bandcamp
    Grumbleweed on Soundclick

    Windows 10 Pro (64 bit), 3770K i7, 8 GB ram, Focusrite Saffire Pro 14, Cubase 9.5, Reason 10, CbB.
    #7
    Jump to:
    © 2024 APG vNext Commercial Version 5.1