Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: JMHaro on August 04, 2016, 07:52:24 PM
-
I have 4 large driveway arches (150 pixels each) that I'm trying to setup. I have one song where I was originally doing them in a VU style when they were AC arches with on 8 channels each, where I was increasing the lighted height on both ends of the arches based on the segments of the music (here is a link to my previous show using AC lights https://vimeo.com/158548286 (https://vimeo.com/158548286), I'm referring to the green aches over the driveway in the video)
Is there an easier way to do this in xLights? I tried the VU effect but I just couldn't find any good settings that made it smooth and only work with the vocals like what I previously had). So I'm down to the pixel levels settings to make it work but this is killing me in the size of the xLights and I'm afraid I'm going to start having problems like I've seen before if the file starts getting too big. (I've only completed one arch so far and the xml file is already over 22Megs and I've tried setting the top level and not pixels when the entire arch is light up)
I'm outlining the house in pixels also so I'm going to be interested in knowing how I can do a similar effect across the house to make the lights move up the house in conjunction with the music vocals.
I appreciate any suggestions for this.
Thanks,
-
I'm not really an expert on the audio activated effects but I'm pretty sure it's going to be hard to it to only react to voice because that's buried in all the other frequencies from the instruments.
-
I think Keith has a way to have it trigger based on marks in a timing track so if you could figure that out then all you gotta do is place all the marks in a timing track and point it to the track.
-
It can trigger on timing marks but when it does it is a flash and fade. I could add a rise and fall if it would help. The question would become how fast to rise and fall and how high to rise.
-
Other option is to play with the note ranges and hope that you can find the range that only triggers on vocals. That is like pulling the yolk out of scrambled eggs.
-
It can trigger on timing marks but when it does it is a flash and fade. I could add a rise and fall if it would help. The question would become how fast to rise and fall and how high to rise.
Actually, I've been wishing that there was a Rise/Fall, in addition to the Flash/Fade option.
-
It can trigger on timing marks but when it does it is a flash and fade. I could add a rise and fall if it would help. The question would become how fast to rise and fall and how high to rise.
Actually, I've been wishing that there was a Rise/Fall, in addition to the Flash/Fade option.
How high should it rise? To the top? To the current frame audio intensity?
-
Hmm...that part I'm not sure. Rise in the current frame to match the intensity is probably how I would use it.
-
New mode will be in next release "Timing Event Jump" ... when a timing event occurs on the nominated timing track it will sample the audio intensity and fill the model to that level. using the selected colours. It then falls back to zero over a nominated number of frames. If another timing event is hit while it is falling it will jump back up again. Hopefully that is what you wanted.
-
New mode will be in next release "Timing Event Jump" ... when a timing event occurs on the nominated timing track it will sample the audio intensity and fill the model to that level. using the selected colours. It then falls back to zero over a nominated number of frames. If another timing event is hit while it is falling it will jump back up again. Hopefully that is what you wanted.
If you created a timing track with 200msec timing, and "nominated" it, then your effect would occur 5 times per second? (see an earlier thread about creating a 200msec timing track)
-
New mode will be in next release "Timing Event Jump" ... when a timing event occurs on the nominated timing track it will sample the audio intensity and fill the model to that level. using the selected colours. It then falls back to zero over a nominated number of frames. If another timing event is hit while it is falling it will jump back up again. Hopefully that is what you wanted.
I like that option, sounds like it would work. Thank you,
-
If you created a timing track with 200msec timing, and "nominated" it, then your effect would occur 5 times per second? (see an earlier thread about creating a 200msec timing track)
Thanks, I'll check that out also.
-
New mode will be in next release "Timing Event Jump" ... when a timing event occurs on the nominated timing track it will sample the audio intensity and fill the model to that level. using the selected colours. It then falls back to zero over a nominated number of frames. If another timing event is hit while it is falling it will jump back up again. Hopefully that is what you wanted.
If you created a timing track with 200msec timing, and "nominated" it, then your effect would occur 5 times per second? (see an earlier thread about creating a 200msec timing track)
I have added a new metronome timing track which then let's you specify an arbitrary time interval as long as it is a multiple of the base timing interval. No more editing xml files
-
Sweet. Thanks.
-
If you created a timing track with 200msec timing, and "nominated" it, then your effect would occur 5 times per second? (see an earlier thread about creating a 200msec timing track)
Jon, I've been trying to search for the other thread about the 200msec timing track but can't find it anywhere, maybe I'm not searching for the right words. Can you point me to it just so I can check that out while waiting for other changes to come out.
Thank
-
I am not finding either. It involved editing a sequence XML file in Notepad++ and was very recent (within a few days). I'll keep looking.
-
I was telling someone just search for the line with the word "fixed" but apparently that was too hard because they said they couldn't find it. The line will look like this. Just change the 50 to any number you like for the number of milliseconds.
<Element type="timing" name="50ms" fixed="50">
-
Now you have to have already created a fixed timing track to be able to alter it in the XML. That's what I bet they didn't realize. Now this isn't changing the minimum sequence duration. That's in a different spot.
-
Now you have to have already created a fixed timing track to be able to alter it in the XML. That's what I bet they didn't realize. Now this isn't changing the minimum sequence duration. That's in a different spot.
I added a timing track (right click, Add Timing), gave it a name but nothing else.
Saved the sequence. Closed the sequence.
Opened the XML in Notepad+++ and searched for Element Type. Clicked next until it found my new timing track
Added fixed="50" to the end of the line but before the >
Before:
<Element type="timing" name="fixed 50msec">
<EffectLayer/>
After:
<Element type="timing" name="fixed 50msec" fixed="50">
<EffectLayer/>
Saved the file. Reopened in xLights and it now has fixed timing of 50msec (20 ticks per sec)
I will say this - having a fixed grid that matches your sequence timing makes alignment of effect starts and stops easier to see, but you really have to zoom in.
-
Ok so that's the hard way. If you click on the button to bring up Sequence Settings you can click on the Timing tab and click the "New" button and create a "50ms" timing track. Its not available from the right-click menu on the row heading.
-
Keep forgetting about adding Timing that way. :-[ :-[