Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Logic Pro X not recognizing VEP in High Sierra
Last post Tue, Jun 12 2018 by Ben Ripley, 14 replies.
Options
Go to last post
Posted on Tue, May 15 2018 09:59
by Rasmus Faber
Joined on Mon, Jul 16 2007, Stockholm, Sweden, Posts 49

Hello!

After upgrading to High Sierra, Logic no longer "sees" the VEP plugin on the master computer. The slave has High Sierra also and works with no issues.

I've updated to 6.0.17011, but still no luck.

The component files reads that they are just 5k in size, and in the installation window, the file size of the AU plugin shows as 0MB, is this how it should be? (pic attached)

Help is much appreaciated!

Rasmus Faber attached the following image(s):
SkärmavbildU00202018-05-15U0020kl.U002011.52.40.png (193kb) downloaded 2 time(s).

You cannot view/download attachments. Try to login or register.
Posted on Wed, May 16 2018 17:01
by Ben Ripley
Joined on Mon, May 14 2018, Posts 8

I just installed today and am having the same problem. AUs are showing as 5k size in /Library/Audio/Plug-Ins/Components/. They are not shown in the Logic plugin manager.

I am running High Sierra also using v6.0.17011 (May 7, 2018). Could this be a regression/related to this thread?

I installed the VST version as well and they are working as expected in Cubase.

Any ideas?

Posted on Sat, May 19 2018 18:17
by Rasmus Faber
Joined on Mon, Jul 16 2007, Stockholm, Sweden, Posts 49

"glad" I'm not the only one with this problem.. However, thread linked to above seems to have solved the OP's problem, which isn't the case for use obviously.

Hope to get some help on this soon!

Posted on Tue, May 22 2018 21:27
by toddpersen
Joined on Tue, May 22 2018, Posts 2

I just bought the Symphonic Cube a couple weeks ago and am having the same issue in Logic Pro X on High Sierra with VI/VE v6.0.16999 (Apr 30, 2018). The standalone player works just fine.

I don't see v6.0.17011 as an available download for me - is that a Pro-only version?

I sent in an email to support as well. Hopefully they can shed some light on the issue.

Posted on Fri, May 25 2018 08:59
by Rasmus Faber
Joined on Mon, Jul 16 2007, Stockholm, Sweden, Posts 49

Hmm.. Anyone from the team here who could chime in and let us know if a solution is underway?

Posted on Fri, May 25 2018 20:22
by toddpersen
Joined on Tue, May 22 2018, Posts 2

VSL Support wrote me back and suggested I just try rescanning plugins in Logic. That initially didn't work for me, but restarting and then rescanning seemed to do the trick, though I'm not sure exactly why. This caused both VI and VI Pro to work correctly for me.

If the problem you're having is isolated to VEP, I think my report may have been a red herring. Sorry!

Posted on Fri, May 25 2018 21:22
by Ben Ripley
Joined on Mon, May 14 2018, Posts 8

Todd, I've rescanned several times with no change. I wouldn't expect the logic scan to see the AUs since they're only 5k in size. It seems the installer perhaps didn't copy them correctly or something.

Any update on this VSL team? Is this something you can reproduce? 

Posted on Mon, May 28 2018 09:03
by Rasmus Faber
Joined on Mon, Jul 16 2007, Stockholm, Sweden, Posts 49

Still havent tried rescanning yet because of massive number of plugins and above poster posting his results. Need some sort of confirmation from VSL team at least re the file size..

Posted on Wed, May 30 2018 19:12
by Ben Ripley
Joined on Mon, May 14 2018, Posts 8

It appears that recently others are having a similar issue with the VSL AUs and High Sierra. 

Posted on Fri, Jun 08 2018 10:46
by Rasmus Faber
Joined on Mon, Jul 16 2007, Stockholm, Sweden, Posts 49

This is really troubling. Anyone care to comment from VSL team? I'm just lucky I dont have to start an orchestral project just yet, but its just a matter of time before this is gonna be a big issue.. Other people must be going frantic as well??

Re-scanning all plugins is a bad option at this point, esp. with close to 1000 plugs, and it doesnt seem to work for others. But most importantly, the size of the component file (being 5k in size) hasnt been adressed by the team in the other thread either (right?). Seems this is likely the culprit, no?

Posted on Sat, Jun 09 2018 13:46
by Ben Ripley
Joined on Mon, May 14 2018, Posts 8

I picked up VEPro in mid-May to start building up a larger template. I wasn't able to use it with Logic due to this problem so I downloaded a trial of Cubase in the hopes that I could at least work on building up the back-end of the template while this was being worked out. My 30 day Cubase trial expires in 3 days and I still have no idea if anyone is even looking at this.

Recap: The problem seems to be related to the installation of the AU component files themselves...

  • There is another unresolved thread of users that are also experiencing this problem
  • The installed component files are only 5k 
  • I have already rescanned my AUs. This made no difference.
  • I've tried uninstalling and re-downloading and re-running the installer
  • I would be happy to try out any new (or older) VEPro installer versions to see if this makes a difference.

Do the VSL team follow these forums? Is there any other support mechanism?

Any kind of response to let us know that you are at least working on this problem would help...

Please advise,

Ben

Posted on Sun, Jun 10 2018 03:58
by RLD
Joined on Thu, Jan 26 2017, Posts 54

Post your problem at

Posted on Sun, Jun 10 2018 13:10
by Ben Ripley
Joined on Mon, May 14 2018, Posts 8

Thanks RLD. Found that and sent an email there yesterday. I'll post here if I am able to resolve.

Posted on Tue, Jun 12 2018 17:00
by Ben Ripley
Joined on Mon, May 14 2018, Posts 8

Guys, the VSL team sent me a "High Sierra Compatibility Layer" installer. This is not supposed to be required for compatibility with High Sierra anymore but installing it has fixed the problem for me. The VSL AUs are showing up in the plugin manager and I am now communicating with my slave!

Hope this helps!

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.