Sorry ... Vista64 ...

Download and install the latest MyDMX from the AmericanDJ web site. Then install the DLL by running the executable after decompressing the files from the ZIP archive.

You're describing otherwise mostly older issues that have been addressed by the latest version of MyDMX.

Validation? Note the lights blinking. Works MOST of the time. Boot computer with dongle disconnected. Then, before running MyDMX, plug in the dongle, wait for it to be recognized, then go have fun by launching MyDMX.

Regarding your last question: No. The MyDMX software only works with the MyDMX dongle, and vice versa.

Thanks for your response, Chris.

I followed the recomendations for installation and updating myDMX for V64 and hit the same wall as described in the initial post.



Any ideas?

Drop Vista 64 like the garbage that it is?

Sorry, my clients don't use Vista and nor do I due to reliability and compatibility issues. So, I unfortunately do not support Vista. I don't have it on any machine in house, and I think I have 2 machines that COULD handle the 64-bit version.

Jingls may have some additional advice on the topic. I'm merely hosting the file for the convenience of whoever needs or wants it.

Thanks again, Chris.

I have too many applications (and not enough $$ if you know what I mean ;-) ) that run as intended on my Toshiba V64 laptop to consider scrapping Vista.

Anyway, (Mr. Jingles are you here?) here's where I stand:

- myDMX installed.
- 64 bit drivers installed
- myDMX opens in both DEMO & USB mode as expected
- In USB mode the dongle's power LED is lit continuously and both the USB and DMX LEDs strobe
- Programming seems MUCH faster and reliable in DEMO mode
- At present neither DMX device tried responds correctly to myDMX in USB mode: The ADJ P64 LED does respond however any/all color value elicits a disturbing strobe effect. Color mixing and other effects seem to work (hard to tell with the fixture strobing). The can works connected to a hardware controller. The HX 700 Intellabeam (reasonably sure the fixture is 100% functional) did not respond at all.

I knew I was risking $$ going for a product not initially built for V64 but received confirmation from the seller and the eye-candy at the ADJ site that the app. was V64 compatible. Caveat emptor AND c'est la vie it seems. PERHAPS I'll have to suck it up, dump the myDMX on ebay, and go for a Sunlite product (SL2014EC) which is V64 friendly.

Any guidance would be graciously accepted.

Hi, I'm Jingles Assistant (if you will) He's out of the office today, and he told me to make sure to let ya'll know, he'll be back and reply ASAP! He passes on his Thanks for understanding.

MyDMX even says on the web site that it is NOT 64-bit Vista compatible.
While things have changed somewhat, that may still not entirely ring true.

My suggestions:
OF course, the typical "make sure you're using a DMX cable and a terminator" thing.

Turn on computer with dongle disconnected. After boot-up, plug in dongle, wait for happy tones, then start MyDMX. It should be fine now. At least this works for me in XP Home.

Check your addressing of the fixture. Trivial, but essential. I've seen this error before.

Check to make sure you're using the right channels in MyDMX, regardless if you have a profile assigned or not. Profiles just make the fixture and MyDMX more human-friendly. I've been guilty of grabbing the wrong channel fader in MyDMX, so double check.

The dongle otherwise appears to be working properly. Just check your start-up sequence.

Subtekkx,
I am having the same problem on my 64bit vista. I bought new cables and and the termination thing. Still nothing seemed to work. I took a computer home from work that uses xp and it worked. I would say if all the lights are working on the dongle it is probably functioning properly. Not sure what we need to do to get it working in v64. But now that I know it is a 64bit issue I will keep working and let you now if I find the answer.

Hi Brent;

Thank you very much.

I believe there is one step I MAY have not tried and will be doing so later this week when I'll have time to fiddle with the issue, place the files Mr. Pickett is hosting directly in the (myDMX) folder. I am fairly sure, but not absolutely certain, I tried that work-around among the dozens of iterative attempts at getting the product to function.

Hello Jingles -

In Kitty's post below it was mentioned you intended to have a go-round with the issue in this thread upon returning from your time away. Have you been able to make anything of the issues that were encountered?

Kitty54401
Posted 30 July 2009 11:02 AM Hide Post
Hi, I'm Jingles Assistant (if you will) He's out of the office today, and he told me to make sure to let ya'll know, he'll be back and reply ASAP! He passes on his Thanks for understanding

Oh i apologize. nobody ever posted an acknowledgment or anything. Subtek I need to know are you running the latest version of my dmx? Has to be the latest from our website. The link to the product page is in my signature below.
Sincerely,

I'm wondering if the right profiles are being used as well as proper addressing.

ADJ makes a 64 LED and an 64 LED PRO, which require different sets of profiles.

I think we gotta get down and dirty.

As is known(or should be), PROFILES are NOT NECESSARY to operate MyDMX. There, said it. Profiles are required for working with the FX Generator and to make fixtures more human friendly.

