During a show tonight I experienced multiple times that a sequence would not turn off after releasing the Button (set up as 'TEMP').
I had 4 one-cue sequs with a short off fade.
Tapping the buttons in a rather random combination would some times leave a sequence on.
I'm thinking that should not be possible - unless there is something I don't know about the Temp-function?
Anyone else noticed this?
With that many lamps in a row you might get some fun from this:
Make on / off phaser, xWings = 2 and add a little fan on speed.
I've made an update to my plugin based on the feedback: ringens_rndpos_limits_v1_1.zip
Removed the unnecessary change of the Readout and used 'PercentFine'
Used the size of the selectiongrid to determine how many times to loop
(This makes the plugin work with MaTricks now!)
Fixed the problem if only one fixture was selected (one grid position)
As far as I could see 'counter' was the only variable not set as local (Except those used across plugins)
I tried the clever code for random between two values but it only returned whole numbers so I reverted to my old version.
I'm sure it will come handy though!
I get all sorts of strange behavior with parts! Had to stop using them for now.
Copying cues or sequences with parts is not possible (If you want identical copy)
Editing Parts is a mess too.
I've just finished my first Lua Plugin and I'm sharing it here: ringens_randompos.zip
This plugin gives random pan/tilt values to the currently selected fixtures.
It's quite fun to use and I'm sure it could be useful too.
There's actually two plugins and this is how to use them:
-- 1. Set your readout to percent
-- 2. Make a note of the minimum and maximum pan and tilt values you would like
-- 3. Run the plugin 'RndPOS Limits' and enter those values
-- 4. Each time you run 'RandomPOS' you will get a different look
If you see something you like, store it - it will never come back
More info in the Lua file.
Tell me what you think !
- - -
To anyone not familiar with how to import plugins:
1. Download and extract the attachment
2. Save a show to your USB stick to create the grandMA3 folder structure on your USB-stick
3. Copy the extracted 4 files into the plugin library folder on your USB-stick:
4. Open a Plugin Window on your grandMA3 and Edit an empty plugin slot/tile
5. Press Import, change drive from Internal to your USB-stick. and select ringens_randompos.xml
6. Press Export, and Export again, if you want the plugin to reside in your internal drive, so it is easy to import into other showfiles Repeat 5 and 6 for ringens_rndpos_limits.xml
7. Close Plugin-editor, and call the plugin whenever you need random positions
(I stole the instructions from a post by Andreas)
I believe the answer is "never" and I'm ok with that.
In fact I think it's a good thing because we will get added functionality and improvements for a long time.
I'm very concerned with the implemented stuff that works poorly.
I constantly run into issues and have to remember specific workarounds and what not to do.
E.g. using and editing parts (Last thing I discovered the hard way was that copying a sequence or a cue with parts does not work!)
I see how missing features could be a deal breaker but me personally hope that v1.5 have big focus on bug fixes and cleaning up existing stuff.
I'm curious if you reproduced and reported the 'Long names won't stick' issue? (Fixture Type edit)
And about the multi-select function, is the procedure that you should hold select-button pressed while selecting several objects?
As mentioned I get multi selection unintentionally when I work fast so maybe it should be adjusted so you actually need to hold it until selected?
Or maybe I should work with one hand on my back
It might look a little scary but here is the same code expanded with comments.
Yes it does
Thanks for posting the code with comments! that's what I need to learn and make my own code.
%d get it's value from st+i - but why %d?
Could I add more and do something like: ('Fixture %d at %x', st+i, xx+i)) with result %d=st+i and %x=xx+i ?
This was of course not meant as bug reports but I appreciate your answer.
MAtricks: Used old plugin
Multiple Sequ: OK, I did not leave enough time between press on SELECT and EXEC and it seemed random.
Presets: Sorry - was some Globals I had forgot.
Recipes: Consistently yesterday - not today. Pressing Edit + Exec and Recipe just showed VERY briefly
(Long names is the same today)
One would like to think I was exaggerating earlier - but here are my notes from today:
Fixture Type edit - Long name does not 'stick'
MATricks - All text in the interface disappeared
Sequence - Got two selected at once
Preset - Trouble deleting presets, some went gray, some no reaction at all.
Recipe - The entered recipes did not show up in the Sequence sheet
These crashes has not been reported.
First of all because I could not reproduce them easily.
But also because I struggle to find a meaningful way to report bugs in general.
To be meaningful ...
- If I've spent one hour to find how to reproduce and send 3 simple steps please try them instead of asking me to prepare showfile.
- Instead of assuming I must be wrong because 'nobody else have seen this' give it a try.
I would need a minimum of feedback
- A confirmation that it is indeed a bug (Or explanation on what I did wrong)
- A confirmation that it has been passed on to MA for investigation. (Most developers would then supply you with a reference..)
I've tried everything - Forum, distributor and directly to MA. Very low success rate.
I have multiple issues my distributor have forwarded to MA months ago.
Bottom line - I like to help because I bought this thing and need it to work.
Problem is it takes SOO much time. I find small bugs almost every time I sit down with the console.
I usually make a small note of it. I have plenty of those.
Also I'd say the software is very stable, I only know of one recently found issue that can cause a crash.
I have managed two myself in a couple of days.
One in Patch and one in Fixture sheet
I count 3 clicks to enable it, is that really a concern?
The procedure necessary to enable AutoSave was not my concern.
For all other software I know enabling AutoSave is a global setting - not a per document setting...
I use AutoSave because I sometimes forget to save.
Having then to remember to enable AutoSave is prone to the same problem (Forgetting)
That's what happened when I lost one hour Fixture Type editing last night.
I guess what I really want is AutoSave as a global setting / User setting.
May I suggest that until this software is more stable AUTO SAVE is enabled as default ?
(is there any reason to turn it off at all?)
Yes I've tried workaround #2...but as you mention...it sucks
I've also noticed that single-fixture groups automatically get appearance from the picture in the Fixture Type file.
Not a fan of that either. Too small to identify by and just makes text less visible.
EDIT: The last one I did solve. It was the Appearance field for a fixture under Fixture Types in Patch.
The Group did not use Appearance but an image from "Fixture Images" directly.
NOTE! Seems like you have to leave Patch twice before the changes update....
Let's say I have some Robe Pointe in my patch and they are called Pointe 1, Pointe 2, Pointe 3...
I select Pointe 2 and store a group.
I rename group "My special spot"
In the patch I now have Pointe 1, My special spot, Pointe 3...
Why would I want that to happen??
Can I do something to avoid it?