OSCope vs Shell Keyboard

OSCope is a simple field-debugging tool for checking OSC (Open Sound Control) over UDP, right on the spot. Ideal for verifying connections with TouchDesigner, Max, Unity, openFrameworks and more. No server, no account, no data collection — just open and go. FEATURES - Real-time OSC receive log (time, address, type tag, arguments) - Per-address scope charts (int / float / bool) - Per-address value meters (0..1 values shown as a bar) - Log filter (by address / value) - Pause and Clear for the display - Record incoming messages and export (Data tab / CSV / JSON) - Manually send any OSC message (int / float / string / bool) - Signal-generator send (fixed / sine / noise / Perlin noise / toggle, auto-repeat) - Save and recall named presets of your send modules - Quick Send buttons (e.g. /test/ping) - Saved settings: receive port, target IP and port - Always-on analog clock for timing during shows - Portrait & landscape layouts, dark instrument-style UI GREAT FOR - Quickly confirming OSC connectivity in installations and live shows - Seeing whether OSC sent from a desktop tool reaches your phone - Watching incoming values as waveforms and recording them to review later - Sending OSC triggers and test signals (GO / RESET, etc.) from your phone CONNECTING WITH TOUCHDESIGNER - Receive: send from TouchDesigner's OSC Out to OSCope's shown IP and receive port (e.g. 8000) - Send: set OSCope's target to TouchDesigner's receive IP and port NOTE Uses UDP on your local network; iOS will ask for Local Network permission on first use. Communicates with devices on the same network/subnet. Receiving supports OSC Bundles; supported types are int / float / string / bool.

Shell Keyboard adds the keys a terminal actually needs — the ones iOS's default keyboard leaves out. Working over SSH or in a local shell needs Ctrl, Esc, Tab, arrow keys, and function keys, none of which exist on the standard iOS keyboard. Shell Keyboard is a custom keyboard built specifically for terminal apps like Blink, Termius, Prompt, a-Shell and iSH — it sends the exact ASCII control codes and ANSI/VT escape sequences your terminal expects, the same bytes a physical keyboard would send. WHAT'S INCLUDED • A dedicated terminal layer: Ctrl, Alt, Esc, Tab, arrow keys, Home/End/PgUp/PgDn, and the punctuation a shell prompt uses constantly • Ctrl and Alt as proper modifiers — latch one for a single keypress, or double-tap to lock it on, like a hardware keyboard • A full function-key layer: tap fn and the top row becomes F1 through F12, while every other row stays exactly where it was • Arrow keys that match the app you're in — Normal for shells, Application for vim, tmux, less and htop, or Move the Cursor for ordinary text fields • Return or Enter: long-press the Return key to switch between a carriage return and a line feed • A plain QWERTY layer and a complete symbols layer, for ordinary text — hostnames, paths, commit messages — without leaving the keyboard • A searchable reference inside the app, listing every key alongside the exact escape sequence and hex bytes it sends • Every key emits the exact byte sequence a real terminal expects BUILT FOR PRIVACY Shell Keyboard never asks for Full Access. It cannot reach the network. It never reads, stores, or transmits anything you type — every key it sends is decided from the key you tapped, and nothing else. No analytics, no crash reporting, no account. GOOD TO KNOW In a terminal or editor running inside a web browser — code-server, Jupyter and the like — the keys that send a multi-character escape sequence don't get through: the arrow keys, F1 through F12, Home, End, Page Up, Page Down, Shift+Tab and Alt combinations. Everything that sends a single byte works there normally, including every Ctrl combination, Esc, Tab, Return and ordinary typing. Web pages listen for key press events and iOS only lets a keyboard extension insert text, so this is an iOS limitation that applies to every third-party keyboard, not something an app can work around. WHO IT'S FOR Anyone who SSHes from an iPhone or iPad — sysadmins, developers, and anyone tired of missing Ctrl+C.