@JoPo:
M7.6.14 is ready and should fix the discussed security leak. I'd appreciate if you would help testing it.
Please install the new MUX 7.6.14 VST, see viewtopic.php?p=6960818#p6960818
Then use it for at least 15-30 minutes and let me know how that works.
Thx.
Vst plugin output number
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRist
- Topic Starter
- 125 posts since 12 Mar, 2004
Oh ! I really don't have time right now ! But be sure that I'll do the test tomorrow ! I'm not working, I'll try it the whole day ! 
-
- KVRist
- Topic Starter
- 125 posts since 12 Mar, 2004
Hi, Jo !
I'm working on my track since 2 hours, now and no issue at all. In this project, there is no less than 4 Mux modular, 3 as intrument + 1 as insert processor.
It is bliss !
I checked and don't see any serial key in the mainsetup file anymore. You're a damn fast worker ! Same mistake as I did is now impossible to happen again.
Thanks a lot !
I'm working on my track since 2 hours, now and no issue at all. In this project, there is no less than 4 Mux modular, 3 as intrument + 1 as insert processor.
It is bliss !
I checked and don't see any serial key in the mainsetup file anymore. You're a damn fast worker ! Same mistake as I did is now impossible to happen again.
Thanks a lot !
-
- KVRist
- Topic Starter
- 125 posts since 12 Mar, 2004
Oh ! I have a very strange behavior, now !
Not easy to explain...
I'm using a mux instrument to control vca modules in my Scope system. Those vca's are part of a simple synth modular patch I made in Scope to control volume with a very accurate timing. So, the mux patch is a simple constant modulation converted in audio signal, through 1 asio channel, going to Scope vca's.
Sometimes the volume signal lowers without any reason ! I checked the audio signal inside mux with a level meter, it didn't move ! But one's outside mux, it lowers, apparently randomly.
I use another mux instrument in wich I loaded 2 lounge lizard piano for modulating them with automation inside mux. Sometimes, like a big reverb sound raise up, like a big wave on a beach, then lowers. It does that for 1 or 2 seconds.
I've never had that kind of strange behavior before ! I closed & restart again cubase and for the moment, it seems to not do those again.
Not easy to explain...
I'm using a mux instrument to control vca modules in my Scope system. Those vca's are part of a simple synth modular patch I made in Scope to control volume with a very accurate timing. So, the mux patch is a simple constant modulation converted in audio signal, through 1 asio channel, going to Scope vca's.
Sometimes the volume signal lowers without any reason ! I checked the audio signal inside mux with a level meter, it didn't move ! But one's outside mux, it lowers, apparently randomly.
I use another mux instrument in wich I loaded 2 lounge lizard piano for modulating them with automation inside mux. Sometimes, like a big reverb sound raise up, like a big wave on a beach, then lowers. It does that for 1 or 2 seconds.
I've never had that kind of strange behavior before ! I closed & restart again cubase and for the moment, it seems to not do those again.
-
- KVRist
- Topic Starter
- 125 posts since 12 Mar, 2004
Impossible for me to know where it came from. For the moment, after having restarted cubase, it works fine.
The strange behavior I described happend after at least 2 hours of correct cubase work.
The strange behavior I described happend after at least 2 hours of correct cubase work.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
That's expected behavior because your previous user key has been blacklisted.
The only thing that i find a bit strange is that the demo noise only came after so long time.
Maybe that's because it was an already existing project and you just loaded it and didn't touch MUX a lot?
I've emailed you a new MUX 7 user key.
The only thing that i find a bit strange is that the demo noise only came after so long time.
Maybe that's because it was an already existing project and you just loaded it and didn't touch MUX a lot?
I've emailed you a new MUX 7 user key.
-
- KVRist
- Topic Starter
- 125 posts since 12 Mar, 2004
Yes. That's right : it was non touched mux patches. Funny ! That's what I thought : like if the plugin was in demo mode !
Before entering the new key, I tried something since after reloading cubase, there was no problem anymore, I just made some changes in a patch and it happend again. That's certainly what I did the first time.
And now with the new keys, nomore big reverb wave nor sound lowering. Thanks a lot, Jo !
If one day, you need someone to help you to do anything, don't hesitate to contact me.
Before entering the new key, I tried something since after reloading cubase, there was no problem anymore, I just made some changes in a patch and it happend again. That's certainly what I did the first time.
And now with the new keys, nomore big reverb wave nor sound lowering. Thanks a lot, Jo !
If one day, you need someone to help you to do anything, don't hesitate to contact me.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
You can always help by further making MuLab and MUX Modular more known via fora and social media, and by testing new test versions and reporting any issues. Thanks.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Why?Pyrotek45 wrote:Im not for tying the key to the system id. I hate that system.
I can already say that changing some hardware in your computer would not cause the need for a new user key. The user key would be linked to the OS installation. You would only need a new user key when you completely reinstall your OS, or do a radical OS restore, or when you go for a new computer of course.
(to avoid confusion: nothing has been decided yet, i'm just evaluating the option)
That doesn't really differ from the current user key system where it is linked to the user's name, does it?Just tie it to an email. Blamo.
-
- KVRist
- Topic Starter
- 125 posts since 12 Mar, 2004
--> Pyrotek.
As the brilliant guy who made THE mistake, I had the honnor to be one of the firsts to test the new serial key !
There is absolutely no difference with before ! On the other hand, I don't know at all what or how the serial key will react to new computer hardware.
For sending me new serial, Jo didn't ask me any ID number. So I'm unable to explain if the new serial key system works but it works very well and there is nomore the serial number in the mainsetup file. This will avoid to involuntarily show it to anyone.
I think it's a good system much safer.
--> Jo (mutools) Will we have to ask for a new serial key when changing computer hardware ?
As the brilliant guy who made THE mistake, I had the honnor to be one of the firsts to test the new serial key !
There is absolutely no difference with before ! On the other hand, I don't know at all what or how the serial key will react to new computer hardware.
For sending me new serial, Jo didn't ask me any ID number. So I'm unable to explain if the new serial key system works but it works very well and there is nomore the serial number in the mainsetup file. This will avoid to involuntarily show it to anyone.
I think it's a good system much safer.
--> Jo (mutools) Will we have to ask for a new serial key when changing computer hardware ?
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Jopo, Please read more carefully.
The new user key system we're talking about is about a possible new key system for a future version (earliest M8), it has nothing to do with M7. Also your last question was already answered before your question.
The new user key system we're talking about is about a possible new key system for a future version (earliest M8), it has nothing to do with M7. Also your last question was already answered before your question.
-
- KVRist
- 401 posts since 4 Nov, 2013
i reformat my computer twice a year(i know i know thats a lot for some people). last time i had to use that system it didn't work, even after i got a new key (bazzism) and its a pain to deal with, while all my other vst's are reinstalling just fine. WHy not have a system like NI, or sylenth or synapse, or d16 or how about no copy protection at all? just give each of your customers their own install file.(sure there are risk but saw studio does it and their software is thousands of dollars.)
~Pyrotek45
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Wow, i'm surprisedPyrotek45 wrote:i reformat my computer twice a year
But it's good that you mention it, there may be more people having good reasons to do so.
So i have to take that into account.
I assume that means you're selectively choosing plugins that do not link to the hardware/OS, right?last time i had to use that system it didn't work, even after i got a new key (bazzism) and its a pain to deal with, while all my other vst's are reinstalling just fine.
I'm quite sure there are many other DAWs/plugins that link to the hardware/OS, right?
A complete Service Center application??WHy not have a system like NI
And are you sure NI products are not linked to the hardware/OS?
What user key strategy do they use?sylenth or synapse, or d16
I think that's too idealistic = unrealistic.how about no copy protection at all?
And not a good feel for paying users, and not a good feel for me.
Definitely not an option.
That's how it works now. Be it that it's not a file but a long key, but in essence that's the same system.just give each of your customers their own install file.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Brainstorming further on this, what about this idea:
The user key is linked to the OS and to the hardware.
If only one of them changes, the user key is still valid.
But if both the OS and hardware do not match anymore, it's reasonable to assume that it's about a new system and so a new user key is necessary.
So in case you change some hardware components on your machine, no new user key necessary.
If you reformat your system drive and reinstall your OS each month, no new user key necessary.
If both the OS is reinstalled and the hardware has been changed, then this really is another system and then yes a new user key would be necessary.
Sounds fair, right?
Let me add the very reason why i'm evaluating linking the user key to the computer:
Imagine someone accidentally / intentionally shares his user key on the web. Then i cannot do anything about that except for building a new version and blacklisting that user key. But even then the previous version will still work fine with the leaked key. And that's also assuming i do know about that leaked user key. It's not my ambition to hunt the net for leaked user keys. I prefer building new features.
The user key is linked to the OS and to the hardware.
If only one of them changes, the user key is still valid.
But if both the OS and hardware do not match anymore, it's reasonable to assume that it's about a new system and so a new user key is necessary.
So in case you change some hardware components on your machine, no new user key necessary.
If you reformat your system drive and reinstall your OS each month, no new user key necessary.
If both the OS is reinstalled and the hardware has been changed, then this really is another system and then yes a new user key would be necessary.
Sounds fair, right?
Let me add the very reason why i'm evaluating linking the user key to the computer:
Imagine someone accidentally / intentionally shares his user key on the web. Then i cannot do anything about that except for building a new version and blacklisting that user key. But even then the previous version will still work fine with the leaked key. And that's also assuming i do know about that leaked user key. It's not my ambition to hunt the net for leaked user keys. I prefer building new features.