Sign In:     

Forum: General Discussion

Topic: Help please....at gig and have issue with VCI-100 Mapper - Page: 1

This part of topic is old and might contain outdated or incorrect information

I'm ready to get started here at the gig and I can't figure out how to get my VCI-100 to come up on my custom mapping

I get the keyboard and a mapper titled Vestax VCM 100.

How to I import my custom map???

Please help. I had to load VISTA and forgot to test the controller. Now it is screwed up and I can't figure out how to load my file.


Thanks,

Jim
 
Posted Fri 07 May 10 @ 6:22 pm
Something is suspicious. The default map named VCM-100 (incorrect) is not picking up the jog wheels. Auto search fails to pick up anything. Maybe my VCI-100 is screwed up. I have volume controls, crossfader, tone controls, and a few more. No wheels.

Am I screwed. I've put my XML file in every Controller folder but it's not getting picked up by the software.

How do I load my XML config ? Please !
 
Crappy night with VDJ. Headphone goes in and out of crackles. Now the app is locked up. I'll be going to CD in a minute. Controller with minimal function. Sucks.
 
 
Ok thanks... I have to get this fixed for the gig tonight.

The controller is ok. It's working fine on my XP Desktop.

On to the patch.
 
Teamer,

Thanks for the suggestion. It did NOT work.

I'm on a VISTA HP DV-9500

I installed the patch and restarted VDJ. No fix. Mapper still shows VCM-100

I re-installed the patch and restarted the computer. Started VDJ. No fix.

I went to backup. Version 6.0.5 and now I am good. Ahhhhhhhhhhhh............. total stress reduction right now.

I wish I would have thought to go to backup at the gig. Would have taken me 1 minute to rename the folders. I was under a lot of pressure from a mutitude of other problems, and just didn't think 6.0.8 would have messed me up like this. I thought the controller went bad.

Yes it was my fault to assume all would work ok. I was concentrating on re-building everything after going back to VISTA to clear the video freeze problem with XP.

If you feel a little bit sorry for me would you please put me on the Full Expo Pass list for Atlantic City in August? Cyder has my address from last year. That and a nice hot shower will be a good way to take the sting out of this horrible night.


regards,

Jim Lawrence

If you want me to debug anything to get your patch to work let me know.


Jim Lawrence
 
What definition files are in your Documents\VirtualDJ\Devices folder?
 
Cstoll,

There are no files in this folder.

Jim
 
That is why the fix did not work ... what did you do after you downloaded the fix ? Did you run the install ?
 
cstoll wrote :
That is why the fix did not work ... what did you do after you downloaded the fix ? Did you run the install ?



Cstoll,

No I only ran the executable and then started VDJ. Then I ran it again and rebooted and then started VDJ.

Sorry I see nothing mentioned to re-install the application in the patch notes. Perhaps put instructions in the description field that a re-install is needed. I'm a num num for not figuring the third option. I was tired from a truely horrible VJ night. This problem was just one of a number of issues I had. VISTA is the biggest one with VGA port stupidness, and express card recognition idiocy.

I'll report in later. I'm gigging tonight so I'll re-install when I get back.

Thanks for your help. I"m optiomistic that I'll be able to upgrade to 8


Jim
 
No you misunderstood my statement ... about running the install. I meant the install (executable) you downloaded. NOT re-installing VirtualDJ. There is no need for that ...

But, after you run the executable for the fix - you should have 2 files in the My Documents\VirtualDJ\Devices folder - 1 for the VCI-100 and 1 for the VCM-100 .... if you do not then something is not right on your machine.
 

Cstoll,

I ran the patch again under 6.0.5 and then renamed my backup folders to make active 6.0.8. Now I look in the My Documents\VirtualDJ\Devices folder and I have 3 files. One is my custom VCI-100 XML, the other is a default VCI-100 file and the 3rd is the VCM-100.

When I launch VDJ the only mappers I have are the keyboard and the VCM-100. Neither VCI-100 ifile s displayed.

I just rebooted and launched VDJ with the VCI-100 attached. No fix. The 3 files are in the Devices folder, yet VCM-100 and keyboard are the only mappers.

It would be great if you could add a "open mapper file" to your drop down listbox. That way we can build mutiple mapper files and choose which one to run for the night. Right now I have no choices. And I don't see a way to make a choice of any mapper file.

