Icon V1-M Support, colour channels for FL Studio

[Paul Henty]

is your script loading OK and functioning but ignoring the mode type?

Yes, the script is running fine, it's just that no matter what mode I send with the value it always uses the same display mode - mode 1. Seems they just haven't implemented the other modes in the firmware. It's not much of a problem, mode 1 is fine for most parameters.

Paul

[stephenb]

Paul,

Please can I Lean on your knowledge again, do you know where I can gain a copy of one of the original MCU scripts? I want to see if any modified scripts have removed any important features around device placement.

I have figured out how to set up all 64 tracks with a script for each Extender and how to make the main script send despatch messages to back the Extenders and init track positions. I know there's a device count function by the main unit to detect Extenders connected and it adjusts its placement, I'm really interested in device identity, a way for the script to call what device it is and where its place as per the x1, x2 and so on, the goal is any order of units can be placed by a user without editing a script

[Paul Henty]

do you know where I can gain a copy of one of the original MCU scripts? I want to see if any modified scripts have removed any important features around device placement.

Each DAW has their own scripts. I can send the Studio One script for the MCU if you like (javascript) but it won't help you with placement. Studio One handles that internally so there's nothing in the scripts to do with placement. S1 just presents each controller with the correct tracks, having already worked out the relative placement and how many channels it has. The placement is setup within Studio One itself.

I'm really interested in device identity, a way for the script to call what device it is and where its place as per the x1, x2 and so on, the goal is any order of units can be placed by a user without editing a script

I've no idea how you would do that in FL Studio as I don't know how the FL scripting works. Do you have a separate script for each extender unit and the channel offsets are hard-coded in each script?

If you don't want users to edit the scripts, you could consider having a settings file (assuming FL scripts are allowed to read files). I have one for my script for setting user preferences. Users could edit that file and specify the order the units are placed on the desk. The individual scripts could use that information to know where it is and work out which tracks it should be dealing with.

If you only have one script that's used for all the extenders then you'll need a way to identify the device you're talking to. Can the script get the Midi port name for example?

Paul

[stephenb]

Hello Paul,

It's been a while, finally got my hands on a P1 nano, I've very quickly got everything working, I'm having an issue on ROW 3 and 4 with my bus information, on the V1 M I used to return 56 char to either row 0x00 or 0x38, now it returns that but adds an unwanted space after each 7 char, I can add a text msg directly to 0x00, 0x07 each for each channel, but when returning my 56 msg and spliting it into 7s to each of the 8 channels starting positions I still get this blank, the msg is defo 56 char, bugging the hell outta me!

[Paul Henty]

Hi Stephen,

It's a bug in the Nano's firmware. It's fixed in V1.22 but iCON haven't released it yet. I'll PM it to you.

Paul

[stephenb]

I've found an extremely painful work around I'm testing it tonight

[stephenb]

Haha did it

[Paul Henty]

Great. But will you not have to remove your hack with the corrected firmware? I've sent you the new firmware - check your private messages on here.

Paul

[stephenb]

Thanks I'll check it out, not so much of a hack but more of the long way round, 16 x sendmsg for each channel each row, with offset texts, but it works