[Repro-1] Public Beta

[Urs]

Ok, thanks, I worked it out. The update rate is, uhm, not quiet audio rate. It just jumps between values "sometimes", much like there was a sample and hold. So the delay isn't just a constant one or two samples, it's, well, dunno.

[simonfloris]

Hi, I attached a preset originating from initial state with some additional knob-noodling that has nothing to do with the issue .

Using windows 10x64 Pro 1511, Cubase 8.5.20 x64, RME UFX

I noticed that I can workaround the issue by putting the sequencer to play with e.g. one note-length at zero pitch for "standard" arp behaviour.
Seems odd, but may be intentional?

Hi Simon,

I have tried the preset on Windows 10 64bit with Cubase 8.5. Everything is playing as it is supposed to, at least over here on my computer.

The envelopes will not re-trigger in your preset because you have to set 'Trigger Mode' from 'Norm' to 'Retrig' (on the synth page, in the Mode section, right next to the Glide section) to make this happen. As long as it is in Norm mode, the arp will play legato, i.e. it will update the pitch (when you hold multiple notes), but it will not trigger the envelopes repeatedly.

And as long as you hold just a single note on your keyboard, the arp will just play a constant note, even if you have set Trigger Mode to Retrig. This is intentional.
But as soon as you hold more than one note, you should hear the pitch changing and the envelopes triggering.

Uhm, that is weird, when I reload the patch now, it is working here correct,too.
Even when I try to reproduce the "only-last-note-playing-bug" by just creating a project, inserting the instrument and switching the arp button: arp works instantly. strange glitch.

The only changes in the meantime on my side were uninstalling a local postgres-server and updating kontakt and positive grid compressors....uhm, does not seem related.
thanks for checking it out, anyway.
Glad it works now

[tasmaniandevil]

Glad it works now

Phew, yep, really glad to hear it's working for you now.
Strange glitch, indeed. I'll keep a note about it on my list.

[Vortifex]

Deleted, my brain wasn't functioning properly

[Alex von Elzer]

I don't know if this is already reported?
When I load repro vst3 and Diva vst3 my daw sonar keep crashing
Has someone else this problem also?

[tasmaniandevil]

When I load repro vst3 and Diva vst3 my daw sonar keep crashing

Yes, there seems to be a problem with VST3 and Sonar. I cannot reproduce it on Windows 10 though. But we know that it can crash on Windows 7.
Which operating system do you use?
And do you know what you did when it crashed?
Does it also crash when only using one or more instances of Repro-1 VST3, without Diva?
Any info would be much appreciated.

[david.beholder]

Btw, Rich Hilton - piano player from band Chic - has mentioned on last Sonicstate Podcast that he is impressed by RePro-1

[Alex von Elzer]

Hi tasmaniandevil

I use windows 10 latest upgrade
The setup is quite simple. load vst3 repro load vst3 diva and crash.
Not alone diva but also zebra lets sonar crashes

However I can load several repros vst3

[tasmaniandevil]

Hi tasmaniandevil

I use windows 10 latest upgrade
The setup is quite simple. load vst3 repro load vst3 diva and crash.
Not alone diva but also zebra lets sonar crashes

However I can load several repros vst3

Thank you Alex. This sounds more like the crash is being caused by the Diva or Zebra VST3s than by Repro-1.
Most of our plugins are still coming with our 'old' VST3 version, and it's best to not use them, but use the regular VST2 version instead (as stated in the readme and the installer).
These old VST3 versions are known to be quite buggy. Thus we rebuilt the VST3 plugins from scratch and Repro-1 is already coming with this newer, much more stable VST3 version.

[Ingonator]

I don't know if this is already reported?
When I load repro vst3 and Diva vst3 my daw sonar keep crashing
Has someone else this problem also?

I just checked with the latest VST3 plugins of Repro-1 and Diva in Cubase Pro 8.5.20 64-bit and Windows 10 64-bit (latest updates). No crashes here so far. Same with both VST3 plugins in Studio One 3.2.3 64-bit.

[The Sarge!]

no more (new) User-Presets?
no more Music-examples by you KVRs?

let me still think that I don´t need it...sorry Urs

[AnX]

no more (new) User-Presets?
no more Music-examples by you KVRs?

let me still think that I don´t need it...sorry Urs

Why do you need presets or music examples? Download it and try it yourself

[Ingonator]

no more (new) User-Presets?

If you search for additional Repro-1 presets you could also have a look here:
http://www.kvraudio.com/forum/viewtopic ... 1&t=473084

Of course you need to install the public beta to use those...

[Aerithos]

I might have run into a bug. Here are Google Drive links for the patch, the FL Studio (12.4) Project, and an audio example (I'm unable to attach the files/file extensions were not allowed).

This patch is relatively simple, and playing it normally provides no issue. However, when pressing play in FL Studio on either the playlist or the pattern, the patch is silent for a second, then the volume comes back in like the release of a limiter.

It seems like a single extremely-large-valued sample is eaten by the limiter in Re-Pro1, then the release settles. I've removed the FL Limiter from the example project, but if you add it back, you will notice that it does not register any peaks, nor does its limiter kick in.

Now for the odd part: This only occurs when BOTH ResQ and Jaws are enabled (the other effects have no impact). If either or both of those two are disabled, the issue does not occur. The order does matter (ResQ -> Jaws), but position doesn't (e.g. SoniCon -> ResQ -> Lyrebrd -> Jaws -> Drench also causes the issue).

If you need any more information, I'll be glad to help in whatever way I can.

Edit: I was also able to get the same effect in Savihost by clicking Engine -> Restart. So something about the initial plugin state on reset is causing this to happen.

[The Sarge!]

thanks Ingo