(teletype) 3.2.0 release

scanner_darkly · 2020-04-28T16:47:32.832Z

there were new ops added for scaling and calibrating faderbank values. try calibrating it and see if you still get negative values. having said that, this change shouldn’t result in negative values being returned without calibration. what range of values are you seeing?

desolationjones · 2020-04-28T16:51:28.318Z

Approximately -32 at minimum fader position, to -16356 at maximum position. Confirmed on two separate Teletype + FB systems.

Is the scaling/calibrating stored within TT global config or is it volatile like TI.PRM.MAP?

scanner_darkly · 2020-04-28T16:56:05.265Z

yeah that’s way off. pinging @discohead

calibration data gets stored to flash whenever you execute the ops.

desolationjones · 2020-04-28T16:59:31.541Z

Calibrating looks like it’s working swell. Not a big annoyance; in fact I have been lazily living with the small offsets so it’s good to force me to calibrate!

discohead · 2020-04-28T17:03:24.164Z

@scanner_darkly @desolationjones it’s working as expected now that you’ve calibrated? if so, sounds like everyone using 3.2 for the first time with a FB will need to calibrate.

scanner_darkly · 2020-04-28T17:05:44.776Z

still weird that it would flip the sign. my guess is that scaling using the default min/max values somehow results in this when the actual range is smaller.

desolationjones · 2020-04-28T17:08:19.354Z

Yeah I just calibrated on one of my systems and it’s all good. Persisting between power-downs too.

In fact I have a weird bonus with the calibration OPs because the F8R module echoes FB 1 thru 8 values on FB 9 thru 16. So I could calibrate the same fader two separate ways and save on some scaling within my code

discohead · 2020-04-28T17:16:39.579Z

@scanner_darkly yea the flipped sign is strange, I’m not sure what would cause that.

@desolationjones glad to hear it… and that is a nice little bonus for the F8R!

discohead · 2020-04-28T17:24:52.565Z

@scanner_darkly ah, I think it’s because ss->cal.f_max[fader] and ss->cal.f_min[fader] will not be initialized if you’ve never run FADER.CAL.MIN and FADER.CAL.MAX (or FADER.CAL.RESET)

unity2k · 2020-04-28T18:39:04.280Z

Could someone refresh my memory if FB in follower mode doesn’t allow TT to poll it for calibration via i2c and that in this mode I have to use the patch jacks to talk between the two devices?

desolationjones · 2020-04-28T18:44:43.323Z

unity2k:

FB in follower mode

will wait for I2C requests and reply with values.

FB in leader mode will send frequent I2C messages (nominally to the ER-301) and won’t respond to requests at all.

TT is leader only, so your FB must be in follower mode unless you stick to CV outputs only.

scanner_darkly · 2020-04-28T20:14:12.556Z

you’re right. it should be added here (otherwise it will initialize it with some garbage and lead to unpredictable results until calibration is done):

github.com

monome/teletype/blob/master/module/flash.c#L85


        scene_state_t scene;
        ss_init(&scene);


        char text[SCENE_TEXT_LINES][SCENE_TEXT_CHARS];
        memset(text, 0, SCENE_TEXT_LINES * SCENE_TEXT_CHARS);


        for (uint8_t i = 0; i < SCENE_SLOTS; i++) {
            flash_write(i, &scene, &text);
        }


        cal_data_t cal = { 0, 16383, 0, 16383 };
        flashc_memcpy((void *)&f.cal, &cal, sizeof(cal), true);
        device_config_t device_config = {.flip = 0 };
        flashc_memcpy((void *)&f.device_config, &device_config,
                      sizeof(device_config), true);
        flash_update_last_saved_scene(0);
        flash_update_last_mode(M_LIVE);
        flashc_memset8((void *)&f.fresh, FIRSTRUN_KEY, 1, true);
    }
}

discohead · 2020-04-29T01:49:24.112Z

github.com

discohead/teletype/blob/initialize-fb-min-max/module/flash.c#L85-L92


cal_data_t cal = { 0,
                   16383,
                   0,
                   16383,
                   { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
                   { 16383, 16383, 16383, 16383, 16383, 16383, 16383,
                     16383, 16383, 16383, 16383, 16383, 16383, 16383,
                     16383, 16383 } };

github.com/monome/teletype

initialize fb min max values

monome:master ← discohead:initialize-fb-min-max

opened 01:47AM - 29 Apr 20 UTC

discohead

+8 -1

eremitalf · 2020-05-04T15:39:59.269Z

no pressure but just to keep this possibility alive!

sendepause · 2020-05-05T13:36:53.860Z

Hi there, n00b teletype starter here. Just finished my diy version and diving with the studies.
Strange question perhaps, but i guess the studies were made with an older firmware. Are there anythings i should keep in mind?
For instance, i tried cv 1 0 which didn’t work and cv 1 v 0 did. So maybe there are a few changes in writing the code?

Starthief · 2020-05-05T14:00:16.656Z

Hmm… CV 1 0 should be identical to CV 1 V 0, because V 0 evaluates to 0.

sendepause · 2020-05-05T14:20:36.367Z

well, i am a n00b hahaha… So let me check later.
But, all things in the studies should work in 3.2…? That’s the most important question

csboling · 2020-05-05T14:36:24.698Z

As far as I know, yes. I reviewed these a while ago while going over documentation and I believe everything was OK. Certainly a lot of new functionality has been added since these were written but the existing studies I think should largely get you on your feet. Joe’s Teletype Talk videos are a really nice, ongoing set of deep dives for some more usage examples that exercise a lot of newer features.

riggar · 2020-06-03T17:17:36.880Z

attempting to update to 3.2.0 via mac BUT getting this on execution of the command update - any ideas?? thanks … ps not a mac user

Last login: Wed Jun 3 18:08:30 on ttys000

The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s /bin/zsh.
For more details, please visit https://support.apple.com/kb/HT208050.
/Users/admin/Desktop/teletype-3.2.0/update_firmware.command ; exit;
Admins-MacBook-Air:~ admin$ /Users/admin/Desktop/teletype-3.2.0/update_firmware.command ; exit;
/Users/admin/Desktop/teletype-3.2.0/update_firmware.command: line 3: dfu-programmer: command not found
/Users/admin/Desktop/teletype-3.2.0/update_firmware.command: line 4: dfu-programmer: command not found
/Users/admin/Desktop/teletype-3.2.0/update_firmware.command: line 5: dfu-programmer: command not found
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.

[Process completed]

infovore · 2020-06-03T17:31:06.227Z

do you have dfu-programmer installed and in your path, as per the instructions on the firmware upgrade page? It’s not clear if it’s installed or not from those errors; either it isn’t, or it is, but it isn’t on your path.