You are here

Wave Editor/iLok/Flux problem, help please....

For current or would-be users of Apple Mac computers, with answers to many FAQs.

Wave Editor/iLok/Flux problem, help please....

Postby Jeraldo » Mon May 14, 2012 10:53 pm

I run Wave Editor (audiofile engineering).

I ran a demo of Verb Session (Flux/IRCAM) which ran great. The demo does not require iLok.

I bought a license, loaded it to iLok2, got rid of the demo version and installed the "real" version.
Now, when the plugin is selected, the app immediately freezes.

Other iLok software has run OK in WE.

Also, the "problem" plugin does run just fine in old versions of Peak LE and Amadeus Pro. So the license, iLok2, and so on seems to be OK. I've made sure everything is up to date on the iLok2.

Now I find that Wave Editor has some problems with some iLok protected plugins. I which they'd put that in BIG BOLD LETTERS over their web site so one would no plunge ahead with iLok plugins.

Anyway, enough complaining.

Does anyone know how I might go about getting this to work?

BTW, I've used Flux excellent freebies, but now that I've bought something I visited their tech support page and forms which are considerably less friendly than competitors. I'm not expecting much their-the automated mail machine said my issue would be investigated, and the priority was "low" and the severity "trivial." Be warned.

But the problem seems it lies with Wave Editor not Flux.

I've written audiofile, and they usually are very good at getting back-but I feel a little burned by them not being much more upfront about iLok problems. (I have run Lex iLok plugins in WE with no problems.) I have done the manual or forced plugin validation thing in WE.

Suggestions are welcome.

Do I sound desperate?
Jeraldo
Frequent Poster
Posts: 1022
Joined: Fri Sep 09, 2005 11:00 pm

Update

Postby Jeraldo » Tue May 15, 2012 1:25 am

Evidently something has gone terribly amiss with Wave Editor.

After removing Wave Editor and every file I could find associated with it, I reinstalled the application from scratch, after cleansing all caches, including audio, AU's, etc.

After a fresh install, both the AU Validator and VST Validator "unexpectedly quit" on app launch. This is without the iLok attached. So now, nothing but Apple's AU's are available.

I have recently done a security update, a flash update, and possibly an incremental system update in the past week. Perhaps something has happened with all of that.

Are other users having problems?

I'm sure I'll hear from audiofile soon-they've been consistently good with communication. Despite that niggle with the iLok thing...

So if I find out something useful, I'll post back.

To end on a slightly more positive note, my level of, um, "frustration!!" is proportional to how much I enjoy working with that application.
Jeraldo
Frequent Poster
Posts: 1022
Joined: Fri Sep 09, 2005 11:00 pm

Re: Update 2

Postby Jeraldo » Tue May 15, 2012 10:05 am

Update 2

Well, it seems to be Wave Editor.

I ran Wave Editor on my cloned HD that was done prior to all the recent updates and the same thing happened when loading the Flux/Ircam plugin.

Meanwhile, Reaper, Peak LE, and Amadeus Pro have no problems with the iLok protected plugin.

I hope audiofile will have a solution.


Any Wave Editor users using Flux/Ircam tools?
Jeraldo
Frequent Poster
Posts: 1022
Joined: Fri Sep 09, 2005 11:00 pm

Re: Update 2

Postby Jeraldo » Tue May 15, 2012 3:37 pm

Predictably, audiofile's support came very quickly and was effective.

Things are running well, and the issue is nearly closed.

I'll post finally when everything is clearly done, and with some comments that might save others some time with Flux and other plugins in WE and other applications.

Audiofile's support cannot be faulted, so far.
Jeraldo
Frequent Poster
Posts: 1022
Joined: Fri Sep 09, 2005 11:00 pm

Re: Update 2

Postby Jeraldo » Tue May 15, 2012 4:32 pm

The issue is now fully resolved, and audiofile-engineering gets only high marks! And they are quick.

There is a known issue with Wave Editor validating some (many?) iLok plugins.

Fortunately, the fix is very straightforward.

It involves using their Backline utility. The utility is free of charge for two weeks, and the problem has to be fixed only once. Among other things, Backline does some cache cleaning and resets, some of which are available in advanced options in more generic OSX utilities. However, I had those other utilities, and Backline got things that the others didn't. Becoming aware of the options in Backline was a bit of a side benefit, and it would be my very first step in fixing plugin problems in general, along with many other audio oddities in the OS and applications (and audio files).

Audiofile is fixing this in a relatively soon to be released incremental upgrade.

My one quible is that this issue and it's easy solution should be prominently displayed on the website-it save many hours of time for many people.

Flux: There are separate demo vs "real" plugins, so you don't really know if you'll have problems. But since the demo versions and the "real" versions validate differently (unlike Lexicon), there is a potential for problems. I assume that they do that so that people are not obligated to buy an iLok to try their products (unlike Lexicon). I was all for that approach-until I had unforeseen problems.

It's worth noting that Flux/IRCAM and audiofile-engineering are at the opposite ends of the continuum for support. Getting something from Flux is daunting and doubtful, and I only hope these relatively new products are kept working through OS changes. (As I like Flux plugins.)
Jeraldo
Frequent Poster
Posts: 1022
Joined: Fri Sep 09, 2005 11:00 pm

Re: Update 3 re Flux

Postby Jeraldo » Tue May 22, 2012 11:47 pm

Since I posted a doubtful expectation on Flux, I thought I should present a now more informed picture.

1. It is true that their support page is absolutely Byzantine, and it leaves one with little hope of response.

2. By happenstance, I discovered the personal email address of someone associated with Flux, who often is publicly "very enthusiastic" about their products.

3. His response was pretty quick, too, and he seemed just as enthusiastic to get the problem solved as he is in his encouragement of people to use the products!

So the impression of Flux support isn't any longer negative from my viewpoint, but if you can't get to someone and you're stuck with that support page.....
Jeraldo
Frequent Poster
Posts: 1022
Joined: Fri Sep 09, 2005 11:00 pm

Re: Update 3 re Flux

Postby Tui » Wed May 23, 2012 12:15 pm

Jeraldo wrote:
2. By happenstance, I discovered the personal email address of someone associated with Flux, who often is publicly "very enthusiastic" about their products.

3. His response was pretty quick, too, and he seemed just as enthusiastic to get the problem solved as he is in his encouragement of people to use the products!

In my experience, communications with the "enthusiastic" Flux associate (probably the same person that sometimes posts at GS) don't necessarily lead to any discernible action on the part of Flux. I hope you're more lucky than I was, though.
User avatar
Tui
Frequent Poster
Posts: 1067
Joined: Sun Sep 01, 2002 11:00 pm
Location: Chiang Mai, Thailand

Re: Update 3 re Flux

Postby Jeraldo » Wed May 23, 2012 2:30 pm

Tui wrote:

In my experience, communications with the "enthusiastic" Flux associate (probably the same person that sometimes posts at GS) don't necessarily lead to any discernible action on the part of Flux. I hope you're more lucky than I was, though.


Hi Tui:
Because I did get a response in a timely manner, I thought that I should at least note that because I may have given the impression they were unreachable.

I think it's fair to say, though, that your experience is not unusual, and, unfortunately, it seems most people's experience with their support is less than satisfactory.

For me, it comes down to what I need in a 'verb, and theirs is it.
Jeraldo
Frequent Poster
Posts: 1022
Joined: Fri Sep 09, 2005 11:00 pm


Who is online

Users browsing this forum: No registered users and 2 guests