#170

To me that sounds a bit dangerous – you could get into a situation where a script keeps hijacking the screen and you can’t stop it or do much of anything.

1 Like
#171

I can confirm that I am also seeing all variables count up when I try , and not update the time

A LAST 1

My build is 58DCD46

1 Like
#173

Thanks for the confirmation! Maybe I’m seeing things but at least I’m not alone :grinning:

#174

I did try with CTRL-F.. but doesn’t this mute scripts rather than the actual trigger outputs? If I have TR.P 1 in one script and also in another, then its not really muted. In other words, the cables I am “pulling out” are the trigger outputs , not inputs, for clarification.

#175

CTRL-F and MUTE apply to incoming triggers. there are no equivalent shortcuts or ops for trigger outputs, but you could use a trick - set trigger pulse length to 0: TR.TIME x 0 where x is the trigger number.

2 Likes
#176

posted new beta:

8 Likes
#177

Thanks!

I can confirm that LAST is working again (building from GitHub)! Just a heads up: building the docs (again from GitHub) is currently failing, but the .hex is fine.

Thanks again!

1 Like
#178

thanks for confirming!

what error are you getting when building the docs? it’s likely from me adding new sections but since i don’t have the toolchain set up for building docs i can’t verify.

#179

Isn’t the build stuff (latex + friends, I guess) included in the docker image, or did I provide those myself ???

Anyways, first stop is here:

Underfull \hbox (badness 10000) in paragraph at lines 1153--1155
[]\TU/RobotoMono-Regular.ttf(0)/bx/n/9 G.FDX id x y w h type level script

Underfull \hbox (badness 10000) in paragraph at lines 1157--1159
[]\TU/RobotoMono-Regular.ttf(0)/bx/n/9 G.GFX group id x y w h type level

Underfull \hbox (badness 10000) in paragraph at lines 1221--1223
[]\TU/RobotoMono-Regular.ttf(0)/bx/n/9 G.GFDR.L group odd_level
[4]
! Extra }, or forgotten $.
<recently read> \egroup 
                        
l.1233 \begin{op}{MI.\$ x / MI.$ x y}
                                     
?

Next (after pressing enter):

! Extra }, or forgotten $.
<recently read> \egroup 
                        
l.1233 \begin{op}{MI.\$ x / MI.$ x y}
                                     
?

Next

! Missing $ inserted.
<inserted text> 
                $
l.1235 \end{op}
               
?

And then it goes on on each press of enter a few more times…

Hope that helps :slight_smile:

2 Likes
#180

thank you! looks like i’ll need to get the toolchain set up, no idea how to fix that (not using the docker image here).

#181

even with the posted warnings, it’s possible that somebody might forget to backup scenes to a USB stick before reflashing the firmware.

i suggest that we update flash.sh and update_firmware.command files so that it creates a backup of the existing firmware/scenes before flashing a new one. it will only take a few extra seconds but this way at least you can restore it and backup the scenes if you forgot to do it. thoughts?

8 Likes
Teletype Talk
#182

Sounds like a good idea. When reflashing firmware I’m always super careful with my scenes. I’m not sure I’d trust the flash.sh to save me, but an extra level of safety net is a really good idea!

1 Like
#183

That would be great!

#184

Hi, I have had a tough bit of trouble finding direct information on this;

What is the status of potential ghost scripts and how do I access them? I wanted to put my 16n faderbank read on one of them.

#185

do you mean shadow scripts? they were never implemented.

1 Like
#186

Ah. Well, that there answers my question! Thanks! With a L function, I’m sure I’ll always have a line of space to have them around.

Thanks!

#187

Looks like the $ in the new op names is interfering with LaTeX, which uses that symbol to start or end an in-line math section. I can take a look if you didn’t already.

1 Like
#188

that would be great! i thought it might have something to do with that and checked what the doc for $ looked like and didn’t see any additional formatting there.

1 Like
#189

@desolationjones have your ops found their way into the consolidated beta yet? No pressure or anything but I also don’t want you to think there’s no interest. I’m eager to try these out, preferably alongside the binary and hex entry ops.

#190

They have not! I had to RMA my CPU so the compy has been sitting idle. But the new CPU is working well and I hope to make time soon for this pull request. I am also eager to try the hex entry mode :smiley:

1 Like