3.0.24_b2

let's go for the new beta wave (a shortbreak one I hope)!

build system is slightly different from previous releases.
now we have :
- MacOS 10.6/10.7 build linked against XQuartz 2.7.4
- MacOS 10.8/10.9 build linked against XQuartz 2.7.5
- and the good old Win32, Linux32, Linux64 releases

on Linux and MacOS, every lib have been updated

here come the news....:
OLA:
on each supported platform (eg MacOS && Linux), OLA is up to date with their GIT repository

INHIBITION:
new concept for this function : from the main board, place the mouse on the channel's number (the white one), hold Shift and drag it to a submaster.
thus the submaster switch to INHIB mode and is loaded with a *non-editable* content that is called VOID.
you can load one or several channels.
it's intended to be a quick access to inhib function. the old method is still functional.

GENERAL:
windows size and position should adapt to current screen size

ARTNET:
with this release you can list and select 3D visualizer (Capture Polar for ex) as a node to stream DMX to it.

MIDI:
a confirmation is now asked when you click on the script button that set factory's connections.


regarding the 4.x.x serie, work is in progress and new updates will come soon.

enjoy and please report any wrong behaviors or satisfaction.

++
Nicolas

Testing it now, the inhibition is VERY intelligently thought of and FAST, chapeau!

One thing I do miss (maybe I am not looking good - I work with 3.0.18 daily and missed out on newer versions): Where can I check the inhibition that is present? I ask because of the following:

It is possible to make an inhibition for, let's say channel 1 -> 6. Let's say we put it on 70.
It is also possible to make an inhibition of channel 4 -> 10 at the same time. Let's say we put it on 50.

How does :Light handle the inhibition in this case? Does it (where it = ch 4-6):

1. Follow the lowest inhibition for channel 4, 5 and 6, i.e. 50?
2. Follow the last made inhibition, so when I first made INHIB 1-6 it will be 70, when I last made 4-10 it will be 50?
3. Follow the last inhibition changed, i.e. when I change 4->10 last the inhib will be 50, if I changed 1-6 last it will be 70?
4. Does it mediate (unlikely but just asking) so 50 & 70 becomes 60?

It would be nice to have an inhibition window like before, even if it is view only, to see which channels are being inhibitioned (new English word?) and by which amount.

By the way: It could come in handy to have the option of two inhibitions overlapping the same channels so I do not see this as a bug but a feature, you do not have to change this overlapping behaviour (IMHO).

Merci beaucoup, a bien tot!

Bug? I cannot use ENTER in the @mode on the main screen. Example: [CH]1[+]2[@]85, when closing the statement with ENTER nothing happens; the statement is still on the screen and no action followed. I tried to delete all shortcuts and load them again but this makes no difference.

Hi Wilf,
sorry for the late reply I was coding....

Testing it now, the inhibition is VERY intelligently thought of and FAST, chapeau!

thanx!
it was during a training course when I've explain the inhibition mechanism that I thought about you said and realize that the 3.0.23 one is not that fast if you want to inhib one or some channels that are not already registered in submasters...

Where can I check the inhibition that is present?

you can't...
especially because inhibition < FF is a scale and scale levels depends on channel's level.
if you set the inhibition to 50% for a channel, channel's level will be half of his registered levels (but i guess you've understood that). So even if you can see how much it's inhibed, it won't tell you the real output's level.

How does :Light handle the inhibition in this case?

if ch 1 is inhibed in sub 1 and sub 2 for ex:
sub 1/50%, sub 2 70%, ch 1 will be inhibed at 70%%
sub 1/50%, sub 2/30%, ch 1 will be inhibed at 50%
it's a kind of HTP merging

inhibitionned (with two n) are viewable from the main screen, I think there's no need for an extra window to see them...

I cannot use ENTER in the @mode on the main screen.

people have ask the ENTER function to be present in the shortcut listing in order to access this function from an external keypad.
Thus you have to register it in the shortcut window.
In order to register it you have to hold the Ctrl button before hitting ENTER (same as arrow's keys and backspace key)
please tell me if it works.

thanx for your feedback,
++

sl1200mk2 écrit: you can't...
especially because inhibition < FF is a scale and scale levels depends on channel's level.
if you set the inhibition to 50% for a channel, channel's level will be half of his registered levels (but i guess you've understood that). So even if you can see how much it's inhibed, it won't tell you the real output's level.

I understand the principle of inhibition, it's a submaster for the selected channels. It could be helpful though to see what the value is of the submaster, for instance when someone made a show that you are taking over and he made a few INHIB's and you don't know which one is inhibitioning the channel.

This sound like something of a long stretch but actually I do share a few shows with a few technicians and sometimes people make unexplicable choices or mistakes working under pressure.
It's not a deal breaker though. Especially since there is a visible cue of inhibitioning in the main screen (white circle).

if ch 1 is inhibed in sub 1 and sub 2 for ex:
sub 1/50%, sub 2 70%, ch 1 will be inhibed at 70%%
sub 1/50%, sub 2/30%, ch 1 will be inhibed at 50%
it's a kind of HTP merging

Thanks, thus higher takes precedence.

