Toms projects

[GaryDouglas]

Is that just with "inuse" ?

[tom]

nope, also in 'all'

[tom]

I've played around with HC.SearchFixtureProperties, it works well enough. Certainly better than getvalue but it does also start to get laggy at around 200 fixtures.

[GaryDouglas]

We put in the search function to allow you to make the queries smaller. There is an internal limitation where if a lua call takes more than a certain amount of time we return nothing. This is a safety mechanism so that LUA doesn't interrupt fades and cause grief for the running show. We were hitting this with an app in development, so we opted to add this search function.

The single largest processing hit is dealing with all of the text. As the text gets larger, the cost of parsing it can increase exponentially, so it's always best to keep the queries small and more frequent. This can result in better perceived performance.

Try changing your page sizes to get things in smaller chunks. This should average-out the load over time.

If this is still laggy, let me know and I'll take a crack at optimizing the search a little more.

[tom]

What I'm working on is a more customisable version of the matrix software i made.

It allows the user to define the grid and then allocate fixtures within that grid.

So when i make the pass to visualise the output of the desk in the matrix software i use the command like this:

Code: Select all

HC.SearchFixtureProperties('#0" & used & "','all','-','-',0," & used_amount & ",'intensity')

used being the fixtures plotted into the matrix, used amount being the total number of those fixtures. I couldn't get a return if i let that blank. Works fine fow anything under 100 fixtures but starts getting clunky after that. I dont really see how that could be made smaller. Should i devide the total number out over a few search commands? Do you think it's even possible to deal with a couple of hundred fixtures at the same time? Maybe i'm aiming a litttle high.

I'm not sure what you mean by page sizes in this context. Is that pages of fixtures?

[RobertBell]

I'm wondering if you should just be monitoring Shownet or Pathport?

[tom]

Needs 10.5.12 to function properly.

Here it is,
Go to setup, define the grid and then press run.
Choose and assignment mode in setup and plot in some fixtures.
Monitor will read the levles from the table.

**Update is posted a few posts down.

[tom]

I've got more HC requests,

GetCuelistProperties(cues, timecode method, htp/ltp)
CueProperties(autofollow or not, run next cue, scripts)
Lookproperties(bump mode, scripts)
consolemode(tracking/cueonly)

[tom]

Matrix control update.

Still needs 10.5.12 to run!!!

Added:
Crude saving function which makes the app nearly usable.
Help function
Clear assigned fixtures function
Quick restart app to clear everything.

Fixed:
Spacing issues of the grid.
The visualiser runs ok up until about 400 fixtures after that it gets too choppy. The maximum grid is 40 x 40 after that it will probably crash.

Enjoy.

[GaryDouglas]

IF you split the entire grid into 4 calls, run at a faster interval (not perfect lua but here's the idea):

page_size = used_amount / 4
HC.SearchFixtureProperties('#0" & used & "','all','-','-',0," & page_size & ",'intensity')
HC.SearchFixtureProperties('#0" & used & "','all','-','-',1," & page_size & ",'intensity')
HC.SearchFixtureProperties('#0" & used & "','all','-','-',2," & page_size & ",'intensity')
HC.SearchFixtureProperties('#0" & used & "','all','-','-',3," & page_size & ",'intensity')

-- this will have issues in 10.5.12, but will work properly in 10.5.14 (due next Friday)