Se Connecter:     


Forum: General Discussion

Sujet: VCI-400 Mappng - Page: 7

Cette partie de ce topic est ancien et peut contenir des informations obselètes ou incorrectes

synth you know im thinking of having different colors on my transport section
 

ok i waant my play button to be green when track is playing.
 

Reading what the new firmware offers, i still cant find a good reason for the VCI-400 users to upgrade.
sorry for the off-topic guys.
Btw, Cioce, it would be useful to post information about your mapper files to the Plugin Forum instead of high-jacking this topic ;)
 

it gives you control of the trackpad leds and more control of the jog, considering that you can't use the soundcard with ASIO drivers in VDJ anyway I think it's all benefits.

It's a shame that when I asked Vestax support about the firmware and more specifically being able to change the trackpad leds that I couldn't get those details coice pasted in above, instead I got a grossly incompetent answer... When I replied asking are they sure I got the same response, By that time about 2 weeks had passed and I already had a mapper fully functioning. Lesson.. don't contact vestax, their support staff don't know anything and aren't prepared to check things with a team who would know.

/rant
 

@djdad i think he was posting it for my benefit...since synth been working on a mapping for my 400
 

synthet1c wrote :
it gives you control of the trackpad leds and more control of the jog, considering that you can't use the soundcard with ASIO drivers in VDJ anyway I think it's all benefits.


Am I missing something? When I used mine I used it with the ASIO drivers, and I've just updated it to the SDJ firmware and it's still working with the ASIO drivers?

 

That's weird... I've tried the original factory, the updated and the Serato DJ firmware and none of them worked, they all have a lot of feedback. I though it was because VDJ was only 44.1khz. The options I had for frequency in my asio settings were something like 78khz for the original and the updated versions, and 48khz for the Serato DJ firmware.. I just use my Audio 2 or Audio 8 depending on whether I need decks or not, but it would be good to have a listen to the much talked about studio sound quality that I still haven't heard yet.
 

Just checked and it was using ASIO at BPM too :)
 

looks like I need to have another try at it.
 

It shouldn't be the update procedure... I have upgraded and downgraded probably 5 or 6 times now on my three computers, unless I got it wrong everytime, or the guy I bought it off wrecked it before he sold it, that's probably it as it has never worked from the first time I plugged it in, I got it pretty cheap so not too many complaints.
 

Im flowing smooth with all upgrade and asio.. i am making a few remapping to have the things me and synth was working on in this thread, but i have one question...is there a way to make the mode 6+6+6 switch to flip to a 4 deck variation of the skin i am using...so i can flip to 4deck mixing on the fly.
 

Nah, I finished the upgrade successfully everytime. I also always uninstalled the previous asio driver before attempting the update.
 

there is a command you can use to change skins that you can use on skins, not sure if you can use it with mapping.. At worst you might need to rename the skins with similar names and add the button to it so you can swap between them. You will have to ask djdad about it though as he is the skin master.
 

also are the transport button the only ones i can change colors. Also Synth how do i get the leds to light up when theres a cue assigned to it....i mixed some of your mapping with this seratodj one and it is beautiful
 

Yep it's only the transport section, the grid is locked to the firmware. In the midi chart from vestax it says that you can control the grid being half brightness, full brightness and off, but I couldn't get it to work. I would have asked Vestax about it but they are useless.

To map the leds you can use this formula

hot_cue # ? var '$shift' ? blink 300ms : on : off

the button would be

var '$shift' ? delete_cue # : hot_cue #

what it is doing is blinking if you are holding shift which will allow you to delete the cue, but it will only blink if the hot cue exists. when not holding shift the led will be on if the cue exists or off if it doesn't. Because the transport section is not mapped to any side you may need to add deck left/right infront of all the actions eg

deck left hot_cue 1 ? var '$shift' ? blink 300ms : on : off
var '$shift' ? deck left delete_cue 1 : deck left hot_cue 1

