Release Candidate Firmware V3.0 RC5

[Tekagrey]

Thanks! This is very nice.
You can have any input as shader manipulation (including Midi). The whole command set is also integrated in the mappings.

Ah, yes.  I will implement the mappings.  Thanks for the response.  

One tip for people to watch out for:  I found myself inadvertently changing values of the shaders when I was adding things in the video sequencer while the sequence was running.  Mainly the Alpha variable. Not a bug or anything, but I found that I had to stop the sequence to avoid messing up settings.

The fastest way of testing out shader code iterations that I found was to use the video expander's USB input and a thumb drive.

One more question:  in the general changes you put (- fixed set CV16 note from mapping).  I tested this and it didn't seem to be working for me.  I had tried before the update, and the behavior seems to be the same.  I am trying to map a midi pitch to CV16 note, and the range seems to be wrong. If I change the mapping destination to any of the 6 normal CV outs, it functions like I would expect.  I can create a video later today.  But maybe I am missing something here as well.  Thanks again

[XORadmin]

Thanks! This is very nice.
You can have any input as shader manipulation (including Midi). The whole command set is also integrated in the mappings.

Ah, yes.  I will implement the mappings.  Thanks for the response.  

One tip for people to watch out for:  I found myself inadvertently changing values of the shaders when I was adding things in the video sequencer while the sequence was running.  Mainly the Alpha variable. Not a bug or anything, but I found that I had to stop the sequence to avoid messing up settings.

The fastest way of testing out shader code iterations that I found was to use the video expander's USB input and a thumb drive.

One more question:  in the general changes you put (- fixed set CV16 note from mapping).  I tested this and it didn't seem to be working for me.  I had tried before the update, and the behavior seems to be the same.  I am trying to map a midi pitch to CV16 note, and the range seems to be wrong. If I change the mapping destination to any of the 6 normal CV outs, it functions like I would expect.  I can create a video later today.  But maybe I am missing something here as well.  Thanks again

For the FX there is a function to not execute the FX where the cursor is to avoid exact that situation. Maybe it is a good idea  to add this here, too. Not for the release though.

I got to test the CV16 situation again before the release. I thought it was fine now.

[rubberband]

I can't believe I missed the original post about the V3 RC firmware.

I'll download it and test everything I use regularly for my current projects tonight and will report back.

[Tekagrey]

XORadmin


"For the FX there is a function to not execute the FX where the cursor is to avoid exact that situation. Maybe it is a good idea  to add this here, too. Not for the release though.

I got to test the CV16 situation again before the release. I thought it was fine now."

                                                                                                                                                                                                                      



Here is a recording of what happens when I change my note mapping to CV16:  https://youtu.be/U-mygth8P-c

Sending midi note info from Reason into nerdseq.  Mapping onto CV1 out functions well.  Changing the mapping to CV16-1 out gives a pitch sequence, but seemingly at a locked low octave?  Flipping the switch to the left results in a solid very low tone.

[XORadmin]

XORadmin


"For the FX there is a function to not execute the FX where the cursor is to avoid exact that situation. Maybe it is a good idea  to add this here, too. Not for the release though.

I got to test the CV16 situation again before the release. I thought it was fine now."

                                                                                                                                                                                                                      



Here is a recording of what happens when I change my note mapping to CV16:  https://youtu.be/U-mygth8P-c

Sending midi note info from Reason into nerdseq.  Mapping onto CV1 out functions well.  Changing the mapping to CV16-1 out gives a pitch sequence, but seemingly at a locked low octave?  Flipping the switch to the left results in a solid very low tone.

OK found that. It affected CV16 on NSA2. Will be fixed with the release.

[flel]

Not sure if this is a software bug (on RC2) or there is something wrong with my NerdSeq, but sending an F-1 to CV1 seems to send the wrong voltage leading to both note 16 and 17 to get triggered in sequence. Sending a C-2 and every note thereafter triggers note 23 (instead of 24) and the entire scale thereafter is off by 1 note. This is not a problem with CV2-4 (I didn't test other CV outputs). Video: https://youtu.be/kRs8JPMdkeI

[XORadmin]

Not sure if this is a software bug (on RC2) or there is something wrong with my NerdSeq, but sending an F-1 to CV1 seems to send the wrong voltage leading to both note 16 and 17 to get triggered in sequence. Sending a C-2 and every note thereafter triggers note 23 (instead of 24) and the entire scale thereafter is off by 1 note. This is not a problem with CV2-4 (I didn't test other CV outputs). Video: https://youtu.be/kRs8JPMdkeI

Not a software bug for sure. Probably issues:
Glide enabled
Calibration issue
Power issue
Scale for track 1 possibly enabled

Calibration seems to me the most likely thing. (Assuming the uTune is fine and calibrated well)

[flel]

Not sure if this is a software bug (on RC2) or there is something wrong with my NerdSeq, but sending an F-1 to CV1 seems to send the wrong voltage leading to both note 16 and 17 to get triggered in sequence. Sending a C-2 and every note thereafter triggers note 23 (instead of 24) and the entire scale thereafter is off by 1 note. This is not a problem with CV2-4 (I didn't test other CV outputs). Video: https://youtu.be/kRs8JPMdkeI

Not a software bug for sure. Probably issues:
Glide enabled
Calibration issue
Power issue
Scale for track 1 possibly enabled

Calibration seems to me the most likely thing. (Assuming the uTune is fine and calibrated well)

Thanks for your response and looking into it I think this is indeed a calibration issue. Since this is unrelated to the V3.0 firmware, I created a separate topic for this here: https://forum.xor.eu/showthread.php?tid=1988

Thank you!

[DriesG]

Not sure if this is V3.0RC2 related. 

Had a problem with CV16 outs 1 and 9 connected to NSA-3, Running cv16 fw 1.2. Outs 1 and 9 are unresponsive.

Switched to NSA-1 and all is working perfectly now.

[XORadmin]

Not sure if this is V3.0RC2 related. 

Had a problem with CV16 outs 1 and 9 connected to NSA-3, Running cv16 fw 1.2. Outs 1 and 9 are unresponsive.

Switched to NSA-1 and all is working perfectly now.

Can you repeat the issue and tell me how do you output exactly, like how did you set it up and do you output from the pattern or mapping, pitches, notes or lfo/envelope? Is it maybe possible that the switch on the front was just not exactly in position since it affected outputs 1 and 9 (did other outputs work well?)
Is it possible that you tried to output notes/pitches but envelopes/lfos have been active on these outputs but 'pure overrule' is not enabled?