Comments by krito
Thanks for the feedback! That would definitely be useful if the device would save its state, as all other devices do by default. I will have a look into it and fix this as soon as possible.
Posted on August 02 2024 by krito |
Report Issue |
See Comment
Hey @maboos,
Thank you so much for the feedback and the bug report on MPE.
I don't have an MPE controller, which makes the whole MPE suppport quite difficult to test for me.
But maybe you could help me here:
You could record an MPE sequence with the ROLI Seaboard to a midi channel in Live, that crashes the midi looper, and then send that live project to public@krito.de :) that way I can reproduce the issue and have a way to fix it, essentially adding MPE support. If you do that, please do it with an Ableton Live 11, I haven't upgraded to 12 yet, you know, money is short.
Depending on how difficult this is to fix, I might be able to roll out an update in the next few weeks.
Thank you so much for the feedback and the bug report on MPE.
I don't have an MPE controller, which makes the whole MPE suppport quite difficult to test for me.
But maybe you could help me here:
You could record an MPE sequence with the ROLI Seaboard to a midi channel in Live, that crashes the midi looper, and then send that live project to public@krito.de :) that way I can reproduce the issue and have a way to fix it, essentially adding MPE support. If you do that, please do it with an Ableton Live 11, I haven't upgraded to 12 yet, you know, money is short.
Depending on how difficult this is to fix, I might be able to roll out an update in the next few weeks.
Thank you for the feedback; it's much appreciated!
- Implementing the replace mode is not straightforward due to its interaction with undo. Adding this feature may take some time.
- @raverpavel: I've investigated the issue you mentioned with multiple midi loopers but couldn't reproduce it. I'd like to fix it, but I need your assistance. Please share an Ableton project, a video demonstrating the problem, or provide a detailed explanation of how to replicate it. You can send it to public@krito.de.
- Regarding the reset clock button, @d0gselfie, could you clarify its purpose and function? Is it for shifting looper content to different timings? While I'm considering this idea, I'm unsure about its usefulness and the interface design, as I don't want to replicate Ableton's existing MIDI editor.
- I won't be adding the ability to fire multiple patterns since this can be achieved easily with multiple loopers.
- Pattern save has been added to the roadmap as a high-priority feature. It will save the pattern whenever the Ableton file is saved and will be implemented next.
- Implementing the replace mode is not straightforward due to its interaction with undo. Adding this feature may take some time.
- @raverpavel: I've investigated the issue you mentioned with multiple midi loopers but couldn't reproduce it. I'd like to fix it, but I need your assistance. Please share an Ableton project, a video demonstrating the problem, or provide a detailed explanation of how to replicate it. You can send it to public@krito.de.
- Regarding the reset clock button, @d0gselfie, could you clarify its purpose and function? Is it for shifting looper content to different timings? While I'm considering this idea, I'm unsure about its usefulness and the interface design, as I don't want to replicate Ableton's existing MIDI editor.
- I won't be adding the ability to fire multiple patterns since this can be achieved easily with multiple loopers.
- Pattern save has been added to the roadmap as a high-priority feature. It will save the pattern whenever the Ableton file is saved and will be implemented next.
Hi Everybody,
I have updated the device (v1.4):
- Support CC messages: It is now possible to record and playback Pitchbend, Modwheel, Aftertouch, PolyPressure and other CC messages.
I have tested the device as good as possible, if you find any issues, please let me know in the comments!
Cheers,
Krito
I have updated the device (v1.4):
- Support CC messages: It is now possible to record and playback Pitchbend, Modwheel, Aftertouch, PolyPressure and other CC messages.
I have tested the device as good as possible, if you find any issues, please let me know in the comments!
Cheers,
Krito
Hi everyone,
I just uploaded a minor update on the device (v1.2.2):
- Undo Button: It let's you undo the current/latest recording layer of the loop. A new layer is created whenever you turn on record.
Enjoy!
Krito
I just uploaded a minor update on the device (v1.2.2):
- Undo Button: It let's you undo the current/latest recording layer of the loop. A new layer is created whenever you turn on record.
Enjoy!
Krito
Hi Everyone, thank you all for you feedback.
I released a minor update on this device, which mainly fixes the bug reported by mangomeat:
- The first note is not dropped anymore when starting to play a previously recorded sequence under normal circumstances. It may still being dropped when using lots of negative delay or the note is supposed to move into negative time for other reasons, e.g. recorded note is very late and lot of quantisation amount. (Thanks for reporting!)
- Playing with the grid settings is more stable and less likely to lose notes or play them twice
- Changed the default settings so that the device is ready to record and play
Enjoy!
I released a minor update on this device, which mainly fixes the bug reported by mangomeat:
- The first note is not dropped anymore when starting to play a previously recorded sequence under normal circumstances. It may still being dropped when using lots of negative delay or the note is supposed to move into negative time for other reasons, e.g. recorded note is very late and lot of quantisation amount. (Thanks for reporting!)
- Playing with the grid settings is more stable and less likely to lose notes or play them twice
- Changed the default settings so that the device is ready to record and play
Enjoy!
Thank you for all your feedback!
I have uploaded a new version:
- Quantisation now works on any time measure, not only 4/4.
- You can decide between beats and bars as unit for the loop length. This enables you to do polyrhythms for example with a length of 7 beats on a standard 4/4 measure.
- Added assignable multi-buttons as an alternative way to change the loop length.
Enjoy
Krito
I have uploaded a new version:
- Quantisation now works on any time measure, not only 4/4.
- You can decide between beats and bars as unit for the loop length. This enables you to do polyrhythms for example with a length of 7 beats on a standard 4/4 measure.
- Added assignable multi-buttons as an alternative way to change the loop length.
Enjoy
Krito
Hey everyone,
Thank you for all this feedback!
I have uploaded a new version to improve on those areas you commented:
1. As I get from the comment of @spacesoul, is that the meaning of the record, overdub and play buttons is ambiguous: Instead of a single state button as used by many loopers I followed the design of this device: https://maxforlive.com/library/device/1757/ck-midiloop
The downside is you can not use it with a single button, however it is a bit more clear what is happening when pressing a button. To make that more clear, buttons without a meaning are greyed out now: For example, "play" has no meaning when "record" is on and "overdub" is off. This is shown in the interface no more clearly.
2. There was a bug that some notes would be played in "record" mode without "overdub" but "play" turned on. I fixed this.
3. @dazeofresistance I clearly see the use of a single automation lane for "Sequencer Mode". I could not reasonably fit a "Sequencer Mode" button on the interface, but I added an automation parameter with that name. You can select it in the automation view as a device parameter. Here you can choose between "off", "Record", "Overdub" and "Play". These modes then change the values of the buttons, and also overwrite their automation if present.
I hope you all enjoy the update! Let me know :)
Krito
Thank you for all this feedback!
I have uploaded a new version to improve on those areas you commented:
1. As I get from the comment of @spacesoul, is that the meaning of the record, overdub and play buttons is ambiguous: Instead of a single state button as used by many loopers I followed the design of this device: https://maxforlive.com/library/device/1757/ck-midiloop
The downside is you can not use it with a single button, however it is a bit more clear what is happening when pressing a button. To make that more clear, buttons without a meaning are greyed out now: For example, "play" has no meaning when "record" is on and "overdub" is off. This is shown in the interface no more clearly.
2. There was a bug that some notes would be played in "record" mode without "overdub" but "play" turned on. I fixed this.
3. @dazeofresistance I clearly see the use of a single automation lane for "Sequencer Mode". I could not reasonably fit a "Sequencer Mode" button on the interface, but I added an automation parameter with that name. You can select it in the automation view as a device parameter. Here you can choose between "off", "Record", "Overdub" and "Play". These modes then change the values of the buttons, and also overwrite their automation if present.
I hope you all enjoy the update! Let me know :)
Krito