Author Topic: VU Meter Issues  (Read 1788 times)

Offline jem5136

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
    • Lights of the Night
VU Meter Issues
« on: September 18, 2017, 09:56:31 PM »
I was sequencing a song a few months ago and I was able to make a really cool effect with the VU meter with my pixel tree and poles (pixel tree is 80 x 120 pixels, 12 poles with 24x20 pixels each). When I used the VU meter it looked great. Since then, I've made a few changes to the layout of my display (added more pixels) and I cannot get the VU meter to work. It seems to have just stopped working all together for the sequence.

I've played around with it, I can get the old rendering (before I changed the pixels) to play, but of course, it doesn't show the updated layout and looks terrible. I have messed with the different settings in the VU effect, but I get absolutely nothing. I've tried updating to the newest version (currently running 2017.27) but still no help.

I'm wondering if I've done something wrong or if there is a bug that needs fixing. I really want this effect because it was REALLY cool when it was working.

PS- all of my other sequences worked just fine after adding the extra pixels to the poles (went from 24x16 to 24x20) the pixel tree remained the same before and after the changes made to the layout.

Thanks-
Jesse

Offline Boof63

  • Full Member
  • ***
  • Posts: 215
    • View Profile
Re: VU Meter Issues
« Reply #1 on: September 19, 2017, 01:04:26 AM »
is the setup for each tree correct,
ie have you added the extra pixels or strings to the actual layout for each model.
try a simple effect like bands and see if that runs smoothly.
If not then check setup, layout and re render everything.
Cheers Boof63
(Not a complete answer but starter only sorry)

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: VU Meter Issues
« Reply #2 on: September 19, 2017, 09:19:59 AM »
If your total number of channels changed then close xlights and delete the old fseq and try again.

Offline jem5136

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
    • Lights of the Night
Re: VU Meter Issues
« Reply #3 on: September 19, 2017, 10:41:09 AM »
is the setup for each tree correct,
ie have you added the extra pixels or strings to the actual layout for each model.
try a simple effect like bands and see if that runs smoothly.
If not then check setup, layout and re render everything.
Cheers Boof63
(Not a complete answer but starter only sorry)

The setup for the tree didn't change and has been set up correctly; no changes in layout or channels whatsoever. The changes that were made were the 12 poles in the display, each originally had 27x12 pixels (324 pixels), but they were changed to 24x20 (480 pixels). As I said before, everything else looked great after re-rendering it.

If your total number of channels changed then close xlights and delete the old fseq and try again.

xLights has been closed and opened many times since I sequenced this song. This song is new this year and uses a completely different setup from last year (nothing was converted or used from last year). I've tried starting a new sequence and importing the effects from the song, but not much luck there, I get the same results. After importing the song and rendering (first time rendering in the "new" sequence), I get the same rendering I had in the old sequence. I might try removing the VU effect and add it in again, not sure it will help but worth a shot.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: VU Meter Issues
« Reply #4 on: September 19, 2017, 10:50:30 AM »
I guess you didn't get what I said because just closing xLights doesn't fix the problem I'm talking about.  If you save a sequence which creates an fseq file and then add any channels for a new model then when you open the sequence it will use the number of channels from the fseq file to define the channel count instead of the number of channels you have in setup.  I said close xLights and delete the fseq file and you just said I close xLights all the time and did not state that you deleted the fseq file.

Offline jem5136

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
    • Lights of the Night
Re: VU Meter Issues
« Reply #5 on: September 19, 2017, 10:54:10 AM »
I guess you didn't get what I said because just closing xLights doesn't fix the problem I'm talking about.  If you save a sequence which creates an fseq file and then add any channels for a new model then when you open the sequence it will use the number of channels from the fseq file to define the channel count instead of the number of channels you have in setup.  I said close xLights and delete the fseq file and you just said I close xLights all the time and did not state that you deleted the fseq file.

If I deleted the .fseq file will I still be able to open the sequence with the xml file? I don't want to lose the sequence I worked on.

Offline jem5136

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
    • Lights of the Night
Re: VU Meter Issues
« Reply #6 on: September 19, 2017, 11:21:02 AM »
I've tried deleting the fseq file, and re-rendering but nothing has changed, still get the old rendering when I re-render. And it's not just for the VU effect, it's for all effects throughout the entire sequence.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: VU Meter Issues
« Reply #7 on: September 19, 2017, 11:29:49 AM »
Well I think we are to you needing to use the Tools -> Package Sequence option and post the file for us to try.

Offline jem5136

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
    • Lights of the Night
Re: VU Meter Issues
« Reply #8 on: September 19, 2017, 03:27:49 PM »
I have the sequence attached.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: VU Meter Issues
« Reply #9 on: September 19, 2017, 09:06:53 PM »
Your sequence renders and previews fine for me.  Maybe download the lastest release from today that fixed some issues.