NG feature request: Self test/ Splash

[Duggle]

TK, I'd like to request the following (or similar):

 

To be able to define commands (splash script) that execute for a short time before the actual NG application.

The idea is that after these commands the usual Default.ngc is loaded and runs completely independent from what commands/allocations were made during the "splash".

 

The kinds of things in the splash script may be sequenced or animated LED patterns that provide a quick test of all display elements, including for example LCD scrolling text etc. The script may require commands that control the sequence e.g how long to execute the splash before loading the default.ngc, etc,etc.

Edited March 5, 2013 by Duggle

[TK.]

I like the idea, but I think that it would be better to load such a file (let's call it .NGR for "NG Run Script") after .NGC, because the .NGC file could contain important configuration commands (e.g. DOUT_MATRIX) which you don't want to duplicate.

 

Such a run script could also open additional possibility, therefore I wouldn't restrict the execution to the startup - it should be executed whenever a .NGC file is loaded.

 

Possible commands:

 

LCD "%CSelftest"

SET LED:1 127
DELAY_MS 10
SET LED:1 0
SET LED:2 127
DELAY_MS 10
SET LED:2 0
SET LED:3 127
DELAY_MS 10

...

LCD "%CFinished."

 

 

Best Regards, Thorsten.

[TK.]

.NGR scripts are now supported in V1.022

I implemented more functions than requested ;-)

-> http://www.ucapps.de/midibox_ng_manual_ngr.html

 

Best Regards, Thorsten.

[Duggle]

Well TK, this is amazing! :frantics:

Within the performance limitations of sdcard, this adds an awesome amount of potential without using precious RAM.

I started this thread with the desire for a sexy, colourful splash of the 64 rgb LEDs on my MIDIbox on startup, and now this!

 

I would like to play phrases with push buttons, to aid with the synth programmer functionality (auditioning while patch editing).

I take it that the performance of run-script events is not guaranteed if other EVENTs are triggered?

 

Say I have a run script that plays a phrase, it loops under push button control.  Meanwhile, I edit the sound. What is the worst thing that could happen?

[TK.]

I take it that the performance of run-script events is not guaranteed if other EVENTs are triggered?

 

Other events shouldn't affect the performance so much (let's say +/- 1 mS).

 

Say I have a run script that plays a phrase, it loops under push button control.  Meanwhile, I edit the sound. What is the worst thing that could happen?

 

The "worst thing" is, that other threads can't access the SD Card as long as the .NGR script is executed.

No issue for conditional labels (because they are processed from the same thread), but it could be an issue if you would like to use the MIOS Filebrowser.

 

Best Regards, Thorsten.

[Duggle]

 

The "worst thing" is, that other threads can't access the SD Card as long as the .NGR script is executed.

No issue for conditional labels (because they are processed from the same thread), but it could be an issue if you would like to use the MIOS Filebrowser.

That seems pretty reasonable, and very workable.

Perhaps, in time, it would be possible to produce a MIOS Studio warning in such a case, and to be able to gracefully terminate the script at a prompt.