Buggy I/O's

Lost a couple of hours messing around with the I/O when they were working fine. For some strange reason - and I will give each step as I did them - the I/O values under custom wouldn't display on the c-touch (fine in piced though).

I created all the I/O's I am using,

Created screen text to desc the function of the user defined integers.

Created nudge up's/down's with arrows above below the level indicator.

Level indicator set up with custom - post text ie hrs, offset of 0 (this could be where the problem resides - I realised it was wrong further down).

Copied and pasted the lvls and buttons for all the functions ie mins and secs and copied all the components for all the other user alterable timers I am running.

Edited each component to set the correct i/o.

Transfered the project, which didn't work - tried to alter the code (didn't know if I had to def the i/o variables - couldn't do this cause the tags had spaces - altered out spaces in the i/o tags. Transfered - still no good.

Realised the gain had to be set to 1 did this and project worked in piced Transfered - still no good. Thought the code was messing with the lvl status. Had a good look in there.

Finally opened i/o in c-touch. Found the values where actually changed to the "0hrs 0mins 0secs" displayed. Played with the lvl status in piced - set to default worked ok - sent back to custom no good again. Finally hit the calculate button and the lvl status started working with the custom post text setting.



I don't know if it is because the initial transfer with i/o's had the wrong gain that it stuck in there till altering or if you just need to hit calculate for it to work. Has anyone else had trouble with the gain getting stuck?

edit :

Found out I had to go all to default visual transfer then take all back to custom and then transfer.

Also in logic I had trouble with tag names - if the tag name was long and similar like : thisismytagtoturnsomethingon1 and thisismytagtoturnsomethingelseon1 the logic would get the value of one of the tags for statements containing either of the i/o tags (it appears to get the value of the shortest written tag) I ended up using the I/O numbers to access the integers and it worked immediately - and anihalated the need for the many lines of text I was writing because it wasn't working.