Jump to content

fwrend

Members
  • Posts

    210
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Kansas

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

fwrend's Achievements

Advanced Member

Advanced Member (3/8)

  1. UPDATE: Success (32 bit) & Failure (64 bit). I have been able to get Independence Pro Premium library accessible on my Desktop PC. I followed the directions in the thread Terry links to above. I did NOT install along within the ProX 6 Suite install package. IOW, I ran all of the Independence files prior to installing ProX 6 Suite. However, I have already been there and done that and it doesn't make a difference. Standalone - The standalone version opens and runs great ONLY in the 32 bit version. When trying to run the 64 bit version, I get the infamous "can't find the file..." error. Within the 64 bit version, I also get an "Activate Independence Pro" button (doesn't show up in the 32 bit version). Pressing this button does nothing but change color when pushed - it doesn't initiate activation whatsoever. This doesn't show up within Sam ProX 6 Independence Live - same problems as the Standalone. 32 bit version works great. DAW - SAMPLITUDE: Independence has always ran fine within Samplitude (64 bit version is what opens I assume since that is how I installed ProX 6 Suite). REAPER: only the 64 bit VSTi showed up. I looked in my VST folders and noticed both the 32 bit & 64 bit Independence.dll's were named exactly the same. I changed their names to Independence32.dll & Independence64.dll respectively. Upon opening Reaper and VST scan, Reaper now showed the 32 bit version, i.e. Independence (x86) (see image below). Independence opened and ALL instruments loaded perfectly. STUDIO ONE 5.5 & CAKEWALK by Bandlab: wouldn't pick up the 32 bit version at all and the 64 bit version ran as described in Standalone description above. Summary: I am happy to be able to use Independence as I'd like (64 bit notwithstanding) but done wasting my time trying. Perhaps (and hopefully) this will help others and we can only wish that MAGIX & devs can clean this all up. Caveat: I noticed recently that the Best Service Engine is obviously based on the same code provided by MAGIX. I sent an inquiry to support who stated "You can use engine libraries in Independence but not vice versa. It is not supported anymore since an early version of engine 2."
  2. @Sean DiMaria, I am curious as to whether you are able to load Independence within other DAWs, e.g. Reaper, Cubase, Studio One, etc.? EDIT: To answer my own question, following Option 1 instructions above, I was successful installing on my Surface Pro 4 and Independence runs as expected in both Standalone and as a VSTi inside my DAWs. IOW: 1 - I installed the Standard Pro version (3.5) as instructed. I opened Independence and activated using my Standard Pro P2 license and then closed Independence. 2 - I copied my library over to the default location. 3 - I opened Independence again and made sure the library location was set in Preferences/Library. 4 - I went to load an instrument and was prompted to Activate/Register the library where I inserted my Pro Premium P2 license. 5 - All GOOD! Caveat - I had completely removed all things Independence AND Samplitude Pro X3-6 from my Surface Pro 4 so basically started from scratch.
  3. Hi @TerryBritton, just seeing this. Before I attempt this again, can you please clarify? Specifically, can you now run Independence both in standalone AND within other DAWs, e.g. Repear or Studio One? I am running the 3.5 version which works fine in Samplitude and also as standalone but it will not run in any of my other DAWs as it should (or is purported to). EDIT: I tried to install 3.6 per these instructions but was unsuccessful. I reverted back to 3.5 with some success - see next post.
  4. Yes, very frustrating. I somehow got it working on my desktop DAW (standalone & plug) but could not get it configured correctly on my Surface Pro 4. I can't recall how as it seemed so convoluted a process trying to find the right combonation of versions and loading sequence. I'm using this version if it helps any.
  5. Yep, I couldn't remember which it was but support was the one that provided it. Typical MAGIX confusion LOL.
  6. MAGIX Pro Support <prosupport@magix.net> is who sent my upgrade serial number. Try that.
  7. No problem, great to hear it's working the way it should!
  8. Go to https://www.vegascreativesoftware.com/int/business-solutions/audio-production/ and scroll down to:
  9. Posted just now Well, while I was successful on my Surface Pro4, I was still not able to activate Independence Pro Premium Suite (standalone) on my Desktop. HOWEVER, last night I decided to strip my computer of all things Samplitude and Independence. I then started the install process of Independence. I got the "cannot find C:\Program Files (x86)\Common Files\MAGIX Services\Independence Libraries\RegIndBundle.exe" which aborted the install. I had saved those files just in case so I replaced them. Install continued without problem. Activating Independence showed that it was already registered and it activated fine. HOWEVER, trying to load an instrument gave me the infamous; On a whim, I decided to try a different Independence.exe. These are found in C:\Program Files (x86)\MAGIX\Independence and look like: Of course, my system is strictly a 64 bit install and I run nearly everything at 64 bit and that is the application that loads when I choose Independence. So, I decided to select the non-64 application file which I assume to be the 32 bit version. Both Independence and Independence Live 32 applications open, allowed activation, and work perfectly! I can access all of the sounds available in the Pro Premium Suite in standalone - GREAT! I pinned both 32 bit apps to the Start menu to have direct access. Now, the NEW problem is that none of my other DAWs pickup on the 32 bit Independence VSTs for some reason though they are there and in the scan path. Only the 64 bit versions are available and they still do not load the Independence instruments. I re-installed Sam Pro X5 and the 64 bit version works just fine in Samplitude. BTW, this is the 3.5.0.285 (Dec. 04, 2017) version. With it working somewhat, I'm nervous about now trying to install the newer 3.6 version but I will and report back. Not perfect nor what I paid for but thought this might help someone. UPDATE: I tried install the 3.6 version which uninstalled the 3.5 version and replaced it BUT once again, neither the 64 bit nor the 32 bit versions would load instruments. I used Windows "Add and Remove" app to uninstall the 3.6 version and re-installed the 3.5 version and now (thankfully) I'm back to only 32 bit standalone versions working properly. What a joke!
  10. Well, while I was successful on my Surface Pro4, I was still not able to activate Independence Pro Premium Suite (standalone) on my Desktop. HOWEVER, last night I decided to strip my computer of all things Samplitude and Independence. I then started the install process of Independence. I got the "cannot find C:\Program Files (x86)\Common Files\MAGIX Services\Independence Libraries\RegIndBundle.exe" which aborted the install. I had saved those files just in case so I replaced them. Install continued without problem. Activating Independence showed that it was already registered and it activated fine. HOWEVER, trying to load an instrument gave me the infamous; On a whim, I decided to try a different Independence.exe. These are found in C:\Program Files (x86)\MAGIX\Independence and look like: Of course, my system is strictly a 64 bit install and I run nearly everything at 64 bit and that is the application that loads when I choose Independence. So, I decided to select the non-64 application file which I assume to be the 32 bit version. Both Independence and Independence Live 32 applications open, allowed activation, and work perfectly! I can access all of the sounds available in the Pro Premium Suite in standalone - GREAT! I pinned both 32 bit apps to the Start menu to have direct access. Now, the NEW problem is that none of my other DAWs pickup on the 32 bit Independence VSTs for some reason though they are there and in the scan path. Only the 64 bit versions are available and they still do not load the Independence instruments. I re-installed Sam Pro X5 and the 64 bit version works just fine in Samplitude. BTW, this is the 3.5.0.285 (Dec. 04, 2017) version. With it working somewhat, I'm nervous about now trying to install the newer 3.6 version but I will and report back. Not perfect nor what I paid for but thought this might help someone. UPDATE: I tried install the 3.6 version which uninstalled the 3.5 version and replaced it BUT once again, neither the 64 bit nor the 32 bit versions would load instruments. I used Windows "Add and Remove" app to uninstall the 3.6 version and re-installed the 3.5 version and now (thankfully) I'm back to only 32 bit standalone versions working properly. What a joke!
  11. HI @Sarband I just tried doing what you described and it worked as expected here on Sam Pro X5 version 208. My process was to start with the already included 8 MonoTrack 8 IO template. I armed all tracks making sure inputs were correct (already set to 1-8 on my interface). Signals registered fine. From the menu dropdown list, I selected File/More/Save Project as Template. I closed Sam and reopened selecting my newly saved template. VIP loaded armed and ready. I test recorded and all worked properly.
  12. Sorry, I don't have an answer but you might read through this thread as it pertains to your inquiry: Working with Solo Modes & the Monitor Bus - Pro X5 - Tutorial - Tips&Tricks - MAGIX Samplitude & Sequoia Board
  13. ANSWERED: Upgrade to Independence Pro Premium Suite VST from limited version in Samplitude Pro X5 Suite - MAGIX VST Plug-ins (English) - MAGIX Samplitude & Sequoia Board This should be a sticky in this forum!
  14. @Sean DiMaria Thank You, Thank You, Thank You!!! This should be a sticky at the very least - in this forum, the Independence forum, and the Beginner forum. In reality, MAGIX should have made this crystal clear from the beginning!! I followed your Option 2 and it worked like a charm. Cheers!!
×
×
  • Create New...