Reaticulate crashes when parsing Reabank file

[madsonix7]

Hi there,

Today when I tried opening my latest Reaper sessions, I received the following ReaScript error message:

...Data\Roaming\REAPER\Scripts\Reaticulate\app\reabank.lua:311: attempt to perform bitwise operation on a nil value (field 'msb')

As such, I've been unable to open and use Reaticulate (which I've come to completely rely upon as part of my workflow).

I've made sure I have the latest versions of both Reaper and Reaticulate installed and have updated all ReaPack packages. Any further advice for how to get Reaticulate back up and running?

Thanks very much for your time!

[jtackaberry]

Can you please attach your Reaticulate.reabank (or email it to me if you're uncomfortable posting that in public)? I strongly suspect a syntactical error in your Reabank that's causing Reaticulate to barf.

I do consider this a bug with Reaticulate though -- it should be more robust against possible syntax errors and should never crash this way -- but in the short term, hopefully we can get you back up and running quickly.

[madsonix7]

Sure thing! I appreciate your reply and thanks for your help. Will this zip file work? GitHub won't let me attach the LUA file itself.

reabank.zip

[jtackaberry]

@madsonix7 oops, I didn't mean reabank.lua but rather Reaticulate.reabank. This can be found in the Data/ directory of your Reaper install, and it should called exactly Reaticulate.reabank. And yeah you'll probably need to zip that one too. :)

[madsonix7]

Ah! Gotcha. Here it is.

Reaticulate.zip

[jtackaberry]

If you look at the very end of that file, notice:

//! g="Spitfire"
Bank 4

It's that half-finished Bank line that's causing the problem. If you delete the quoted lines you should be good to go.

I'll leave this issue open so that I can make Reaticulate's reabank parsing code properly resilient to scenario.

[madsonix7]

Ah! No wonder. I was in the middle of editing a new bank yesterday. Thanks for that. Good to know that can happen.