Recommandation for better organise Press/Visibility Digital join


 

Hi there,
 
How do you guys manange your Press/Visibility Digital Join ? Until now, I simply use the Automatic assigment but I find it can get quite messy. 
 
Thanks,
 
 


 

Definitely don't use automatic assignment.  Organize your joins in logical groups and start each group at a nice round number with some space for expansion.  Don't be afraid to leave stretches of unused joins.  You'll thank yourself later when you need to add one more source or one more transport control.


On Tue, Dec 10, 2024 at 11:02 AM anhtu.vu via groups.io <anhtu.vu=polymtl.ca@groups.io> wrote:
Hi there,
 
How do you guys manange your Press/Visibility Digital Join ? Until now, I simply use the Automatic assigment but I find it can get quite messy. 
 
Thanks,
 
 


 

When he says leave some space, think in tens or hundreds not thousands. I had a takeover that they had decided to use thousands for source control. It was something like, Satellite started on 6001, Blu-ray 7001, Apple TV 8001 and so on. This makes for a lot of time scrolling. Plus i think the last usable join it 14999. Something to keep in mind, every join number from 1 to the last used join gets assigned in the simpl program. So if you are only using join 10000 and opened that program in a text editor you see all 10000 joined defined. I’m not sure how this is interpreted during compile, but I would guess it gets compiled as well.


 

Definitely agree with Jeremy and Eric...
 
I also find it helpful to assign joins so that the last digit matches what I'm using it for. So, for my source and destination signals, src1 might be at join 401, and dst1 might be at 501. Their serial joins for button labels match those joins. If I need to also "enable" the buttons (maybe to show whether the source is available or not), I'll often use 451 and 551 as the starting joins for that (rather than using up 2 more blocks of 100 joins). This helps me be able to quickly confirm that things look right in my interface when I'm assigning joins there. A button that I'm using for src28 should have joins 428 digital, 428 serial, and maybe 478 for enable. Join 400 would be the src0 button (none/clear/off).
 
This also helps when you're running all those same signals through crosspoints, or an EISC, so it's easier to verify that things are where they should be. Using the same join numbers there isn't mandatory, but I find it helpful. For projects where it's possible, I try to keep the joins packed in under 1000, so they play nicely with the limitations of crosspoints. Or, at least the signals I plan to run through the crosspoints will be under join 1000. 
 
--
Josh Winn
The LiquidPixel Group