3.0.8_b1

If i build a Fx and want to change the fade time in the editor i use to type the time and dubbel click ad the time part.

This seems not to work anymore in 3.0.7 and 3.0.8.

Or am i doing something wrong???

Nico,

That all sounds great! I will play around with what's there over the week-end...

and yes, when I mean AND I mean what DL calls +, when I mean NOT I mean what DL calls -... Once again, my brain is mostly in ETC Express syntax, pardonne-moi, s'il te plait .


As the Aussies would say -

Love your work!


Freddy

Can not edit time or submaster in Master link

How i edit is firts ad a masterlink but if i want to tell with submaster i can not change the nummer.
Or if i want to change the time same thing.

Vincent

@Vincent
MLink editing have change a little bit, and if you have suggestions, they are more than welcome...

the proper way is :
add MLink
after define the sub linked (you MUST -for what i remember- use shorcuts to define the sub. 'ù' is the one define in the standard distribution, but you can easily change it)
after define times or target (you MUST use shortcuts too)

++

c'est vrai que l'accès au clic est bien pratique sur la fenêtre principale, est-ce compliqué de faire la même interface pour la fenetre mlink?
pipou

Âllo tout-le-monde,


I have experimented a bit with building a simple, 24ch plus grandmaster bi-directional Ipad OSC interface for :Light using TouchOSC and OSCulator. See attached example files for the three programs to work together. This is designed for a Lighting Designer to sit/wander somewhere and manipulating the individual channels via faders rather than by typing, and then yelling to the operator sitting at the computer "modify that cue, please". It might grow further, but that was the initial, humble goal .

During the building and testing, I noted an odd behaviour.

Test:

1. After all three programs are up and running the attached templates, I pressed GO in :Light, causing a whole lot of levels to change/rise/....

2. Then I slid my finger around the different marks (i.e. all channels to be between 5% and 9%) across all iPad faders repeatedly. Most of the channels will _not_ react in :Light and retain their original (:Light dictacted) value. On the ipad, they would change to the new desired value, as I have also built a kind of feedback into the OSC Routing.

3. The "stuck" channels only react to the ipad again once I reach 0 (or for some of them 100).


Also, I noticed that the rounding/converting from 255-base to 100-base (and necessary integer conversion within OSCulator) resulted in 1% differences between the percentage in :Light and the ipad. I fixed this by using ranges from 0.5 to 100.5 instead of 0 to 100, which worked.

Finally, the /pad/saisieText only ever displays nothing or "null", no matter if I switch to RPN or @mode.


There you go - any similar things met? How can one make the bidirectional connection between the channel faders more reliable?


Cheers,

Freddy

@Vincent & Pipou
i'll see if i can bring this functionnality back...
can you please list every windows when it should be this way?

@ freddy
there should be a 'leader' issue between DL and external controller.
i've to figure out how this happen and when...
the problem is i do not have acces to an ipad...

for the 255/percent conversion, here's the formula i use
Round(( (float)i * 100)/255)
and for the 100->255 conversion
Round(( (float)i * 255)/100)

can you try with something similar?

for the /pad/saisieText issue, maybe i've introduced a bug with @Mode attempt.
i'll look into it in April.

did you tried with Control app (available for both i^pad and android)?
the layer i've made is called dlPad.js

sorry for the lack of times in this moment...
++
Nico

Bonjour tous le monde,

J'ai un petit soucis avec les shortcut personnalisé une fois exporter mes propres shortcut quand je les importes dans une nouvelle session ils apparaissent bien comme changé mais ne fonctionne pas!!!

Je suis sous mac osx 10.7.3

Quelqu'un aurait-il le même soucis

Soizic aka oneshot

@Soizic,
je pense que c'est un petit bug...
pourrais tu essayer de :
-faire un Save et voir si ils fonctionnent
-si ça ne suffit pas, faire un Save, Quitter et réouvrir le sho pour voir si ils fonctionnent.

++

@Nico

En effet en suivant tes conseils cela marche à merveille
Merci beaucoup.



Petite question au niveau TouchOSC, j'essaie de corriger les boutons GO, GOBACK, sur la dernière version des download du site,
Je n'arrive malheureusement pas. Sais-tu la commande qu'il faut écrire sachant que /seq/go ne fonctionne pas ?

D'avance merci

Soizic

OSX TouchOSC Editor

@Soizic
et alors, quel est ton diagnostic pour le pb des shortcuts?

les commandes OSC fonctionnent, il faut juste ajouter un argument de 1 au message envoyé, genre:
/seq/go 1
(qui correspond au bouton appuyé... appuyé = 1, relaché = 0)

++

save + quit+ open et c'est opérationnel

J'ai modifié une n ième fois le thème d'affichage de mon PC et miracle, le texte est visible ! Ça ne venait donc sans doute pas de ton superbe software mais de ce *+####^*+= de windows !

Concernant l'accès au changement de valeurs avec pavé num + double clic, nous avions repéré la fenêtre du Mlink editor, je rajoute la fenêtre du FXeditor, pour les temps de montée, descente, di, do, w, etc... qui ne sont accessibles qu'avec les raccourcis clavier (ce qui est certes plus commode, mais des fois, le clic peut être pratique)
J'en ai pas repéré d'autres pour l'instant...
A+
pipou

Thanx pipou,
je vais continuer en anglais car j'aimerais bien savoir ce que pense Vincent de la suite et vu que tu m'a l'air de bien comprendre l'anglais...

Regarding the double-clic function to set value in the Fx Editor or the MLink Editor, i think we will face an issue:
with the new @Mode functions, when you hit a number, DL automagically add [CH] in front of it as generally when you hit numbers it's to define a channel.
And thus, it become complicated to assign by double-clic to times for example something called [CH] [1] (if you hit 1).
Don't doubt that @Mode will be present in both of these editors!

a workaround can be to disable leading [CH] when it's not explicitely specified.

what do you think ?
(it can be nice if experienced @Mode users also give their opinion)

++