Hi everyone,
I recently found out that the linnstrument does not store some light settings in its 6 memories. To overcome this limitation I have made a max 4 live patch that is able to change the memories and set the lights as I need. I can control which memory slot is selected from either from the patch or from the linnstrument itself using the PC messages or the two switches (CC). However it would be nice to detect when a memory slot has been selected in the linnstrument and make the lights go accordingly. I have seen there is a bunch of midi data sent each time a memory slot is selected, that I could use for that. But before getting to study number by number, does anyone know which messages would be better suited for this purpose? Ideally not tied to the configuration of the memory, to avoid changing some parameter in the future and breaking the detection.
Thanks!
Memory slot detection
-
- KVRAF
- 2724 posts since 8 Jun, 2010
- Roger Linn Design
Please visit the LinnStrument Support page and click "MIDI Implementation".
-
- KVRer
- Topic Starter
- 7 posts since 18 Aug, 2022
Hi Roger, I have done that, all the way to the midi.txt file, which I used a lot for the m4l patch. But I have not found the answer to that? May I have overlooked something?
-
- KVRAF
- 2724 posts since 8 Jun, 2010
- Roger Linn Design
To be clear, I think you are asking if, when you load one of the 6 "All Settings" memories from flash into LinnStrument's RAM by pressing one of the 6 blue buttons on the right side of the Preset screen, either 1) LinnStrument sends a message to indicate that it has just made such a copying operation, or 2) if it is possible to query LinnStrument from an external computer in order to learn that last time that such a copy operation was made.
If this is your question, I'm sorry to report that LinnStrument does neither. But you're welcome to change the source code to add your desired feature. If you'd like to learn my guiding principle for adding software features, it's on the LinnStrument FAQ page, "General" tab, FAQ "Can you add this feature ________?".
If this is your question, I'm sorry to report that LinnStrument does neither. But you're welcome to change the source code to add your desired feature. If you'd like to learn my guiding principle for adding software features, it's on the LinnStrument FAQ page, "General" tab, FAQ "Can you add this feature ________?".
-
- KVRer
- Topic Starter
- 7 posts since 18 Aug, 2022
Thanks Roger! yes, 1). The idea is that Max for live can get a message from linnstrument when one of the slots is selected, so Max can configure custom light settings accordingly via CC messages.
I have already a Max patch that can change the memory slot via NRPN and then configures the lights, In fact, the patch colors the panel for drums (i.e. in groups of 4x4, similar to a novation launckkey, maschine, etc) for certain slots and revert to the default for others more synth oriented. It would be wonderful to make the same operation from linnstrument: change the slot in the panel -> Max receives the message -> Max sends the CCs and colors the surface.
I have been taking a look at the code and seems feasible. I will report back when I have something. If anyone is interested in the max patch, let me know and I will share it.
I have already a Max patch that can change the memory slot via NRPN and then configures the lights, In fact, the patch colors the panel for drums (i.e. in groups of 4x4, similar to a novation launckkey, maschine, etc) for certain slots and revert to the default for others more synth oriented. It would be wonderful to make the same operation from linnstrument: change the slot in the panel -> Max receives the message -> Max sends the CCs and colors the surface.
I have been taking a look at the code and seems feasible. I will report back when I have something. If anyone is interested in the max patch, let me know and I will share it.
-
- KVRAF
- 2724 posts since 8 Jun, 2010
- Roger Linn Design
I’m glad you’ve found where to implement your feature in the code.
-
- KVRAF
- 9583 posts since 6 Jan, 2017 from Outer Space
Would you mind to share your Max patch? Could also be on the Cycling74 forum as inline with a link here (or both ; - )Chan649 wrote: Tue Aug 27, 2024 8:49 am I have already a Max patch that can change the memory slot via NRPN and then configures the lights, In fact, the patch colors the panel for drums (i.e. in groups of 4x4, similar to a novation launckkey, maschine, etc) for certain slots and revert to the default for others more synth oriented.
And there is the new Linstrument Wiki…
-
- KVRer
- Topic Starter
- 7 posts since 18 Aug, 2022
Sure thing! Here it is: https://drive.google.com/file/d/1G96nr6 ... sp=sharing
It is a bit specific to my needs but happy to help anyone modify it to suit other purposes. A bit of explanation:
- It changes memory slots suing NRPN. These buttons can be midi mapped. I have them on linnstrument switch 1 and 2. The patch also configures these switches at start up for this, but this feature can be easily removed from the patch by deleting "p set switch 1 and 2 Linn"
- All memory slots revert the colors to the default (i.e. stored settings in linnstrument) except for the 6th, which creates a sort of drum pad colouring from C1. My 6th preset is configured to have a major third interval (i.e. like MPC, Maschine and other common drum pads) and to be regular MIDI on split 1 and MPE on split 2. Where to change the preset with the drum mode is documented in the patch
- It can also color any preset as a drum mode using the "drum mode" button, and also revert to default using the "Revert" button
- It has a feature to send a specific color to a pad, just for fun
- It blocks midi thru since I prefer to have this devices on separate tracks and in general it is a good practice to avoid unintended midi loops, but if needed it is as simple as wiring midiin to midiout in the patch. The track must send midi out to the Linnstrument.
I did not know about the wiki for Linnstrument, but happy to contribute where I can.
It is a bit specific to my needs but happy to help anyone modify it to suit other purposes. A bit of explanation:
- It changes memory slots suing NRPN. These buttons can be midi mapped. I have them on linnstrument switch 1 and 2. The patch also configures these switches at start up for this, but this feature can be easily removed from the patch by deleting "p set switch 1 and 2 Linn"
- All memory slots revert the colors to the default (i.e. stored settings in linnstrument) except for the 6th, which creates a sort of drum pad colouring from C1. My 6th preset is configured to have a major third interval (i.e. like MPC, Maschine and other common drum pads) and to be regular MIDI on split 1 and MPE on split 2. Where to change the preset with the drum mode is documented in the patch
- It can also color any preset as a drum mode using the "drum mode" button, and also revert to default using the "Revert" button
- It has a feature to send a specific color to a pad, just for fun
- It blocks midi thru since I prefer to have this devices on separate tracks and in general it is a good practice to avoid unintended midi loops, but if needed it is as simple as wiring midiin to midiout in the patch. The track must send midi out to the Linnstrument.
I did not know about the wiki for Linnstrument, but happy to contribute where I can.
-
FranklyFlawless FranklyFlawless https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=586325
- KVRian
- 1091 posts since 24 Oct, 2022
Which is currently marked as inactive:Chan649 wrote: Fri Aug 30, 2024 8:43 am I did not know about the wiki for Linnstrument, but happy to contribute where I can.
This wiki has had no edits or log actions made within the last 45 days and has been automatically marked as inactive. If you would like to prevent this wiki from being closed, please start showing signs of activity here. If there are no signs of this wiki being used within the next 15 days, this wiki will be closed in accordance to the Dormancy Policy (which all wiki founders accept when requesting a wiki). If this wiki is closed and no one reopens it 135 days from now, this wiki will become eligible for deletion. Note: If you are a bureaucrat, you can go to Special:ManageWiki and uncheck "inactive" yourself.