#83

I am on fates. I am not sure that’s the only problem as also Enc 2 does not do anything.

I am new to norns, but perhaps is something related to the block of code between 486 and 500 in fm7.lua?

#84

@rossominerale so I don’t think it is related to that part. I think the issue is that the script is not properly loading the .pset files that are in /home/we/dust/code/fm7/data on the Shield, but even with moving the files to the seemingly right path the script still does not look like it is loading properly. The expected behaviour is at https://youtu.be/HI9B-vuWF4A?t=42 where you can see that on the right hand side of the norns screen there are a bunch of ‘pages’ with the presets that are loaded. On mine there is only one, the current page.

I’m not much help in debugging this as I’m just getting started with the platform. I’m still trying to figure out what part of the code is attempting to load the presets :slight_smile: I’m sure that @lazzarello would know how to fix this instantly.

1 Like
#85

Interesting. The contribution system was recently given a complete redesign. Are you using the Maiden library feature to install?

#86

Yes I updated the system from within Norns, and then installed the script through Maiden. Is there another way to install the script that I can try?

#87

so FWIW i can reproduce both issues:

  1. the default .pset files are indeed not seen by the norns system because they need to be in the ~/dust/data/fm7. i guess i would have the script look for them there at launch, and copy the files if needed. (and maybe we should provide a system utility for this behavior: scripts wanting to provide default parameter sets and mappings.) at minimum should mention something in script README.

([ed. or other solutions, like: system looks for .pset files in code + data, or script always populates some preset slots with lib/.psets, i dunno)

  1. encoders aren’t working for me. i could be misunderstanding something (is a grid required for basic functionality), or enc_mapping isn’t being initialized as expected. but i’ll know more in a moment.

ok, actually encoders are fine but page switching isn’t happening. looking at the code, that makes sense; the pages object is not being initialized usefully, nor used anywhere, the dx7_algos module isn’t included, &c.

i see some things in the commit history, which indicate that:

  • the “algos” page isnt intended to be shown any more,
  • enc1 is now for coarse tuning and enc2 for fine tuning, &c.

so i guess the intended behavior has changed, in which case the video is just misleading and the script could use a lot of cleanup for dead code &c.

4 Likes
#88

i need to revisit the mechanism for default pset copying… that may have broken recently

#89

I think it is broken @tehn. for my recent script I tried it. I saw how playfair did it (pset file in ash/data/playfair.pset), but that didn’t work (I tried m18s/data/m18s.pset). I went into github and saw you changed the paramset default comment to mention -01, so I tried changing it to m18s/data/m18s-01.pset and that didn’t work either.

For my case (wanting to package the script with different default values), I just copied we/lib/polysub.lua and edited the default values

#90

made an issue

2 Likes
#91

Hi. Do any of you know how I get my midi keyboard(keystep) to work with this? Can’t seem to get it to work :frowning: