Jump to content
Light-O-Rama Forums

bmkalbf

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

3 Neutral

About bmkalbf

  • Rank
    New Forum User

Profile Information

  • Gender
    Male
  • Location
    St. Louis MO
  • Occupation
    Systems Engineer

More About Me

  • How I learned about Light-O-Rama -
    Online Videos
  • Favorite Decorating Holiday?
    Christmas

LOR Software

  • LOR Software Version
    5.1.4
  • License Level
    Pro

Recent Profile Visitors

182 profile views
  1. bmkalbf

    PE from SE timing grid out of sync

    Thank you for the reply. I did check the bitrate and all looks good. However, the only thing I could think of that was different is the version of Audacity that I used on each computer. I recently started creating my music files in Audacity on a new computer, exporting the file, and moving to my sequencing computer to sequence. I found that only the files I would create on the other computer would have this issue. So I created the files in Audacity on my sequencing computer again like I used to, and now it seems to be working fine. Same settings, and same bitrate but different versions of Audacity and moving between computers seemed to be the issue. Maybe a codec issue? still not sure.
  2. bmkalbf

    PE from SE timing grid out of sync

    I think I have narrowed down the issue a bit more. So playing the sequence from the beginning, the timings are flawless, it seems to only throw them off when using the "play from current location to end" play button. It seems like the red play line is making a hop ahead for some reason putting the timeline out of sync with the music. I guess I need to trust my initial timing marks and then play from beginning to verify everything looks as it should. Still a big pain, but better than nothing, any input would still be appreciated on how to fix that issue. Take care.
  3. Hello, Hopefully someone can help me out with this issue I am having. I have been using SE and PE for 3 years now, and this is the first time I am seeing this issue. If I create a sequence in SE, with a song (musical sequence) and add timings using the tapper wizard, all of the timings match up in SE perfectly as they should. When I bring that sequence (.lms) file into PE, it seems that the timings from the tapper wizard are off by a significant margin. Sometimes when I first bring in the sequence, they match up, but when I apply an effect or work along the timeline in the sequence, the timings become off. I have made new files thinking maybe it was corrupt, and have checked my computer resources, and nothing is strained like CPU or disk or memory. Any thoughts or ideas would be greatly appreciated, this makes LOR pretty much useless if I cannot trust the timings in the timing grid I have set up. Thank you. I am running PE version 4.3.14
  4. These are great! And answered so many questions. People like you are why these communities are so great! Thanks again!
  5. Absolutely! I would love to check them out if you don't mind. I appreciate it!
  6. Thanks SPaschall. Nice video. There is not a lot out there on PE for new users. This taught me a few other helpful things as well. Dennis I will give this a go too. Still trying to figure which way is up on this. But so far I think this is going to be helpful with my sequencing.
  7. I am just getting started with Pixel editor and I know I still have a lot to learn. But it does not seem that you are able to make a "dummy" sequence in PE with effects in it for your props, and then copy those effects into another sequence within SE. Is this possible? What I am wanting to do it do all of my normal sequencing in SE where I am familiar, but at certain parts of the song/sequence, I want to have an effect that was made in PE. But when I open up a sequence with an Intensity file, there is really no way to copy data from the intensity file to paste into my other sequence. I guess in the end, I could do all of my sequencing in PE, but I have some sequences that I have started in SE, that I would like to enhance with PE effects. I hope this makes sense. Thanks a lot.
  8. Hey Christmascrossing I did get an update on this. Sorry for not posting sooner. I worked with David from HolidayCoro on this, and we found a solution that seemed to work. I'm still not sure why these controllers are different than the older ones, but this is what we did. Before you do anything, just confirm that all outputs are working with the on board test feature, and maybe test in xLights as well, if all of that is working, then this is what we did next. On the Alphapix Web GUI page, on the SPI outputs, I made all of my output be exactly the number of pixels I have connected to that specific output. So for example, I think the default number in there is 340, (which is 2 universes) so we thought there might be some universe overlap happening. So I dropped them down to 170 pixels, ..still no luck. But when I set them to the exact number of pixels I had connected to that opt put, it started to work. I did not have to do this for my older controller last year, but David mentioned how putting the exact number of pixels in, creates less network overhead and will eliminate any possible lag issues. I hope this gets you up and running, I spent about a month and a half on it before we finally got it figured out. Let me know if you have any other questions.
  9. Thanks for all the help Grinch. I really do appreciate it. There really is nothing different between the 2 controllers so I contacted the manufacturer for some support. Hopefully they find a quick solution. I'll let you know what I find out. Thanks again for all the help.
  10. So changing the IP's on the controller did not fix it. The issue followed the controller when I gave it the IP of the working controller. I isolated it completely so it was not conflicting with the other controller. It seems like it could be hardware, but all outputs work fine with the controller is put into test mode.
  11. Agreed. This is a good idea. That might narrow it down to see if the problem follows the IP and then it could point to a config issue. I will try that tomorrow. I appreciate it. I will let you know what I find. Thanks.
  12. Yes, that is how I originally set it up, by itself, and when I started seeing the issues, I added to the switch thinking since it was using the higher universe numbers it needed to "fall in order" on the switch. I can ping both controllers when they are plugged into the switch and if they are connected independently. Thanks again.
  13. Yes,I have a Cat5 going from the computer to the switch, and both controllers are plugged into the switch. I have changed out the cables and even tried a different switch, but with no luck. Thanks for the reply.
  14. Thank you greenie and BMurray for the replies. I am assuming that within my controller GUI on controller 2, my first SPI output sohuld be 17? That is the way I have it configured. I wouldnt imagine that it would start back at 1, correct? Everything is set up exactly the same way on the 2nd controller as the one that works, with the exception of the universe output numbers. This is reflected in xlights and LOR as well. Is there any other place I can check or any other test I can run to confirm the setup and configuration? Thanks again for the help. It really is appreciated.
  15. Hello, This is my 2nd year using RGB lights, and I have been using the Holiday Coro Alphapix 16 controller. (V2.0) Last year, with the single controller, all of the channel mapping was fairly east and straight forward. All of the channels, lights, universes worked as they should. I used a single universe for each output to make it simple. This year, I am adding a second controller of the same type and I am seeing odd behavior. I am testing the outputs in x lights to find this. I am using UNICAST with different IP's on each controller, controller one controls Universes 1-16 and controller 2 is 17-32. When testing in xlights, (and in LOR) all channels perform as they should on the first controller, but on the 2nd controller, only the 1st output works as it should. The rest of the outputs on controller 2, do nothing. I have triple checked the network preferences, IP's, and channel mappings in LOR and xlights, with even starting from scratch on the channel mapping set up but getting the same results. All tests that run locally on the controller check out fine, so it has to be an issue with my set up somewhere either in LOR or the GUI interface of the controller in the SPI configuration. I have both controllers plugged into a 5 port switch, when last year I plugged directly into the onboard laptop nic. Any advice, tips, pointers would be appreciated. Thanks a lot.
×