I would like to be able to control the local note value of the DualChord track CV output (which normally would remain unused). 
Trigger16 tracks already have this, through the NOTE parameter. 
Could this be implemented for the DualChord track type too?

Hi,

A cut sentence from page 68 from the manual: "Destinations for the Drummatrix can be: (...), Midi Notes, (...)".

Is this DrumMatrix (from the TR16) only for the Multi IO expander Midi or is this also possible for the 2HP Midi expander?

If also possible for the 2HP expander, how do I set this up? If no, any plans for it in the future? (I saw a two year old post in which this was being discussed...)

Cheers, Ian

I'm having an issue with recording the midi input for audio channel 8 from an external keyboard, I have no problem recording on audio channel 7, I use the latest firmware 2.02 and the multi io for the external keyboard, every channel records the midi ok, when I want to record on channel 8 no matter what I try, it does not record the note off at all or maybe sometimes at a weird moment. This also happens in other projects. Audio channel 7 works fine with the midi.

So in the setup settings I have setup:
midi channel 7 to record on audio channel 7 ---> it works like expected 
midi channel 8 to record on audio channel 8 ----> only midi notes on
every other midi channel to audio channel 8 same problem

Attached my project, but it happens in a new project as well.

Attached Files

  TEMP02.NRD (Size: 547,29 KB / Downloads: 0)

This isn't really a bug, more of an unexpected behaviour with the Automator LFOs that I couldn't find documented in the manual. I thought I'd post it here along with a workaround in case anyone else is running into the same issue.

1. In the Automator screen, assign an LFO to a CV output
2. In the Automator screen the LFO will oscillate around a zero-point (as expected). However, the CV output values don't match what's on the screen. Only the positive half of the waveform will appear at the CV output, and the LFO output voltage will be centered on the lowest voltage of the hardware output (-5v or 0v, depending on the hardware switch) rather than starting in the middle (0V or +5V as expected)
3. Applying positive offset in the Automator screen will only offset up to 5V from this starting position, which is less than the expected 10V.

There is a workaround to get to the expected behaviour: manually set the assigned CV/MOD output to a value of 800, either in the Patch screen, with a patch in a pattern, or through the Mapping screen. This will output the full range of the LFO, centred on either 0 or +5v (depending on the hardware switch). This workaround removes the need to add offset in the Automator screen and makes the full +10v range Automator LFO offset available at the CV output.


An interesting correlation—when the assigned modulator is started, the manually-set MOD or CV amount will be re-mapped in the Patch screen to match the calibration for the nearest voltage assigned to that output.

This behaviour and workaround don't affect the value of the LFO in the mapping screen. It also doesn't matter which physical output is used (CV or MOD output) nor the position of the hardware offset switches (+/- 5V or +10V) except to offset the starting voltage.

A small bug with this workaround—the manually assigned CV/MOD amount will occasionally reset to the calibration amount for a different voltage (often ~1V in my case). This happens even in a blank project, with no other assignments to the MOD or CV outputs. However, I haven't been able to reliably reproduce this bug. I'll keep trying and put up a bug report if I can document when it happens.

I’d like to experiment with live recording voltages into cv16 tracks with midi controller pots and attenuated offsets into the input channels, but cannot figure out how to set this up in the settings. it was hinted in the manual that this was possible but couldn’t find a clear explanation in regards to cv 16 track types. if it’s something in the mapping menu i would be grateful for mapping examples for the use case of a midi controller cc ->cv16 pitch and live input channel voltages-> cv16 pitch

This release candidate contains some minor updates/fixes as well as some Dualchord additions:

- Added Dualchord Presets. They are now 4 possible presets per project (Don't ask for more, there is no memory for that). For earlier Dualchord projects the current NSA channel will be automatically assigned to the preset (e.g. if the Dualchord was set to NSA channel 3 then the loaded settings will be stored in preset 3.)
- Preset can be set from the track setup screen (via the menu row or SHIFT+OK+LEFT/RIGHT anywhere in the dualchord track setup), via FX and the mappings
- Added Dualchord Preset Import/Export to/from the SD Card
- Added missing Dualchord LFO FX functions. Added DC Part Mode to the FX (SET FX)
- Fixed wrong clock settings from the Track Setup menu (https://forum.xor.eu/showthread.php?tid=1927)
- Fixed beauty issue with Midi Program Change Mapping input

As usual, this is a release candidate. It is not intended for productive use as I can't guarantee that they are no unexpected side effects. Also saved projects will guaranteed work for the release version but are not backwards compatible to 2.02A or earlier. So be aware to backup your projects / SD Card first!!! (Which is something you should do anyways from time to time)
But with installing it and trying it out/testing you help getting the version ready for stable use. I aim for a release within 1-2 weeks.

Please report any issues with that only in this thread here as this is not a stable version. 

Download the release candidate below, follow the firmware update rules and if you get stuck there and it doesn't work, read the many threads about it and it will be fine!! Updating the NerdSEQ always works!

Update: I deleted the release candidate files and closed this release candidate / skipped the stable update for this because of too little interrest.

NerdSEQ 2.02A

If I set a track's clock to "MAPPING" and then trigger it from the Mapping Screen (using "TICK" pattern ticks) all works as expected. 

However, if I then set the track clock to any multiple (*2, *4 etc.), the track will be reset to normal (no multiple) whenever playback is started. 

This only occurs for track clock multipliers, and only after setting the track clock to MAPPING. Divisions work as expected.

Hi, maybe someone has an idea what’s going wrong here. In a project that I’m working on suddenly the samples on track 7 just produce a click sound. I can adjust the volume and the pitch of the click sound. So it seems like an envelope problem or maybe not but I can hear the pitch change and the volume also when I adjust this in the tracker. I have set both channel 7 and 8 as my audio channels. I don’t have any envelopes active on the tracks. When I open another project track 7 and 8 work like they should. 

I can’t find what the problem is. I have the latest firmware installed. Channel 8 works fine in the project that has this problem.

It would be great to be able to save all the relevant current Dualchord settings into a Patch. 

This would make for a very quick and easy way to create Dualchord "presets"

I realise you could create a patch and then make the changes from within the patch directly, but the UI isn't as intuitive to use as the Settings UI and it is missing things like Part 1 Mode.

Greetings, Nerds!

TL;DR - Two questions:

1. Is there a way to set up NerdSEQ's pattern interface (the UI screen) to display precise [summed] voltage values leaving the CV or MOD output jacks?
   
2. Can I set a specific Track to be Microtonal? I do see SCALE in Track Setup, but still seem to be locked to CV values of C1, C#1, etc.
   

• Em needs 1.00v
  
• Cmaj needs 1.05v (but C#1 is 1.083v)
  
• Dm needs 1.10v (but D1 is 1.17v) so this sequence step is skipped
  
• B needs 1.15v (but D# is 1.25v)
  

1. Can I change NerdSEQs pattern (UI) display to show CV = 1.17v instead of C#1?
   
2. How can I convince NerdSEQ CV or MOD output to be "precise voltage" instead of locked to C1, C#1, D1, etc?