MIDIbox NG Release + Feedback

[FantomXR]

1 hour ago, TK. said:

Are you using the set_lock command in your .NGR script?

No, I don't use that. 
Hm... strange. At least the LED rings do not update. I didn't doublecheck with the controllers itself. I'll investigate .... 

 

Thanks for adding the load command!! ;-)

Edited December 30, 2016 by FantomXR

[Zam]

1 hour ago, TK. said:

The load command is supported now! :)

Great !

I go to test it right now :)

Best

Zam

[TK.]

1 hour ago, FantomXR said:

No, I don't use that. 
Hm... strange. At least the LED rings do not update. I didn't doublecheck with the controllers itself. I'll investigate .... 

I checked this with LRE2x8 - the LED rings will be updated

Or do you mean LED rings, which are assigned to various banks, but not to the selected bank?
Then I guess that they won't show the updated value until the assigned bank will be selected.

Best Regards, Thorsten.

[FantomXR]

45 minutes ago, TK. said:

Or do you mean LED rings, which are assigned to various banks, but not to the selected bank?
Then I guess that they won't show the updated value until the assigned bank will be selected

Yes. That's what I meant. Simple example:

LED ring 1 CC1 bank = 1

LED ring 2 CC2 bank = 2

if my software now sends both values for CC1 and CC2 only the selected bank gets updated. The unselected bank doesnt. If I switch to the unselected bank it shows the old value. If I than turn the controller in my software, the LED ring jumps to this value. 

[TK.]

Such a configuration doesn't fit to the intended use case.

Actually only a single bank is supported, and it's intended that all display elements have either an assigned EVENT for this bank, or that they are not assigned to any bank.

Best Regards, Thorsten.

[Duggle]

LOAD <setup>

Switch to another setup (.NGC, .NGS, .NGR, ... files)

 

So <setup> is filename without extension and all .NGC .NGR, etc that match will be loaded?

[TK.]

1 minute ago, Duggle said:

LOAD <setup>

Switch to another setup (.NGC, .NGS, .NGR, ... files)

 

So <setup> is filename without extension and all .NGC .NGR, etc that match will be loaded?

yes

[Zam]

Hi

Load command work fine :)

I just have a question regarding ^section == 0

When this script is read ? only after startup or reset ? before or after .NGC load ?

I'm able to automaticity load another setup without conditional with load setupA at section 0

if ^section == 0
 load setupA
 exit
endif

But I'm not able to chose a setup (with conditional)

The use case is to have "default" acting like configuration router

setupA (user config) automatically loaded at startup,

but if I press some button at startup it will load other setup, like setupB for dedicated calibration, or setupC etc..

if ^section == 0

 delay_ms 2000

 if button:1 == 127
  load setupB
 else
  load setupA
 endif

 exit

endif

 I have the event_button definition at NGC but if I press it, noting happen, setupA nor setupB are loaded and system is locked at default setup.

 

Best

Zam

[FantomXR]

I have another bug report. It's about the NRPNs. As far as I understand a NRPN contains at least three different CCs:

CC#98 = NRPN number
CC#99 = NRPN "bank"
CC#6   = NRPN value

So if I set nrpn=20, it sends CC#98 20, CC#99 0 and CC#6 depending on the value of the controller. If I go over 127, CC#99 changes to 1 and CC#98 counts again from 0. That makes totally sense. But! If I go over 256, CC#99 stays at 1 and doesn't count up to 2. 

Or do I overlook something?

[latigid on]

Is the range constrained to 255? NRPN works fine for me, at least internally controlling WS2812 hue.

[FantomXR]

45 minutes ago, latigid on said:

Is the range constrained to 255? NRPN works fine for me, at least internally controlling WS2812 hue.

I don't talk about range. I talk about NRPN number and referring to the NG manual this should go up to 16383...

[latigid on]

Maybe post the relevant part of an NGC?

[norbim1]

On 2016. 12. 30. at 3:41 PM, Zam said:

The use case is to have "default" acting like configuration router

setupA (user config) automatically loaded at startup,

but if I press some button at startup it will load other setup, like setupB for dedicated calibration, or setupC etc..

if ^section == 0

 delay_ms 2000

 if button:1 == 127
  load setupB
 else
  load setupA
 endif

 exit

endif

 I have the event_button definition at NGC but if I press it, noting happen, setupA nor setupB are loaded and system is locked at default setup.

The same problem for me. By further investigate NGR script doesn't go beyond the load command. Anything after "load <setup>" command doesn't execute.

BR Norbim

[FantomXR]

Why don't you call nothing with section == 0 but assign metas to the buttons directly so that they load a NGC file when hitting them?

[Zam]

8 hours ago, FantomXR said:

Why don't you call nothing with section == 0 but assign metas to the buttons directly so that they load a NGC file when hitting them?

Hey Fantom

Don't know about Norbim usecase.

In my case it was to select a config at start up, before all buttons get busy for other task.

