KVR Audio

pylon · Post by **pylon** » Tue Nov 10, 2015 8:41 am

Something I'm unclear on - is the use of freeware filters permitted?

Chris-S · Post by **Chris-S** » Tue Nov 10, 2015 8:44 am

@H-man, yes also noticed some funny behaviour when using Mod Dest.
It's not only when using Filter as destination, also pitch/LFO depth.

H-man · Post by **H-man** » Tue Nov 10, 2015 8:50 am

pylon wrote:Something I'm unclear on - is the use of freeware filters permitted?

Yes they are, however, they do kind of sit in the grey area (similar to saturation) so use wisely. Automating EQs (Sweeping) is similar and also neither in nor out.

Chris-S wrote:@H-man, yes also noticed some funny behaviour when using Mod Dest.
It's not only when using Filter as destination, also pitch/LFO depth.

Yeah okay. Kind of pity as there is some definite tone tweaking to be had if they were working.

Chris-S · Post by **Chris-S** » Tue Nov 10, 2015 8:50 am

pylon wrote:Something I'm unclear on - is the use of freeware filters permitted?

not allowed:
Any effect that transforms the sound to make them unrecognizable as being from the synth

Whatever this means.

So: using the filter like an EQ is ok, using the filter as a replacment for the synth's own filter (with heavy resonance, automation) is probably not permitted.

H-man · Post by **H-man** » Tue Nov 10, 2015 8:54 am

@Chris - SNAP!

Edit: Keep in mind that there is no official penalty or anything like that. The risk is that someone voting on your track may choose to take off a point or two if they think that you have gone too far away from the capabilities of the synth.

pylon · Post by **pylon** » Tue Nov 10, 2015 1:33 pm

Got it

Cheers

H-man wrote: Automating EQs (Sweeping) is similar and also neither in nor out.

Thanks, you pre-empted my next question

I shall refrain from either

MTLE · Post by **MTLE** » Tue Nov 10, 2015 5:31 pm

Just in case somebody wants to use the Oxe internal effects. It was already written before they are not stored in the patches and they are not stored in projects files (reaper), too. There's a little workaround for this. Activate the automation for these parameters to save the dialed value in projects.

ontrackp · Post by **ontrackp** » Wed Nov 11, 2015 2:42 pm

INSANITY -- Every time I close Reaper and then open it, Oxe FM does not remember the patches I've made. I've saved them and they show up as user presets in the list but when I select them nothing happens. I've also exported them and tried importing, also no luck. So each time I work on my piece I end up re-building sounds, which is sometimes ok, but in general, totally frustrating. It may have something to do with midi channels, but I've tried changing those settings too. I realize this may be more of a Reaper issue than an Oxe issue but any help would be greatly appreciated.

Any advice??!?!

Thanks.

psmacmur · Post by **psmacmur** » Wed Nov 11, 2015 3:01 pm

I'm using OXE in Reaper and, for the most part, not having these issues. I think I have the latest Reaper, or maybe one back. I'm using 64 bit for both Reaper and OXE?

I did notice that multitimbrality didn't restore correctly. That is, I had a sound on one of the other channels/layers in OXE and when I reloaded the project, it came in as the default sound. The first/top/default layer/channel restored correctly. I quickly gave up on multimbral use of OXE as it doesn't seem to offer me much anyway.

Another plausible culprit is permission issues, although I only recall having those with synthedit synths.

Taron · Post by **Taron** » Wed Nov 11, 2015 3:02 pm

My advice:
Root of Valerian, I think... maybe some meditation... avoid too much caffeine... maybe eat a banana?

Wow, I haven't tried it, yet, but I hope I won't run into that in MuLab!

ontrackp · Post by **ontrackp** » Wed Nov 11, 2015 3:11 pm

psmacmur wrote:I'm using OXE in Reaper and, for the most part, not having these issues. I think I have the latest Reaper, or maybe one back. I'm using 64 bit for both Reaper and OXE?

I did notice that multitimbrality didn't restore correctly. That is, I had a sound on one of the other channels/layers in OXE and when I reloaded the project, it came in as the default sound. The first/top/default layer/channel restored correctly. I quickly gave up on multimbral use of OXE as it doesn't seem to offer me much anyway.

Another plausible culprit is permission issues, although I only recall having those with synthedit synths.

Thanks. I'm new to Reaper (usually use Logic) and I think it may have something to do with the midi channels. My keyboard comes into the computer through a MOTU midi/av+ interface on channel 4 and Reaper is set to receive on all channels, but to register control changes I have to change Oxe to Ch 4, which makes sense, so it should just work but it doesn't. I tried changing the midi channel setting on each track from all to 4 to see if that would help and it doesn't either. Oxe just doesn't want to see the user presets. It's weird.

psmacmur · Post by **psmacmur** » Wed Nov 11, 2015 3:26 pm

Ok that's it then. You need to use channel 1. I don't know why; I suspect a bug but can't even guess if it's OXE or Reaper since I've never tried multiple channels before.

You can work around it in several ways. I'm only handwavy here, I don't have a DAW handy or a MOTU (must be nice, I want one but can't justify the $). In my personal order of preference:
- change your MOTU to output on channel 1. You can probably do this in their software or right on the device.
- use a Midi tool outside reaper (e.g. LoopBe, CopperLan, something like that). This would be set up to listen to the MOTU on channel 4 and output channel 1; you'd then set Reaper to listen to the midi tool instead of the motu
- use a midi tool inside reaper (e.g. pizMidi plugins). Again, probably a per-track solution, but you can set up a default FX chain in Reaper somehow
- route channel 4 to channel 1 within each reaper track's routing panel. I'm not 100% on this, but Reaper's routing is unbelievably flexible so I'm sure there's a Reaper way. You might be able to do this globally, but probably have to do it per track, which is a bit much so I'm putting this last.

Not exactly fun, but where there's a will, there's a way.

ontrackp · Post by **ontrackp** » Wed Nov 11, 2015 3:36 pm

OK. That's got to be the culprit. I'll set my keyboard to transmit on 1 instead of 4 (that was leftover from the days of having lots of hardware synths setup) and then follow the path back thru Reaper. Hopefully I can avoid going into the MOTU control panel but I could do that as well. Reapers track routing panel is definitely flexible, but I'm hoping if I just put everything to channel 1 it will cure the problem.

Thanks for the advice! I'll let you know how it works out.

MTLE · Post by **MTLE** » Wed Nov 11, 2015 3:45 pm

Additional to normal FX chain each channel has an Input FX Chain and Input configuration to manipulate MIDI in different ways. Right click on the tracks Record Arm shows a different popup menu. There you find MIDI:Input for recieve and also routing parameters. And the menu gives acces to Input FX Chain ...

ontrackp · Post by **ontrackp** » Wed Nov 11, 2015 3:57 pm

Cool. Thanks everyone, I thought the days of complicated midi routing were long behind me.....

One Synth Challenge #81: Oxe FM (z.prime wins!)