#41

This is something I’ve thought about a lot, as well. On one hand I agree with you, apps like Kria and Earthsea that could be considered “Monome branded” feel like they’re lacking the refinement and nuance on Norns that has been built out for Ansible, which feels like a shame.

On the other hand, a lot community contributions from @csboling and @scanner_darkly respectively are what have helped those apps become what we as users may desire. Should Monome be responsible for providing these apps with community contributions as direct ports on Norns? Could that have other implications on the open source nature of Monome?

On the other other hand, it feels slightly absured that I’ve considered leaving Norns behind in favor of a CV to Midi controller just to use the apps I know and love with Midi when they could likely be ported relatively easily and the CV middle man seems unnecessary.

But on the other other other hand, having these apps work on Norns is something I could do if I learned to code and took advantage of the open source nature of the community, but honestly I don’t know if I could do such things justice and in a reasonable amount of time given my coding experience (i.e. little to none). But, I could still start…

All of this to say, I have this round about conversation in my head every time I see this thread bumped and it’s hard to see any of these perspectives as “right.”

1 Like
#42

ok - grabbed some time today. I copied @ngwese repo into a new clean one (there was nothing useful in the commit history, seemed easier to make a clean repo)

I’ve added ratcheting and the moving playhead on the probability page for now. Looking to add scales but see how time goes.

I’ve not got a good list of the recent changes to Kria in Ansible - what other things did I miss that should be added?

@robotboot - you said “If you sequence a note on the top row it doesn’t trigger.” - that’s not an issue I can reproduce. Can you check with latest etc and then I find for this kind of thing a little video made on your phone often helps - showing what you are doing, settings etc.

“and some other stuff.” - I know I’m not very responsive but please report in this thread - I will get around to it! I’ve noticed triggers switching themselves on and off when I change other things - not sure if this was user error or a bug - keeping an eye

My personal view on the “official monome” versions is that Monome is increasingly a community effort - just that maintainers like myself need to keep up the standards better (this applies solely to me right now - everyone else is doing Stirling work)

Hopefully will get scales done today or tomorrow

8 Likes
#43

(oh and thank you for all the kind words and offers of support - really appreciated)

7 Likes
#44

I apologize if my ramblings above made it seem like I was calling you a slacker or anything of that nature, which was not my intent. Your efforts are appreciated and I hope you are doing well. Looking forward to driving into this update soon.

As far as updates made to Kria on Ansible, I think all of them have been logged here: Ansible Development and Beta Firmware Discussion

1 Like
#45

let’s be clear: I have been AWOL (see above) so fair comment quite honestly

on Ansible changes - That’s the list I found - cool I’ll search through for other stuff to add/update

[update] Ah ok - Rev/Tri/Drunk etc - they look cool - will add at some point but I think for moment I’ll add scales and then there will be another gap before I get a chance to do more

1 Like
#46

I’ve updated the community catalog to point at your new repo!

4 Likes
#47

cheers!

I’m also about 1/2 way through adding scales - might be tonight or might be in tomorrow…

(edit: tomorrow now but it’s going to be cool… :wink: )

1 Like
#48

i would love to devote time to getting some fully-implemented and expanded versions of the modules onto norns.

that said, i spent most of my coding time working on infrastructure that supports the various community contributors here— people making new and original scripts, in addition to those people porting existing apps and ideas.

i’m hoping as some of the norns core ecosystem stabilizes i will be spending much more time working on the actual playable applications— i apologize that i haven’t as of yet been able to put in the time myself.

that said, i am astounded by the quantity and quality of scripts contributed to the norns library.

thanks @junklight and @ngwese for keeping kria alive

14 Likes
#49

would it make any sense to toss the firmware code into matron w/ lua calls and build scripts around that ?

not familiar with the firmware but that sounds like a potential time-saving way to go about direct ports

#50

I think that’s the direction @scanner_darkly’s ‘multipass’ is heading in. I suspect that the initial emulation of the environment is likely more work than the Lua port was. Also the modules are all about control voltages - I’ve definitely skewed the port in a more midified direction