people have ask the ENTER function to be present in the shortcut listing in order to access this function from an external keypad.
Thus you have to register it in the shortcut window.
In order to register it you have to hold the Ctrl button before hitting ENTER (same as arrow's keys and backspace key)
please tell me if it works.

Forgot about the Ctrl :blush:

for instance when someone made a show that you are taking over and he made a few INHIB's and you don't know which one is inhibitioning the channel.

with the new inhibition mechanism, 'VOID' are not recorded with the sho.
the sub remains in inhib state, but it's empty after a re-open...

otherwise, does everything seems fine?

++

@Wilf,
I've forgot to ask you:
does the window size/position tweaks works fine?

++

hello

I tried this version yesterday with an external display (vp). I got the same bug as usual with the main window:

1. start dlight in the main screen, clic on run,
2. x11 open in the main screen
3. the dlight logo and the loader is running on the second screen
4. the software open on the main screen, but half way on the top. it's not possible to reach the dlight menus. the only trick, is to zoom with the x11 >window>zoom. Then you got the main soft window and you can resize it.

the same issue happen with the Patch menu window. You need to zoom and resize it with x11. Before this version, this menu was opening in the second screen all the time. Hardcore with the iphone remote...

mostly all the submenus open in the main window now, cool. except : MLink, Midi Timecode Editor, Chrono

hope that this helps somehow...

bye

dlight 3.0.24_b2 xquartz 2.7.5 osx 10.9.3

merci aroom, ça m'aide en tout cas à fabriquer un soft fonctionnel!

donc il y aura une autre beta où je vais corriger tout ça... l'algorithme de positionnement des fenêtres doit pas être tout à fait bon....

merci en tout cas d'avoir lister les fenêtres qui posent problème.

++

Sorry for my late reply, I've been busy (mostly with sound design) last days.

There is one more thing that changed a lot of releases ago (before 3.0.18) and I forgot to mention every time:

When patching, I usually type something like [CH]34[@][DIMMER]67
Sometimes I use the number boxes with the up and down arrow. But… when one accidentally clicks on the number box one cannot type anymore. I found out one can undo this by clicking on the test button, but I forget this a lot and then I'm just frustratingly typing in the air

When one selects one of those number boxes one can see a thin black border around the selected box. It used to be possible to type in those boxes too if I remember correct, but that's not possible anymore, but when it's selected one cannot type at all.

Hello,
Petit bug detecté aujourd'hui :
Je pilotes des players (sous Isadora) en OSC avec :Light. J'assigne un circuit de :Light au play on/off de mon player, et le circuit suivant au volume du même player.
Ca marche super en pilotage de circuits pur (à la main, dans le séquentiel...), mais lorsque je colle ces circuits dans un sub, les valeurs sortantes en OSC ne retournent pas complètement à 0 :

Je monte le sub à FF : les circuits contenus dans le sub montent à FF (255 en réception OSC dans Isadora)

Je baisse le sub à 0 : les circuits contenus dans le sub baissent à 0 sur l'écran de :Light (mais tombent aléatoirement à 01, 02, 03, 07 en OSC)

Si je flashe le sub, les circuits montent à FF dans :Light, mais le niveau du circuit n'est pas reporté en OSC, rien ne bouge... Les niveaux des subs semblent, par contre, être bien traduit en OSC.

Bug ? Problème d'OSC qui m'échappe ?

@Wilf,
thanx for reporting that, I'll check it for the upcoming release.

@fifou
oulala, ça fait mal....
je vais regarder ça.
thanx

++

Bonjour,

Désolé j'ai un petit problème d'installation de la 3.0.24b

Ma config
MacBookPro 15" early 2011
Mac OS X 10.6.8 v11

J'avais installé XQuartz 2.7.5 et DLight 3.0.23.

J'ai mis à la corbeille XQuartz et DLight,
redémarré
réparé mes autorisations
installé XQuartz 2.7.4
installé DLight 3.0.24b2_X6_X7

Ensuite j'ai lancé DLight.
dans le pop-up j'ai cliqué sur Run
ensuite j'ai attendu (car j'ai bien lu que le premier lancement de X11 était long) mais aucune fenêtre ne s'est ouvert.
au bout d'une heure et demie, j'ai ouvert la fenêtre "Forcer à quitter"
DLight était noté "ne répond pas"
J'ai forcé à quitter DLight
Ensuite j'ai quitté X11 normalement.
Et j'ai éteint l'ordi.

Aujourd'hui je retente et au bout de 35 minutes, toujours pas de fenêtre.

1h30 c'est anormalement long, non?
Que dois-je faire? Des conseils?
Merci

David

hello,
peux-tu lancer DL depuis le terminal de xquartz pour voir:
/Applications/DLight.app/Contents/Resources/DLight

++

Merci encore Nico!

Voici ce que j'ai fait.
J'ai forcé DLight à Quitter
quitté X11

Lancé XQuartz
et là DLight s'est lancé directement (pas de 1er pop up Run)

Depuis tout marche normalement :
J'ai ouvert une session
ensuite j'ai tout éteint, allumé ordi, lancé DLight et tout s'est passé normalement (pop-up run, etc...)

Problème réglé! Merci encore


J'ai pas bien compris les post d'avant de ce forum.
Mais chez moi les fenetres s'ouvrent normalement, je peux les agrandir, réduire, déplacer.
J'ai pas compris ce qu'est le Inhibit (je suis pas éclairagiste à la base mais tech son), mais si tu veux que je test un truc, dis moi quoi faire

A+
David