Your option need a spare/unused button or a conditional flow by hitting two buttons.

Anyway, it's not a critical function for me any more

Best

Zam

[norbim1]

18 hours ago, norbim1 said:

The same problem for me. By further investigate NGR script doesn't go beyond the load command. Anything after "load <setup>" command doesn't execute.

The problem is that even the load command is in a conditional branch and the condition doesn't match, the commands after load doesn't execute. In the above example the "load setupA" doesn't execute in the else branch. Also miss the other commands outside the if branch.

15 hours ago, FantomXR said:

assign metas to the buttons directly so that they load a NGC file

Is there a meta op that loads a new NGC config?  I coluldn't find it in the user manual. Am I miss something?

BR Norbim

[Zam]

46 minutes ago, norbim1 said:

Is there a meta op that loads a new NGC config?  I coluldn't find it in the user manual. Am I miss something?

IIRC it's the same command as NGR:  type=meta  meta=LOAD<setup> ???

also I remember the function was deleted, then implemented again, not sure the downloadable NG1.035 have it,

you may probably build 1.036 from the source.

LOAD will load a "full" config NGC + NGR etc, if you just need to change .NGC you have to duplicate your NGR and just change the name according to both config

Best

Zam

[norbim1]

4 hours ago, Zam said:

IIRC it's the same command as NGR:  type=meta  meta=LOAD<setup> ???

AFAIK the load command works only from NGR. But never mind, I found the cause in "mbng_file_r.c", corrected and built it and now load commands in conditional branches work correctly.

BR Norbim 

Edit: Attached the diff

mbng_file_r.c.diff

Edited August 27, 2017 by norbim1
File attached

[TK.]

Hi Norbim,

thanks a lot for the bugfix! :)

It's in the repo now.

Best Regards, Thorsten.

[TK.]

I noticed that the last release was done 2 years ago, although many preliminary versions have been created meanwhile.

Therefore it's now officially available.

From the ChangeLog:

MIDIbox NG V1.036
~~~~~~~~~~~~~~~~~

   o new .NGR script command: send_seq (see cfg/test/seq* examples)

   o added new MIDI event types: Clock, Start, Stop, Cont

   o added new meta events to control a MIDI clock divider:
     MClkSetDivider, MClkDecDivider, MClkIncDivider

   o added new .NGC file configuration parameters:
     MidiClkOutPorts and MidiClkInPorts

   o new LCD format character '%L' allows to display logic control digits
     (MTC and status digits)

   o added new .NGR commands SET_KB_TRANSPOSE and SET_KB_VELOCITY_MAP.
     The configuration example can be found under cfg/tests/kb_6.ng*

   o encoder absolute mode: negative ranges are now handled correctly

   o .NGR LCD command: %d outputs the ^value

Best Regards, Thorsten.

[Zam]

On 04/03/2018 at 10:42 PM, TK. said:

I noticed that the last release was done 2 years ago, although many preliminary versions have been created meanwhile.

Therefore it's now officially available.

Hello

Now I'm used to build my MB_NG with latest pre release and updated code from SVN

But thanks for the official release !

Since I use this one for months, I don't catch any bug so far.

Best

Zam

[slo]

What is the correct usage of MidiClkOutPorts and MidiClkInPorts?

Is this all I need? I'm trying to send an incoming clock on Midi 1 to USB 1, I can't make it work so I'm thinking I might have to insert it into a Receiver / Sender event. Real newbie here on MB_NG, but what potential!

#Set Midi clock input port
MidiClkInPorts = 00001000000000000000
#Set Midi clock output port
MidiClkOutPorts = 10000000000000000000

 

 

[slo]

Ok, figured it out. I found an example of  MidiClkInPorts in one of the test examples seq1.ngc. I can see the clock start/stop now in MIOS Studio but no clock data (FE) I'm thinking it's filtered out so as not to mess up the input monitor display.

[ssp]

Hi Thorsten, was there a resolution to this? as I am looking to display the channel/track info on a glcd over each fader. i saw john finsters mackie clone and he was aable to have track info on his displays, I have messaged him hoping he will pop in at some time and i can discuss it with him, but i think he just used the mb_lc setup.

On 16/12/2012 at 9:22 PM, Duggle said:

Some questions:

 

• How about LCD display of dynamic text as in patch name(s) contained within a received Sysex message?

I've no solution for this yet, but to ensure that this won't be forgotten I just have added this topic to the MBLC page.
It will probably work in conjunction with a EVENT_RECEIVER which listens to multiple bytes instead only one - but this would blow up the memory storage format, because each EVENT would need to store the byte range.
Once a solution has been found, the label could be inserted into outgoing SysEx, but also displayed on LCD with a special formatting directive (such as %t)

Edited November 30, 2019 by ssp

[sprintf]

It is confirmed the actual NG-Firmware was not tested for a LPC-Core (maybe someone made changes, but tested it only on STM32?

 

The actual NG Release (1.037) in the github trunk does not work on LPC-Core !

see this thread :