Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 7 of 16     «   Prev   4   5   6   7   8   9   10   Next   »
BillCat

Registered:
Posts: 7
Reply with quote  #91 
I've already ordered another controller (ENTTEC Open) because I blew the whole day trying to make it work without success, but I really appreciate your offer. I think this could be a good lower end entry level controller for a quarter the cost of the ENTTEC unit. Right now I'm only really out the $20 and a days worth of work trying to tinker with it. I've learned a boatload about DMX, but I think you are right, there may be a bug in there someplace.

Could I just send you the uDMX controller so you had one to test and make it right for someone in the future? I wouldn't mind paying it forward and if I'm not going to use it because i have the ENTTEC, someone may as well have it.

Thanks again for making ABT!

Dave Thaler

Registered:
Posts: 452
Reply with quote  #92 
Quote:
Originally Posted by BillCat
Could I just send you the uDMX controller so you had one to test and make it right for someone in the future?


Absolutely!
BillCat

Registered:
Posts: 7
Reply with quote  #93 
Cool. Pm me your shipping details and I'll get it into the mail. The drivers are available online so I'll just stuff the cable into a mailing envelope and toss the driver CD and box, if that works. 
Dave Thaler

Registered:
Posts: 452
Reply with quote  #94 
Artemis Bridge Tools v3.4 is now released.  Changelog:
  • Fixed crashing bug with Enttec Open controller by reverting fix from v3.2 for bug where additional mission script commands don't work unless a CUSTOM_* cue was also used.  As such, CUSTOM_* cues should not be used with Enttec Open controllers until a better fix comes along later.
  • Finished support for uDMX controllers, now confirmed to work (thanks to BillCat for donating a controller to the cause)
  • Added a File->Settings dialog to allow testing future versions of Artemis.  This replaces the temporary "alpha=" workaround mentioned earlier in this thread, that parameter is now ignored.
  • Added ability to bulk-add any device types (previously only some types were bulk addable)
  • The Validate button in Artemis DMX Editor will now complain about non-zero change values on video devices and WeMo switches
  • When adding new devices, default to the same type as the last device added
  • Support Artemis 2.5.1 by default
  • Fixed automatically generated comments in DMXcommands file for commands that play videos
BillCat

Registered:
Posts: 7
Reply with quote  #95 
Dave,
Thanks again for your help and coding this software. I'm sure I'd go slightly insane using notepad to do all of this, which is why...

If I might ask.. How do I handle DMX devices that have more than 4 channels? I have 6 par can lights that work great under the open ENTEC controller and I'm working to get events assigned to each station. I have a 1byone disco ball stage LED light that appears to have seven channels. https://www.amazon.com/gp/product/B00GN4VP6A/ There is another video guide on these forums using this gear and it seems to work for him, but the video guide uses notepad on the raw ABS config, instead of having the ease of using your great testing interface. 

Is it possible to use this with your software or do I have to append the 7 channel device config to the file after I've used ABT to do everything I want to do on the exiting 4 channel par cans?

Thanks,
BillCat
Dave Thaler

Registered:
Posts: 452
Reply with quote  #96 
Quote:
Originally Posted by BillCat
How do I handle DMX devices that have more than 4 channels? ... I have a 1byone disco ball stage LED light that appears to have seven channels. https://www.amazon.com/gp/product/B00GN4VP6A/

The Amazon link says the item model number is O00QS-0060, and I can find what claims to be a user manual for that model number here.  Does that match the manual for your device?  That manual only mentions six channels rather than seven, but if I answer for that and yours is different you can hopefully figure out how to adapt.  So looking at the manual at the link I found, channels 2-4 are the colors in the order GBR.  CH1 is used just to select which mode, CH5 is rotation speed, and CH6 is strobe speed.  The easiest way to use that using Artemis DMX Editor is to add it as 4 separate devices: a 1 channel device, a 3-channel device with color order GBR, and 2 more 1 channel devices.  In your command profile, you can then set constant values (say in ALWAYS_ON) on the 1-channel devices, and use the 3-channel device just like any other 3-channel light.  Does that make sense?
BillCat

Registered:
Posts: 7
Reply with quote  #97 
DMX hacking at it's finest! This is great and makes perfect sense. It doesn't have to be a "single light" as long as each channel is doing the right thing. I love it! I suppose if I really wanted to change the rotation i could just add both devices to the same event and then tinker with each channel as needed, using three "lights" to control a single real one.

