OP-X 2 and 3, change patch random problem

Gig Performer on Windows
42

Were you able to replicate the issue?

43

I didn’t think to use 1. That seems to have stopped the problem. Thank you!

44

Oh, no, that’s not good we want to figure out how to reproduce the issue for Peter to fix it for everybody. We don’t want a kind of workaround for you only. Please give us your settings to reproduce the issue with the gig file provided by Peter.

45

So finally, don’t use 1 :disappointed_relieved:

46

Ok I’ll try to explain again.

  1. Use Peter’s gig file or use your own. Simply use 10 Rackspaces, each with one instance of OPX Pro 2 or 3. Save each with a different patch.

  2. Turn on Predictive loading (if it’s not already on) and set it to 3.

  3. Now just randomly, one at a time, change to different Rackspaces. After each respective Rackspace loads, open up the OP-X plugin and see if that patch is correct to what it should be.

If you do this truely randomly throughout the Rackspaces, you should be able to replicate the issue pretty fast.

47

I confirm I could reproduce the issue. I just had the Arpeggio preset « duplicated » to the Luftballons Strings. :+1:

1 Like
48

OK - so why can’t Peter reproduce the problem?

49

I don’t know, I just sent him the procedure using Predictive Loading with a depth of three. Not sure he tested with Predictive Loading enabled.

50

I was beginning to think I was losing my mind! Lol

51

I had the issue before without using Predictive Loading, so I believe you, no question. But, I never could reproduce it easily.

52

Peter could reproduce the issue and will probably have to talk with you.

53

Sounds good. thanks

54

I was also able to replicate the problem - just like 6 years ago when I unfortunately had to stop using OP-X II live because the problem could never be solved back then.

Great to hear that Peter was able to recreate it and that there’s new hope.

1 Like
55

Hi GP and OP-X Pro users (like @Basty85, @SirTommes, @Krucible, @tripleB, @mikelupo, @Beatlab, @jazzundso, @ahutnick, @jeebustrain, @Milesmf, @billw, @waltercruz, @Tsunami.Warning, @DKnight71), you might get some very good news with the next OP-X Pro 3 update! Stay tuned :wink:

4 Likes
56

Oh? I’ve been using the op-x pro 3 since it came out with no issues. Don’t jinx it. :slight_smile:

57

Our aim here is simply to help make it more robust. :crossed_fingers:

1 Like
58

I have stopped using OP-X Pro inside GP. I didn’t even bother trying v3 (It does work great on my DAW computer though). This is a good sign, though.

59

In the next V3 update, you probably can think of using it again… :wink:

2 Likes
60

of course! I was just responding because I was tagged a bit back. I’d love to start using it live again. It’s still the best Oberheim VST out there.

61

EDIT: 1.04 adds another bug, don’t use it! Use 1.05 instead!

Hi guys, I just received a message from Peter, the OP-X Pro 3 dev, who wanted to let us know that the 1.0.4 fixed version for OP-X PRO-3 is online now. This version solves the bug related to the lost of the stored patch in a gig file. :smiley: :wink:

The message from Peter:

I hope we will have a fixed Mac VST3 version too.

But, you can already enjoy working with the Win VST3 and Mac AU version.

I also wanted to thank one of our GP Dev, @Dadi, who worked actively with Peter to figure out how to fix this bug.

3 Likes