Im trying to use a mixer midi key to nudge a song that I want to mix in either forward or backwards slightly to get beeter syncing.
crossfader right play? deck left nudge -20ms : deck right nudge -20ms
When I use +20ms, this works but not -ms. Is it not possible to be bale to nudge the incoming song left or right? Or perhaps my syntax is wrong?
crossfader right play? deck left nudge -20ms : deck right nudge -20ms
When I use +20ms, this works but not -ms. Is it not possible to be bale to nudge the incoming song left or right? Or perhaps my syntax is wrong?
geposted Sun 29 Jan 17 @ 7:28 am
Have you not got jogwheels?
I guess that in order to be nudged backwards, the track would have to already be playing (i.e. not right at the start).
If it's at the start, then you can't go back as you've not gone forward yet, if you see what I mean.
I guess that in order to be nudged backwards, the track would have to already be playing (i.e. not right at the start).
If it's at the start, then you can't go back as you've not gone forward yet, if you see what I mean.
geposted Sun 29 Jan 17 @ 9:00 am
So sometimes when I sync, the actual beats are slightly out and I want to be able to just nudge the track thats coming in and thought nudge could do it. Perhaps this isn't the best parameter to map to a button? Also, the song that I'm trying to mix in isn't at the start so it should be able to go backwards
Is there a better way?
Is there a better way?
geposted Sun 29 Jan 17 @ 5:07 pm
I don't get what your first query in your script is about.
geposted Sun 29 Jan 17 @ 5:50 pm
So I have my mixer connected and mapped to VDJ. What I want to do is:
1: Have a song 1 playing on deck 1
2: My aim is to mix a 2nd song 2 using deck 2
3: So with the cross fader on my mixer over to the left and with song 1 playing, I load up song 2 on deck 2.
4: I then sync the BPM using "play_sync_onbeat" which generally works very well (my music is mainly techno and house)
5: I then want to bring in song 2 at the appropriate time slowly using my cross fader.
6: Sometimes, the beats become slightly misaligned (the image above is an over exageration).
7: So I want to do whats normally done on record decks, i.e. to nudge the record coming in so it again overlaps perfectly.
So I thought I could do this in a script. I have 2 arrow buttons on my mixer that I want to assign move the song coming in forward e.g. 20ms with the right arrow button, and -20ms with the left arrow button. But these two buttons should work for which ever song is coming in so can be either the left deck or right deck. (Both records will be playing at this time).
So I thought, the best way was to determine where the crossfader was, to the left or right, so I guessed the following would be correct for the conditional statement
crossfader right play?
And then use the script for the left arrow button:
crossfader right play? deck left goto -20ms : deck right goto -20ms
and for the right arrow button:
crossfader right play? deck left goto +20ms : deck right goto +20ms
I have since found that goto might be better than nudge. I also wondered how you determine whether the crossfader is to the left of the middle or to the right of the middle, not necessarily all the way to the left or to the right.
Im not sure I've explained this any better?
Thanks for any help,
Jason
1: Have a song 1 playing on deck 1
2: My aim is to mix a 2nd song 2 using deck 2
3: So with the cross fader on my mixer over to the left and with song 1 playing, I load up song 2 on deck 2.
4: I then sync the BPM using "play_sync_onbeat" which generally works very well (my music is mainly techno and house)
5: I then want to bring in song 2 at the appropriate time slowly using my cross fader.
6: Sometimes, the beats become slightly misaligned (the image above is an over exageration).
7: So I want to do whats normally done on record decks, i.e. to nudge the record coming in so it again overlaps perfectly.
So I thought I could do this in a script. I have 2 arrow buttons on my mixer that I want to assign move the song coming in forward e.g. 20ms with the right arrow button, and -20ms with the left arrow button. But these two buttons should work for which ever song is coming in so can be either the left deck or right deck. (Both records will be playing at this time).
So I thought, the best way was to determine where the crossfader was, to the left or right, so I guessed the following would be correct for the conditional statement
crossfader right play?
And then use the script for the left arrow button:
crossfader right play? deck left goto -20ms : deck right goto -20ms
and for the right arrow button:
crossfader right play? deck left goto +20ms : deck right goto +20ms
I have since found that goto might be better than nudge. I also wondered how you determine whether the crossfader is to the left of the middle or to the right of the middle, not necessarily all the way to the left or to the right.
Im not sure I've explained this any better?
Thanks for any help,
Jason
geposted Sun 29 Jan 17 @ 6:27 pm
....Also tried this but no luck:
crossfader & param_smaller 50%? deck left goto +20ms : deck right goto +20ms
crossfader & param_smaller 50%? deck left goto +20ms : deck right goto +20ms
geposted Sun 29 Jan 17 @ 6:52 pm
You're missing a space between %? Your first script is missing a space between play?
Actually I'm not sure you first query is right at all, not at a machine to test...... but generally the last loaded deck becomes the selected deck therefore if your buttons are not deck assigned, (in the def)
Then just nudge should do it, or if they are deck assigned then deck default nudge
Actually I'm not sure you first query is right at all, not at a machine to test...... but generally the last loaded deck becomes the selected deck therefore if your buttons are not deck assigned, (in the def)
Then just nudge should do it, or if they are deck assigned then deck default nudge
geposted Sun 29 Jan 17 @ 7:03 pm
ha ha...nearly there.
left button:
crossfader & param_smaller 50% ? deck left goto +20ms : deck right goto +20ms
right buttons:
crossfader & param_bigger 50% ? deck left goto +20ms : deck right goto +20ms
It always does deck 2 regardless of where the cross fader is?
left button:
crossfader & param_smaller 50% ? deck left goto +20ms : deck right goto +20ms
right buttons:
crossfader & param_bigger 50% ? deck left goto +20ms : deck right goto +20ms
It always does deck 2 regardless of where the cross fader is?
geposted Sun 29 Jan 17 @ 7:10 pm
Thanks locodog.
You were right I can just assign goto +20ms and goto -20ms to the right and left buttons without having to determine which deck is coming in
Thanks
You were right I can just assign goto +20ms and goto -20ms to the right and left buttons without having to determine which deck is coming in
Thanks
geposted Mon 30 Jan 17 @ 9:07 pm
Hi,can anyone tell me using scripts, the command or set of commands that correspond to the deck (assume only 2) that the crossfader corresponds to?
Thanks for any help.
Thanks for any help.
geposted Sat 04 Feb 17 @ 6:37 pm