It’s true. The two of them make a great combination, but sometimes the issue I run into is there are so many possibilities it’s hard to decide where to start.
Breaking it down into smaller exercises or ideas helps. I think I just need to tie the two together and get working on a couple of ideas.
Maybe like this: Instead of using an osc per voice, you could use a sequencer (controlled by note ?) to hold the detune values and send those to the oscilator. should be cpu cheaper.
There was a Scala G2 online tool written in an old version of Python. The link to the tool seems to be dead though:
http://electro-music.com/forum/topic-61234.html
Older Scala G2 thread:
http://electro-music.com/forum/topic-17192.html
I think you have to download the zip file on page 1 of the older thread since the online app is gone.
Thanks.
It’s a bit overwhelming.
And I don’t want to use Scala files. Just want to be able to “fine tune each D” or “fine tune each A#”.
Any help on how to detect if a played note is “a C” ? I made a few attempts without luck (for now !)
Have you checked electro-music forum? There are a ton of patches, even though the forum is pretty quiet. I have to imagine someone else has explored this and posted results.
Well you asked about microtonality and the Scala file format is what people use to share microtunings with each other.
I understand the reluctance though to download the g2ools suite and also have to install Python.
Your questions about detecting whether the oscillator is playing in tune with middle C, and strategies for fine-tuning can probably be answered on the electro-music forum. I’ve been out of the Nord game for too long.
For anyone who is interested, i found the GitHub repo for g2ools. If you’re willing to install Python on your computer and build g2ools yourself, this is what you get in return for your trouble
Description:
g2ools is a set of python applications and libraries to handle the Nord
Modular G2 synthesizer. It allows a person to write simple tools to process
G2 .pch2 patch files as well as .prf2 performance files. Python was chosen
because of the authors knowledge of the langauge and portability. The main
application written was nm2g2 Nord Modular (nm1) to G2 patch converter. The
first version took 3 weeks from start to finish. After the initial release,
3phase provided main models of the various modules available within the nm1
as they are quite different or missing from the Nord Modular G2. It works
on many patches, but there are patches that will not work after the converted
patch is loaded into the G2. 3phase and I have made every attempt to do the
best convertion possible.
This software is released under the GPL licence and comes complete with
source code to the applications and libraries.
nm2g2.py
nm2g2.py is a converter from Clavia’s original Nord Modular (nm1) patch file
to the Nord Modular G2 (g2) patch file. It can convert whole directories and
currently is used to converter the Nord Modular Patch Collection consisting
of almost 30000 patches. Many patches work and some do not. You’re success
will vary depending on the complexity of the original patch and the
differences between the two synthesizers.
dx2g2.py
dx2g2.py converts DX7 syx files into G2 patch files containing 8 DX7 patches
each. The operators are converted exactly as the G2 contains 2 modules:
DXRouter and Operator. The is extra circuitry for the LFO, PitchEG and
transpose. The LFO and PitchEG are modeled as closely as possible (and may
get better) but there are differences. The LFO rates are different between
the DX7 and G2 so the closests match is used. The PitchEG rate parameter
is constant reguardless of the levels used. This requires determining a
normalized time for the rate and caculating the actual time to go from one
level to the next. Then the G2’s envelope time is set to the closest match.
Making progress. Hopefully I’ll sort it out. Window Switches, some maths, multiplexer and a Ctrl Seq as a “table” of detuning.
I’ll post my results if I manage to make it work !
Here’s the first usable patch that allows a manual detuning of on specific target notes (meaning, it creates a 12-tone scale that repeats across octaves).
The CtrlSequencer’s first 12 steps are the detuning for notes C to B. I hope you get the logic. There are probably other ways to do it, I’m interested in your opinions.
One problem is that the total MIDI notes cover 11 octaves, but the Multiplexer at the end restricts it to 8 octaves. Any idea how to “link” two multiplexers ?
microtunable1.pch2 (3.0 KB)
Microtonal stuff is way out of my realm to be honest, but if the problem is the multiplexer doesn’t cover enough ground, you could try duplicating the patch in the FX section (depending on what it is), or creating an accompanying patch, and use the key range module to determine the range for each patch. Do you need a full 12 octaves though? Serious question.
Good thoughts, thanks. I might be able to switch between two multiplexers (after a good sleep night).
I don’t really need 11 octaves but I like when it’s clean and logical.
Just curious, has anyone used a Nord G2 with Overhub? I’m going to need more USB ports but I know the Nord is notoriously finicky about ports, and I’m wondering if anyone has tried this specific combination here with any success or issues.
I have a G2 and an overhub. I can try (on a laptop running win 98 and a MacBook Pro with Yosemite) within a few days. But from my experience, G2 + hubs = fail.
JLS posted this self-generating patch on electro-music. I haven’t uploaded it to the G2, but his recording on Soundcloud is sweet. Great to see new patch/performance shares.
Greets G2 heads. I posted this question on electro-music.com, but it’s very quiet there and no response so far: I confess I’ve barely used the DX 7 modules - but I sure use the multiple FM capabilities elsewhere - and want to dig in but go beyond “just” DX emulation. Can anyone recommend some clever innovative patches from the electro-music patch archive, or tips, which use the DX 7 modules in innovative ways like using either the Operators or Router without the other but in other contexts, or placing some modulators, utilities etc. between them?
I haven’t used the algorithm module much, but it’s just a routing system. I’d try it with some Perc modules routed to pitch, or maybe with some sequencer modules.
I’ll try some things tonight or this weekend and post.
Perc routed to pitch is a great idea. Time with G2 of late has been patching much percussion, or patching something or re-tweaking my older patches to fit into a track in the making. Hopefully I’ll have time to experiment with the DX modules in the next few days; will report if I come up with anything I deem remotely worthwhile.
I remember a patch where the router is used for a 4OP FM patch. Not that different but just to say you don’t need all the 4 routing options.
Routing percussion is an interesting idea!
Mmm thinking if it: maybe you can put it to good use for FX routing…
Never used the DX for anything else than FM-synthesis, great idea to be more creative!
Maybe it can be used as part of a delay network matrix? To create reverb like delay algorithms? I’ve been thinking of trying out something like that for a while and this might be a way to do that efficiently. My G2 is not “activated” (sleeping in a cupboard) but I’ll try that out when i get the time.