No GUI in Reaper 7.22

[sewerynstawiarski]

Hello!
I had a brake in using Reaticulate, and when I got back there is just no GUI and it doesn't work. When I open the MIDI window on the track I can still choose and use articulations from the bank I have made, like it was before, but other than that nothing works. No GUI and no articulations changes. What should I do?
I did updated it through Extension -> Manage extensions.
I will be grateful for help!
Love your work :)

[jtackaberry]

The screenshot is from the JSFX (plugin) window, which generally you'll never need to interact with.

Have you start Reaticulate's GUI using the Reaticulate_Main.lua action?

See the first run section in the documentation: https://reaticulate.com/usage/#first-run

[sewerynstawiarski]

Thanks! It worked.
I have GUI know, but articulations still does not work. I am using it with sforzando and Standard Guitar from Native Instruments.
Can I ask if there is anything I can check to figure out why, despite adding articulations to the track, it doesn't work? I put Reaticulate first in FX Chain. I am using my own bank which I used many times before, it seems everything is in place but still...

[sewerynstawiarski]

So I have opened old projects, in which I am 100% sure that Reaticulate was working fine, but now there is no response. GUI works but no change of articulations. So I have opened a new project, created new track, did Reaticulate_Main.lua action and when I was trying to set an articulations this error came up:

22:27:30.432 [ERROR]   fatal: ...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:8622: bad argument #1 to 'SetMediaItemInfo_Value' (MediaItem expected)
stack traceback:
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:205: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:204>
	[C]: in field 'SetMediaItemInfo_Value'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:8622: in method '_insert_articulation'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:8697: in method 'activate_articulation'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:9353: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:9353>
	(...tail calls...)
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:2523: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:2451>
	(...tail calls...)
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3334: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3313>
	(...tail calls...)
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3334: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3313>
	(...tail calls...)
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3334: in method '_handle_event'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:2933: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:2897>
	(...tail calls...)
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3334: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3313>
	(...tail calls...)
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3334: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3313>
	(...tail calls...)
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3334: in method '_handle_event'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:4114: in method '_handle_window_event'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:4019: in method '_update'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3520: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:3520>
	[C]: in function 'xpcall'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:210: in field 'call'
	...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:218: in function <...pData\Roaming\REAPER\Scripts\Reaticulate\reaticulate.lua:218>

Can this info help somehow to make it work again? It's great script and I would love to be able to use it again.

EDIT:
So just a second ago, I did the same procedure just to be sure. The only thing I did different was clicking on a Bank/Set Program line where I wanted to put articulation and then I have chosen My bank because default was something else. And bang it works! But when I did the same thing in other track (adding articulations by clicking on the line not by GUI), it doesn't work. So now I have two instances of Reaticulate on separate projects. One works, one doesn't, and I have no idea why.

[jtackaberry]

Looks like it's very easy to reproduce that long error. Would you be able to send me a small example project where this occurs? Either attach the RPP here or, if you're not comfortable with that, you can email it to me . Thanks!

[jtackaberry]

Also, just to be sure, what version is being reported at the bottom of Reaticulate's settings page? (Click the cog icon on the top right of Reaticulate's main window and scroll to the bottom.)

[sewerynstawiarski]

Hey! Man, I'm sorry, it's messy situation, I don't know what is going on here.
I was not able to recreate this long error. After deleting the track and starting over on a new track everything worked fine.
So I went to the project where it was not working, just opened new track, did the start.lua action and it worked on the new track. So I had one track working fine and one not working at all in the same project. I just copied all vst to the new track and it seems to work just fine.

My version is 0.5.13

I will make some more test at the evening or tomorrow depending on the time available. Sorry for weird changes of the story here, it's surprising for me too.

ANOTHER CRAZY EDIT:
Just out of curiosity I opened the track where Reaticulate wasn't working. I had my own bank set. I changed the bank for one of factories bank, then I chenged again to my user bank. And everything started to work just fine. So I guess it was something with loading of the banks?