Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: pjones on October 30, 2016, 04:56:30 PM
-
I have a sequence where i have recently added additional controllers and re-channeled the models associated with that sequence. I have one model that continues to show as activated (turned on) on preview when i play the sequence even though i don't have any events programmed for that portion of the song with that model. I have deleted the model and recreated it but it still appears, I have deleted every event in that section of song by clicking and drag but it still shows up with nothing sequenced in that slot.
Has anyone felt with this issue before? Render All does nothing to resolve this, neither does closing and reopening the app I'm using version 4.3.00
-
If I understand you correctly in your post you are using 2016.30? If thats the case you are about 20 updates off and that includes alot of bug fixes. I would suggest updating
-
He said 4.3.0, that is from December. He is more than 50 off. Time to update.
Sent from my Pixel using Tapatalk
-
Ok, I just downloaded the newest MAC version 2016.50.something
It's my first time updating the app, it always just worked for me so I had no reason to update before.
What files should I be replacing when I update? Do I just take the old X-Lights App and trash it then replace it with the new one? or are there hidden files that need to be removed also?
-
Unless you changed directory, it overwrote the old version. Just launch it.
Sent from my Nexus 6P using Tapatalk
-
ok, I've updated but the issue persists... I'm at a loss as to what is causing this. Does anyone have any further ideas?
On a side note though, I like the looks of the update! :)
-
Do you have a data layer?
-
Great success! I found a model group was not deleted that contained it. I don't know why it was showing even though nothing was programmed on the sequencer but deleting the group fixed it.
On a side note, I had to go back to the original version that I was using because the new one was running too glitchy... keyboard would not respond and mouse would not work in some windows. If I had more time i would try to resolve it but I have a lot to do before the end of november comes so I'll stick with this for right now and update later to a newer version.
-
So you're back to 4.3.0? Good luck....probably been 1000 other bugs fixed since then.