Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Firmware V1.28 Test Version
#11
More infos on my issue, I have this outputs (bottom of the screen) for this different entries:

- 2-1 -> " on output CV16-NSA2->1"
- 2-2 -> " on output CV16-NSA2->2"
- 2-3 -> " on output CV16-NSA2->3"
- 2-4 -> " on output CV16-NSA2->4"
- 2-5 -> " on output CV16-NSA2->5"
- 2-6 -> " on output CV16-NSA2->6"
- 2-7 -> " on output CV16-NSA2->7"
- 2-8 -> " on output CV16-NSA2->8"
- 2-9 -> " on output CV16-NSA2->9"
- 2-10 -> "0 on output CV16-NSA2->10"
- 2-11 -> "1 on output CV16-NSA2->11"
- 2-12 -> "2 on output CV16-NSA2->12"
- 2-13 -> "3 on output CV16-NSA2->13"
- 2-14 -> "4 on output CV16-NSA2->14"
- 2-15 -> "5 on output CV16-NSA2->15"
- 2-16 -> "6 on output CV16-NSA2->16"


As you can see, the text is weird from `2-1` to `2-9` (look like a value is missing)
And it's the same for NSA 1, 3 and 4


I currently have this simple mapping:

```
MCC CH1 #1 > CV PTCH 2-1
```

I'm sure my cc is sent because I can see the value change in real-time on the selected line.

In addition I can confirm this mapping work:

```
MCC CH1 #1 > CV PTCH CV1
```

my "more cv 15" expander firmware version is 1.2
Reply
#12
enjoy your vacations Thomas, you're the best thanks a lot
Reply
#13
- I got a crash when I set the global tempo to zero.
- I can mute but I'm not able to unmute a track.
Reply
#14
Updated to Beta 2 (files in the first post updated)

- fixed load old project crash
- fixed CV16 mapping output
- fixed crash on global tempo 0 with mapping
- fixed mute with mapping
- fixed wrong octave with usb keyboard (video expander)


And now I will go on vacation!
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#15
OMG you are the best, thank you again Thomas! enjoy your vacations!
Reply
#16
Hey Thomas,

Thank you so much for sharing this. Very excited to see we can modulate the individual columns of the CV16 expander, it's a bit like christmas. One nice application I see would be to trigger one AR envelopes regarding other events. For that, after looking at available parameters in the mapping screen, I guess we could :
- assign track 7 to CV16
- keep destination CV1,2,3,4,5,6 in the track setup
- set a trigger for AR envelope 1 on each step of the first column, track 7
- set column 1 probability to 0%
- in the mapping setup, set : "CV IN 1 - > TRCK TRK7 PRB1"
- plug a gate sequencer to CV1

It doesn't work as expected however, it seems the CV has no impact on the column probability. We can see the value moving in the mapping screen.

I also tried with a second strategy:
- assign track 7 to CV16
- keep destination CV1,2,3,4,5,6 in the track setup
- set a trigger for AR envelope 1 on each step of the first column, track 7
- on each step, set FX 1 : PRC1 0064
- on each step, set FX 2 : PRC1 0000
- in the mapping setup, set : "CV IN 1 - > TRCK TRK7 PRB7"
- modulate the CV IN 1 between -5V and 5V

Not any impact neither.

To check if it was related to the CV input, I tried the mapping setup : "TRIG TR 1 - > TRCK TRK7 PRB1", and played with the gate on/off on track 1, no change. Am I missing something obvious, or is this part still in development?

Anyway, it's not an emergency, enjoy your holidays!
Reply
#17
(08-02-2023, 08:54 AM)st3rk Wrote: Hey Thomas,

Thank you so much for sharing this. Very excited to see we can modulate the individual columns of the CV16 expander, it's a bit like christmas. One nice application I see would be to trigger one AR envelopes regarding other events. For that, after looking at available parameters in the mapping screen, I guess we could :
- assign track 7 to CV16
- keep destination CV1,2,3,4,5,6 in the track setup
- set a trigger for AR envelope 1 on each step of the first column, track 7
- set column 1 probability to 0%
- in the mapping setup, set : "CV    IN 1    -    >    TRCK    TRK7    PRB1"
- plug a gate sequencer to CV1

It doesn't work as expected however, it seems the CV has no impact on the column probability. We can see the value moving in the mapping screen.

I also tried with a second strategy:
- assign track 7 to CV16
- keep destination CV1,2,3,4,5,6 in the track setup
- set a trigger for AR envelope 1 on each step of the first column, track 7
- on each step, set FX 1 : PRC1 0064
- on each step, set FX 2 : PRC1 0000
- in the mapping setup, set : "CV    IN 1    -    >    TRCK    TRK7    PRB7"
- modulate the CV IN 1 between -5V and 5V

Not any impact neither.

To check if it was related to the CV input, I tried the mapping setup :  "TRIG    TR 1    -    >    TRCK    TRK7    PRB1", and played with the gate on/off on track 1, no change. Am I missing something obvious, or is this part still in development?

