4.0.0_b14

sl1200mk2 écrit: Hi Carlo,
I compile DL on 10.10 thanx to a virtualization of the OS.
on the virtualization, DL is very very laggish... at boot, main window is drawing each sub by each sub, it takes a while.... it's unusable....
but I thought it was a virtualization issue.
do you run 10.10 native on your mac?

++

I run 10.10 native. (I had to update as soon as possible, don't ask. Grrr.)

It takes not so much time to launch, about 9s since when I start my shell script (it doesn't run without it).
The program works as always. Still drawing process at the launch is "sub by sub", I can see them. Later don't. It's true they're there, so no need to redraw.
It's definitely usable.
I'm using it in rehearsal stage.

Maybe it's just Xquartz, waiting for an update.

A new thing: if I plug a midi controller (NanoKontrol) while it's running, then refresh midi sources and activate it... everything seems to be ok. Control changes faders rise up subs value but they don't pull down. I had to restart DL and than It works again.
It happened two times, tomorrow I will try to recreate it.

Carlo.

Maybe it's just Xquartz, waiting for an update.

maybe... we should ask XQuartz crew for an update....

A new thing: if I plug a midi controller (NanoKontrol) while it's running, then refresh midi sources and activate it... everything seems to be ok. Control changes faders rise up subs value but they don't pull down. I had to restart DL and than It works again.

please post results of your tests in order to identify the issue...

++

sl1200mk2 écrit:

A new thing: if I plug a midi controller (NanoKontrol) while it's running, then refresh midi sources and activate it... everything seems to be ok. Control changes faders rise up subs value but they don't pull down. I had to restart DL and than It works again.

please post results of your tests in order to identify the issue...

++

So...

Midi controller issue...

Midi controller unplugged / run dlight / load a show with midi plugin saved as active / plug midi control / Refresh Midi (controller is already active) -> control changes work to raise values but not to decrease them

If I create a new show, plug the midi controller and activate it for the first time it works properly.

If I'm running a show, unplug then replug it, DL doesn't work anymore.

In any case, I have to restart Dlight (not just reload the show) to do it works again.

That's it.
Could be a problem if, during a performance, it happens to unplug.

New bug or issue or something I didn't notice.

I'm on cue N in X1 and I change some values: if don't want to save it but to restore smoothly previous version I think I could load N in X2 than crossfade between the two... On the contrary when I load N on X2, output cut to saved one.
Crossfading leads to unpredictable results.

Thanks for your job,

Carlo.

Salut,Pour ma part pas de soucis de temps.

Par contre, dans le Device Listing, la fonction "Clone device model" ne fonctionne pas. Lorsque je clique dessus, rien ne se passe. Bug ?
Peut être que c'est que cette fonction n'est pas encore développée, mais dans ce cas là, y'a-t-il possibilité d'importer en une fois plusieurs exemplaire d'un même modèles de device ou faut-il importer autant de fois un modèle que le nombre de device utilisés ? par exemple j'ai 20 par led que je veux adresser à 20 channels différents, faut-il que j'importe 20 fois mon modèle par led ?

Merci d'avance !

Tibo

@Carlo,
thanx for the test about midi, I'll investigate.

for X2 loading, you're right, there's something wrong.. I'll fix it.
can you elaborate on: Crossfading leads to unpredictable results.

@Tibo

Par contre, dans le Device Listing, la fonction "Clone device model" ne fonctionne pas. Lorsque je clique dessus, rien ne se passe. Bug ?

la fonction n'est pas encore écrite... :whistle:

je pense que je vais l'écrire comme ça:
tu importes un Device
tu inscris 20 puis Clone.
DL va te proposer de cloner à la suite des circuits du Device référent, idem pour les gradas et va te demander si tu veux y inscrire un offset de grada (cad, tous les 50 addresses par exemple)

mais pour l'instant, c'est à la mano que tu dois les importer.

peux-tu me dire comme DL se comporte avec tes 20 pars?
les palettes?
les transferts?
la conduite?

++

Bonjour,
Il y a peut-être un problème au passage d'un cue à l'autre :
quand j'ai un WAIT sur un cue et que je fais un GO pendant le décompte du WAIT, si des circuits sont censés baisser du cue précédent à celui où il y a le wait, ils montent jusqu'à FF puis repartent de 0 à FF en boucle. Par contre si tous les circuits doivent monter, pas de problème, le wait est zappé et la montée programmée se passe bien.
Merci pour ton travail.
Jef