I knew some of my VM training would be useful elsewhere in life! lol. Thx for the push in the right direction! (And yes, that's the exact manual I have with the unit, good finding!)
Kalid0r

Registered:
Posts: 24
Reply with quote  #98 
Hi everyone,

First, apologies if this is the wrong place to say this (first post so go easy on me).

I am using a vellerman dmx controller and I have found that the latest version of bridge tools crashes when the vellerman is selected. I have uninstalled and reinstalled an older version, 2.4 I think, to get around the issue.

Anyway. I love the program so thanks very much!

Jon
Tiwato

Registered:
Posts: 8
Reply with quote  #99 
I'm also seeing a crash with artnet-3ch.  The DMX Editor also crashes when I select "Test Active...", so I'm wondering if they are related.  I created a brand new profile, with only 1 artnet-3ch device added. 

I'm running Win7 Ultimate. I used the auto updater to go from Bridge Tools 3.3 to 3.4.   Uninstalling and reverting back to 3.3 fixes the crash.  Let me know if you need any other info to reproduce the crash.



Kalid0r

Registered:
Posts: 24
Reply with quote  #100 
I too used the auto updater but then I also tried a clean install of 3.4 and had the same issue so I don't think it is related to the auto updater.

I also found that it crashed when testing the active profile or running Artemis.
Dave Thaler

Registered:
Posts: 452
Reply with quote  #101 
Thanks for the reports.  I don't have a Velleman or Art-Net controller myself so it's harder to verify them compared to the others.  I just tested with an Art-net simulator and fixed an issue that I think will also fix the Velleman issue.  Stay tuned for 3.5 if you have Velleman or Art-Net controllers (stick with v3.3 in the meantime.)  It's about ready now but I want to run it through some more tests just to be safe.
Dave Thaler

Registered:
Posts: 452
Reply with quote  #102 
Quote:
Originally Posted by Kalid0r
I am using a vellerman dmx controller and I have found that the latest version of bridge tools crashes when the vellerman is selected. I have uninstalled and reinstalled an older version, 2.4 I think, to get around the issue. Anyway. I love the program so thanks very much!


Previously I had Velleman on the "unverified" list since I don't have a Velleman controller and hadn't gotten positive confirmation that someone had gotten it to work successfully with Artemis Bridge Tools.  Can I take your comment as confirmation that the previous version of Artemis Bridge Tools did work with your Velleman controller?  If so, I'll update Velleman to be listed as verified.
Kalid0r

Registered:
Posts: 24
Reply with quote  #103 
It is working for me. I am in the very early stages of with the whole thing but I have one 8 channel light  which I have configured as a combination of 3 and 1 channel devices in bridge tools and it is working consistently with my Velleman controller.

Dave Thaler

Registered:
Posts: 452
Reply with quote  #104 
Artemis Bridge Tools v3.5 is now released.  Changelog:
  • Fixed bug with Art-Net and Velleman controllers reported by folks in this thread
  • Added support for using 2 universes, allowing up to 1024 channels rather than just 512. This allows using multiple DMX controllers at the same time, whether or not the controllers are of the same type. Channels 513-1024 are DMX addresses 1-512 on a second controller.  Note that uDMX and Velleman controllers only support universe 0.  
  • Added built-in support for 4-channel RGBW lights, rather than requiring them to be manually added as separate RGB and 1-channel W devices.  That is, RGBW (and other orders) can be selected as the channel order of a 4-channel device.
  • Added ability to change the (only) device in all timeblocks of a command in Artemis DMX Editor, when the timeblocks are collapsed into a single row for the command
  • Display WeMo switch values as "on" or "off" rather than trying to display it as a color
  • Fixed channel order bug when an RGB-order device appeared after a device with a different channel order, where the RGB device would be incorrectly interpreted as having the other channel order
  • Allow CUSTOM_* cues to be used with Enttec controllers without causing problems
  • Fixed bug in Artemis DMX Editor when adding a 1-channel device to a timeblock with a 4-channel device
  • Fixed bug in Artemis DMX Editor when changing a DMX command's device from a light to a video player, where the dialog's controls weren't updated correctly
Tiwato

Registered:
Posts: 8
Reply with quote  #105 
Ok, finally got around to testing out 3.5. Art-Net seems to work a lot better (at least with my custom ardunio decoder), so a big thanks there!  
I was also testing out the second universe with an artnet debugger, and it changes normally on events, but it doesn't seem to send out the periodic (every 4-5 second) refresh that I'm seeing on universe 0.  I don't have enough lights yet to worry about it, but just something I noticed.

Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.