#150

OK, i got this. I for got that I was using @okyeron oscgrid scripts :blush: I’ve unloaded this and it works :))
Now I need to prepare Bigger template.
Thanks!!

1 Like
#151

awesome, thanks so much for the report back – totally weird! i’ll add that as a step in the post

#152

No problem,
Btw can you confirm that norns doesn’t send any response? It would be nice if start/stop sliders was changing as i change pad :))

#153

norns does send response, see demo video – all of those parameters should be updating as you change pads. I’d say restart both devices to get a clean slate and try hotspot. hope this helps! :slight_smile:

#154

Unfortunately I cannot get any response, will check with other devices and maybe flash clean norns image(?)

#155

do you mean other mobile devices? might be worthwhile – i haven’t run into any trouble with iOS devices :confused:

a clean flash wouldn’t likely help here.

otherwise, please give this a try:

  • run cheat codes but don’t run TouchOSC on your Android
  • open up the OSC setup in cheat codes
  • hit refresh OSC in that menu (IP + Port should say none)
  • open TouchOSC on your Android and connect to norns, load the cheat_codes template
  • IP and Port on cheat codes will autofill
  • edit the OSC port on cheat codes to one digit higher than the auto-fill
  • edit TouchOSC’s port (incoming) to match
[cheat codes]: v1.3.1 (May 4, 2020)
#156

Yaay it worked. Thanks :slight_smile:
Great app, is it possible to add mappings for pattern recording controls?

#157

excellent news! super weird that it all works on iOS, but that there’d be a port conflict on Android. I’ll continue looking into this.

pattern recording with TouchOSC is sadly a no-go. the OSC traffic becomes too heavy and the UI loses responsiveness.

also, thank you for the kind words! please share what you’re making!!

#158

the app/script latency is up to about 7 seconds today pretty consistently and the softcut buffers don’t seem to be recording anything at all. any ideas? tried removing/reinstalling the script

#159

sorry to hear about the slowdowns – the cheat codes script isn’t the trouble, though (it would’ve not worked out the gate if so), it’s the connection between your devices. there’s a decent amount of data being sent between TouchOSC + norns with every pad (led, start/stop position, start/stop time, rate, direction, loop, etc), so any environmental WIFI thing is going to pose a potential hurdle.

have you tried hotspot? have you turned off Bridge? have you removed the oscgrid stuff?

#160

i’m not sure what removing the oscgrid stuff means. are you talking about the oscgrid templates? if so, i never synced them to the ipad. did not try the hotspot, but that’ll be the next step. i didn’t have to the first time, so it kind of sucks but i will if i have to. bridge has been off, i just turned it on temporarily while i was trying different things. the softcut thing might be a bigger issue so disregard that

Responding here so i don’t bump with unnecessary follow-up posts:
*no not at all, sorry if that came off as annoyed. i was trying to be specific. I appreciate the help very much. i actually connected with my iphone xr and it seems to be mirroring exactly the same performance quality as the extremely old ipad. I don’t know what that means. like the iphone also worked perfectly at first, around the same time i first used the ipad, then when the ipad slowed, so did the iphone. very weird. i’ll figure it out eventually i imagine, like most things involving the fates. let me know if you have any other ideas in the meantime. i’ll try the hotspot once i work up the nerve. trying to stay in creative mode without being bogged down in technicalities too much so i can really take advantage of this free time i have. i know that if i have to end up re-flashing the fates, it will take up a couple hours of my time that i could have been making something.
thanks again

1 Like
#161

totally understandable — having initial success and then repeatedly not is super frustrating. i also didn’t mean to ask you three questions in a row, i just didn’t know the parameters of the incident and if anything changed from the other day.

re: oscgrid, i think the template was all @okyeron was referencing. idk if there’s installation past that, was just recycling terminology from his post the other day :slight_smile:

please do lmk how you get on with hotspot, but i’d also suggest testing with another (maybe newer) device just to have some success to buoy. also, try toggling off the message bundling — maybe that’s causing some weirdness with the older ipad? a consistent delay makes me wonder if TouchOSC is just waiting to collect and then giving you everything at once, rather than allowing whatever messages can go through.

1 Like
#162

If you ever ran the oscgrid/load script you need to run the oscgrid/unload script

You may also want to confirm oscgrid is not listed in any slots under SYSTEM>DEVICES>GRID

To reiterate the warning - oscgrid is some hacky experimental shit and may break your system. It is not compatible with cheat codes

3 Likes
#163

oh ok, i never even downloaded that script. i was unaware of it. i assume this means the oscgrid templates for other Touchosc norns scripts aren’t safe to use? i think im confused on that whole thing, so i just wont touch any of it.

in trying to fix the Softcut/whatever issue i had with Cheat Codes not recording or playing back incoming audio loops, i found that some error was popping up with a PSET that i had saved that included a collection of pad params so i wouldn’t have to reset pad controls every time in the cheat codes script, but once i opened a blank PSET, that was fixed and it seems like TouchOsc for iPhone isn’t giving me the lag issue anymore. so crossing my fingers that that issue is gone now. thanks for the help

#164

oh! super glad to hear you solved it. excellent, but very strange.

fwiw, these aren’t actually saved in PSETs. cheat codes uses a method called collections, which is unique to the script but is the best way to manage all ~500 unique variables. the manual covers the best practices :slight_smile:. using collections, you can set a “default” state as collection 1 and then do your session and save the edits as collection 2, 3, 4…100

#165

Right, I understand collections but I assumed that maybe collections were saved in psets. Now I see they are probably independent of one another completely

When I said “a collection”, I meant the “collection” bank

1 Like
#166

ahhh gotcha. yes, completely independent. PSETs are only useful in cheat codes for snapshotting MIDI mappings. collections are separate from PSETs so that you can have one MIDI map template and many collections of sets :slight_smile:

1 Like
#167

edit: released! see below.

7 Likes
#168

Yeeey!
So awesome!
Many thanks: this thing is getting better and better!
:heart::facepunch:

1 Like
#169

yeeeee! thanks for implementing :slight_smile:

1 Like