Some time ago I had a terrible experience using the Robe Spiider official GDTF. No response from the manufacturer. Had to use an anonymous built fixture type...
Okay. Thats a shame. I was shocked how fast they responded to me and fixed the files. And it's an old lamp from a discontinued line.
Did you contact them by this email? And i am in europe if that makes a difference.
Display MorePersonally, ai see it in a much simple way.
When I use “block cue x” I don’t want to block the tracking of the saved paraneters ONLY. I want to block ALL the parameters of every single fixture used on that sequence x.
That way I am sure that cue is totally protected. (Shouldn’t the LOCK option on sequences sheet do this??)
I am avoiding to use the example of eos’ blocking and auto-blocking tool…
zangetsu : that macro might be useful but it seems way too dangerous to use on a fast theater programming environment like the one I work at. Thanks anyway!
For that I would block the cue and use release on it. That way the tracking ends there and all the value that are actually needet are stored as hard values or am I missing something here?
Well at least Robe is very quick in their responses. Got an answer and a new profile for dl7f fixtures in 48h from robe.
You could make a group out of your houselights and assing that tho exec and make that group additive. Only set back with this is that all of the fixtures in that group will be at same level. But if it just "worklights" it does not really matter does it? And another set back is that you cannot fade groups execs in or out with commands.
Can't you use block plus release on that cue. That way its blocks all active parameters and stops tracking there? And I mean release from the cuelist.
Is not Go+ macro x working?
I'm still not understanding what the problem is. Not saying there isn't a problem I just don't get it yet. Can you brake it down to steps? What should happen and what should not happen.
And now reading previous post and waiting for answer.
If you have more than one cue then the store syntax is bit different.
Store cue please /remove
Or specify the exact cue number an store please / remove
Hello!
First to remove fixture from a sequence can be done in a few different ways.
From tracking sheet where u can manually select atributes you want to manipulate and with two finger tap open the calculator and from specials select remove.
Or you can use store remove witch in your case I would use. So select fixture by selfix twice to active all atrributes used by that fixture, then store/ remove from the sequence you want to remove it from.
Same method goes for presets groups etc.
For store problems I dont fully understand how you are storing atm.
But still if you don't use presets at all that would be a great place to start. Example you can use All presest to store looks or use other preset pools and combine looks from there. Then you could easily mix and match presets for each sets and keep them in line shen you modify and uptade the presets only.
And from store options I only usually only use source programmer and status active. That way I always know what I am saving just looking in the fixture window.
Hope you can get something out of this and its no too difficult to understand.
I use 1.9.0.1 and I use onPC as well, do you think this could be why does not work for me?
My bad dude. I did not realize that this was the dot2 forum. I'm talking about MA3 software not dot2
1.8.1.0
And tested on onpc.
And now i feel very stupid because i fid not realize that this is the dot2 forum and I am talking about grandma 3 software.
This exact line works for me. Load Seq 1 cue 1 please
I think the syntax might go like this load seq x cue x please
If I undertood you corretly. Edit the layout object and change the property to Goto. You need to be on setup mode in layout view when doing this.
Umm its still there. In the right upper corner there are these small toggle buttons. The one with MA is the ma2 and ma3 library.
And also make sure that you have the right sequence selected.
Use quotes if using MAtricks pool item name.
If using only pool number use Set MAtricks 1 "phasetox" 90
Set MAtricks "Fx Group 3" "phasetox" 90
U can filter Input and Output in the seq setting with worlds. GrandMaster will still kill all Output. But atleast this way you could stop worrying that you will mess up the other areas seqences. And u can still use world master instead of GrandMaster.
But ofcourse all in all it would be safest to use own sessions for both floors.
