Jump to content

HOG 500


Recommended Posts



I got a concert that will have to be busked later this week. The venue is more of a theater type of place and the only decent console is a HOG-500. Bringing in another console will probably not be a option for this gig so I will most likely have to stick with the HOG-500 even tho its not a ideal solution for busking at all.


Anyway having only 8 sub-masters or quelists I plan on building different states into each quelist. Lets say QL1 "Front" 1.ALL profiles 2.Center-Vox 3.Drums etc. easy enough.


But for the chases im a bit unsure. So lets say QL7 will be "Chases" how does I then go forward ? I did try this one time before but without any luck to to short programing time.


Last time I did make up a page 2 that contained the chases on QL 1-8 on that page, then I made blank ques in QL 7 on page 1 were I in comment field wrote P2G1 (Page 1 Go 1) , I did also try G9 , neither did work.


If anyone could please help me out with this one it would be highly appreciated.


Anyone who have ever had to busk a show on a HOG-500 are also welcome to trow in any comments on how they did solve it and . 





Link to comment
Share on other sites

Triggering various chases from a 'master' cuelist is definitely a job for comment macros on a Hog 500. The chases don't necessarily have to be sitting on a physical fader for that to work - you can trigger virtual cuelists with comment macros.


It's been a long time since I got to grips with a Hog 2/500/1000 so I can't remember off-hand what the particular comment macros are that you'd need - but a glance through the manual will tell you what you need to know, I reckon.

Link to comment
Share on other sites

On the Hog 2 you need to put > before the action to make the macro. For example >g7:c7:r6 would cause fader 7 to go whilst also choosing 7 and releasing 6. A full list of the commands are in the (Hog 2) manual. I assume 500's use the same syntax.
Link to comment
Share on other sites

The way I tend to busk on the Hog 500 is by using external monitr, load virtual masters onto the screen, and trigger from the mouse, On there you can store all your non dim essential cues, ie position, chases, gobos,


I for example would have the intensits of any moving lights stored onto faders, depending on how many movers I would use 1-2 faders for this, ie 10 movers across the back truss I would store fixture 1, 3, 5, 7, 9 on fader 1 and 2, 4, 6, 8,10 on fader 2 to give the ability to flash them very easily, also on these faders I would have colours stacked to make it very easy to select certain colours ( only if you label everything ) whilst intensity is at zero


store essential generics on fader 3, for example x 6 profiles front light, I would have fader 3 cue 1 all 6 profiles on for full stage wash, fader 3 cue 2 DSC profiles 4 DSR profiles and 5 DSL and so on, if you take the times out of this cue it gives you a versatile way to switch from full stge wsh to DSC at the push of a button all in one fader.


If a monitor isnt available you can still use the Virtual list on the LCD screen ( pig+List ), this gives you a good place to store chases, positions etc to enable easy access to trigger them.


Another quick trick is although there is no intensity value on gobos I do a stack of them onto a fader to enable easy acess, also can be turned into a chase to create a very easy simple bnut effective look with full pause play control


Hope these tips help,



Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.