Emulation is not a direction I’m overly interested in (at the moment) (although I can’t remember why I was struck with the need to make a port - there must have been a reason!) - with the scales work I’m finally starting to take a bit more advantage of the Norns environment too - which would be harder with an emulation.

anyway - I’ll keep this one going until something better comes along

(to be clear - maintaining it isn’t normally too onerous - just personal crap been getting in the way - but hopefully I can stay on top of it moving forwards)

3 Likes
#51

very much i’m not interested in putting application-specific code into matron, which needs to stay clean and focused.

given the module and norns are not one-for-one compatible regarding hardware (outputs, controls, etc) it makes sense to maintain different branches.

@junklight thank you for all of your efforts!

3 Likes
#52

Likewise thanks for the effort on this @junklight. If you want to offload any off the effort or want a second set of eyes on anything feel free to shout out :slight_smile:. I’d love to see Kria flourish on norns.

4 Likes
#53

thirded (fourthed? tenth’d?)! i didn’t mean for that quick patch-up to feel like a “not my problem” move — didn’t know the full scope of the situation and just saw some low hanging fruit. excited for this to become a community effort, which is the most norns approach imo!

2 Likes
#54

absolutely definitely not.

i think one thing that would be helpful is documenting the behavior of kria (and other sequencers) in a language-agnostic way. none are really that difficult to understand and implement. but kria’s main.c is very unfriendly and unportable. so kudos to @junklight for digging into a port already.

1 Like
#55

i feel

the suggestion doesn’t really solve any problem beyond quickly have the thing now & creates barriers for editing anyway - not sure why i thought to bring it up tbh

would contribute my efforts to some lua adible-y stuff in the future - would love to have access to these tools in non-modular form

#56

Oksy I do under stand all the point of views and I know my tone in real life isn’t very accurate about hoe i feel in my head and my internet tone is worse. I just updated the Kira and here are some constructive comments about whats not working. This might be tough cause of names of stuff i might be confusing but ill give it a go.

  • Scales are not working at all. I do have a suggestion for improving this page in general. the first 2 vertical rows become the preset scales then there is a blank row then there is the crest scale set up but there are 12 spots for notes to be more open scale wise and getting over the root note issue being able to get all 12 notes.

  • clock out. When i turn this on the bpm on connectived device goes to it maximum bpm. I tried my digitize and it goes to 300bpm when kira is set to 110 and the digitize becomes unresponise. i also tested a intelligent umidi and the clock on that isn’t even blinking it going so fast.

  • “loop points” or loops. you can not have a single row loop. when you hit the first button nothing happens and the shortest is 2

  • Meta sequencing once you enter it it saves like your stuck in it and can’t go back to normal normal.

  • most noticeable missing thing from current kira are the “track run modes” where the tracks only advance when a gate is programed in, and then i believe there are some other ping png, drunken, and etc modes.

Im no loger haveing the top note not triggering…maybe that was a one off.

#57

Yeah. Not pushed scales yet. I have a different solution in mind. Have a look tomorrow morning uk time. Should have pushed a new version then.

Hmm. I’ll look into that. Definitely broken!

I’ll look. Does the module behave like that?

  • Meta sequencing once you enter it it saves like your stuck in it and can’t go back to normal normal.

  • most noticeable missing thing from current kira are the “track run modes” where the tracks only advance when a gate is programed in, and then i believe there are some other ping png, drunken, and etc modes.
    [/quote]

Meta thing - sounds like a bug

Yeah I’ve not added those to the port & they are unlikely to get added this week either. I’ve just carved out a couple of days on this for now. More later…

#58

Yeah that is how the modular behaves with ability to have just one step in a sequence. Comes in handy when tuning or gif or simple octave changes or if you use the alt not sequence to transpose sequence. Totally understand these aren’t just all fix ASAP just wanted to help out more and try and identify stuff. Your doing a great job.

1 Like
#59

I’m happy to take a swing at crow/jf integration. I had a half baked implementation for meadowphysics so I might be able to do both at once

4 Likes
#60

yeah - going to be a couple of months or so before I can afford a crow so feel free (but no hassle - I will buy one at some point)