Any thing else I can try? I appreciate you helping me (us) out. I really like my VCI-100 and would love to be able to continue using your new releases.

The VCI-100 ran flawless tonight with version 6.0.5 using my custom mapper.

Regards,

Jim

P.S. I thought I'd try it. I have the VCI-100 hooked up. I re-installed 6.0.8. The 3 files are still in the Devices folder. Mapper still shows the keyboard and VCM-100. No fix.
 
Please do not quote the post right before your reply ...


As for your issue ... remove the Custom VCI-100 definition ... this is what is causing the problem. You should only have 2 files in your Devices folder. The 2 from the fix.
 
Cstoll,

I removed my custom XML file. I rebooted. I see 2 files now. VCM & VCI definition files.

Launch VDJ and Mapper tab still only lists keyboard and VCM-100. No fix


Jim
 
Ok, then download this tool - http://www.virtualdj.com/download/miditrace.exe

Run the tool with the VCI connected ... from the right two boxes on the interface select the VCI so it is highlighted in both boxes, then click the Send button. Copy and paste back here the String you get back from the SysExID request.
 
Cstoll,

Here is the string:


F0 7E 00 06 02 00 40 02 01 00 05 00 01 00 00 00 F7


Thank You,

Jim Jamz
 
Jimmy - thanks ... give me a day to look into what can be done ... its a bit more complicated now.

Seems that Vestax is using the same SysExID as the original release of the VCI-100 for the VCM-100 ... this is not the first time a vendor has done this :(

So, for an immediate fix to your situation ... you can correct the SysExID in the VCI-100 definition file to match your exact ID posted above.

We typically use ?? wildcards to accomodate future changes do to firmware updates, but in this case if you modify the ID to exactly match your unit you should be back in business.

You can also then delete the VCM-100 definition from the Devices folder.


But, I will work on a long-term solution in the meantime - so others don't have to go through this situation.
 
Cstoll,

I got the fix. I'm working fine now.

Your were spot on guru about the SysExID snafu.

The problem is not that the SysExIDs are duplicates. Each definition file has a unique number.

The VCM-100 has a SysExID of: F0 7E 00 06 02 00 40 02 01 00 05 00 01 00 00 00 F7

The VCI-100 has a SysExID of: F0 7E 00 06 02 00 40 02 01 00 05 00 02 00 00 00 F7

I changed the VCI-100 SysExId to: F0 7E 00 06 02 00 40 02 01 00 05 00 01 00 00 00 F7

And renamed the VCM-100 file.

Launched VDJ and voila I have VCI control again ..... BABY !!!

So there you go. Shouldn't be too bad to build the patch.

Thanks so very much.


Regards,


Jim Jamz
 
JimmyL-DJ wrote :

The problem is not that the SysExIDs are duplicates. Each definition file has a unique number.

The VCM-100 has a SysExID of: F0 7E 00 06 02 00 40 02 01 00 05 00 01 00 00 00 F7
The VCI-100 has a SysExID of: F0 7E 00 06 02 00 40 02 01 00 05 00 02 00 00 00 F7

...

So there you go. Shouldn't be too bad to build the patch.


No what you don't understand is that the VCI-100 first release (which you have) is the same as the VCM-100 ....

The - VCI-100 SysExID of: F0 7E 00 06 02 00 40 02 01 00 05 00 02 00 00 00 F7

That is for the firmware upgrade Vestax put on that unit ... and from what it looks like Vestax then recycled the original VCI-100 SysExID for the VCM-100 - that is why you have the conflict.
 
Cstoll,

So I got the VCI-100 to work with my mapper. Thank you for your help. But now I have another problem. Serious frame jump when using my jog wheel. I spin video either forward or backwards and the video will lock till I stop the FF or RW or slow the spin down. Then all goes normal. Both decks have same problem.

I do not have this problem in 6.0.5

Do I still have a issue with the sysexid causing this frame skip? I did fake out the software by changing the digit 2 to a 1 in the sysexid string.

Or was there a modification to the video engine in 6.0.8 ?

At this point I am stuck on 6.0.5 The frame skip is a serious problem for me.


Regards,

Jim
 
95%