FM7 (Norns)

mlogger · 2019-04-15T12:14:34.113Z

this is working for me now as I had similar issues.
It’s a fantastic synth and well worth taking the time to explore the many parameters. Here’s an improv i did today

instagram.com

mudlogger

5 Likes, 0 Comments - mudlogger (@mlogger) on Instagram: “this is #monome #norns #fm #synth called fm7 #improv #improvisation #classicalmusic #classical…”

cfurrow · 2019-04-15T15:51:43.839Z

I’ve tried using Librarian and Cyberduck but keep getting the message: error: load fail. I have a feeling it’s a simple fix…I hope. Thoughts?

EDIT: I fixed this using maiden and changed line 14 to : local FM7 = require ‘fm7/lib/fm7’ instead of: local FM7 = require ‘fm7_norns/lib/fm7’

tehn · 2019-04-15T19:00:48.777Z

the require suggests the name of the FM7 folder should be:

dust/code/fm7

if it’s called anything else it’s not going to work.

Dewb · 2019-04-16T03:22:52.620Z

Here’s some python code to parse DX7 sysex (and convert to Nord G2 patches)

github.com

msg/g2ools/blob/master/dx2g2.py

#!/usr/bin/env python2

import logging
import os, sys, traceback
from optparse import OptionParser, make_option
from array import array
sys.path.append('.')
from nord import units
from nord.g2.file import Pch2File, crc
from nord.g2.colors import g2modulecolors
from nord.convert.version import version as g2oolsversion
from nord.convert.dx7 import dxtable

class DX7Converter: 
  def __init__(self):
    self.pch2 = Pch2File('dx7.pch2')
    self.dxrouter = self.module_by_name('DXRouter1')
    self.operators = [self.module_by_name('Operator%d'%i) for i in range(1, 7)]
    self.lfo = self.module_by_name('LFO')
    self.lfosync = self.module_by_name('LFO Sync')

This file has been truncated. show original

lazzarello · 2019-04-16T19:16:45.640Z

Very interesting. If I can extract the sysex functions from this, modifying the output format to Norns pmap would be straightforward. It’s also a good way to add all the missing pieces of the engine.

brndnwilliams · 2019-04-16T22:44:45.707Z

Hello, I had FM7 working and now it does not. This is what transpired: I wanted to use Haven so I loaded it on and it wouldn’t work. I read that there were duplicate engines in the WE section so I deleted WE and loaded Haven and it worked. I added the newer WE back on and now FM7 says FM7 (error: init). Did I delete something that FM7 needs when I removed the original WE folder? I don’t know a thing about GitHub or anything so If there’s something that must be loaded back onto my Norns, please explain how I can do it. Thanks so much. I love FM7!

EDIT:
I did some investigating and found an FM7.lua in the WE folder so I deleted it and the FM7 works now! slowly learning but now I want to know why it was in WE and what happens when whatever in WE that requires it tries to open. Will it work because it’s on my Norns but just in this FM7 folder? thanks again. Again, not a very computer savvy person so even simple things intimidate me

mlogger · 2019-04-17T02:23:59.232Z

Here’s another quick demo. Because of the tones and timbres you get out of it, I think it would work really well tied to @dan_derks Less Concepts script. FM7 is a fantastic sounding script and much easier to program than my FSR1

instagram.com

mudlogger

41 Likes, 0 Comments - mudlogger (@mlogger) on Instagram: “demo #monome #norns fm7 synth app - its a 6 operator fm synth with a pattern recorder #fm”

instagram.com

mudlogger

86 Likes, 1 Comments - mudlogger (@mlogger) on Instagram: “this is #monome #norns #fm #synth called fm7 #improv #improvisation #classicalmusic #classical…”

lazzarello · 2019-04-17T03:58:42.075Z

I think the 2.0 update changed many things. The engine is also in we…we should sort this out as I want to update the engine. I excluded it from my own repo. @tehn might be able to help. Should we remove Engine_FM7.sc from we?

lazzarello · 2019-04-17T04:01:18.449Z

