[quote=locodog]no, not with how the script works at the moment.
to what performance purpose would you need to switch sample positions?[/
because for example if i’m using deck 1 and 3 for track mixing and i would use a sampler in pad position 1-8...if i move this sampler in pad position 9 (for example) i can use the same sampler in deck 2 or 4 that are free track mixing in this moment :)
to what performance purpose would you need to switch sample positions?[/
because for example if i’m using deck 1 and 3 for track mixing and i would use a sampler in pad position 1-8...if i move this sampler in pad position 9 (for example) i can use the same sampler in deck 2 or 4 that are free track mixing in this moment :)
geposted Wed 24 Feb 21 @ 6:40 am
i have written this script in a “pad editor name” for have 2 information in a pad1 (for example) layout: get_text “ `sampler_volume_nogroup & param_cast ‘integer’ ` \n `get_sampler_name 1 `”
but i can see only sampler volume 1 in %, i can’t see under (I would like it to wrap up) nothing :( can you help me?
thanks!!!
but i can see only sampler volume 1 in %, i can’t see under (I would like it to wrap up) nothing :( can you help me?
thanks!!!
geposted Thu 25 Feb 21 @ 11:15 am
Because script is bad and actions used are wrong
`sampler_volume_nogroup` \n`get_sample_name 1`
or
`sampler_volume_nogroup` \n`get_sampler_bank`
`sampler_volume_nogroup` \n`get_sample_name 1`
or
`sampler_volume_nogroup` \n`get_sampler_bank`
geposted Thu 25 Feb 21 @ 12:38 pm
Nicotux wrote :
Because script is bad and actions used are wrong
`sampler_volume_nogroup` \n`get_sample_name 1`
or
`sampler_volume_nogroup` \n`get_sampler_bank`
`sampler_volume_nogroup` \n`get_sample_name 1`
or
`sampler_volume_nogroup` \n`get_sampler_bank`
sorry but this scripts doesn't work :(
geposted Thu 25 Feb 21 @ 8:46 pm
strange... they wouldn't work in b61xx and earlier without at least one leading space
was fixed in b62xx
in 63xx it needs the leading space (or other chars) again
" `sampler_volume_nogroup` \n`get_sample_name 1`"
" `sampler_volume_nogroup` \n`get_sampler_bank`"
without the double quotes of course ^^
was fixed in b62xx
in 63xx it needs the leading space (or other chars) again
" `sampler_volume_nogroup` \n`get_sample_name 1`"
" `sampler_volume_nogroup` \n`get_sampler_bank`"
without the double quotes of course ^^
geposted Thu 25 Feb 21 @ 9:13 pm
Nicotux wrote :
strange... they wouldn't work in b61xx and earlier without at least one leading space
was fixed in b62xx
in 63xx it needs the leading space (or other chars) again
" `sampler_volume_nogroup` \n`get_sample_name 1`"
" `sampler_volume_nogroup` \n`get_sampler_bank`"
without the double quotes of course ^^
was fixed in b62xx
in 63xx it needs the leading space (or other chars) again
" `sampler_volume_nogroup` \n`get_sample_name 1`"
" `sampler_volume_nogroup` \n`get_sampler_bank`"
without the double quotes of course ^^
i think there is a little bug in last version
6294 because my friend have controller Nunark NV and in it’s display default mapper (effects section) there is “action 1\naction 2” but don’t work now :(
geposted Mon 01 Mar 21 @ 12:20 pm
mg_1978 wrote :
i think there is a little bug in last version
6294 because my friend have controller Nunark NV and in it’s display default mapper (effects section) there is “action 1\naction 2” but don’t work now :(
Nicotux wrote :
strange... they wouldn't work in b61xx and earlier without at least one leading space
was fixed in b62xx
in 63xx it needs the leading space (or other chars) again
" `sampler_volume_nogroup` \n`get_sample_name 1`"
" `sampler_volume_nogroup` \n`get_sampler_bank`"
without the double quotes of course ^^
was fixed in b62xx
in 63xx it needs the leading space (or other chars) again
" `sampler_volume_nogroup` \n`get_sample_name 1`"
" `sampler_volume_nogroup` \n`get_sampler_bank`"
without the double quotes of course ^^
i think there is a little bug in last version
6294 because my friend have controller Nunark NV and in it’s display default mapper (effects section) there is “action 1\naction 2” but don’t work now :(
Eureka! i have understand problem :) is the skin! with PRO skin works better.....with PERFORMANCE skin don't work....
geposted Mon 01 Mar 21 @ 10:42 pm
hi! if i would only 5 letters about sampler name is correct this script?
- get_sample_name 1 & param_cast ‘text’ 5
i think is correct but don’t work :(
- get_sample_name 1 & param_cast ‘text’ 5
i think is correct but don’t work :(
geposted Tue 02 Mar 21 @ 7:21 am
Vci400, using 4 decks, setting Ducking Echo activate. Mapping has to be set for decks 1 and 3 which are the left side. This is what I came up with by truncating the mapping that was used to mimic a post fader effect before the software add a post fader effect. I thought it would work but it doesn't.
geposted Tue 02 Mar 21 @ 7:46 am
@3X just strip it out, as far as I remember work around pffx was a button and a crossfader script, button; delete the mapping. crossfader change it back to just
crossfader.
if you're wary of killing your mapping just make a copy, experimenting with this kind of stuff is risk free.
crossfader.
if you're wary of killing your mapping just make a copy, experimenting with this kind of stuff is risk free.
geposted Tue 02 Mar 21 @ 6:29 pm
@mg_1978 tested here without problem
warn the quotes in your post were not correct ones, must be simple quote or double quotes and are optional here :
get_sample_name 12 & param_cast text 4
warn the quotes in your post were not correct ones, must be simple quote or double quotes and are optional here :
get_sample_name 12 & param_cast text 4
geposted Tue 02 Mar 21 @ 6:38 pm
Djratedxxx919 wrote :
Vci400, using 4 decks, setting Ducking Echo activate. Mapping has to be set for decks 1 and 3 which are the left side. This is what I came up with by truncating the mapping that was used to mimic a post fader effect before the software add a post fader effect. I thought it would work but it doesn't.

geposted Tue 02 Mar 21 @ 8:22 pm
just to rememder :
leftcross ? deck all leftcross ? xxxx : : rightcross ? deck all rightcross ? xxxx : : xxxx
will do xxxx on all the decks affected to the same crossfader side as calling deck or to the calling deck only if not affected to crossfader
usefull even with more than 4 decks
leftcross ? deck all leftcross ? xxxx : : rightcross ? deck all rightcross ? xxxx : : xxxx
will do xxxx on all the decks affected to the same crossfader side as calling deck or to the calling deck only if not affected to crossfader
usefull even with more than 4 decks
geposted Tue 02 Mar 21 @ 8:49 pm
Nicotux wrote :
just to rememder :
leftcross ? deck all leftcross ? xxxx : : rightcross ? deck all rightcross ? xxxx : : xxxx
will do xxxx on all the decks affected to the same crossfader side as calling deck or to the calling deck only if not affected to crossfader
usefull even with more than 4 decks
leftcross ? deck all leftcross ? xxxx : : rightcross ? deck all rightcross ? xxxx : : xxxx
will do xxxx on all the decks affected to the same crossfader side as calling deck or to the calling deck only if not affected to crossfader
usefull even with more than 4 decks
If this was for me, you just lost me....
geposted Tue 02 Mar 21 @ 9:25 pm
@3X vars have no place with default fx, neither sides/deck really
effect_active 'ducking echo'
post fader fx before official was a patchwork, press this - turn on some fx - trigger a var, var lets the XF script know to use a variation script.
a work around but at the time that made the impossible possible, I don't know if the devs adopted any of my methods or thinking, but I believe my bodge attempt - at least - somewhat encouraged official.
All that said, after poking around new stuff, effect_stems currently isn't post fader, so the method isn't completely dead
effect_active 'ducking echo'
post fader fx before official was a patchwork, press this - turn on some fx - trigger a var, var lets the XF script know to use a variation script.
a work around but at the time that made the impossible possible, I don't know if the devs adopted any of my methods or thinking, but I believe my bodge attempt - at least - somewhat encouraged official.
All that said, after poking around new stuff, effect_stems currently isn't post fader, so the method isn't completely dead
geposted Tue 02 Mar 21 @ 9:33 pm
locodog wrote :
@3X vars have no place with default fx, neither sides/deck really
effect_active 'ducking echo'
post fader fx before official was a patchwork, press this - turn on some fx - trigger a var, var lets the XF script know to use a variation script.
a work around but at the time that made the impossible possible, I don't know if the devs adopted any of my methods or thinking, but I believe my bodge attempt - at least - somewhat encouraged official.
All that said, after poking around new stuff, effect_stems currently isn't post fader, so the method isn't completely dead
effect_active 'ducking echo'
post fader fx before official was a patchwork, press this - turn on some fx - trigger a var, var lets the XF script know to use a variation script.
a work around but at the time that made the impossible possible, I don't know if the devs adopted any of my methods or thinking, but I believe my bodge attempt - at least - somewhat encouraged official.
All that said, after poking around new stuff, effect_stems currently isn't post fader, so the method isn't completely dead
Is it possible to work with you on reworking the mapping to fit today's software structure?...
geposted Tue 02 Mar 21 @ 9:37 pm
Djratedxxx919 wrote :
Is it possible to work with you on reworking the mapping to fit today's software structure?...
locodog wrote :
@3X vars have no place with default fx, neither sides/deck really
effect_active 'ducking echo'
post fader fx before official was a patchwork, press this - turn on some fx - trigger a var, var lets the XF script know to use a variation script.
a work around but at the time that made the impossible possible, I don't know if the devs adopted any of my methods or thinking, but I believe my bodge attempt - at least - somewhat encouraged official.
All that said, after poking around new stuff, effect_stems currently isn't post fader, so the method isn't completely dead
effect_active 'ducking echo'
post fader fx before official was a patchwork, press this - turn on some fx - trigger a var, var lets the XF script know to use a variation script.
a work around but at the time that made the impossible possible, I don't know if the devs adopted any of my methods or thinking, but I believe my bodge attempt - at least - somewhat encouraged official.
All that said, after poking around new stuff, effect_stems currently isn't post fader, so the method isn't completely dead
Is it possible to work with you on reworking the mapping to fit today's software structure?...
I got beer money
geposted Wed 03 Mar 21 @ 12:24 am
Nicotux wrote :
@mg_1978 tested here without problem
warn the quotes in your post were not correct ones, must be simple quote or double quotes and are optional here :
get_sample_name 12 & param_cast text 4
warn the quotes in your post were not correct ones, must be simple quote or double quotes and are optional here :
get_sample_name 12 & param_cast text 4
yes work! thanks (i was wrong to write)
geposted Wed 03 Mar 21 @ 6:32 am
hi! i would map a button like “mic_talkover”, but for line input! because my microphone is used by soundcard that is connected in line 4 my controller. If button is toggle i have mapped:
button: toggle ‘talkover’ and var ‘talkover’ 1 ? get_vu_meter ‘linein’ ? deck all volume 20% : volume : volume
but don’t work :( can you help me??
button: toggle ‘talkover’ and var ‘talkover’ 1 ? get_vu_meter ‘linein’ ? deck all volume 20% : volume : volume
but don’t work :( can you help me??
geposted Wed 03 Mar 21 @ 6:38 am
Djratedxxx919 wrote :
[quote=locodog]@3X vars have no place with default fx, neither sides/deck really
effect_active 'ducking echo'
effect_active 'ducking echo'
Ok this works on deck 1 but does not when I switch the left side to be deck 3.
geposted Wed 03 Mar 21 @ 6:54 am