What channels are you assigning to what fixtures?
Do they match in MyDMX? It's important. Some people didn't realize they have to also set the channels on the fixture as well. Channels have to match.
Are you using the right profiles? Using the wrong profile could result in considerably less than expected performance. Mainly because "well, the profile tells me this, but I see something else" is often a symptom of the wrong profile, or the wrong mode profile. As some lights have multiple profile modes, it's critical to ensure you have the right profile selected for your proper relation to the fixture. Match those channels up.

It's entirely possible that your jumping ship won't address the issue. Gotta make sure the troubleshooting is done.

The description is that the dongle is behaving as it should.

Hello,

Yes the myDMX installed is from the website.

The channel mapping is correct on both the application and fixture(s).

Finally, I was wondering if there was any explanation handy for the DLL error shown as an image earlier in the thread.

the DLL error seems like it is missing the DLL file. In the files that you should have downloaded from the chris's website is a .EXe file and a .DLL file. you need to uncompress the .zip folder and drag and drop the .exe and the .DLL file into the my dmx folder, let it copy over the existing ones and you should be good to go. Let me know.
Sincerely,

Hello;

I'll try to be concise, but likely not succeed.

• The DLL error pic above indicates a problem with "DllOem.dll", the DLL file that Chris (Thanks Chris!) is hosting is "winusb.dll"
  
• I finally had the opportunity to move the files (myDMX.exe & winusb.dll into the myDMX(myDMX) folder.
  
• It was observed that the target of the desktop shortcut and the Start Menu shortcut is an executable file entitled "esa.exe"
  
• I made changes to to the shortcuts and the application myDMX (myDMX.exe) now launches instead of esa.exe.
  
• After re-booting the PC with the dongle attached only to the PC I then connected the dongle to an NSI DM 5000 dimmer pack, dmx dipswitches set for addresses 1-4 (all at zero). Then invoked the myDMX application. LED status: Power, ON; USB, strobing; DMX strobing.
  
• Without any profile I tried moving the faders for all 4 channels, no predictable activity was observed. Every PAR 64 incandescent can attached to the dimmer went full on without any dimming occurring. At least it wasn't strobing!

Guidance will be appreciated.

quote:

I made changes to to the shortcuts and the application myDMX (myDMX.exe) now launches instead of esa.exe.

Explain what changes you made please.

Previously when myDMX was launched it was via an application called esa.exe.


Now I the targer is myDMX.

I think you have messed it up quite a bit and should start over. do a uninstall. Then a new install from website then DRAG and DROO the files you download from chris's website AFTER you extract to the desk top the individual files (should only be two of them), then move them into the my DMX folder. If it asks to save over click ok to confirm. If you still need help go to www.crossloop.com and download there and join up then send me an email with a time in central time and i will do it for you on your computer through crossloop.
Sincerely,

Jingles, Chris and anyone else lurking;

Thank you very much!! Your time and efforts were very much appreciated.

I still don't have a functional myDMX as I have moved on to a package that took me 40 minutes from unboxing to making a moving head move under Vista 64, including AC & DMX cable connecting. I may continue to toy with myDMX when time permits.

Thanks again for your time and valiant efforts!

SubTekkX

I still think we should do cross loop sometime. i think i can get it working for you.
Sincerely,

I think the MyDMX developers need to make 64-bit a more reliable reality as one of their first priorities.

Microsoft has decided to kill off XP, but is allowing us XP user extra time since we hate Vista so much(Intel giveth speed, Microsoft taketh away....), and with Windows 7 right around the corner, that means at least a mininum of a year before I migrate off the XP platform onto Windows 7. I still may buy a Vista license in both 32 and 64 bit version for support purposes.

Hi Jingles.

That sounds fine to me, however I am on a tight time schedule for a while. When I get back from Korea/Japan in the middle of September I'll knock on your door.

Going to do a tour of US Armed Forces bases in the Orient running Front of House for Rusty Wright Blue starting 9/1 and returning 9/15.


Cheers!
SubTekkX

Hey, I'm pretty much completely new to mydmx, but I'm encountering pretty much the same problem that subtekk has been working on.

I'm running the latest version of mydmx, have downloaded and installed the 64-bit drivers from the website, and have downloaded the files that chris pickett has been hosting, dropping them into the mydmx folder.

When I attach only 2 38B LED Pro Lights to my dongle, they both just strobe and don't respond to anything from mydmx other than color changes. i've checked the led display for the dmx address, and i believe i've got them correct on the fixtures.

When I have tried attaching my chauvet intimidator 2.0's, they don't respond to mydmx at all.

Any help is much appreciated. Thanks.

Well, first, start with the typical advise:

Check your channel assignments and double check that you're using the right fader. You should be aware you do not need profiles to use MyDMX, profiles just make things easier for us to relate to.

Make sure you're in DMX mode on your fixtures.

Use DMX cabling and use a terminator. It helps more than you'd like to think. Shorten your cable lenght up for testing.

There have been reports of certain brands not properl using the channels, or even wrong channesl(one starts with an unused and undocumented channel). Likewise, some fixtures don't work so well.

Also, Jingles has better install instructions for the files.

omni is having the same issues that others are having. I do not have a fix for it yet. I am still working on it. But ya any led fixture will just strobe and either a scanner or a moving head just won;t respond. It's something with the 64 bit system. I am looking into this.
Sincerely,

thanks to you both.

the only thing i haven't tried that chris has listed is using a terminator, which actually just hasn't arrived yet.

Greetings from South Korea.

I wish to repeat that the terminating resistor had zero effect on the myDMX problem I encountered.

In fact I ran a single can UN-terminated both with myDMX and a known working DMX controller, myDMX had the unexpected, uncontrollable strobing problem and the dedicated controller did not.

Yes this seems to be some adverse effect from the 64 bit drivers. I am looking into this issue. I hope to have an answer for you all soon. I apologize for the inconvenience guys.
Sincerely,

Hi Jingles,

You are to be commended for your perseverance on this maddening issue!


Cheers,
SubtekkX

Thanks. By the end of this week i will have my own 64 bit vista desktop to test this on.
Sincerely,

As much as I'd like a 64-bit OS, I am sticking with 32-bit XP for reliability and stability until mayb a year or so after Windows 7 comes out.

On the plus side, developers appear to be trying to address the 64-bit Vista issue.

Hey Guys i got my dmx working on my 64 bit desktop. It's a bit tricky. I will be posting the details in a new thread a little bit later on. hopefully with some screen shots.

Sincerely,

It's always best when you have the right tools to replicate the issues with.

Way to go! What took ya so long?

Had to reinstall my Os last night took forever. Dell tried to help but in the end wasted my time. i took matters into my own hands and it worked. Link to instructions
http://forums.americandj.com/e...21078525/m/565108713

Sincerely,

Thanks Jingles -

Did you encounter any of the bizarre behaviors, hopefully similar to problems mentioned here & elsewhere, with any interfaced products?

IT's all explained in the post i linked above. But what weird behavior are you talking about?
Sincerely,

Hi Jingles

>IT's all explained in the post i linked above. But what weird behavior are you talking about?

Below is what is meant:

- The ADJ P64 LED does respond however any/all color value elicits a disturbing strobe effect. Color mixing and other effects seem to work (hard to tell with the fixture strobing)
- ... NSI DM 5000 dimmer pack, dmx dipswitches set for addresses 1-4 (all at zero). Then invoked the myDMX application. LED status: Power, ON; USB, strobing; DMX strobing.
Without any profile I tried moving the faders for all 4 channels, no predictable activity was observed. Every PAR 64 incandescent can attached to the dimmer went full on without any dimming occurring. At least it wasn't strobing!

Ultimately my question SHOULD have been 'have you attached the dongle to a fixture and verified it a functional install?'.

I ask that for 2 reasons; 1) I loathe trusting implicit statements. 2) With a few stylistic differences (by stylistic I mean there is more than one way to get EXACTLY the same end result with Windows ie, file moving [Ctrl+C, Ctrl+V vs. dragging and dropping with the starboard mouse button])I do not see anything that was not done during my iterations of installs, especially my final attempt that would qualify as a different install result from your description.