Also I should mention that you could write the led like this if it makes more sense to you. The other way is just more efficient, but they do the same thing

var '$shift' ? hot_cue 1 ? blink 300ms : off : hot_cue 1 ? on : off
 

synthet1c wrote :
Yep it's only the transport section, the grid is locked to the firmware. In the midi chart from vestax it says that you can control the grid being half brightness, full brightness and off, but I couldn't get it to work. I would have asked Vestax about it but they are useless.

To map the leds you can use this formula

hot_cue # ? var '$shift' ? blink 300ms : on : off

the button would be

var '$shift' ? delete_cue # : hot_cue #

what it is doing is blinking if you are holding shift which will allow you to delete the cue, but it will only blink if the hot cue exists. when not holding shift the led will be on if the cue exists or off if it doesn't. Because the transport section is not mapped to any side you may need to add deck left/right infront of all the actions eg

deck left hot_cue 1 ? var '$shift' ? blink 300ms : on : off
var '$shift' ? deck left delete_cue 1 : deck left hot_cue 1

Also I should mention that you could write the led like this if it makes more sense to you. The other way is just more efficient, but they do the same thing

var '$shift' ? hot_cue 1 ? blink 300ms : off : hot_cue 1 ? on : off


well i did alter the mapping with our mapping
the button is

pad1
var '$sampler' ? sampler 1 play_stutter & sampler 1 select : var '$shift' ? delete_cue 1 : hot_cue 1

led pad1
var '$sampler' ? sampler 1 play ? blink : on : loop 0.125

how would i write it with this mapping
 

Dont worry i got it...
 

Sorry to jump in on your thread, but I’m thinking seriously about getting a 400 and I’m trying to figure out a few things about how it works and maps...

Scanning through this thread, I’m a little confused about what can and can’t be done to the LED colours and brightness on the pad grid. If I understand correctly, the entire bank must be the same colour, but can I have those colours switch depending on modes? I’m thinking about using the smaller buttons underneath as mode selectors (sort of like how the DDJ-SX is set up), but I’d like to be able to cycle through colours (ie. yellow for cues, green for sampler, red for loops, etc) and I’d prefer if they were dim until set/activated and bright afterwards. Actually, for that matter, what colours are even available on the pad grid? In videos I’ve been able to find it seems the only colour changes on the pad are based on what deck is selected by the rocker switch.

Is this actually possible? (Don’t need to know how to program it, just curious if it is actually doable!)
 

you have no control over the grid color or brightness. If the led is meant to be off it will be dim if it's meant to me on it will be full brightness at no time will it ever be off so there is no third state which would have been handy.

The transport buttons don't give you the ability to use all three colors only green and red on the outside four and orange and green on the inside two, that does mean you can make them all green though, it is a firmware limitation imposed by vestax so maybe if you begged them they could release a better firmware, but it's doubtful.

Back onto the LEDS I couldn't figure out how to set the color with "get constant" so had to program the on and off colors in the definition file, I contacted cstoll but he offered no insight to the issue, so it may be something I was doing wrong.

It's a good controller... there could definitely be improvements but the good definitely outweighs the bad by a long shot.
 

synthet1c wrote :
you have no control over the grid color or brightness. If the led is meant to be off it will be dim if it's meant to me on it will be full brightness at no time will it ever be off so there is no third state which would have been handy.

The transport buttons don't give you the ability to use all three colors only green and red on the outside four and orange and green on the inside two, that does mean you can make them all green though, it is a firmware limitation imposed by vestax so maybe if you begged them they could release a better firmware, but it's doubtful.

Back onto the LEDS I couldn't figure out how to set the color with "get constant" so had to program the on and off colors in the definition file, I contacted cstoll but he offered no insight to the issue, so it may be something I was doing wrong.

It's a good controller... there could definitely be improvements but the good definitely outweighs the bad by a long shot.


Synth is right if yo can get your hands on one, you wont be disappointed. i love this thing...

 

97%