< Back to IRCAM Forum

OM-SuperVP display initialization failed again after using a new key successful use

Dear Friend,

Again, it’s about the Supervp display Initialization failed.I consulted you(karim) last week. I don’t know if you remember. We tried a lot of things ,and finally you give me a new key, and it succeed that day.(picture 1)

But the next day when I opened OM again I used supervp, It can’t work which displayed “Initialization failed: please register an activation key…”. And all the programs in supervp I had done yesterday were gone, of course it’s not that important, The important thing is supervp display initialization failed. (picture 2,3)


So,I tried the previous method that you give me again on the computer terminal using the key that you gave me and it still didn’t work. (picture 4)

What can I do? It’s so weird…

My computer is Mac pro, inter Core i7, macOS13.7
OM7.4 and 7.3
Another thing is that when I save the program I did on supervp, I get an error (see picture 5) and can’t save it .I don’t know if this is related to the above question, so i offer it to you.

Best Regards
J

You have many confused things here.

  1. To be sure your supervp is authorized and i think it is please open a terminal and type:
    supervp -h

send theanswer

Best
K

Ok.the answer is: zsh: command not found:supervp-h

it is:
supervp -h

(wiht a space between supervp and -h

I didn’t do anythings. Just now I tried again, just type cd Desktop and then type supervp, and it worked.

But yesterday morning and this morning, I had typed supervp -h that displayed "Supervp::Initialization failed: please register an activation key… "

So weird… I also didn’t do anything yesterday night. I tried it at the terminal and it worked, but it didn’t work this morning. So I gust it will fail again tomorrow morning. I’m already convinced of that. :cry: It’s like being caught in a strange cycle.

Is there any way to know what the problem is?

Yes,

First: when calling supervp on terminal, this shows IT IS WORKING and no issues with the authorization.

Second: you shoild NOT authorized it everytime PLEASE!

third: You should set supervp and NOT SuperVP.app in om’s Externals preferences.

Best
K

1 Like

Thank you so much!!! :heart: :heart:
I changed OM Externals preferences setting because superevp is not available. I thought it would work, so I tried it. I usually set supervp, not SuperVp. app, and it loads automatically in OM Libraries.
Anyway, now I know. I’ll see if it works tomorrow.
I’m very sorry to bother you. Thany you for your patiently answer.
Have a nice day! :sun_with_face:

Best Regards
J

Dear IRCAM Support Team,

I’m sorry that recently my supervp is unusable again, repeatedly showing ::: SuperVP::Initialization failed: please register an activation key by using -init_key_file Ircam_Activation_Key.txt.

I’ve tried repeatedly these days but to no avail. I’m wondering if there’s something wrong with the key. So today I re-applied for a new key in my account and activated it in the terminal following the previous operation, but it showed that it could not be activated (see picture 1).

At the same time I also in Om/preferences/Externals/SuperVp/Options/go! I tried to activate it here but it didn’t work (see picture 2). May I ask what’s going on? How should I operate?

Besides, I don’t know why I received a key named Authorization this time. I remember it was called Activation before. I also tried to change the command “supervp-init_key_file Ircam_Activation_key.txt” in the terminal to “supervp-init_key_file Ircam_Authorization_key.txt” still doesn’t work.

The processor of my computer is inter Corei7, the system is MacOS Ventura13.7, and the SuperVp version is 2.103.13.

Best Regards
Jing


Dear Jing,

This problem is not related directly to OM. It is specific to the protection of supervp and apparently has some bug:

  1. The name of the authorization/activation is not important. What is important is to point to the correct name of the file. So it is irrelevant
  2. The authorization process doesn’t work in the OM preferences. Use only the authorization process from the Terminal.
  3. It could be that supevp was "sandboxed’ by Apple. This happened to me also.

So the best thing to do is to address this issue in the command line tools in a different thread here:

Best
K