Some new Titan requests

[(iCe)]

I've got some more concerning Titan.

1) When patching, you can't quickly see what the next free address. Also, it would be great if you could select an existing (patched) fixture so the "fixture-to-patch" is set to the same DMX line and the next free address on that line.

2) It's possible to batch delete fixtures, could it also be possible to batch move fixtures to another line?

3) I played around with the overlap functions for chases a bit. It's great, but it would be even better when that stuff could be controlled via the wheels as done with the shape gen. And for the second wheel; a phase offset could be added. Offcourse that wouldn't be an actual phase offset, but perhaps it could shuffle the fixture order to get more random effects (i.e. not the straight offset offered now). A softkey could be used to switch wheel function.

4) There was something strange going on with the colour effects for MAC250 Entour fixtures. I couldn't get a normal colour bump out of it, it only seemed to work with the flip down shape (color 1) and when the colour on the fixture was set to split colours. I would expect it to work when even when the fixture is at locate (white) and I select any shape which works on colour 1. One thing I noticed on the DMX output, is that the console was actually doing things with the second (16 bit) DMX channel for colour.

5) An extra option "Set locate values" in, for instance, the patch menu would be great. That way you could set default values for for instance the Focus attribute. That's one which you want to set once and then have it back to the set default value which you programmed before everytime Locate Fixture is pressed.


I had some more, which I will probably remember later on

[(iCe)]

Remembered one! Is there an option to view what's currently in the programmer? That would be a nice one for the VDU.

[(iCe)]

And another. For unknown reasons I couldn't get the Wheels view to show on the VDU. The option was checked, but no window appeared. Tried unchecking / checking a few times, also tried restarting Titan; nothing helped.

Also; for some reason I couldn't get the flash buttons to work as normal flash buttons. Pressing one blacked out everything apart from the pressed flash button. In take over mode, the flash button acted as a pallet select button (as expected). In run mode, the black-out behaviour appeared. I tried playing around with the key profiles, but couldn't find a solution there.

[niclights]

1) When patching, you can't quickly see what the next free address.

The software will always show the next suitable available address when you choose DMX line.

4) There was something strange going on with the colour effects for MAC250 Entour fixtures. I couldn't get a normal colour bump out of it, it only seemed to work with the flip down shape (color 1) and when the colour on the fixture was set to split colours. I would expect it to work when even when the fixture is at locate (white) and I select any shape which works on colour 1. One thing I noticed on the DMX output, is that the console was actually doing things with the second (16 bit) DMX channel for colour.

Agreed. Actually I'm not sure if it's working in split/step down either. I think the problem is somehow related to 16-bit within ranges. I tried on a Mac700 in 31ch mode and this also did strange things. Testing on fixtures with 8-bit colour wheels there is no problem. If you set the colour attribute to raw it will work correctly. Which also raises the question about the 'raw' colour function on the Entours. What on earth happened there? Aliens. Almost certainly.

5) An extra option "Set locate values".....

Agreed again. Also highlight/lowlight. I believe the latter is already available in Titan engine and would just(!) need UI.

Is there an option to view what's currently in the programmer? That would be a nice one for the VDU.

Not yet.

For unknown reasons I couldn't get the Wheels view to show on the VDU

There are maybe a few possibilities - window is undocked, perhaps also resized and moved somewhere you can't see it; window is hidden (docked or undocked) although this should resolve with deselect/select; window is docked but resized so you can't see it. This might be the most likely - with a standard dock on the left side of the window it is possible to drag the resize bar all the way to the left making it look like there's no window. Try hovering mouse over left side and see if a window division icon thing appears (I invented the term)

for some reason I couldn't get the flash buttons to work as normal flash buttons

Are you sure it's not key profile? Sounds awfully like swop. Any individual key profiles will override globals, even run and run takeover. Or perhaps the run profile has become altered although this should not be possible in v2.

[ChiekuRs]

I would like to add request for feature that was in pearl, but is gone from Titan - blind mode. Also it would be good if visualizer could 'follow' in blind mode - when it's activated, show contents of programmer, not console output.