Thanks!

PS(1) The reason your one graphic is darkish is that the window captured was NOT active at the time of the screen cap.

PS (2)Anyone thought of creating a piggyback application that would provide a GUI of a generic DMX box/controller? So that fader 1 is DMX channel (x), fader 2 is DMX channel (x+1) etc.?

subtekk no worries yes i have tried this with dmx lights hooked up via a dmx line cable and it did work. The lights i used were two design spot 300e's from elation and 2X mega bar pro's from ADJ as well as a Tri spot LED also from ADJ.

thanks for the tip on the yellowish screen shot

Explain to me your PS(2) questions.
Sincerely,

Might be some repeat:

The 64 LED isn't getting power from the dimmer, right?
Are you using the right profile? Have you skipped the profile and just gone direct to the channel? Profiles are just for us humans to relate easier to the stuff anyways.

The dimmer pack, is it set to dimming or switching per channel? A switching pack would be full on/off, which is what you describe.

PS2(2): There are free DMX packages and DIY dongles. You do get what you pay for.

Hi Jingles & Chris -

Mr. Jingles; My PS(2) suggestion would be similar to the 3D Visualizer. An application that could be invoked that would 'hook in', via APIs (code writers know that stuff) to MyDMX and extract the info needed to show a simulacrum of a DMX control box. In this instance a 2D or 3D box with clickable/selectable faders that display the current DMX value of the 'hot' fader.



I am pretty certain there is already a function that does this, however as I recall it is mode-dependent. Perhaps this application could be mode independent.

Mr. Pickett; Thanks greatly!