Jump to content
Light-O-Rama Forums

MazdaFan

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

4 Neutral

About MazdaFan

  • Rank
    New Forum User
  • Birthday 11/03/1960

Profile Information

  • Gender
    Male
  • Location
    Sardinia, Indiana
  • Occupation
    Industrial Electrician/Machine Repair

More About Me

  • Interests
    Racing - F1, SCCA, Grand-Am, NASCAR
    Electronics - DIY Lighting and microcontrollers
    Programming - Delphi XE4
  • How I learned about Light-O-Rama -
    Web
  • Favorite Decorating Holiday?
    Christmas

LOR Software

  • LOR Software Version
    3.10.14
  • License Level
    Advanced

Recent Profile Visitors

159 profile views
  1. In that case, what are the maximum number of fixtures that can be contained in a prop now? I believe it used to be 64, is it now 170 to accommodate a full string of pixels?
  2. I didn't get any response to this in the Beta General Comments, so I'll give it a shot here... I have a few questions on crossing universe boundaries. I've used the visualizer to create 8 corners for my house. Each corner has 75 pixels. My first corner starts on u2,C1 (universe 2, Channel 1). Since those are created using the "master pixel" method, I would set the first corner as U2, Pixel 1, and the second corner as U2, Pixel 76, Third as U2, Pixel 151... Now comes the problem. My forth corner would start at U2, Pixel 226.. that is to say, U3, Pixel 56 (channel 168).. BUT.. there are two unused channels in there. The pixel actually starts on channel 166. Does this mean I have to change to a 510 channel universe? The other problem I have is the Arch wizard. I have 12 arches (yes, 12) of 40 pixels each. Using the wizard, I can create the first 4 arches, but it says that pixel XX in arch 4 doesn't have a channel assigned. Going to that pixel and changing it over to the next universe and setting it to pixel 1 runs into the same problem as above. Again, are we limited to 510 channel universes or is there another way around this? I'm using controllers that allow me to set consecutive channels, disregarding universe boundaries. I don't believe it allows me to set for 510 channel universes. If I have to use 510 channels per universe, there will be a significant amount of channels that can't be used because I can't get a string to "skip two channels in the middle" so that a pixel lines up on a universe boundary.
  3. I, too, have a few questions on crossing universe boundries. I've used the visualizer to create 8 corners for my house. Each corner has 75 pixels. My first corner starts on u2,C1 (universe 2, Channel 1). Since those are created using the "master pixel" method, I would set the first corner as U2, Pixel 1, and the second corner as U2, Pixel 76, Third as U2, Pixel 151... Now comes the problem. My forth corner would start at U2, Pixel 226.. that is to say, U3, Pixel 56 (channel 168).. BUT.. there are two unused channels in there. The pixel actually starts on channel 166. Does this mean I have to change to a 510 channel universe? The other problem I have is the Arch wizard. I have 12 arches (yes, 12) of 40 pixels each. Using the wizard, I can create the first 4 arches, but it says that pixel XXX in arch 4 doesn't have a channel assigned. Going to that pixel and changing it over to the next universe and setting it to pixel 1 runs into the same problem as above. Again, are we limited to 510 channel universes or is there another way around this? I'm using controllers that allow me to set consecutive channels, disregarding universe boundries. I don't believe it allows me to set for 510 channel universes. If I have to use 510 channels per universe, there will be a significant amount of channels that can't be used because I can't get a string to "skip two channels in the middle" so that a pixel lines up on a universe boundery.
  4. Report Number: JT01 Module: Pixel Editor Software Version: 4.0.2 OS Version: Win7 64bit Description: When creating a prop in the pixel editor/prop editor, under Channels. If a number is typed into "Unit" while LOR is selected, then if the selection is changed to DMX, the channel number will not exceed two digits (eg. you can not type channel # 312, only 32 is shown) Repeatability: Create a prop Under channels, with LOR selected, click in the Unit box and type any number (simulate someone putting in Universe 1 and not noticing LOR is selected above) Select DMX above Click in Start Channel below Attempt to type in any three digit number - Only first two digits are displayed This is more of a nusance item. It can be solved by saving the prop and reopening (I'm assuming that the LOR unit variable is staying populated until the editor is closed). Once reopened, a three digit number can be typed into the channel box. Possible solution? (psudo code) If DMX.selected then LOR.unit = null else if LOR.selected then LOR.unit = <default> or if event driven on LOR.selected( LOR.unit = <default>) on DMX.selected (LOR.unit = null)
  5. I would think a "Sticky" post here in the forum. I know SS has some comments that can be used in visualizer (superstar dmx=x,x), but just a locked post (only writeable by you) here in the forum would be a great place to post them.
  6. Hey Brian, Would it be possible to have an index of sorts on this forum for all the superstar comments in visualizer? Having a quick reference would sure be appreciated, and having a complete listing of all of them might clue some (me) into those that are lesser known. Thanks Jamie Tomlinson
  7. Shows you what you know... cows can't talk. It might have startled the racoons and deer a bit, but I don't value their opinion very much.
  8. These are the words I spoke to my wife this morning... but lets start at the beginning. As you may or may not know, a pretty good storm just passed through Indiana. It dumped some freezing rain, sleet, and about 6" of the white stuff on my area. Well, it just happened that I was starting my show the night the storm hit (Thursday night). Now I had set my show to run from 6pm to 10pm on week nights and 6pm to 11pm on Friday and Saturday. I was working a night shift this week, and I was frustrated that I wouldn't be able to see the show until the weekend, so I set it up so that it would be on when I got home from work at about 2AM. I figured I'd run it from 1:30am to 3am (with the sound turned down low on the outdoor speakers) so that I'd be able to see what it looked like at night (I go to work at 3pm). Well, wouldn't you know I had to work overtime that night, and didn't arrive home until 3:03am... drat.. Well, such is life, so I set it to do the same thing again last night. I come home to see the show running, but notice that one of the controllers (an LOR "build-it-yourself" CTB16PC controller) is not turning on the icecicle lights. *much grumbling here* I did notice that one string of lights were flickering erratically and that all the rest were completely out. Being 2:30am I just figured I'd check it out in the morning. Flash forward to this morning. I get up, fix my coffee, sit down at the computer to check DLA to see if anything neat and nifty got posted last night. At about 10am I decide its time to go out and check out the controller. Bundle up (its about 18* F), walk out side to the controller, where I find its laying on the ground... OPEN! There it sits, laying open like a book, filled with about 6 inches of fluffy white goodness. (did I mention it snowed? with freezing rain? and sleet?) There is a small area that isn't covered right around the transformer, but everything else is packed. Wednesday, I had been having a few problems with connections, so I had been visiting the different controllers (two active hubs, two Lynx Expresses, and two LOR 16PCs) trying to figure out where the issue was. Well, apparently, in my haste to troubleshoot the issue, I had left the LOR box open and never returned. I walked inside with the frozen controller and uttered those disturbing words you see in the title. (anyone in disagreement here?) I figured the controller was toast and would make a nice doorstop at this point, but being an adventureous individual, I decided to see if it could be saved. We use a wood burning furnace for heat, and if you've ever used one, you know that it really drys out the air in the house so I put the controller, standing on end so the water would run out, over one of our heating vents to see if it could be salvaged. Jump forward again, a couple of hours. The controller has dried out... no water anywhere, and just a very small amount of corrosion (that milky white dusty film) on the board. Saying a prayer to the lighting gods I plugged the controller in. Upon opening my eyes (I had closed them to protect them from the shower of sparks I was SURE were going to come streaming out controller), there, on the board, between the transformer and the PIC, sat the status LED blinking happily. "Surely not!" I exclaimed... "Yes, and don't call me Shirley" it muttered in reply. Wishing to push my luck a little further, I plugged in a CAT5 cable attached to the LOR 485B and powered up the LOR hardware utility. ***NO DEVICE FOUND*** ARRRGH! "I KNEW it was too good to be true" I cried... but as those pesky referees say in pro football... "upon further review"... I noticed that the utility was trying to connect to the wrong comm port. Timidly, I moved the mouse to select the proper comm port. I very very carefully reduced the network scan range to reduce the time it takes to scan for the controller... Then, after sacrificing several (non-working) candy canes to the lighting gods, I pressed the scan button.... **** LOR CTB16PC 02 FOUND ON COMM 13 **** The status LED went solid red (as it was supposed to do). "I CAN'T BELIEVE IT!!!" "Oh ye have little faith" it chirped in reply. I quickly attached several strings of incans and ran the controller through its paces.. The lights faded up and down in response to the commands... they twinkled merrily when I pressed the twinkle button... the shimmered shimmeringly when I pressed the shimmer button!!! The controller was SAVED! (sorry.. there's no emoticon for jumping and yelling and screaming in joy) So, now you understand the title of this little tale... and the value of SLOWING DOWN as you are setting up and trouble shooting your display.. and say what you will about LOR's controllers... too commercial... too high priced... whatever... but those things are ROCK SOLID. Jamie ** Note - I originally posted this on another site and figured I'd post here as well as a testament to LOR's equipment.
  9. Last year I bought all my stuff from Light-O-Rama, including the *cough*Whole Home*cough* FM Transmitter... (no researching first.. ya pay the price) This year I switched to the CZH05B and have been thrilled with it, and for the price ($86.00 shipped), you really can't beat it. Jamie
  10. Ok... what you need to do pixels. Your controller is a good start, but its only going to control 1 DMX universe (512 channels). To convert that to the number of pixels its going to control, divide that by three, so that controller will control 170 pixels. Any more, and you are going to need another controller. Next, you are going to need a power supply for your controller. Holidaycoro sells supplys, so you will probably end up buying it there. Be aware that the longer your string is, the more amperage it draws, so you may need an additional power supply to inject power somewhere down the string. This allows you to use the smaller gage wire that comes with the strings. You might also have to inject power if you notice that the pixels at the end of your string are dimmer than the ones at the beginning of the string... You may not need to, but its something to keep in mind. Next, you are going to need a DMX dongle to send your lights their commands. There are a lot of dongles out there, so its going to be up to you to do your homework and figure out what will work for you. Currently, LOR supports "Raw DMX", "Entec DMX Pro USB", "Lynx" and E1.31. I'm not too sure about the first two, but Lynx is a "do it yourself" dongle. Its not a hard build, but it does take some soldering skill. E1.31 is DMX over Ethernet and to do that, you have to have the advanced license. That, and a lot of patience learning how to sequence RGBs, is pretty much it. So, once you decide how many lights you want you can proceed to gather the rest of the equipment. I'd suggest getting samples of your lights to go with your chosen controller to see how they behave before you pull the trigger and make a big buy only to find out you don't have what you really want. Jamie
  11. Hi Brian. Well, I began playing with the "Superstar DMX=" keyword and created a visualization to be imported into SSEdit. I created 8 strings of 75 lights each, and 12 Arches (using the arch wizard and telling it that it was a CCR string) of 40 lights each. I don't know if that is supported or not, but I figured I'd give it a try. When I imported the visualization into Superstar, I got the following error messages: New Light Visualization.leeWarning: Found one or more fixtures with unassigned channels.Fixture [Arch 11 - CCR 09] has no channels assignedThis, and any other fixtures with no channels assigned will be darkgray and inactive. pressing OK results in the following: Warning: Visualizer CCR or CCB strings of size 124 exceeded,remaining CCR or CCB strings not loaded.It appears importing arches as CCRs does work, btw. I'm getting reactions on them from previous sequences I've done. Attached is the visualization file. I'm using 24 CCR v 3.10.14. Jamie New Light Visualization.lee
  12. Brian, If the bug is the fact that the props/strands end up "backwards" in the horizontal layout, the issue is not just with the DMX= keyword and the CCR props. It occurs in all props that I've created so far. I created a series of individual pixels (fixtures) and then grouped them into two props. The second prop ends up on the horizontal line before the first thereby putting the middle of the props (where the two props meet) at the ends of the horizontal display, and the beginnings of the props in the middle of the display. eg: Lights 1 2 3 4 5 6 7 8 9 10 11 12 turn it into props (1 2 3 4 5 6) (7 8 9 10 11 12) It ends up displaying in SSEdit as (7 8 9 10 11 12) (1 2 3 4 5 6) Is this what the fix addresses? Jamie
  13. Copy / Paste has no issues. It appears that SS is not exporting the final smooth effect. Its not in the file that I import into SE.
  14. Brian, You mentioned being able to get a new copy of SS that did not have the horizontal bug. It occured to me that I needed the horizontal feature so that I see if the visualization pairing works properly. Would you mind passing along the instructions to get the new SSEdit.exe? Jamie
×
×
  • Create New...