Control Surface Integration (CSI) Technical Feature Discussion

[MixMonkey]

Originally Posted by Geoff Waddington

Hmmm...

The monitoring works fine here.

It's not in Reaper Actions anymore, it's on the Advanced Page.

I ticked the check boxes and..... nuttin'

[Geoff Waddington]

Originally Posted by MixMonkey

I ticked the check boxes and..... nuttin'

If you go back, are they set as you expect ?

Don't forget to OK the dialogs.

[MixMonkey]

Originally Posted by Geoff Waddington

What happens if you don't change CSI.ini ?

I end up with an updated CSI.ini that I don't want to use with my stable set up

[Geoff Waddington]

Originally Posted by MixMonkey

I end up with an updated CSI.ini that I don't want to use with my stable set up

What's the difference between the 2 CSI.ini files ?

[MixMonkey]

Originally Posted by Geoff Waddington

What's the difference between the 2 CSI.ini files ?

No idea. You said it was probably a good idea to let the new version create its own .ini, so I assumed there were changes. Hence the quarantine.

[Geoff Waddington]

Originally Posted by MixMonkey

No idea. You said it was probably a good idea to let the new version create its own .ini, so I assumed there were changes. Hence the quarantine.

Actually, the only difference is the refresh rate, CSI can read either style.

There were going to be more changes, but decided against it.

Also, did you see the post a few back about how to see if monitoring is working ?

[MixMonkey]

Originally Posted by Geoff Waddington

Actually, the only difference is the refresh rate, CSI can read either style.

There were going to be more changes, but decided against it.

Also, did you see the post a few back about how to see if monitoring is working ?

The boxes stay ticked, but no console window appears when controls are moved.

[Geoff Waddington]

Originally Posted by MixMonkey

The boxes stay ticked, but no console window appears when controls are moved.

Right you are, it was working yesterday, wondering what I did now

[Geoff Waddington]

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Hopefully fixed monitoring.

[MixMonkey]

Originally Posted by Geoff Waddington

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Hopefully fixed monitoring.

Still no go , i'm afraid.

[Geoff Waddington]

Originally Posted by MixMonkey

Still no go , i'm afraid.

Ah, got it, works in debug mode, but not release mode.

That's pretty rare, but I have seen it before, investigating...

[Geoff Waddington]

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

One more try at fixing monitoring

[MixMonkey]

Originally Posted by Geoff Waddington

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

One more try at fixing monitoring

Working now (including writing FX params, thanks!)

Icon B+ now working - idiot mistake on my part.

[Geoff Waddington]

Originally Posted by MixMonkey

Working now (including writing FX params, thanks!)

Icon B+ now working - idiot mistake on my part.

Good stuff !

Thanks everyone for all this testing, there is a reason for the rewrite

[Geoff Waddington]

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Fixed bug where adding a tab would mark the project dirty.

[Geoff Waddington]

Did I miss any bugs folks ?

Other than fourdogslong's strange button behaviour, which should be much easier to diagnose, now that monitoring is working, anyone got anything outstanding ?

[Funkybot]

Hey Geoff, I'll definitely jump in and catch up on all of this tomorrow. Was hoping to do it today but I've got people coming over later and have been choring all day (always seems to take way longer than I anticipate).

Sounds like no major syntax changes except for perhaps the CSI.ini right?

[Geoff Waddington]

Originally Posted by Funkybot

Hey Geoff, I'll definitely jump in and catch up on all of this tomorrow. Was hoping to do it today but I've got people coming over later and have been choring all day (always seems to take way longer than I anticipate).

Sounds like no major syntax changes except for perhaps the CSI.ini right?

Should be fine even with the slight change to CSI.ini.

MidiSurface "X-Touch" 8 8 60 
MidiSurface "SCE24" 9 9 60

The last number (60) is surface refresh rate, if it is missing CSI defaults to 15.

[edit] And, as discussed before, old auto mapped Zones will still work fine, but won't import correctly into Remap.

[jacksoonbrowne]

Hi Geoff,

I am going to testing out the new code on the X32 tonight.
Will let you know the results.

Cheers,
Roy

[Geoff Waddington]

Originally Posted by jacksoonbrowne

Hi Geoff,

I am going to testing out the new code on the X32 tonight.
Will let you know the results.

Cheers,
Roy

Thanks, looking forward to the results.

[jacksoonbrowne]

Hi Geoff,

When adding CSI control surface Reaper crashes if CSI.ini file does not exist.


Can we have CSI create a minimal CSI.ini file if it does not exist.
Something like the code in blue (I tested it and it works)

