496

got it, I still have fun with it.

Implementing an switch „edit“ / „play“ mode, where in edit mode OSC commands are send to the touchosc-layout, would that be an option, dan?

2 Likes
497

this is actually what i was planning to start with, yeah! :slight_smile:

i might also replace the position bars with encoders, since there’s no way to clearly manage relative positions if one clip sample is 30 seconds and another is 2 seconds. the bar in touchosc is a fixed width and range, so it’d need to represent the largest range and that would be much less playable. i think encoders will largely solve the issue, even without bi-directional communication, because the trouble (i’m assuming) is that when you move the bar from one position to another it does a nasty jump — i feel like replicating the arc via touchosc will be much more satisfying.

i’m gonna do a one-week sprint on the feedback from the music hackspace workshops next week, so look for this then :sparkles:

2 Likes
498

I can definitely rework the layout, makes sense to use encoders.

2 Likes
499

Forgive me if this has already been asked, but does cheat codes expect audio files of a particular format [mono/stereo, bit/sample rate, file format]?

500

i don’t think it has, good q!

i always go with 48khz wavs, since that’s the “norns norm”. flac works as well :slight_smile:

to accommodate more audio to be loaded, cheat codes just uses the left channel of stereo samples – so the samples can be stereo or mono.

bit depth is irrelevant.

hope this helps!

4 Likes
501

rev 210227

fixed

  • waveforms for live input now update correctly when erased (previously, was clearing entire visual waveform, which was not representative of the actual buffer content)

added

  • very minor Push 2 scaffolding for @airportpeople, so Leon doesn’t have to maintain a fork :slight_smile:
5 Likes
502

…[quote=“CarlosUnch, post:498, topic:38414”]
I can definitely rework
[/quote]…
That would be great.

1 Like
503

48khz is required/recommended, as there’s no resampling on import (at this time)

3 Likes
504

Good point regarding the sample length fpor the touchosc-laylout.
Is the lemur osc implementation more flexibel?

505

good q! i don’t think any OSC app allows the bounds of its controls to be redefined on-the-fly without an editor program running.

i’m curious about your desired use, if you’re willing to share? that could help fine-tune development. from what you’ve shared so far, this is how i understand the potential OSC problem space:

  • you might be looking for a way to surveil multiple data points at once, as banks of numbers rather than the visual representation of the [loops] L sub-page, but you’re generally happy with using virtual encoders to set loop points
  • you might be looking for a way to set loop points without encoder-scrolling – so, point to a place on a virtual timeline and the loop point just goes there
  • you might be happy with the information displayed in each of the individual [loops] pages, but you want to jump between pages with less effort. so perhaps it’d be useful to have a virtual navigation tool which lets you quickly jump around the most valuable pages, so you can then use the norns encoders to fine-tune start and end points?

happy to help with more info!

506

can someone confirm working with Launchpad Mini MK1 or MK2?

507

others should offer direct experience, but the launchpad compatibility is defined by midigrid, which seems to support mk1 mini’s and up: Norns: alternative grids - #453 by 2197

(the alternative grids / midigrid thread might be a better resource for compatibility q’s — as a rule if it works with midigrid, it’ll work with cheat codes)

3 Likes
508

I bought the MusicHack space course, but stayed up too late last night trying to figure out how to get my audio routed to Zoom that I overslept. The question I had was how I change the bpm in both transport and tap tempo? Whenever I change the tempo by moving E2, E3, or tap it in, the tempo always defaults back to 120.

1 Like
509

thanks again for the great session and hopefully you are taking a CC break for a bit!

…but when you are back and refreshed. i am still having trouble with CC sending midi cc commands to my op-z. i believe you said to turn off midi echo in the parameters/midi note/op-z page. i have enable midi control set to off, midi echo off and even scrolled down to the zilchmo section and selected “no” for bank (a),(b),© midi zilchmo.

any ideas what to try next possibly? thanks!

1 Like
510

oh no, sorry to hear you got waylaid!

ah! what’s your clock source? if you’re set to be driven by MIDI clock or crow, norns won’t adjust the tempo manually – it requires the tempo to change at the source.

i typically keep cheat codes on internal clock and just route MIDI clock out to my external devices. under PARAMS > transport, you’ll find a MIDI clock out tree which allows you to send MIDI clock from cheat codes to any or all of your connected devices. you can also send transport start/stop messages from cheat codes, so everything starts and stops at the same time :slight_smile:

lmk if you have any other q’s! i’ll likely just make some videos for this sort of stuff setup :sparkles:

2 Likes
511

no worries, happy to help!

here are the settings that would cause MIDI CC output from cheat codes:

  • PARAMS > MIDI note/OP-Z setup > enable MIDI control? yes
  • PARAMS > MIDI note/OP-Z setup > enable MIDI echo? yes
  • PARAMS > MIDI encoder setup > enable MIDI enc control? yes
  • PARAMS > MIDI encoder setup > enable MIDI enc echo? yes
  • PARAMS > pad to note setup > if any of the MIDI dest's are the OP-Z then…
    • nav back to the main cheat codes menu and hold K1 until you see the context menu, then press K3. in each tab, check to make sure that the CC column doesn’t have a value for any pad.

feel free to DM for further troubleshooting!

2 Likes
512

Normally I work with grid/arc combination and I was out only with the norns and the iPad, tried to learn more your fantastic CC-enviroment. So my idea is - in “edit-mode” - with the touchosc-layout to adjust via an encoder the start/endpoints and position of the sample and level of each pad/ sample.
Your third comment about virtual navigation would be very handy and a extension to the grid/arc combi.

513

hi @dani_derks, so it turns out to be really easy to get the push working with midigrid, all the hard work already done. There are a few considerations, but before I get to that there was one issue with using midigrid + push with cc2, on load it failed with an exception saying no grid:rotation function.

As far as I can tell there is indeed no grid:rotation in midigrid, so what am I missing? I implemented a do nothing version in midigrid and everything worked as expected. I sure I must be missing something simple here.

1 Like
514

oh, woahhh i am super excited for this!

this came up before and i feel like it’s a good time to maybe split the alternative grids thread into specific discussion about @JaggedNZ 's incredible work updating the midigrid library: GitHub - jaggednz/midigrid: A helper library for midi grids and monome norns. funny enough, there’s also a do nothing in this updated library :slight_smile:. for monome grids, this is a function which allows the user to change the rotation of their device, if they want the USB cable to come from another side. likely wouldn’t be useful for Push, as the orientation is fixed.

if you’re not seeing grid:rotation, then it sounds like you might be working from @beepboop 's original library, which laid fantastic foundation but hasn’t been updated in almost a year.

please lmk if i can do any additional testing or help with anything at all!

515

also, thank you to the folks who advocated for adding a threshold mechanism to live recording – it is indeed super helpful and will be released tomorrow (edit: added one small other new thing, just want to test, one more day!)!

:revolving_hearts:

14 Likes