www Remote Control GET/PROJEXTSTATE/section/key

[lollo]

Hi guys,

I don't know if this section is right, in case, suggest me where I must to write.

I'm not be able to show in the www_remote_control the string about this command.
I used the command suggest from main.js
[* GET/PROJEXTSTATE/section/key
Returns:
PROJEXTSTATE \t section \t key \t string]

changed it GET/PROJEXTSTATE/storage/text
for my needs.
On Reaper, I'm sure that the string is set because I used:

reaper.SetProjExtState(0,"storage","text","EEEE")

Can someone help me to understand why I'm not be able to show this value in the Browser.

Thx

[cfillion]

What have you tried? What is the response from REAPER to the GET/PROJEXTSTATE/storage/text request?

[lollo]

Originally Posted by cfillion

What have you tried? What is the response from REAPER to the GET/PROJEXTSTATE/storage/text request?

Hi Cfillion. Thx for your reply.
The key, as I wrote is 'text' and his value is 'EEE'.
This variable/key value is set by lua script, and I would like to recall this value by reaper web control in a simple variable or in a div (JavaScript).
But I can't able :-(

[lollo]

Hi again,

I'm sorry, yesterday I'm been writing by my phone and it doesn't suitable to write long text.

As I said, I tried to set the key'value, but I can not to see the reply from Reaper.
I used:

function wwr_onreply(results) {
var ar = results.split("\n");
var x;
for (x=0;x<ar.length;x++)
{
var tok = ar[x].split("\t");
$('#mydiv').html(ar[0])
}
}

and use this function to call the function

wwr_onreply('GET/PROJEXTSTATE/storage/text')

but in mydiv returns the string as I wrote (GET/PROJEXTSTATE/storage/text)
and not "EEEE" as I had set.

Another test has been:

function wwr_onreply(results) {
var ar = results.split("\n");
var x;
for (x=0;x<ar.length;x++)
{
var tok = ar[x].split("\t");
for (y=0;y<tok .length;y++)
{
$('#mydiv').append(tok[y])
}
}
}

but the result has been the same.

[cfillion]

Don't call wwr_onreply yourself. If you do wwr_onreply('something'), the "results" variable in wwr_onreply will not be set to something else: it'll just be the "something" you gave it.

// initialization
wwr_start()

// makes an HTTP request to "/_/GET/PROJEXTSTATE/storage/text" in the background
wwr_req('GET/PROJEXTSTATE/storage/text') 

// main.js will call this once a response has been received from the server (REAPER)
function wwr_onreply(results)
{
  // do something with results (the server's response)
  console.log(results)
}

[lollo]

Yeah Cfillion!

It works!
I was completely wrong. Wow, you has opened up a world to me!

Many thanks!

[lollo]

Ah, I forgot to ask you if you know the maximun size of the memory allocation of this function, beacause seems that it truncate or not memorize if the string is big too

Thx

[cfillion]

I wasn't aware of any limitation but I've just tested it: it appears to be 16,383 () characters for GET/PROJEXTSTATE. reaper.GetProjExtState can retrieve the full string. However, when saving the project, it gets truncated in the file to 2^13-(key length)-2 characters. It's truncated again to 2^12-(key length)-2 chars when opening it (subtract 4 instead of 2 to account for the quotes added in the project file if the key contains spaces). Funny how one bit is lost at each step.

[lollo]

Thx Cfillion,

do you think that SetExtData (so, no SetProjExtData) has the same limits?
Can you suggest me which method I can use to pass lot of data from Reaper to Browser?
Maybe with txt files and load by JavaScript, but seems an old method...

Thx

[cfillion]

GET/EXTSTATE doesn't seem to have the same limitation as GET/PROJEXTSTATE. I'm able to retrieve a 1MB-long string with both persist=false and true. It's slow though (~3 secs - curl reports an average download speed of 333k/s).

You could work around GET/PROJEXTSTATE's limitation by splitting the data in 2^12-(key length)-2 sized chunks over multiple keys. Project extstates are saved inside the project file while extstates are not: they're either stored in reaper-extstate.ini (persist=true) or in memory (persist=false).

[lollo]

Ok, so maybe is better to use tradition txt to pass the data?

Send an wwr_req('_[script lua to write file txt];GET/PROJEXTDATA/storage/text');

This double method allow me to know when the script (lua) has finished and by wwr_onreplay response I can recall a JavaScript function to load the txt. When The function has load datas, I resent the wwr_req as above.

What do you think?

[cfillion]

Do you need the data to be stored in the project file? Do you want it to persist across REAPER restarts? Or persist when loading a project file?

A text file would be pretty much the same as EXTSTATE: not linked with a project (unless you implement that yourself). (And you'd need an <input type="file">...)

[lollo]

I want only pass momentarily from reaper to browser some information. Name items, position, length and other parameters. I don't want to save in rpp project, but I only pass these infos.
I thought to use projextdata or extdata to share this info

[cfillion]

Then reaper.SetExtState('section', 'key', 'data', false) and GET/EXTSTATE/section/key is all you need. There is no apparent length limit and the data is stored in memory until deleted or REAPER is closed.

[lollo]

Understood!
Many thanks. You were very kind to help me.

You have answered to all my doubts.

[spk77]

Originally Posted by cfillion

I wasn't aware of any limitation but I've just tested it: it appears to be 16,383 () characters for GET/PROJEXTSTATE. reaper.GetProjExtState can retrieve the full string. However, when saving the project, it gets truncated in the file to 2^13-(key length)-2 characters. It's truncated again to 2^12-(key length)-2 chars when opening it (subtract 4 instead of 2 to account for the quotes added in the project file if the key contains spaces). Funny how one bit is lost at each step.

Isn't this a bug? What do you think

[lollo]

I don't know if it is a bug or not.
I discovered that the strings from browser to Reaper must to be long maximun 1023 characters (with ExtState mode).
Instead from Reaper to browser can be more and more long. I tried with 8000 characters and it works.
If there were a method from browser to Reaper to send more characters, would be fantastic.

[Meo-Ada Mespotine]

For whom it concerns:
I once wrote me a little programming-introduction for the WebRC:

http://mespotine.de/Ultraschall/Reaper_API_Web.html

maybe it of use for newbies in WebRC-programming.


@lollo
This seems to be some kind of limitation in Lua, but don't know much about that. I just read this here and there about that...