case WM_INITDIALOG:
{
    string iniFilePath = string(GetResourcePath()) + "/CSI/CSI.ini";

    // IF CSI.ini does not exist, create it.
    struct stat buffer;
    if (statUTF8(iniFilePath.c_str(), &buffer) == -1)
    {
        FILE * fpIniFile = fopenUTF8(iniFilePath.c_str(), "wb");
        fprintf(fpIniFile, "%s\nPage \"HomePage\"\n", s_MajorVersionToken);
        fclose(fpIniFile);
    }

    .....

[jacksoonbrowne]

Geoff,

Question: Is the source code on github up to date?

I am getting memory violations in

static oscpkt::UdpSocket *GetInputSocketForPort(string surfaceName, int inputPort)

at line:

if (s_inputSockets.Add(surfaceSocket))

[Geoff Waddington]

Originally Posted by jacksoonbrowne

Hi Geoff,

When adding CSI control surface Reaper crashes if CSI.ini file does not exist.


Can we have CSI create a minimal CSI.ini file if it does not exist.
Something like the code in blue (I tested it and it works)

case WM_INITDIALOG:
{
    string iniFilePath = string(GetResourcePath()) + "/CSI/CSI.ini";

    // IF CSI.ini does not exist, create it.
    struct stat buffer;
    if (statUTF8(iniFilePath.c_str(), &buffer) == -1)
    {
        FILE * fpIniFile = fopenUTF8(iniFilePath.c_str(), "wb");
        fprintf(fpIniFile, "%s\nPage \"HomePage\"\n", s_MajorVersionToken);
        fclose(fpIniFile);
    }

    .....

Thanks for testing !

No need for that fix, corrected it at source.

[Geoff Waddington]

Originally Posted by jacksoonbrowne

Geoff,

Question: Is the source code on github up to date?

I am getting memory violations in

static oscpkt::UdpSocket *GetInputSocketForPort(string surfaceName, int inputPort)

at line:

if (s_inputSockets.Add(surfaceSocket))

GitHub is always up to date, it's the working repo.

Matter of fact, check the last 2 commits, they are for the 2 bugs you reported, let me know if the fixes worked.

[Geoff Waddington]

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Fixed crash caused by missing files.

Possible fix for Windows OSC crash.

[fourdogslong]

Originally Posted by Geoff Waddington

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Fixed crash caused by missing files.

Possible fix for Windows OSC crash.

I just tested this, to see if any of the issues I've experienced have been resolved.

The TrackSend zone is not slow to load anymore, whatever you did that fixed it for me.

My scrub button (that is associated with a subzone) now works, but my buttons 13 to 16 still don't. Kindda weird that one button got fixed but I'll take it

Recalling visibility snapshot is still unpredictable, the visible tracks seem to land randomly on the controller instead of always starting from Channel 1. Also sometimes the first couple tracks of a snapshot land too far right on the controller making some other tracks inaccessible since banking doesn't seem to work when that happens.

For the assignment display, I noticed that there's always a small dot showing after the two letters I assigned, is that normal? For example the SE that shows by default is shown as SE in capital, not dot. The PN I assigned for pan mode is shows Pn. with a capital P and lowercase n with a dot right after.
It's no big deal I'm just curious about it.

Thanks a lot for all the work!

[Geoff Waddington]

Originally Posted by fourdogslong

My scrub button (that is associated with a subzone) now works, but my buttons 13 to 16 still don't. Kindda weird that one button got fixed but I'll take it

Now that monitoring works, you can use it to see if 13-16 are sending to Reaper/CSI.

Originally Posted by fourdogslong

Recalling visibility snapshot is still unpredictable, the visible tracks seem to land randomly on the controller instead of always starting from Channel 1. Also sometimes the first couple tracks of a snapshot land too far right on the controller making some other tracks inaccessible since banking doesn't seem to work when that happens.

Anyone else seeing this ?

Originally Posted by fourdogslong

For the assignment display, I noticed that there's always a small dot showing after the two letters I assigned, is that normal? For example the SE that shows by default is shown as SE in capital, not dot. The PN I assigned for pan mode is shows Pn. with a capital P and lowercase n with a dot right after.
It's no big deal I'm just curious about it.

See page 117, the example does exactly the same thing.

https://images.thomann.de/pics/prod/151261_manual.pdf

[fourdogslong]

Originally Posted by Geoff Waddington

Now that monitoring works, you can use it to see if 13-16 are sending to Reaper/CSI.

Yes, I tested buttons 9 to 16 and here's the result:

 IN <- SSL Nucleus 2 Press9 1.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 Press9 0.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 Press10 1.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 Press10 0.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 Press11 1.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 Press11 0.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 Press12 1.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 Press12 0.000000
Zone -- C:\Users\mathi\AppData\Roaming\REAPER/CSI/Zones/SSL Nucleus 2\Buttons.zon

IN <- SSL Nucleus 2 F5 1.000000
IN <- SSL Nucleus 2 F5 0.000000
IN <- SSL Nucleus 2 F6 1.000000
IN <- SSL Nucleus 2 F6 0.000000
IN <- SSL Nucleus 2 F7 1.000000
IN <- SSL Nucleus 2 F7 0.000000
IN <- SSL Nucleus 2 F8 1.000000
IN <- SSL Nucleus 2 F8 0.000000

Thanks to this I was able to find out that my Press13 to Press16 also had duplicates called F5 To F8, I guess in the official CSI release it didn't matter because Press13 to 16 still worked but in the experimental versions it caused a conflict.
I deleted these duplicates and now it works!

I knew it was probably something fishy with my setup since I was the only one seeing this but didn't know how to troubleshoot it, thanks to CSI input monitoring for allowing me to fix this!!
I hope you didn't lose too much sleep over this Thanks a lot.

[fourdogslong]

Originally Posted by Geoff Waddington

See page 117, the example does exactly the same thing.

https://images.thomann.de/pics/prod/151261_manual.pdf

Good call, thanks.

[Geoff Waddington]

Originally Posted by fourdogslong

Thanks to this I was able to find out that my Press13 to Press16 also had duplicates called F5 To F8, I guess in the official CSI release it didn't matter because Press13 to 16 still worked but in the experimental versions it caused a conflict.
I deleted these duplicates and now it works!

I knew it was probably something fishy with my setup since I was the only one seeing this but didn't know how to troubleshoot it, thanks to CSI input monitoring for allowing me to fix this!!
I hope you didn't lose too much sleep over this Thanks a lot.

Great, yeah, it seemed like a definition problem, glad it's sorted !

[Funkybot]

Geoff, using the latest EXP build and a fresh CSI.ini, setting up from scratch, I somehow ended up with crazy values in the refresh rates.

MidiSurface "MFTwister" 6 8 394702720 
OSCSurface "iPad" 8008 9008 192.168.1.168 
MidiSurface "X-Touch Universal" 25 26 1868181321

...this was on Windows in case that's relevant.

[Geoff Waddington]

Originally Posted by Funkybot

Geoff, using the latest EXP build and a fresh CSI.ini, setting up from scratch, I somehow ended up with crazy values in the refresh rates.

MidiSurface "MFTwister" 6 8 394702720 
OSCSurface "iPad" 8008 9008 192.168.1.168 
MidiSurface "X-Touch Universal" 25 26 1868181321

...this was on Windows in case that's relevant.

What happens if you now edit them using the config panel ?

[Funkybot]

Originally Posted by Geoff Waddington

What happens if you now edit them using the config panel ?

Reaper crashes mid-edit.

The first surface I edit seems to work. I enter the new amount and hit ok. But in the process of clicking OK after editing the value in the second surface, Reaper crashes consistently.

[Geoff Waddington]

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Fix for Windows refresh rate crash.

[jacksoonbrowne]

Originally Posted by Geoff Waddington

GitHub is always up to date, it's the working repo.

Matter of fact, check the last 2 commits, they are for the 2 bugs you reported, let me know if the fixes worked.

The fixes worked

[Funkybot]

Originally Posted by Geoff Waddington

New Exp build is up.

https://stash.reaper.fm/v/42044/CSI%20Exp.zip

Fix for Windows refresh rate crash.

Just checked and still crashing here.

Steps:

1. Open CSI prefs
2. Edit the refresh rate on MIDI Surface 1
3. Click OK
4. Edit the refresh rate on MIDI Surface 2*
5. Click OK

Result: Reaper crashes to desktop.


EDIT
*Not sure if this is related but the second surface is the X-Touch Universal and the Output port gets lost and doesn't show up when I edit it. So I'm adding the Output port back in before clicking ok.



Also, I don't actually have to change the refresh rate for the crash to occur. Just editing that second surface, and adding the missing output port will do it.

[Geoff Waddington]

Originally Posted by jacksoonbrowne

The fixes worked

Excellent !

[Geoff Waddington]

Originally Posted by Funkybot

Just checked and still crashing here.

Steps:

1. Open CSI prefs
2. Edit the refresh rate on MIDI Surface 1
3. Click OK
4. Edit the refresh rate on MIDI Surface 2*
5. Click OK

Result: Reaper crashes to desktop.


EDIT
*Not sure if this is related but the second surface is the X-Touch Universal and the Output port gets lost and doesn't show up when I edit it. So I'm adding the Output port back in before clicking ok.



Also, I don't actually have to change the refresh rate for the crash to occur. Just editing that second surface, and adding the missing output port will do it.

Just tried it again here, worked fine on Win 11 with 2 MIDI surfaces.

Are you trying to edit that messed up CSI.ini, if so, please chuck it and start fresh.

[Funkybot]

Originally Posted by Geoff Waddington

Just tried it again here, worked fine on Win 11 with 2 MIDI surfaces.

Are you trying to edit that messed up CSI.ini, if so, please chuck it and start fresh.

Ok, starting fresh seemed to do the trick. Thanks Geoff!

[Geoff Waddington]

Originally Posted by Funkybot

Ok, starting fresh seemed to do the trick. Thanks Geoff!

Excellent !