Nektar Panorama Remote Maps Thread
-
- Posts: 1
- Joined: 24 Jul 2024
Hello.
I see this is quite an old post, but I've just dug up my old Panorama P6 and looking for help mapping it to REASON (and ABLETON). This seems a wonderful resource, but the Dropbox seems to have closed. Does the archive exist anywhere currently ? and/or can you recommend other resources ?
Thank you,
Peter
I see this is quite an old post, but I've just dug up my old Panorama P6 and looking for help mapping it to REASON (and ABLETON). This seems a wonderful resource, but the Dropbox seems to have closed. Does the archive exist anywhere currently ? and/or can you recommend other resources ?
Thank you,
Peter
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
It link was on the last page (before your post)..ProfessorJock wrote: ↑24 Jul 2024Hello.
I see this is quite an old post, but I've just dug up my old Panorama P6 and looking for help mapping it to REASON (and ABLETON). This seems a wonderful resource, but the Dropbox seems to have closed. Does the archive exist anywhere currently ? and/or can you recommend other resources ?
Thank you,
Peter
https://www.dropbox.com/sh/uac0qdt33eyr ... kyTya?dl=0
Yes, but it is a shame that the last Update for reason is from 2022.jackss wrote: ↑07 Aug 2024The Nektar Panorama is a fantastic controller for music production, especially with its ability to map seamlessly to various DAWs. The remote maps provide excellent integration and workflow enhancements. Has anyone explored custom mappings or found specific features that significantly boost their productivity? I'd love to hear your experiences!
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
that's why we update the mappings, there are quite a few here or the last main mapping I did included all the new devices however the mapping for Polytone was just a grab map.polysix wrote: ↑02 Sep 2024Yes, but it is a shame that the last Update for reason is from 2022.jackss wrote: ↑07 Aug 2024The Nektar Panorama is a fantastic controller for music production, especially with its ability to map seamlessly to various DAWs. The remote maps provide excellent integration and workflow enhancements. Has anyone explored custom mappings or found specific features that significantly boost their productivity? I'd love to hear your experiences!
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
if you have been upgrading using it then yes it should, if this is the first time then you need to make sure you are running the latest firmware.
Which P series map are you having issues with ?
there is more info here
Code: Select all
https://www.facebook.com/groups/915283455174650/permalink/2328963467139968
Thanks Carly, that got me sorted, the multitude of errors disappeared when i moved my backup. Was left with only one error, which seems to be a duplicate scope.Carly(Poohbear) wrote: ↑06 Sep 2024if you have been upgrading using it then yes it should, if this is the first time then you need to make sure you are running the latest firmware.
Which P series map are you having issues with ?
there is more info hereCode: Select all
https://www.facebook.com/groups/915283455174650/permalink/2328963467139968
Map File Errors:
Line 593077: Scope already defined.
not knowing enough about it i popped a 2 on the end. "Scope MagmaSonic drno.magmasonic.Retrazoo2"
Everything is happy again.
I am trying to create a simple Mimic mapping for a P4 , but even this basic one below is not working. Any ideas whats wrong?
Code: Select all
///MIMIC
Scope Propellerhead Software se.propellerheads.Mimic
Define Group Mode Instrument Mixer Transport Channel
Define Group X_Mode Default
Define Group Page Home
Map Mixer Mode Mode=Mixer
Map Instrument Mode Mode=Instrument
Map Transport Mode Mode=Transport
Map Channel Mode Mode=Channel
Map Device "Mimic"
Map Bypass Enabled Instrument
Map Display Default 0 Mixer
Map Display Default Page=Home Instrument
Map Instrument Mode X_Mode=Default Instrument
Map Name Element 1 "Stretch Speed 1" Instrument
Map Ch Knob 1 Stretch Speed 1 NAME Instrument
Map Name Element 2 "Effect Mod 1" Instrument
Map Ch Knob 2 Effect Mod 1 NAME Instrument
Map Name Element 3 "Loop Length 1" Instrument
Map Ch Knob 3 Loop Length 1 NAME Instrument
Map Name Element 5 "Pitch Semi 1" Instrument
Map Ch Knob 5 Pitch Semi 1 NAME Instrument
Map Fader Name Element 1 "Amp Gain 1" FADERS Instrument
Map Fader 1 Amp Gain 1 NAME Instrument
Map Fader Name Element 2 "Amp Attack 1" FADERS Instrument
Map Fader 2 Amp Attack 1 NAME Instrument
Map Fader Name Element 3 "Amp Decay 1" FADERS Instrument
Map Fader 3 Amp Decay 1 NAME Instrument
Map Fader Name Element 4 "Amp Release 1" FADERS Instrument
Map Fader 4 Amp Release 1 NAME Instrument
Map Fader Name Element 5 "Filter Attack 1" FADERS Instrument
Map Fader 5 Filter Attack 1 NAME Instrument
Map Fader Name Element 6 "Filter Decay 1" FADERS Instrument
Map Fader 6 Filter Decay 1 NAME Instrument
Map Fader Name Element 7 "Filter Release 1" FADERS Instrument
Map Fader 7 Filter Release 1 NAME Instrument
Map Button 1 Reverse 1 Instrument
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
Fusion wrote: ↑07 Sep 2024I am trying to create a simple Mimic mapping for a P4 , but even this basic one below is not working. Any ideas whats wrong?
Code: Select all
///MIMIC Scope Propellerhead Software se.propellerheads.Mimic Define Group Mode Instrument Mixer Transport Channel Define Group X_Mode Default Define Group Page Home Map Mixer Mode Mode=Mixer Map Instrument Mode Mode=Instrument Map Transport Mode Mode=Transport Map Channel Mode Mode=Channel Map Device "Mimic" Map Bypass Enabled Instrument Map Display Default 0 Mixer Map Display Default Page=Home Instrument Map Instrument Mode X_Mode=Default Instrument Map Name Element 1 "Stretch Speed 1" Instrument Map Ch Knob 1 Stretch Speed 1 NAME Instrument Map Name Element 2 "Effect Mod 1" Instrument Map Ch Knob 2 Effect Mod 1 NAME Instrument Map Name Element 3 "Loop Length 1" Instrument Map Ch Knob 3 Loop Length 1 NAME Instrument Map Name Element 5 "Pitch Semi 1" Instrument Map Ch Knob 5 Pitch Semi 1 NAME Instrument Map Fader Name Element 1 "Amp Gain 1" FADERS Instrument Map Fader 1 Amp Gain 1 NAME Instrument Map Fader Name Element 2 "Amp Attack 1" FADERS Instrument Map Fader 2 Amp Attack 1 NAME Instrument Map Fader Name Element 3 "Amp Decay 1" FADERS Instrument Map Fader 3 Amp Decay 1 NAME Instrument Map Fader Name Element 4 "Amp Release 1" FADERS Instrument Map Fader 4 Amp Release 1 NAME Instrument Map Fader Name Element 5 "Filter Attack 1" FADERS Instrument Map Fader 5 Filter Attack 1 NAME Instrument Map Fader Name Element 6 "Filter Decay 1" FADERS Instrument Map Fader 6 Filter Decay 1 NAME Instrument Map Fader Name Element 7 "Filter Release 1" FADERS Instrument Map Fader 7 Filter Release 1 NAME Instrument Map Button 1 Reverse 1 Instrument
Code: Select all
change
Map Device "Mimic"
to
Map Device Name "Mimic"
Still nothing. Maybe there is a reason why no one has mapped Mimic yet.Carly(Poohbear) wrote: ↑07 Sep 2024Fusion wrote: ↑07 Sep 2024I am trying to create a simple Mimic mapping for a P4 , but even this basic one below is not working. Any ideas whats wrong?
Code: Select all
///MIMIC Scope Propellerhead Software se.propellerheads.Mimic Define Group Mode Instrument Mixer Transport Channel Define Group X_Mode Default Define Group Page Home Map Mixer Mode Mode=Mixer Map Instrument Mode Mode=Instrument Map Transport Mode Mode=Transport Map Channel Mode Mode=Channel Map Device "Mimic" Map Bypass Enabled Instrument Map Display Default 0 Mixer Map Display Default Page=Home Instrument Map Instrument Mode X_Mode=Default Instrument Map Name Element 1 "Stretch Speed 1" Instrument Map Ch Knob 1 Stretch Speed 1 NAME Instrument Map Name Element 2 "Effect Mod 1" Instrument Map Ch Knob 2 Effect Mod 1 NAME Instrument Map Name Element 3 "Loop Length 1" Instrument Map Ch Knob 3 Loop Length 1 NAME Instrument Map Name Element 5 "Pitch Semi 1" Instrument Map Ch Knob 5 Pitch Semi 1 NAME Instrument Map Fader Name Element 1 "Amp Gain 1" FADERS Instrument Map Fader 1 Amp Gain 1 NAME Instrument Map Fader Name Element 2 "Amp Attack 1" FADERS Instrument Map Fader 2 Amp Attack 1 NAME Instrument Map Fader Name Element 3 "Amp Decay 1" FADERS Instrument Map Fader 3 Amp Decay 1 NAME Instrument Map Fader Name Element 4 "Amp Release 1" FADERS Instrument Map Fader 4 Amp Release 1 NAME Instrument Map Fader Name Element 5 "Filter Attack 1" FADERS Instrument Map Fader 5 Filter Attack 1 NAME Instrument Map Fader Name Element 6 "Filter Decay 1" FADERS Instrument Map Fader 6 Filter Decay 1 NAME Instrument Map Fader Name Element 7 "Filter Release 1" FADERS Instrument Map Fader 7 Filter Release 1 NAME Instrument Map Button 1 Reverse 1 Instrument
Code: Select all
change Map Device "Mimic" to Map Device Name "Mimic"
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
It works for me and I do have a grab mapping, just never posted it.Fusion wrote: ↑07 Sep 2024Still nothing. Maybe there is a reason why no one has mapped Mimic yet.Carly(Poohbear) wrote: ↑07 Sep 2024
Code: Select all
change Map Device "Mimic" to Map Device Name "Mimic"
Code: Select all
Scope Propellerhead Software se.propellerheads.Mimic
Define Group Mode Instrument Mixer Transport Channel
Define Group X_Mode Default
Define Group Page Home
Map Device Name "Mimic"
Map Bypass Enabled Instrument
Map Display Default 0 Mixer
Map Display Default Page=Home Instrument
Map Instrument Mode X_Mode=Default Instrument
Map Name Element 1 "Stretch Speed 1" Instrument
Map Ch Knob 1 Stretch Speed 1 NAME Instrument
Map Name Element 2 "Effect Mod 1" Instrument
Map Ch Knob 2 Effect Mod 1 NAME Instrument
Map Name Element 3 "Loop Length 1" Instrument
Map Ch Knob 3 Loop Length 1 NAME Instrument
Map Name Element 5 "Pitch Semi 1" Instrument
Map Ch Knob 5 Pitch Semi 1 NAME Instrument
Map Fader Name Element 1 "Amp Gain 1" FADERS Instrument
Map Fader 1 Amp Gain 1 NAME Instrument
Map Fader Name Element 2 "Amp Attack 1" FADERS Instrument
Map Fader 2 Amp Attack 1 NAME Instrument
Map Fader Name Element 3 "Amp Decay 1" FADERS Instrument
Map Fader 3 Amp Decay 1 NAME Instrument
Map Fader Name Element 4 "Amp Release 1" FADERS Instrument
Map Fader 4 Amp Release 1 NAME Instrument
Map Fader Name Element 5 "Filter Attack 1" FADERS Instrument
Map Fader 5 Filter Attack 1 NAME Instrument
Map Fader Name Element 6 "Filter Decay 1" FADERS Instrument
Map Fader 6 Filter Decay 1 NAME Instrument
Map Fader Name Element 7 "Filter Release 1" FADERS Instrument
Map Fader 7 Filter Release 1 NAME Instrument
Map Button 1 Reverse 1 Instrument
Last edited by Carly(Poohbear) on 07 Sep 2024, edited 1 time in total.
Not sure whats going on.Carly(Poohbear) wrote: ↑07 Sep 2024It works for me and I do have a grab mapping, just ever posted it.
Code: Select all
Scope Propellerhead Software se.propellerheads.Mimic Define Group Mode Instrument Mixer Transport Channel Define Group X_Mode Default Define Group Page Home Map Device Name "Mimic" Map Bypass Enabled Instrument Map Display Default 0 Mixer Map Display Default Page=Home Instrument Map Instrument Mode X_Mode=Default Instrument Map Name Element 1 "Stretch Speed 1" Instrument Map Ch Knob 1 Stretch Speed 1 NAME Instrument Map Name Element 2 "Effect Mod 1" Instrument Map Ch Knob 2 Effect Mod 1 NAME Instrument Map Name Element 3 "Loop Length 1" Instrument Map Ch Knob 3 Loop Length 1 NAME Instrument Map Name Element 5 "Pitch Semi 1" Instrument Map Ch Knob 5 Pitch Semi 1 NAME Instrument Map Fader Name Element 1 "Amp Gain 1" FADERS Instrument Map Fader 1 Amp Gain 1 NAME Instrument Map Fader Name Element 2 "Amp Attack 1" FADERS Instrument Map Fader 2 Amp Attack 1 NAME Instrument Map Fader Name Element 3 "Amp Decay 1" FADERS Instrument Map Fader 3 Amp Decay 1 NAME Instrument Map Fader Name Element 4 "Amp Release 1" FADERS Instrument Map Fader 4 Amp Release 1 NAME Instrument Map Fader Name Element 5 "Filter Attack 1" FADERS Instrument Map Fader 5 Filter Attack 1 NAME Instrument Map Fader Name Element 6 "Filter Decay 1" FADERS Instrument Map Fader 6 Filter Decay 1 NAME Instrument Map Fader Name Element 7 "Filter Release 1" FADERS Instrument Map Fader 7 Filter Release 1 NAME Instrument Map Button 1 Reverse 1 Instrument
Still not working. Thought it maybe not reading the correct file , but somehow added a m to the top line and settings said could not read correct fille , which pointed to the one I have been editing (Library/Application Support/Propellerhead Software/Remote/Maps/Nektar/Panorama.remotemap). Before editing I updated the file with the latest verion.
Could you share your Mimic mapping or add it to the Dropbox file?
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
What errors are you getting?Fusion wrote: ↑07 Sep 2024
Not sure whats going on.
Still not working. Thought it maybe not reading the correct file , but somehow added a m to the top line and settings said could not read correct fille , which pointed to the one I have been editing (Library/Application Support/Propellerhead Software/Remote/Maps/Nektar/Panorama.remotemap). Before editing I updated the file with the latest verion.
Could you share your Mimic mapping or add it to the Dropbox file?
double click the red cross and copy and paste the results here.
Just tested this mimic mapping and I've no errors loading it. It's working fine.
Albums: BandCamp | Youtubz: Noise Channel
Projects: P1 Easy Remote Mapping | Personal Refill Sale Store: https://payhip.com/noisesystems | Title Generator! untitled.noiseshadow.com
Projects: P1 Easy Remote Mapping | Personal Refill Sale Store: https://payhip.com/noisesystems | Title Generator! untitled.noiseshadow.com
The error is fine now. but still nothing is mapped in Mimic.Carly(Poohbear) wrote: ↑07 Sep 2024What errors are you getting?Fusion wrote: ↑07 Sep 2024
Not sure whats going on.
Still not working. Thought it maybe not reading the correct file , but somehow added a m to the top line and settings said could not read correct fille , which pointed to the one I have been editing (Library/Application Support/Propellerhead Software/Remote/Maps/Nektar/Panorama.remotemap). Before editing I updated the file with the latest verion.
Could you share your Mimic mapping or add it to the Dropbox file?
double click the red cross and copy and paste the results here.
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
Maybe he means the same as me.
There is no error. But none of the functions get mapped to the keyboard, so you cannot control mimic from the Nektar.
Not sure how its working your side, with the same code. I have a P4 with Reason 12
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
The only other comment I can make about the mapping is, I never make the "Name Element x" more than 8 characters and the "Fader Name Element x" more than 4 characters, I have seen that mess things up.
Another addition for this recent Metalazer, much easier (Fader 8 , 9 to Wet & Dry Level) _
https://www.reasonstudios.com/shop/rack ... le-filter/
https://www.reasonstudios.com/shop/rack ... le-filter/
Code: Select all
Scope Turn2on Software ru.turn2on.MetaLazer
Define Group Mode Instrument Mixer Transport Channel
Define Group force_patch_Feedback Patch 1 Patch 2
Define Group X_Mode Default
Define Group ch_Mode ch_Default
Define Group Mode_1 1_Free 1_Synced
// Control Surface Item Key Remotable Item Scale Mode
Map Mixer Mode Mode=Mixer
Map Instrument Mode Mode=Instrument
Map Transport Mode Mode=Transport
Map Channel Mode Mode=Channel
Map Patch Name Patch Name Instrument Patch 1
Map Patch Name Patch Name Instrument Patch 2
Map Force_patch_change force_patch_Feedback=Patch 1 Instrument Patch 2
Map Force_patch_change force_patch_Feedback=Patch 2 Instrument Patch 1
Map Display Default 0 Mixer
Map Display Default ch_Mode=ch_Default Instrument
Map Instrument Mode X_Mode=Default Instrument
Map Device Name "MetaLazer" HOME
Map Modifier1 1 Mode_1=1_Synced Instrument
Map Modifier1 0 Mode_1=1_Free Instrument
Map Bypass Enabled Instrument
Map Fader 8 Dry Level Instrument Default
Map Fader 9 Wet Level Instrument Default
Map Page Name "" Instrument Default
Map X1_Labeli "Bypass" Instrument Default
Map X2_Labeli "Polarity" Instrument Default
Map X3_Labeli "L F O " Instrument Default
Map X4_Labeli "Sync" MENU_ESC Instrument Default
Map X5_Labeli "Chance" Instrument Default
Map X1 0 BYPASS Instrument Default
Map X2 Polarity CTRL Instrument Default
Map X3 LFO On/Off CTRL Instrument Default
Map X4 LFO Sync MODIFIER1 Instrument Default
Map X5 0 RANDOMIZE Instrument Default
Map Ch Knob 1 Tone Frequency Instrument ch_Default
Map Ch Knob 2 Feedback Instrument ch_Default
Map Ch Knob 3 Sharpness Resonance Instrument ch_Default
Map Ch Knob 4 Central Frequency Instrument ch_Default
Map Ch Knob 7 LFO Speed Instrument ch_Default 1_Free
Map Ch Knob 7 LFO Rate Instrument ch_Default 1_Synced
Map Ch Knob 6 Filter Smooth Instrument ch_Default
Map Ch Knob 5 Mix Instrument ch_Default
Map Ch Knob 8 LFO Amount Instrument ch_Default
I’ve been scratching a bald spot on my head with this, so I was thinking its time to ask someone wiser.
I was trying to use a modifier in order to assign four parameters on to the same fader, but could not make it work. The device is Valhalla Delay. It has a control that controls the delay in Msec or steps (its the “knob” in the picture which is labeled “DELAY”). Whether the delay is in Msec or steps is decided by the drop-down menu that you can see in the picture below the “knob”.
I saw instruction only on how to create a modifier with an on/off button, but this drop-down menu has four values for Msec, note, dotted and triplet, thus I mapped it to a fader. Nevertheless, in the code only two remotes are used: DelayL_Ms for Msec and DelayLNote which covers all three step values (note, dotted and triplet)
My first problem is that I don’t know the values that are used for Msec, note, dotted and triplet. When I move the fader that I have assigned to control the drop-down menu, the values on the display are MSEC, NOTE, ., and T. But if I use these in the code to give modifier1 its values, I get the error message: “Map entry with unknown control surface item." That’s why I’ve put a question mark in place of the values in the code.
The second problem is that there’s something wrong with the line:
“Map Fader 1 DelayLSync MODIFIER1 Instrument”.
This gives the following error message: “Map entry with unknown mode.”
What would be the best way to go on with this? Any help would be much appreciated!
Here the whole code related to the modifier:
Define Group Delay_time Ms Note Dotted Triplet
//Sync Modifier
Map Modifier1 ? Delay_time=Ms Instrument
Map Modifier1 ? Delay_time=Note Instrument
Map Modifier1 ? Delay_time=Dotted Instrument
Map Modifier1 ? Delay_time=Triplet Instrument
Map Fader 1 DelayLSync MODIFIER1 Instrument
Map Fader 2 DelayL_Ms NAME Instrument Ms
Map Fader 2 DelayLNote NAME Instrument Note
Map Fader 2 DelayLNote NAME Instrument Dotted
Map Fader 2 DelayLNote NAME Instrument Triplet
I was trying to use a modifier in order to assign four parameters on to the same fader, but could not make it work. The device is Valhalla Delay. It has a control that controls the delay in Msec or steps (its the “knob” in the picture which is labeled “DELAY”). Whether the delay is in Msec or steps is decided by the drop-down menu that you can see in the picture below the “knob”.
I saw instruction only on how to create a modifier with an on/off button, but this drop-down menu has four values for Msec, note, dotted and triplet, thus I mapped it to a fader. Nevertheless, in the code only two remotes are used: DelayL_Ms for Msec and DelayLNote which covers all three step values (note, dotted and triplet)
My first problem is that I don’t know the values that are used for Msec, note, dotted and triplet. When I move the fader that I have assigned to control the drop-down menu, the values on the display are MSEC, NOTE, ., and T. But if I use these in the code to give modifier1 its values, I get the error message: “Map entry with unknown control surface item." That’s why I’ve put a question mark in place of the values in the code.
The second problem is that there’s something wrong with the line:
“Map Fader 1 DelayLSync MODIFIER1 Instrument”.
This gives the following error message: “Map entry with unknown mode.”
What would be the best way to go on with this? Any help would be much appreciated!
Here the whole code related to the modifier:
Define Group Delay_time Ms Note Dotted Triplet
//Sync Modifier
Map Modifier1 ? Delay_time=Ms Instrument
Map Modifier1 ? Delay_time=Note Instrument
Map Modifier1 ? Delay_time=Dotted Instrument
Map Modifier1 ? Delay_time=Triplet Instrument
Map Fader 1 DelayLSync MODIFIER1 Instrument
Map Fader 2 DelayL_Ms NAME Instrument Ms
Map Fader 2 DelayLNote NAME Instrument Note
Map Fader 2 DelayLNote NAME Instrument Dotted
Map Fader 2 DelayLNote NAME Instrument Triplet
- Attachments
-
- Valhalla Delay.jpg (111.9 KiB) Viewed 1887 times
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
Faders don't support the mode MODIFIERx, you need to use a knob or button or the x buttons or the data encoder.
Note normal buttons don't support MODIFIER3
They should be 0,1,2,3
However VST's are different from RE's and this system was built with RE's in mind so when things don't seam right I try out what I'm doing with a RE first, if the VST fails after that then I usually put it down to the VST e.g. VST's ranges for controls are set 0 to 4194304, with RE's if you had a control that only had 4 positions it would be set as 0 to 3 etc.
Thanks a lot, I think I made some progress. I mapped to knobs instead of faders. Now I only get one error message.
This line:
Map Knob 1 DelayLSync MODIFIER1 Instrument
It gives the error message: "Map entry with unknown mode."
This is how the code looks now:
Define Group Delay_time Ms Note Dotted Triplet
//Sync Modifier
Map Modifier1 0 Delay_time=Ms Instrument
Map Modifier1 1 Delay_time=Note Instrument
Map Modifier1 2 Delay_time=Dotted Instrument
Map Modifier1 3 Delay_time=Triplet Instrument
Map Knob 1 DelayLSync MODIFIER1 Instrument
Map Knob 2 DelayL_Ms NAME Instrument Ms
Map Knob 2 DelayLNote NAME Instrument Note
Map Knob 2 DelayL_Ms NAME Instrument Dotted
Map Knob 2 DelayLNote NAME Instrument Triplet
Did I understand correctly from your answer that the number after the modifier (modifier1, modifier2, modifier3..) affects how the modifier functions? I thought it was a number just to separate the modifiers from each other if one uses many of them.
This line:
Map Knob 1 DelayLSync MODIFIER1 Instrument
It gives the error message: "Map entry with unknown mode."
This is how the code looks now:
Define Group Delay_time Ms Note Dotted Triplet
//Sync Modifier
Map Modifier1 0 Delay_time=Ms Instrument
Map Modifier1 1 Delay_time=Note Instrument
Map Modifier1 2 Delay_time=Dotted Instrument
Map Modifier1 3 Delay_time=Triplet Instrument
Map Knob 1 DelayLSync MODIFIER1 Instrument
Map Knob 2 DelayL_Ms NAME Instrument Ms
Map Knob 2 DelayLNote NAME Instrument Note
Map Knob 2 DelayL_Ms NAME Instrument Dotted
Map Knob 2 DelayLNote NAME Instrument Triplet
Did I understand correctly from your answer that the number after the modifier (modifier1, modifier2, modifier3..) affects how the modifier functions? I thought it was a number just to separate the modifiers from each other if one uses many of them.
- Carly(Poohbear)
- Competition Winner
- Posts: 2945
- Joined: 25 Jan 2015
- Location: UK
The knobs you have to use are the "Ch Knob 2"Maxim wrote: ↑08 Nov 2024Thanks a lot, I think I made some progress. I mapped to knobs instead of faders. Now I only get one error message.
This line:
Map Knob 1 DelayLSync MODIFIER1 Instrument
It gives the error message: "Map entry with unknown mode."
This is how the code looks now:
Define Group Delay_time Ms Note Dotted Triplet
//Sync Modifier
Map Modifier1 0 Delay_time=Ms Instrument
Map Modifier1 1 Delay_time=Note Instrument
Map Modifier1 2 Delay_time=Dotted Instrument
Map Modifier1 3 Delay_time=Triplet Instrument
Map Knob 1 DelayLSync MODIFIER1 Instrument
Map Knob 2 DelayL_Ms NAME Instrument Ms
Map Knob 2 DelayLNote NAME Instrument Note
Map Knob 2 DelayL_Ms NAME Instrument Dotted
Map Knob 2 DelayLNote NAME Instrument Triplet
Did I understand correctly from your answer that the number after the modifier (modifier1, modifier2, modifier3..) affects how the modifier functions? I thought it was a number just to separate the modifiers from each other if one uses many of them.
The number after the modifier is for separation.
The DelayLSync may cause unexpected results as it's range is 0 to 4194304
Yeah, it definitely caused unexpected results. No more errors in the lines, but it works in a weird way, and the dotted mode doesn't work at all. I'll just map the msec and steps to different controls to have it work. There are so many intricacies in the remote mapping that its a shame there is no in-depth tutorial available for this. But your advice helped a lot for me to understand how the modifiers work, so I can definitely use this in the future in some other mappings. So thanks for that!Carly(Poohbear) wrote: ↑08 Nov 2024The knobs you have to use are the "Ch Knob 2"
The number after the modifier is for separation.
The DelayLSync may cause unexpected results as it's range is 0 to 4194304
-
- Information
-
Who is online
Users browsing this forum: Google [Bot] and 1 guest