RB-DMX1 - Fixture Frustrations

All Fixtures are Chauvet:

1. ColorSTRIP - https://www.chauvetdj.com/wp-content/uploads/2015/12/COLORstrip-COLORstrip_Mini_UM_Rev3_WO.pdf 

2. Scorpion FXRG

3. Scorpion RVM

4. Scorpion GVC

5. Scorpion RGY - https://www.chauvetdj.com/wp-content/uploads/2015/12/Scorpion_RVM-GVC-RGY_UM_Rev10_WO.pdf 

The fixtures already exist in the database.

@Steven > The ColorSTRIP is the only fixture of a compatible type; the lasers are not supported.

As for the fixture assignments, the placement in the grid is the starting address for your light, which you should match on the fixture itself. Here you can see I've placed my lights wherever I want - and as long as I have the same starting address and channel mode on the light as within the software, all functions will work. Clicking on it in the grid will make it illuminate so it can be identified.

@Pulse. Yea, I already seen this (generic) response and I have tried that (highlighting the fixture) and the colorstrip does nothing. I am an avid freestyler user so I know how to DMX address. I tried other ColorStrip modes from the database to see if it's receiving a signal and for some, it does, but it's doing random things as opposed to exact settings from the RGB values for the obvious reasons. Also, when I plug my other dmx interface into my freestyler computer, with all my fixtures addressed, to rule out any cabling issues they respond accordingly. The universe/dmx addressing in rekordbox is identical to my freestyler one. It was pretty easy to follow out the box in that regard if you are familiar with DMX. The colorstrip is set to channel 17 and patched into rekordbox with the starting address of 17. I will post a youtube video to show exactly what I am talking about. On a side note, is there any future support for lasers and if not, why do they exist in the database already?

So you can see... https://youtu.be/RG1rtO_27L8

For the Colorstrip to work in RGB Colormix mode (4 Channels) the channel values should be as follows (based on the manual linked above):

Channel 1 - RGB Color Mixing = 210-219

Channel 2 - Red = 0-255

Channel 3 - Green = 0-255

Channel 4 - Blue = 0-255

The lasers are in the database because they exist within the AltaBase database. You'll note that the only currently supported fixture types that have the ability to be controlled by rekordbox lighting are pars, bars, movers, strobes, and pin spots. Other fixture types (eg. FX, foggers, hazers, lasers, etc) will be added as updates are released, but we don't have any detail on when / how that will look.

As for the COLORstrip, I made a video of my findings here.

@Pulse Thanks for the video. It pretty much confirms that channel 1 was receiving a null value instead of a value between 210-219.

Yeah, just a quirk of their DMX implementation with those "modes," hopefully something that can be addressed with a quick fix.

Agreed. I'm sure it's an easy fix, but wanted to make sure I was not going insane with my universe. Great video btw

We have updated the RGB color mixing mode of the fixture. The default value of channel 1 for that mode is now 214. It will be reflected in the next rekordbox fixture library update. Please find the latest update of the fixture library here.

On behalf of Pioneer DJ,
AtlaBase Ltd

Just as a note from a consumers perspective... When accustomed to being unrestricted in terms of fixture(s) creation and mapping from other free products, like freestyler, it is very disconcerting when I have to sit around and wait for updates. I know I am a 48 year that is sounding like an "instant gratification millennial", but version 1.0009 did not addressed the issue with the light bar nor the ability to add the additional functions to the moving heads (Gobo, Zoom, Prism, Focus). I have since switched to serato soundswitch and have run into little or no issues. Now I am uncertain if I will even keep the RB-DMX1. So in the future, I suggest that you improve your turn around rate on your updates or allow the end-user a bit more flexibility to create fixtures. Maybe that will allow you to concentrate on the macros that create the scenes that map to the songs.

Regards

@Steven > As previously noted, there are many fixture types which are not yet supported (eg. lasers, FX lights, hazers), and many functions on supported features which are not yet available (zoom, gobo, prism). Database updates may correct fixture DMX issues, but those updates don't change overall application functionality.

Our team is working hard to update and improve the product (which has yet to receive an update), so rest assured, there are already updates in the pipeline and we hope to provide a superior product as it evolves.

@Pulse > To date, none of the recent updates to Rekordbox & the AltaBase fixture DB has resolved these issues.

Could anyone tell me if this issue is believed to be resolved after all the recent updates?!?!?! It is still an issue for me.

Regards,

Steve

Which specific issue were you referring to?

@Pulse Thanks for the response. My colorstrip still does nothing, but with my other interfaaces, works correctly. Am i missing something with Rekordbox? If channel 1 is set to 214, then it should be correct, but I get nothing..

See here for my issue. I am even running Rekordbox 5.3.0 and Fixture Database 1021

https://www.youtube.com/watch?v=WYkDbLqp7wQ&t=21s

In your video, did you happen to have Venue2 selected as the venue within the rekordbox preferences? Even though it's the tab you're working on, if you don't have that venue selected in the prefs, it won't send signal.

I am pretty sure that I do but will confirm. Also, the fixture is patched into both venues on the same channel. Thanks for the response.

Confirmed, Venue2 selected and still nothing.

I just did some signal sniffing and it seems it's the same as when I posted my video earlier; the channel 1 signal is not sending the signal in that 210-219 range as required. I've passed it along to the database team to see if it was modified or if perhaps it just wasn't included in v1021.

Thanks for confirming that I am not going insane or have some form of cabling/fixture malfunction. I will look out for DB Team's response. 

We have checked the fixture once again. The default values for the channel are unchanged. Our default value provided for the RGB Color Mix Mode is still 214.

@AltaBase... I suggest you look again. Both I and @Pulse see that is not the case. On ver. 1025 and still nothing. If Pulse is saying he did signal sniffing and it's not on 214, then you should check to see what else may be triggering the value back to null. Because both of us have the same results and have posted videos to prove it. Rest assured, these frustrations have been followed by 15 DJs that i am aware of that stopped them from purchasing the rbdmx-1 over little issues such as these, and they in turn have been spreading the word to those in their DJ inner circles.

@Steven > The Altabase team had verified the correct values are configured in their database, and we've been communicating internally on troubleshooting this issue further. Your patience is appreciated while this is addressed. Please understand that it's sometimes small non-standard configuration hiccups such as the requirement for this fixture's colormixing channel to have a value in a certain range for RGB values on other channels to become effective. Thanks!

@Pulse Understood, but I have been patient since April 20th... it is now August.

@Steven > We had discussed it Apr. 20th, I passed along my findings Apr. 25th, they had addressed it by May 3rd. That's pretty good turn-around. You posted back 26 days later that there was still an issue, and regrettably it was missed and took 2 months for us to re-visit. I tested it, found there was still a problem with the DMX output, took it back to the database team, within days they once again confirmed it was configured properly, and now we have our lighting engineers looking into it.

I agree it's frustrating, but these things take time, and it is being addressed - so yes, your patience is appreciated. Thank you.

Just in case this fell off supports radar or do I just still need to exercise patience?!?!?!

Sorry, I don't have any information for you at this time.

@Pulse Thanks, I applaud your responsiveness & interactions with the forum. May not be the solution, but it's an answer. That's the one positive I can take from this. I'm sure there are other issues being dealt with and at the very least, you did what you could to bring my issue to your team.