About VDU - I have encountered with similar problem - I was unable to see one window (can't remember now which one exactly) - when playing around with window positions I somehow moved it out of screen. Enabling and disabling didn't help. At startup I was able to notice it showing for a split second, but after that it was gone. I can't remember how I got it back.

[(iCe)]

And another one (I'll read your reply tonight Nick!).

How about a release mask for pallets? That way you could create strobe buttons which make the fixtures strobe as long as their pressed and return to their original values once release. This would be a very simple but powerfull option in my opinion.

[(iCe)]

I think I brought this up before, but why isn't there an online list we can view? Now, we have no idea what Avo is working on, which features will be included in next versions and which won't make it (in the next version or at all). With a voting system, Avo could also monitor which feature requests get the most votes to address priority to the features which the most users find interesting enough.

[(iCe)]

The software will always show the next suitable available address when you choose DMX line.

I don't think this goes for parked fixtures.

Agreed. Actually I'm not sure if it's working in split/step down either. I think the problem is somehow related to 16-bit within ranges. I tried on a Mac700 in 31ch mode and this also did strange things. Testing on fixtures with 8-bit colour wheels there is no problem. If you set the colour attribute to raw it will work correctly. Which also raises the question about the 'raw' colour function on the Entours. What on earth happened there? Aliens. Almost certainly.

Major problem if you ask me; this should definitely be addressed in the next version of Titan, perhaps even a minor release to fix it. I'll patch the non-extended version for my next show, but that's an ugly workaround for a bug which shouldn't be there.

Agreed again. Also highlight/lowlight. I believe the latter is already available in Titan engine and would just(!) need UI.

Yeah I thought I'd already posted this before. I can only assume that this won't be too big of a problem to implement.

Not yet.

Ok. Would be nice though. VDU views need attention, but we've been there before. One thing which I find weird is that menu options which aren't working are left in for production builds of the software. That doesn't give users a good impression of the software if you ask me.

There are maybe a few possibilities - window is undocked, perhaps also resized and moved somewhere you can't see it; window is hidden (docked or undocked) although this should resolve with deselect/select; window is docked but resized so you can't see it. This might be the most likely - with a standard dock on the left side of the window it is possible to drag the resize bar all the way to the left making it look like there's no window. Try hovering mouse over left side and see if a window division icon thing appears (I invented the term)

I'll try that. The weird thing is that the window actually showed during the startup of the software. But once it finished loading, it just disappeared. Might make sence when window states / positions are saved and restored on load.

Are you sure it's not key profile? Sounds awfully like swop. Any individual key profiles will override globals, even run and run takeover. Or perhaps the run profile has become altered although this should not be possible in v2.

I must say I really can't get my head around this key profile thing. Apart from not totally getting what it's meant for or how it should be used, it seems to bother me more then it actually helps. Where should I look to address this problem? You're probably right on swop, just need to find the way to return it to flash again


Thanks for your input again, just hope Olie is getting this too!

[niclights]

You come across as angry today

why isn't there an online list we can view? Now, we have no idea what Avo is working on, which features will be included in next versions and which won't make it (in the next version or at all). With a voting system, Avo could also monitor which feature requests get the most votes to address priority to the features which the most users find interesting enough.

I understand where you're coming from but personally I think that could go horribly wrong. Features that might be intended may be dropped or postponed for various reasons. Also, the development time periods are long so chances are such input would not be able to influence the immediate version.
Maybe some subforums instead - ie. feature requests/bugs?

Major problem if you ask me; this should definitely be addressed in the next version of Titan, perhaps even a minor release to fix it. I'll patch the non-extended version for my next show, but that's an ugly workaround for a bug which shouldn't be there.

No bug should be there and obviously they should all be fixed. I've already forwarded this in case it is not known. I'll let someone else comment on the priority.

I must say I really can't get my head around this key profile thing. Apart from not totally getting what it's meant for or how it should be used, it seems to bother me more then it actually helps. Where should I look to address this problem? You're probably right on swop, just need to find the way to return it to flash again

Program mode. Playback options. Select playback. Have a look at the key profile softkey. If it's set to 'global' then it should respond normally in standard run mode.

[EmmaThompson]

Thanks for your input again, just hope Olie is getting this too!

Suggestions and feedback from this forum is put to our directors regularly, and although the software team are super busy and might not always have the time to reply personally, they are listening to what our users have to say

[(iCe)]

You come across as angry today

Sure didn't mean to, sorry! I'm a bit tired though, so that may be it. Sorry again!

I understand where you're coming from but personally I think that could go horribly wrong. Features that might be intended may be dropped or postponed for various reasons. Also, the development time periods are long so chances are such input would not be able to influence the immediate version.
Maybe some subforums instead - ie. feature requests/bugs?

Doesn't even have to go that far, just a list of things which are on the roll for the next version is a step ahead. Now I don't have a clue on what the plans are, apart from the stuff you mention sometimes. And without feedback, I also don't know what actually happens with the things I report. Could be that the developer(s) misinterpret something mentioned here and end up implementing it wrong (from end-user point of view) or even implementing something else as intended. That sort of thing could be avoided when there's a little more two-way communication between development and end-users.

Program mode. Playback options. Select playback. Have a look at the key profile softkey. If it's set to 'global' then it should respond normally in standard run mode.

Will do, thanks. But you mention playbacks, I wasn't having any problems with those; those worked as expected.

@EmmaThompson: thanks, I'm eager to get my hands on v3 (e.t.a.?)!

[niclights]

Ah. Oh dear. Now I see the problem. Fixture profile for the grey button isn't working properly. How embarrassing!

Essentially what's happening is the grey key is duplicating the definition for the blue key for fixtures (only flash & swop, not selection). So in run mode you are getting a swop action when you should get a flash.
The only workaround I can think of is to create a profile where the blue key is flash. This will then ensure you get a flash on the grey key as expected. Obviously this means you can't swop but it only applies to fixtures.
If you must have swop and flash then you could create cues that mimic the fixtures.

Maybe you should consider beta-testing?

[niclights]

Actually there's a simpler workaround. The problem only occurs when there is no palette on the fixture handle (and explains why I hadn't noticed this). So you could store a palette there instead. Chances are groups or macros will work equally well.

HTH

[EmmaThompson]

@EmmaThompson: thanks, I'm eager to get my hands on v3 (e.t.a.?)!

It will be officially launched at Prolight and Sound in Frankfurt on the 24th March

[(iCe)]

Maybe you should consider beta-testing?

Is this fixed in the curreny beta release? I'm doing a show next weekend so if it's stable enough I'll give it a try, but if it's still dodgy I'll go with the workaround for now. The console was pretty empty at the time I was there, so there probably wasn't a pallet. Weird though that I'm the first one to notice with v3 already coming up!