Anyway, it's not an emergency, enjoy your holidays!

Maybe it is that tracks 7+8 got not all features for being a CV16 track.
You can always look into the current values screen if anything changes.

For the rest it sounds too complicated for my head right now and I got to do that myself to find out what you mean exactly.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#18
(08-02-2023, 09:04 AM)XORadmin Wrote:
(08-02-2023, 08:54 AM)st3rk Wrote: Hey Thomas,

Thank you so much for sharing this. Very excited to see we can modulate the individual columns of the CV16 expander, it's a bit like christmas. One nice application I see would be to trigger one AR envelopes regarding other events. For that, after looking at available parameters in the mapping screen, I guess we could :
- assign track 7 to CV16
- keep destination CV1,2,3,4,5,6 in the track setup
- set a trigger for AR envelope 1 on each step of the first column, track 7
- set column 1 probability to 0%
- in the mapping setup, set : "CV    IN 1    -    >    TRCK    TRK7    PRB1"
- plug a gate sequencer to CV1

It doesn't work as expected however, it seems the CV has no impact on the column probability. We can see the value moving in the mapping screen.

I also tried with a second strategy:
- assign track 7 to CV16
- keep destination CV1,2,3,4,5,6 in the track setup
- set a trigger for AR envelope 1 on each step of the first column, track 7
- on each step, set FX 1 : PRC1 0064
- on each step, set FX 2 : PRC1 0000
- in the mapping setup, set : "CV    IN 1    -    >    TRCK    TRK7    PRB7"
- modulate the CV IN 1 between -5V and 5V

Not any impact neither.

To check if it was related to the CV input, I tried the mapping setup :  "TRIG    TR 1    -    >    TRCK    TRK7    PRB1", and played with the gate on/off on track 1, no change. Am I missing something obvious, or is this part still in development?

Anyway, it's not an emergency, enjoy your holidays!

Maybe it is that tracks 7+8 got not all features for being a CV16 track.
You can always look into the current values screen if anything changes.

For the rest it sounds too complicated for my head right now and I got to do that myself to find out what you mean exactly.

By the way, the value you see is the result of the source. It doesn’t say what happens to the destination.
Also I think the trigger source might not set the full 100% but more of a logical one. Check if it does 0 - 4095 as values or else you would need to use a multiplication or one of the many other tricks to get to your 100%
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#19
Actually I tried on a standard modular track and it seems like a bug. Boolean parameters are working well, for example mute or solo track.

But :
- PRB1 to PRB8 : no effect in the patch screen of the track, even if the input modulation is clearly shown in the mapping menu (from HEX:0, Bool: 0 to HEX:FFF, Bool: 1, I'm using the second channel of Maths)
- PRB9, subtitled as "row probability" : the patch screen shows it affects CV probability of the target track instead of the row probability. The value is affected from 0 (empty green gauge) to 64 (max value and full green gauge)
- GLC : update the glide CV of the track, but with a 64 maximum value while it can be set to FFF in the patch screen
- GLCS : update the glide CV steps of the track, but with a C8 maximum value while it can be set to FFF in the patch screen
- GL M : update the glide modulate steps of the track, but with a 64 maximum value while it can be set to FFF in the patch screen
- GLMS : update the glide modulate steps of the track, but with a C8 maximum value while it can be set to FFF in the patch screen

Anyway, I was looking forward to test the firmware but you probably need a break, I guess we can all wait for your return Smile
Reply
#20
(08-02-2023, 10:34 AM)st3rk Wrote: Actually I tried on a standard modular track and it seems like a bug. Boolean parameters are working well, for example mute or solo track.

But :
- PRB1 to PRB8 : no effect in the patch screen of the track, even if the input modulation is clearly shown in the mapping menu (from HEX:0, Bool: 0 to HEX:FFF, Bool: 1, I'm using the second channel of Maths)
- PRB9, subtitled as "row probability" : the patch screen shows it affects CV probability of the target track instead of the row probability. The value is affected from 0 (empty green gauge) to 64 (max value and full green gauge)
- GLC : update the glide CV of the track, but with a 64 maximum value while it can be set to FFF in the patch screen
- GLCS : update the glide CV steps of the track, but with a C8 maximum value while it can be set to FFF in the patch screen
- GL M : update the glide modulate steps of the track, but with a 64 maximum value while it can be set to FFF in the patch screen
- GLMS : update the glide modulate steps of the track, but with a C8 maximum value while it can be set to FFF in the patch screen

Anyway, I was looking forward to test the firmware but you probably need a break, I guess we can all wait for your return Smile

It is a play-around version and there is much to play around already and yes surely not everything is working 100% correctly = not everything has been tested fully. There is also the chance that some functions only work for Modular tracks at the moment. Still it is totally worth to keep on playing with it. I got to check the probabilities though, I remember I had them working but also changed something here.

As for the glides, if you use a fader for example it doesn’t make any sense to use the too high values as your glide would be already too long with the smallest movement. I reduced that a bit to working values.

By the way, I will turn off notifications for this in the next days so I can relax a bit  Cool
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)