bypass slices
- rawdesigns
- Posts: 323
- Joined: Mon Mar 04, 2013 08:22
- Location: Henderson, NV
bypass slices
Not sure if this is a bug or not but I remember in res5 in the advanced output window, if you select multiple slices, your "Input Opacity" and "Input Bypass/Solo" check boxes are present. But in res6 it looks like you have to do that individually on each slice. Not a big deal but just curious
Re: bypass slices
This is actually a bug. And you'll be pleased to know it has ticket number 10666 

Re: bypass slices
Oops. This is not actually a bug. We removed this option from multiselect, because this caused problems when the selection contained both slices with composition and routed inputs.
Ticket 10666 is related, but not the same.
Ticket 10666 is related, but not the same.
-
- Posts: 388
- Joined: Sat Oct 29, 2011 22:24
- Location: Las Vegas, NV
Re: bypass slices
Is this fixed in 6.06? I have around 1500 slices i have to change the bypass option for 

Re: bypass slices
What on GOD'S GREEN EARTH are you doing with 1500 SLICES? More information required for proper diagnosis!
-
- Posts: 388
- Joined: Sat Oct 29, 2011 22:24
- Location: Las Vegas, NV
Re: bypass slices
Programming fun with chaser. It’s so hard to draw in every square to make things look random
3 virtual output to group my slices per screen, then 1 slice per screen in my main output to pull the virtual outputs.
If you add a group or layer , it resets the group in the input routing and end up have to uncheck every bypass again

3 virtual output to group my slices per screen, then 1 slice per screen in my main output to pull the virtual outputs.
If you add a group or layer , it resets the group in the input routing and end up have to uncheck every bypass again

Re: bypass slices
dirtyjohn_lv wrote:Programming fun with chaser. It’s so hard to draw in every square to make things look random![]()
3 virtual output to group my slices per screen, then 1 slice per screen in my main output to pull the virtual outputs.
If you add a group or layer , it resets the group in the input routing and end up have to uncheck every bypass again
I had a similar issue in December with 1700 slices. My
Solution was to copy and paste after creating the right bypass settings.
I felt like I reported this awhile ago surprised its kicking around d.
Re: bypass slices
#9848 is the one where we made a change for the multi select, so composition slices can't be set to ignore opacity and bypass via multi select.
If you add a layer below a routed layer then the routed layer above will have the layer index increased, so of course you'll have to set that layer as input again.
In such a case then When I multi select my slices which have different settings for ignore bypass and opacity, and set the same type (layer) as input for them with a different layer, then my settings are kept. for the individual slices.
Selecting a group instead of a layer resets the ignore settings.
Adding a layer or a group should not have any effect on the Advanced output slice routings.dirtyjohn_lv wrote:If you add a group or layer , it resets the group in the input routing and end up have to uncheck every bypass again
If you add a layer below a routed layer then the routed layer above will have the layer index increased, so of course you'll have to set that layer as input again.
In such a case then When I multi select my slices which have different settings for ignore bypass and opacity, and set the same type (layer) as input for them with a different layer, then my settings are kept. for the individual slices.
Selecting a group instead of a layer resets the ignore settings.
Software developer, Sound Engineer,
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
-
- Posts: 388
- Joined: Sat Oct 29, 2011 22:24
- Location: Las Vegas, NV
Re: bypass slices
I'm kind of stuck then.
My original chaser output is from a completely different advanced output/composition setup. It's easy enough to copy/paste XML from one composition to another, but still have to change bypass setting because compositions/outputs don't match.
I could use drazkers method, but I would essentially have to recreate the whole chaser again. Either way, lots of lost time
My original chaser output is from a completely different advanced output/composition setup. It's easy enough to copy/paste XML from one composition to another, but still have to change bypass setting because compositions/outputs don't match.
I could use drazkers method, but I would essentially have to recreate the whole chaser again. Either way, lots of lost time