Saw this link. Sounds interesting. Basically converts Nord modular patches to Csound and makes the Nord Modular GUI useful for controlling Csound.
It's open source. Wonder how hard it would be to adapt this software to convert NM patches to axoloti?
-ry
well axoloti is not going to run csound... without a lot of work.
so that means this converter would have to be written to map everything to axoloti objects/connections, which basically is most of the work involved in doing this from scratch.
(all you basically get from this project is something which can parse a NM2 file)
that said, not an impossible task.. just lots of dev work.
note: Ive seen quite a few saying how great this is... but if you read the docs at the developers site, he clearly states there are quite a few 'NM2' objects missing... so as it stands (and it been around quiet a while... its only new to CDM 
) , its not going to covert every NM2 patch.
I was just speculating about this in another thread, as it happens.
I imagine you’d need either to create an entire set of Axoloti objects emulating the NM modules, or a very complicated database of recipes for emulating them with existing objects, including transfer functions and ranges for all controls etc.
It would be a Lot of work, but I guess it would be possible.
a|x
Nord G2 also runs 96 khz internally. Axoloti runs 48. That could potentially create some issues too.
That's really what I was wondering about. I've never had a Nord Modular, but I know there's a ton of patches still out there. Sometimes cracking the proprietary format is the hard part, sounds like in this case, not so much.
Emulating all NM modules sounds a bit much too. Anyway, just something I saw and thought worth noting.
(Oh and thanks for moving this to the correct category, "lounge." Wasn't quite sure where it should go.)
To do an exact emulation of the Nord Modular or G2, it requires exact replicas of the algorithms. Getting access to those algorithms involves reverse engineering its firmware, essentially disassembling its DSP code. All that DSP code is written/optimized specifically for the Motorola/Freescale DSP56K... DSP chip architecture. Emulating such code on other processor architectures would result in very sub-optimal solutions. (24bit registers, 56bit accumulator)
Disassembling or making copies for emulation of the Nord firmware would be an infringement of Nord's copyright.
Inexact emulations (as pch2csd seems to do) may be satisfactory in some cases, but significantly different in other cases, a subject for endless discussion. I think this is also the reason why Nord did not create a Modular to G2 patch importer.
The NM patch files are all text files so parsing them to something that may run on a Axo is not impossible, but would be a ton of work. For the CSound version, I imagine they found a way yo convert the parameters given for the Nord modules and applied them to similar (but not exact) modules in the CSound complement. The same would have to happen in the Axo world to make this work. Somebody would hace to create all the modules that are in a Nord Modular, with the same In's and Out's and knobs and controls, and then just re-direct the NM's patch commands to apply to those modules. They of course would not sound the same, but would function similarly.
The patch file names the modules used and the knob positions and the cables connections and more. A Nord Modular (NM1) patch file looks like this:
[Header]
Version=Nord Modular patch 3.0
0 127 0 127 1 0 0 16 4000 2 1 0 1 1 1 1 1 1 1 1 1 1 1
[/Header]
[ModuleDump]
1
1 9 0 0
2 13 0 4
3 13 0 8
4 13 0 12
5 13 0 16
6 13 0 20
7 13 0 24
8 13 0 28
9 13 0 32
13 4 2 24
14 20 1 6
15 20 1 16
16 20 1 28
18 19 1 4
19 19 1 14
20 19 1 26
23 40 2 16
25 94 2 20
26 1 1 0
[/ModuleDump]
[ModuleDump]
0
[/ModuleDump]
[CurrentNoteDump]
64 0 0 51 78 5 63 98 1 63 114 26 63 84 5 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0 64 0 0
[/CurrentNoteDump]
[CableDump]
1
3 1 1 1 2 0 0
3 3 0 0 2 0 0
3 4 0 0 3 0 0
3 5 0 0 4 0 0
3 6 0 0 5 0 0
3 7 0 0 6 0 0
3 8 0 0 7 0 0 -----Etc, Etc.....
They didn’t, but there is a 3rd-party script to do that.
I have both an original Nord Modular keyboard, and a G2 Engine, but to be honest, never tried converting an NM1 patch to G2 format and comparing, so can’t comment on how close they sound.
a|x
Sorry for awakening this old thread. I have a question that relates to the discussion in this thread regarding NM G2 & Axoloti.
I'm trying to find any info on how many (if any) and if so, which of the modules in the NM G2 that have inspired any similar modules in the Axoloti editor?
I'm not looking for finding them being exact replicas (aka reverse engineered) in sound as I'm not expecting (not even wanting) that. But I'm trying try to get to a point of understanding what I'm even looking at when it comes to certain Axoloti modules. Many modules have quite confusing 'names' that of course relates to their intended functionality. And I feel overwhelmed at any time trying to figure what each one offers. Which of course is due to my attempts of understanding, if there are any similarities to the modules I'm more familiar with in the NM G2.
Is there some kind of a list to read of the Axoloti modules and their features/functionalities?
Or any possibilities to extract such information out of the Axoloti editor?
I realise this may not be what you are driving at, but it is easier to browse while being away from your axo and may stir some ideas
http://www.privatepublic.de/public/factory-objectlist.html
to respond to your actual enquiry, I am sure there is a lot of crossover in the basic factory objects and Nord modules, but it will be rare to find an exact port of them, the exception being toneburst/pattern/nmpgen3 which is a clone of the nord modular pattern generator, and a hell of a lot of fun.....
If you are just browsing and don't have a specific idea in mind that you want to implement, I often find it helpful myself trawling the communinty help patches and then the contributions thread ( https://sebiik.github.io/community.axoloti.com.backup/c/community-library ) to see what people have uploaded on a contributor basis, found a few hidden gems that way, that I don't think I would have come across by merely searching.....these allow the contributor the chance to fully explain an object, where the object browser may just be a few lines, you may find that objects are uploaded to be used together or with a specific patch in mind...just more information in general.
Hope that is of some use