I’ve been doing some improv stuff on my commuter ferry ride and I agree more sequencers and modulators would open new frontiers. I like this engine more than I did when I first made it.

I have some arc + grid ideas…

mutedial · 2019-04-17T05:07:37.805Z

I haven’t followed the technical side of Norns development/programming but is it possible to pipe MIDI internally in Norns? (E.g. have less concepts sequence fm7)

speakerdamage · 2019-04-17T15:57:47.487Z

wherever Sun Ra is in the cosmos I hope he has a norns/grid with fm7 loaded up

dan_derks · 2019-04-17T16:47:02.520Z

mutedial:

is it possible to pipe MIDI internally in Norns? (E.g. have less concepts sequence fm7)

speaking for less concepts, the MIDI output is just a translation of the data generated by the script’s sequencing maths – so the data is able to be agnostically re-formatted to the syntax a particular sound engine expects

this happens in the iterate() function which starts on line 175:
if seed_as_binary[v1_bit] == 1 then
engine.noteOn(1,midi_to_hz((notes[coll][scaled])+(48+(v1_octave * 12)+semi)),127)

the engine.noteOn... part is just the formatting Passersby expects (voice,hz,velocity), so it could easily be substituted for the syntax required by FM7.

@lazzarello, seems like FM7's engine.start() command requires a voice ID and a “MIDI” note?

zebra · 2019-04-17T16:49:28.097Z

lazzarello:

Should we remove Engine_FM7.sc from we?

yes ‘we’ should, indeed

lazzarello · 2019-04-19T04:40:41.731Z

I see what you did there. Let me know when that’s a thing. I have a branch to include the engine. It’ll be a breaking change.

lazzarello · 2019-04-19T04:42:00.756Z

I have some changes to the midi code to merge in. Gonna work on it this weekend.

zebra · 2019-04-20T02:28:03.680Z

lazzarello:

Let me know when that’s a thing.

i made a PR:

github.com/monome/we

remove fm7 engine

by catfact on 02:25AM - 20 Apr 19 UTC

1 commits changed 1 files with 0 additions and 193 deletions.

in general: i think the “best practice” if one wants to ‘take ownership’ of something stuff currently in we, is to fork we and make one’s own PR removing the thing in question.

lazzarello · 2019-04-23T03:16:25.796Z

Clearly I didn’t get to this over the weekend. I mean, San Francisco had a downhill big wheel race how could I miss that?!? I’ll get my Norns code in line soon I promise.

michael_matos · 2019-04-23T06:54:50.464Z

that big wheel race sounds rad! hope you had a blast.

I’m getting this new error.
if anyone an help me troubleshoot I’d be grateful.

script load: /home/we/dust/code/fm7/fm7.lua

cleanup failed

script clear

pset >> write: /home/we/dust/data/system.pset

script run

loading engine: FM7

Engine.register_commands; count: 0

___ engine commands ___

___ polls ___

amp_in_l

amp_in_r

amp_out_l

amp_out_r

cpu_avg

cpu_peak

pitch_in_l

pitch_in_r

script init

SCRIPT ERROR: init

/home/we/dust/code/fm7/fm7.lua:85: attempt to call a nil value (field ‘amp’)

stack traceback:

/home/we/norns/lua/core/norns.lua:185: in field ‘amp’

/home/we/dust/code/fm7/fm7.lua:85: in function ‘init’

/home/we/norns/lua/core/script.lua:71: in function ‘core/script.init’

[C]: in function ‘xpcall’

/home/we/norns/lua/core/norns.lua:186: in field ‘try’

/home/we/norns/lua/core/engine.lua:83: in function </home/we/norns/lua/core/engine.lua:82>

>> reading PMAP /home/we/dust/data/fm7/fm7.pmap

rbxbx · 2019-04-24T23:02:41.912Z

Getting the same error here, I think we might just need to wait for the next release from @lazzarello

michael_matos · 2019-04-25T00:36:23.718Z

Glad it’s not just me. No worries. There’s plenty to explore. I’m stoked that so many people are sharing such cool things.