catching "get:no valid object set" errors

    Mar 28 2011 | 4:20 pm
    Is it bad to have a load of invalid paths when setting an object? Any performance overheads? Is there some way of checking if a path exists before setting the live.object up?
    I'm building something that auto maps to the 1st device in a given chain within an instrument rack. In some instances there maybe no device in the chain. So I obviously get an error in the max window. Should I be worried about so many errors firing?