#285

Thinking about this again last night, I came to the conclusion that adding a “voice 1-6, or 0 for all” argument to the JF.SHIFT OP would be the most graceful solution. But at the PES level I guess the JF.VOX messages could be individually detuned. My chords are just too concordant! :joy:

#286

do you have teletype as part of your setup? if you do perhaps JF.TUNE chan numerator denominator could be used to detune?

#287

Yep, I’ll test it and get back to you! I’ve been extensively using JF.SHIFT with PES so far. The TT’s message tends to get dropped if it comes in at the same time as a note press though.

#288

PES is so great that it’s distracting me from patching the rest of my system :sweat_smile: Grand plans of algorithmic sequencing melt away…

@scanner_darkly, is there currently a way to decouple a pattern from the clock and reset inputs? I’d love to be able to loop an unquantized pattern over a clocked one.

EDIT: Did some research; pretty sure my answer is no. And a source code review leaves me thinking that the clock function would be difficult to disable on a per-pattern basis.

2 Likes
#289

i think it’s doable but yeah, the codebase is getting to the point where such changes are tricky and can lead to some difficult to find bugs. it could really use a rewrite, but then i might as well just start working on archipelago.

1 Like
#290

Trying to update my WW for poly es today worked on MP but won’t work on WW I’m using terminal and OS X 10.11.6

Just curious if I might need a older version or?

Thanks for your time!

#291

can you provide more details on what exactly is not working?

#292

Sorry! Of course it seems I can’t get the device to be reconized therefore cannot update firmware on my white whale.

Seems to work on Meadowphysics when updating but not with whale

Hope this clears it up

#293

so when you connect ww module in flash update mode to computer it’s not recognized, but mp is? are you using the same cable for both? try connecting it first, and then powering the module (with the front button pressed), and try it with powering the module first and then connecting.

#294

spent the afternoon porting polyES to teletype. or, to be more accurate, i’ve added teletype support to multipass, so once done it was just a matter of building the same firmware for teletype. this also means that any firmware built with multipass will be able to run on ww/es/mp/ansible/teletype right from the start.

should post the firmware soon (week/two hopefully) - need to utilize the screen fully first (which will be really handy for some of the more complex pages).

15 Likes
#295

Ohhhh yes. Is Orca coming to Teletype in the future?! :smiley:

#296

yes, started on porting orca to multipass (slow going right now - need to add USB save/load support to multipass), once done it’ll run on all multipass supporting modules, which now includes teletype. there’ll be a couple of new capabilities in orca too… :slight_smile:

edit: should clarify - orca the alt firmware for white whale, not the live coding environment.

10 Likes
#297

So exciting about these!!!

1 Like
#298

Whoa, so would this completely replace the Teletype firmware, or be like an alternate mode we can enter?
Looks great

#299

it’s a stand-alone app, no plans on integrating it with teletype original firmware - feasible, but introduces additional overhead for maintaining it that would just take time away from building something new :slight_smile:

3 Likes
#300

I’ve been using polyES recently to play JF and it’s a blast. I am looking for some clarification on a few things, if you’ve got a minute. firstly, are videos still coming? some pages said video coming soon and Id love for that to still be true. What does KEY actually mean? is it when I hit a specific button something happens? I have XY down just fine. Also, I wish so badly there was a way for the loop length to be predefined but I think i remember someone else asking for this a few months ago and it’s probably not possible. also the notes sound different when externally clocking. whats happening here? some sustained note turn to faster notes once the ext clock comes into play. not specific to poly ES but can you tell me what the controls on JF do while JF is being used as a sound source in polyES? does intone weight the voices differently or something? Freq changes the envelope length?

here’s a real weird question also not specific to polyES probably but is there a way the priority of the notes/outputs work? like if I have mangrove 1 and 2 and 301 and i play three note chords, is there a way to always make the lowest note come out of the 301 or something? I’ve not really gotten far enough to try this myself yet but since I’m a bit of a mess, I figured Id try to get some info first. Thanks for doing this. polyEs has become my favorite part about jamming lately

1 Like
#301

due to family circumstances i have very limited time to work on any projects at the moment, so no videos for the foreseeable future i’m afraid.

so you can map CV outputs to x or y coordinates of the key being pressed, but you can also use the key number as a modulation source - that’s what key refers to in the doc. keys are numbered by columns and then by rows, starting with the bottom left key. this gives you much finer control over a parameter than x/y do.

you can sort of do this by designating one of the patterns as the leader pattern that resets other patterns, and then control the length by just recording a couple of rests into the pattern.

when clocked externally, notes are linearized - all the original timing info is discarded, including notes length, it’ll just send gates with length determined by the gates settings.

i think intone controls the overall envelope shape, time (if that’s what you mean by freq) changes the length. but other than basic use i don’t know JF well - might be a better question for the JF thread!

no way to change this - if a pattern has more than one voice enabled, it will always start with the lowest voice. so if you play note 1 it’ll go to the lowest voice, if you then play note 2 while note 1 is still playing you’ll get note 1 being sent to voice 1 and note 2 being sent to voice 2. hope this makes sense!

2 Likes
#302

All of this is super helpful to me. I appreciate you taking the time to give detailed answers and I hope whatever’s going on works out for the best.

3 Likes
#303

hi, me again, I removed TT and 301 from my case but kept the powered backpack and polyES continued to work. I rearranged the case to close some gaps where those modules used to be and I can’t get i2c recognition. If at some point the backpack touched the case, did I ruin something? I don’t think that happened but I’m not sure what’s up. The only other variable is 2 w/'s with a slashes built by someone on here used to be connected to the backpack as well. so its just ansible to backpack to JF now. I tried two JF’s and different 3 pin cables and feel lost. it works as it should via Ansible outputs. Thanks for any tips or help!

1 Like
#304

I think… You need to have a Leader here - so polyES needs in “leader” mode.

JF and ansible (stock firmware) together won’t work without a leader (TT or polyES)