MOK Forum - Discuss all things MOK. - Recent questions and answers in Bugs

Answered: Plugin state not saving with Reaper project.

Mon, 11 Jul 2022 07:50:20 +0000

Yikes, that does sound like a bug and thanks for reporting it! I am working on a new build for beta (a week or two away) that should fix this issue, and will post here when that is available for testing. In the meantime I will investigate further, but at this point, this does appear to be a bug... the issue is that some DAWs will send a Program Number 0 after they send the State Information, which Waverazor is interpreting as a "please load the last patch". I didn't catch this earlier, because not all DAWs do this.

Cheers! - Rob

Answered: SOLVED (Note-off in monophonic mode problem)

Wed, 13 Oct 2021 06:09:31 +0000

Thanks for documenting that Brendan. I went to verify this myself, found it all to be working correctly, and came back here to find you had already figured it out! Agreed to keep this here in case someone is searching for a Mono mode case in Waverazor.

You are correct that the various Voice modes can be confusing, but they are there to provide specific types of allocation that might be applicable to certain playing situations. For Mono mode, using Direct voice stealing and Stage steal order is the most common (what you were looking for here I think). The patch, TunedFeedback, is one example of the traditional mono mode style.

Answered: Couple of slight errors in the user manual

Tue, 12 Oct 2021 23:23:18 +0000

Brendan, you're amazing, thank you! Few people ever read manuals, so I'm doubly thankful for both the proofreading and the fact that you're taking the time to really get to know Waverazor.

About "cur step", yes, you're right. I'm adding this to the manual:

Cur Step - This output maps steps 1 through 8 across the full range of modulation, and the modulation amount is equivalent to the current step being played.

And regarding Lag Down, yes, you're right on that one as well. You caught me in a copy paste error, and I've now fixed it just as you've written.

It may take a bit of time for the revised manual to propagate. We can update the website fairly soon, but the one imbedded in the plugin will have to wait for the next build. They will get done though. Thanks again, I really appreciate your help!

All the best,

Taiho

Answered: MOK - Waverazor 2.6 issues

Mon, 11 Oct 2021 18:57:52 +0000

I'm so sorry for this late response, and thank you so much for helping out with testing!

The Waverazor effects routing is extremely flexible, but that also makes it quite complicated. I have to stop and think about it myself whenever I want to set things up beyond the INIT patch.

In order to activate effects 2 and 3, you need to turn up levels in at least three places. Let's start from the INIT patch and use effects 2 for our example.

Under the AMP nav button, turn up EFX2 SND levels in both the Voice Amp Mixer and the Amp ADSR envelope. Then, under the OUT nav button, turn up the EFX2 RTN level. That will enable the whole effect bus and you should be able to hear whatever effect your choose for bus 2 at this time.

What I just described enables effects bus 2 in parallel to effects bus 1, but you can also have bus 1 feed into bus 2, or into bus 3. Additionally, you can have bus 2 feed into 3, or even go completely serial and feed 1 into 2 into 3. These routings can be set up under the MIX nav button. In the Pre FX Mixer, you will find levels for EFX1 -> 2 lev, EFX1 -> 3 lev, and EFX2 -> 3 lev. Use these levels in conjunction with the effects sends and returns to create the routing you want. The buses can be serial, parallel, or even some combination of both.

One additional thing to note about the INIT patch is that the AMP / Voice Amp Mixer / EFX1 SND level is set to zero. This is because we've assigned the main page FX MIX macro control to turn it up, allowing the player to hear the effect using that knob. The FX BYPASS control is also affecting the EFX1 SND level, turning it all the way down.

As for the speaker icon Mute button not working on the effects, those are all active for me in v2.6.0. You may have run into a bug where they became inactive, but I would need more information on how to reproduce the bug.

Once again, I really appreciate you contacting us, and I apologize for the late response! I hope this information helps.

All the best,

Taiho

MOK

Answered: A short list of bugs and issues following One-Synth-Challenge Jan 2019

Sun, 03 Feb 2019 04:31:45 +0000

Hi Richard! Thank you for this detailed list, some of these we are aware of, and have an open bug, however the LFO rate and AmpEnv Velocity scale I was not aware of. I will take a look at these in the coming weeks.

And also, many thanks for all of the efforts, assistance, and tutorials during One Synth Challenge #119 !

- Rob

Answered: WaveRazor 2.0.5 + Cubase 9.5.4 = hangs?

Sat, 08 Dec 2018 22:37:35 +0000

@fresha : Following up on this, with v2.0.9, updates should be super fast and a clean install (with no db) should be faster than before.

Answered: Rescaling v2.0.3 - differences between VST2 and VST3

Thu, 08 Nov 2018 18:50:33 +0000

v2.0.3 VST2 works fine in Reason, rescale window all good. It does take a while for the patch database to build (I presume this is what is happening in the background while the daw is 'hanging', but once finished WaveRazor appears). On restarting any DAW the plugin loads up instantly. This patch database build seems to have happened on both my machines (Win10 x64, laptop and pc), so both were fresh installs uniquely.

If it is possible to have the popup progress bar for the patch database build for newbie users to understand something is happening and not bug out or mash up a half build database that might be a good approach. Something to do with:

mokzen - mokReBuildUserPatchEntries, patchFolder is NOT directory stat: patch << this was in the log file today, after I installed 2.0.3 on top of 2.0.2 (without uninstalling)

