#134

Ta. I’ll have a look and see what differences I can find.

Found this from here, will copy and use that instead of removing and adding the timers.

void pause_timers (void) {
  cpu_irq_disable_level(APP_TC_IRQ_PRIORITY);
}

void start_timers (void) {
  cpu_irq_enable_level(APP_TC_IRQ_PRIORITY);
}
#135

Yeah, exactly in aleph we put application timers on their own priority level for just this reason

1 Like
#136

It does not support Trilogy Meadowphysics remote by now, does it? At least I cannot get it to respond.

1 Like
#137

Are you sure you’re using the Trilogy commands and not the Ansible ones?

Ansilbe commands are:

  • MP.PRE
  • MP.RES
  • MP.OFF
  • MP.SCALE
  • MP.PERIOD

Medowphysics are:

  • MP.PRESET
  • MP.RESET
  • MP.SYNC
  • MP.MUTE
  • MP.UNMUTE
  • MP.FREEZE
  • MP.UNFREEZE
  • MP.STOP
#138

Yes, I am using L 1 8: MP.FREEZE I

The other commands do not work either here, so they should?

Of course the cable could have gone loose inside the case but checking this is very tedious - I am happy that I eventually got them all in with the interconnections. So it would be great if someone else could try it first…

1 Like
#139

I got another weird one. I was using the script I posted at > teletype : code exchange for about an hour without issue.

I switched scenes to 4Track, and TR.PULSE was broken. When I switched scenes, all four TR outputs stayed lit. I had to manually do TR.TOG to turn them off. However, upon receiving a PULSE, the TR stayed lit and would not turn off on its own without another TR.TOG.

I checked TR.TIME for all four outputs in Live mode, and they were all set to 100.

1 Like
#140

My MP is in my main case, and I won’t be able to remove it till the weekend. If anyone else that’s running the 2.0 beta wanted to test that would be great. One thing you could do @Leverkusen is try downgrading to 1.4.0 and see if it works with that?

@trickyflemming hopefully that’s something straightforward. Sounds like the pulse countdowns are getting confused on scene change.

Bug reporters… first of all thanks for the reports. If you want to make my life a bit easier, can you try and always upload and attach the scene text whenever you report a new bug. Even if you think it’s online already, please download it from your teletype again.

Also…

  1. Please report the full firmware version as reported in the front screen when you power up.
  2. Check bugs twice, including a power cycle between them (it’s okay to still report it if you think there is a bug, but you cant easily recreate it).
  3. If you have a bit of extra time, can you try and make the smallest example of the bug possible.
  4. If you really have some extra time. Can you try firmware 1.4 and see if that has the same bug too.
1 Like
#141

I downgraded to 1.4 and MP commands worked, then reinstalled 2.0 beta 5 (wich is actually called beta 4 in the OP) and it still works now. A bit strange since I tried it quite a lot yesterday but also good.

1 Like
#142

Okay, best to be on the watch to see if it happens again. Bugs like that are the worst to fix…

And I’ve sorted the first post out.

Next beta looks like it will be out over the coming May Day weekend. We’ve got the builders in at the moment, which is always far more disruptive than you imagine…

1 Like
#143

At the moment, the code remembers if you’re in live mode or in pattern mode and saves that to flash so that when you power up again it comes up in the same mode.

Does anyone find that particularly useful? Would anyone be sad if I removed it?

#144

I would not be sad. A little morose perhaps. :wink:

#145

In my opinion it is always good if modules remember their state on startup.
Always.
:slight_smile:

1 Like
#146

But it doesn’t though. All it remembers is if you’re in live or pattern mode. Not if you’re editing a script, not what line you’re editing, not which bit of the pattern you’re editing. Any unsaved scripts are also lost, along with variables, mutes, slew times, pulse times, etc, etc.

What we do do, is load the last saved preset. That’s the important bit surely?

Anyway. I removed it just to make it easier to make a change to USB saving and loading. I can re-add it very easily, but only as the simple live / pattern choice is was before.

New beta should be out today or tomorrow.

1 Like
#147

I’ve added some robustness to the TR.PULSE code, particularly with respect to checking that the timers are always less than the TR.TIME. That code with be in the next beta, hopefully it will fix the problem you had. I can’t do too much more without a simplified example, so if it reoccurs, I would appreciate any time you’d be able to give to that.

#148

this was a feature i requested a while back - i perform with teletype connected to a numeric keypad and like to have my scenes load in pattern view so i can keep an eye on things. i would trade the autoload for a way to toggle between live and pattern views on the numpad :slight_smile:

also, being able to load scenes with the numpad would be awesome. i know you can do this with the TT hardware - i just love the numpad ergonomics.

#149

Do you want to post a picture of your number pad so I can see what keys are available.

Anyone else using one, or is it just you?

#150

here it is:

numpad.jpg2448×3264 644 KB

perhaps forward slash ( / ) as pattern view toggle? if you’re considering scene loading as well, asterisk could bring up the load menu, with plus and minus to navigate and enter to execute.

not sure - but i suspect i’m alone.

1 Like
#151

I haven’t done this, but will absolutely try it now. For performance I rarely need the full keyboard, but would love something small like a numpad to enter data into the tracker view. Thanks for the idea!

#152

Sounds good to me.

The / will be mapped as TAB, so it will rotate through the modes. I’ll also map the + and - to behave like [ and ] in live and script edit mode (that way you could review the content of scripts even if you can’t edit them).

Are you running the beta yet? If not ping me when you are. I won’t implement the extra bindings until you can test them (as I can’t).

Numpad numbers run scripts, so can’t be used for data entry. Sorry!

#153

ah to clarify the numpad will not enter numeric values in the tracker/pattern view. it’s merely a manual script trigger pad. so key 1 will trigger script 1 and so on. i like it because i can keep all the TT inputs patched to sources in the modular while still having manual access to scripts. so one song might be totally driven by meadowphysics while another has a bunch of hand activated events.

2 Likes