#402

Then we won’t be able to work with CV.OFF to compensate for an existing voltage offset at an output. I’ll play around and see if I can think of something else. Otherwise CV 3 and 4 not great for melody work, if using same system as CV 1 and 2.

#403

Hey Brian, In the Tutorial 5 example, I’m not understanding what CV B C does in script 1. You state that it is setting CV B to match CV A, but I don’t understand how C is being assigned to A? B is only switching between octaves as it is. If I assign CV A to x variable, and then replace the C in your example with X, it seems to achieve the effect of your video. What do you think?

#404

it’s a typo-- should be

CV B CV A

or more appropriately

CV 2 CV 1
#405

Cool, thanks, @tehn

(and here are some random words so I reach the 20 word limit)

#407

had a weird/silly idea last night that TT could be booted in “numeric keypad mode” with special support for a usb numeric keypad.

0006995_for-hp-usb-numeric-keypad-w-hub_670.jpeg670×527 31.7 KB

purpose? live performance mode where you want to trigger scripts manually via one usb cable instead of 8 1/8" cables.

OR

maybe just get a usb HID interface and map the firmware to the desired keystrokes (windows-1, windows-2, etc)

http://www.chromationsystems.com/store/index.php?main_page=product_info&cPath=65&products_id=273

2 Likes
#408

i like this idea! conceivably very easy to implement. would be good to test with an easily-obtainable keypad if you know one.

#409

i have one i got a while back on amazon. there are a ton of cheap options. i’ll test it out today.
now the question is, what to do with the rest of those keys? :wink:

#410

i wonder if it would still be manageable to have the ability to add “hotkey” scripts, so instead of assigning a hotkey to a trigger script you can create additional scripts that are associated with hotkeys directly. would be more work to scroll through them but could have shortcuts (ctrl+key or something) to jump to a specific script.

assuming the processing power is sufficient… and wouldn’t need to be too many, maybe add another 8?

#411

@tehn just tried my keypad with TT. no response. i guess the num-pad keys are read as different inputs. seems that this makes it even easier to implement, yeah? just adding support for those new keystrokes?

#412

I ran some more tests and INIT script doesn’t seems to work with the keyboard-less scene selection method ( select with the PARAM + Button ) :persevere: Anyone experiencing the same issue ???

Here is the test scene:

I:
M.ACT 1
T 0

M:
M 1000
T ADD T 1

So I can monitor T in live mode. If I switch to another scene and come back to the test one T isn’t rebooted…

EDIT: Ok i just encountered another BUG in the same scene. PARAM value get stuck. It freezes whenever i input X DIV PARAM 163 and then i got to reboot the modular o make it work again :cry: :

2:
X DIV PARAM 163
PROB X : TR.PULSE A

#413

I’m not sure if this is the right place for this… please let me know if bug reports, etc, should be somewhere else…

I was about to perform a patch leaning fairly heavily on Teletype today, but yesterday in ‘rehearsals’ (run throughs in my hotel room) on several occasions trigger outs became locked on, the script called for triggers, specified at 10ms in the INIT script, but once in a while a trigger would somehow become gate on and I would need to type a remedy to put the output back to zero, after which the script functioned as expected. I couldn’t go on stage knowing this might happen so I constructed a new piece with no triggers generated by TT.

The good news is the new piece is better than the old one, so as far as the audience is concerned - thanks Monome. As far as I’m concerned… I await response.

Yes, I was switching the input which triggered the script, but I’m not sure I’d see how this would be a problem unless there were voltage spikes which I’m pretty sure there weren’t.

Sorry I can’t give more detail now. Had to jump ship, so to speak, to save the show, and didn’t have time to make measurements, etc…

#415

doh! i just accidentally overwrote scene 02 that shipped with TT…
was looking the scene 02 description, then realized i needed to save my currently open scene before opening scene 02. so i hit alt-esc to save, but i guess TT loads the write screen on whatever slot you were last viewing, not the slot your scene was last saved to. because it had my current scene’s name up, i thought all was good. i didn’t notice it said “2” in the upper right hand corner.

if it’s not too much trouble, would someone mind sharing scene 2? was hoping to study it a bit.

also, i’d like to offer the suggestion that v2 firmware opens the “write” dialog set to the last memory slot that current scene was saved to.

1 Like
#416

i feel this would start down a road of diminishing what i feel is now a very comprehensible interface. the more we add, the higher the learning curve. i totally get that it’d be cool to add features like this-- i come up with my own ideas often that i tend to nix because they’re specialized.

i am also concerned that the opportunity to bottleneck performance could happen quite quickly if we add much more, as you mention.

i do have some ideas about alternative interfaces that might accommodate what you’re suggesting-- for example, i’d love to be able to dynamically create/destroy metro timers-- ie, have lots of them. similar to the hotkey feature, this would require some interface rethinking.

…and a whole lot of code.

#417

this should be an easy fix. maybe if the numlock is on it can be equivalent to holding WIN, ie trigger-scripts only.

confirmed this bug, will fix in next rev.

i suspect there are timing issues where multiple pulses get queued and then the polarity gets flipped. i’ve written scripts where this happens undesirably. i’ll consider some sort of enforcement method for when we only want same-polarity trigger pulses.

agreed! and i’ll get the scenes retyped and posted.

#418

yeah, agreed about the added complexity. i was thinking about the convenience of having more “gestures” available at any given time but 8 is plenty (and one thing i like about TT is limitations actually). and having SCRIPT and hotkeys for scripts 1-8 will also help a lot.

it’ll also be interesting using patterns and SCRIPT to sequence scripts.

#419

Can someone explain how mod is working in this context?

CV 3 V MOD DRUNK 5 (this is from the ‘manual’)

Says it will wrap the edges between 0 and 4. I understand mod (superficially) and drunk, and how to ‘set’ drunk, but I’m not understanding how they are interacting here.

Thanks.

#420

Every time DRUNK is called it increments it’s value by -1, 0 or 1. It is however still a ‘read’ operation, and is then being processed by MOD x 5 where x is the result of the newly updated DRUNK.

In other words, DRUNK is being updated every trigger, then being wrapped to the 0 to 4 range. You could do the same thing with the WRAP operator. From there it’s simply converted to a whole volt output and sent to the 3rd CV output.

#421

oh…i think i just wrapped (pun intended) my head around MOD…so no matter how large the called drunk value becomes…4 will always be the highest value. For instance: MOD 75 5 returns 0. MOD 74 5 returns 4. I get it! (I think…)

Thanks!

#422

http://monome.org/docs/modular/teletype/scenes-1.0/

1 Like
#423

Experiencing a bit of buggy behavior…

Sending a regular clock pulse (op-1 midi clock via opLAB) to input 8 on TT.
Simple script:

8:
TR.PULSE 1
CV 1 N P.NEXT

I:
TR.TIME 1 30
P.N 0

And then I have an 8 note sequence in pattern 0.

Occasionally the TR.PULSE 1 freezes up. Check out this video:

You’ll hear the audio from the sequence as well as the metronome from the op-1 for timing reference.
This happens more frequently when I’m running at a faster clock.
I tested running the clock directly from the OPLAB to my synth’s gate input, no problems with the clock source.

Sometimes it freezes up indefinitely and I have to reboot TT to snap it back.