hope this helps a bit more

Answered: Waverazor 2.01

Mon, 09 Apr 2018 16:56:23 +0000

Thanks for reporting this, Mark! I'm adding it to our bug tracker for Rob to take a look... If it's possible for you to generate a crash log, that would really help us track things down more quickly.

Sorry for the interruptions to your wave slicing! We'll get on this right away.

All the best,

Taiho

Answered: Possible bugs, feature request, and some basic questions

Fri, 06 Apr 2018 01:48:30 +0000

Setting the Destination of a Modulator - To me this is the converse to your impulse to right click on a destination and pick a source. In both cases, what's missing is the modulation route in between, and those are currently set up in the Modulation Matrix (MTRX nav button). In a modular synth paradigm, the matrix mod route is the equivalent of your patch cable, but a digital mod route adds a ton of capability that a cable can't. For instance, you can split the "cable" from one source to up to 16 different destinations using a 1xN route, or set the modulation response with different curvatures, or change modulation modes for different overall behavior. You can even use a mod route to modulate the parameters of another mod route! To do that in a modular, you'd need a bunch of other modules and a bunch of cables...

I suppose the funny thing in Waverazor is that, at the moment, you sort of need to start with the "cable" itself. Once you identify the need for a modulation, head over to the matrix (MTRX nav) and select either the VOICE or GLOBAL Focus tabs. (Essentially, a Voice level mod route is polyphonic, while the Global level is monophonic. It should be noted that a Global route can modulate downward to Voice level destinations, like oscillator tuning, but Voice routes can't modulate upward to Global level destinations, such as the bus effects parameters.) To the right of the Voice and Global tabs is a drop down menu for adding new mod routes, and it gives you a choice of 1x1 (one routed to one) and 1xN (one routed to many). Once you select the route type, it's added to the matrix list and you can fill in your Source modulator and your Destination parameter, and then set levels for each. Inside the route is a triangle pointed at the destination, and if you click on it, you can change the advanced settings for altering the route's behavior.

I'm trying to steer the conversation to the modulation matrix because I think the routings need to live there in order to keep the rest of the user interface clean. All the routes are there in one place. Beyond that, there are additional reasons for separating routes from the source and destination modules. One is that when segregated to the mod matrix, your routes can have clear, independent or group-able modulation amount levels, if multiple destinations are routed after the source. And Two, both source and destination modules would otherwise get bloated with mod routes hanging off of them, and that clutter would make it harder to see other modules in the same section.

However, I think the desire to route directly from a source or destination module is valid. I'm open to discussion as always, but probably the way to go is to allow initiation of a modulation route from a source or destination module, but then jump the focus to the route that has just been created. By focusing on the individual route, you would also bring up the source module in the Input column, and the destination module in the Output column, so the entire chain can be visualized.

Getting signal to and from an Effect - Yes, this one is tough because you have a lot of mixing options. I think it will help once I get the audio block diagram into the manual (as of this writing, it's not quite there yet). And we're also already looking at improving the mixing workflow in general, wherever it appears in the synth. But in the meantime, the way to configure an effect send is to turn up the desired effect send bus on the active Amplitude Envelope Mixer(s), and in the Voice Amp Master Mixer. To do this, press the AMP nav button, and then the VOICE AMP focus tab. Once there, you will find the EFX1 bus levels (let's use EFX1 as an example), and since the active envelopes feed the master mixer in series, both the envelope bus and the voice amp master bus effect levels need to be turned up. That will get signal to the effect block, where you can populate EFX1 with your desired bus effect. Next, click the OUT nav button and turn up the EFX1 bus level there, which is the effect output level parallel to the Main output level.

When you're feeling more adventurous, you can feed the main EFX blocks into each other by using the level controls at the bottom of the Pre FX Mixer (press the MIX nav button to the left of the EFX blocks to get there). You can also load up each EFX block with a Bank if you want to get nested multi-effects chains going. That stuff is crazy!

Tutorial videos - Yes, I absolutely want to do tutorial videos! I'd like to do more to explain patch creation and even get into Waverazor synthesis theory, particularly around the never-before-seen oscillator parameters. The first video I've done in this series is an introduction to the editor - did you see it? You can find it here on MOK's YouTube channel:

https://www.youtube.com/watch?v=AoHEXUSH580

Giving a tour of a basic subtractive patch from end to end is a good idea. I'll try and do some stuff like that soon.

Once again, thanks for getting in touch with us and sparking a discussion! I think Waverazor will be improved for everyone because of this. :)

All the best,

Taiho

Answered: Parameter reset to patch default

Tue, 16 Jan 2018 16:26:08 +0000

Totally agreed... double-click makes sense for reset to default of a parameter.

Currently on OSX you can use Cmd+Click to reset a parameter. On Win/Linux, it should be Alt+Click, but that combination can be problematic in some situations as the Alt doesn't always get passed to my code, so it isn't reliable.

Answered: [Linux] Sync to external (DAW) BPM ?

Tue, 16 Jan 2018 16:18:49 +0000

Showing the current external BPM is on my list of things to do.

We don't have a way to attach screen shots here yet, but we will in the very near future.

Answered: Waverazor v1.0.4 Linux - some reports of problems

Sat, 13 Jan 2018 18:24:14 +0000

I have some great info from the guys on the KVR post, and am looking into this.

Figured I would post here in case anyone has this same problem and stumbles here while searching for a solution.