(03-13-2021, 09:48 PM)Jesse Johannesen Wrote:

(03-13-2021, 10:58 AM)Ghostz_of_Moar Wrote: Update:

Technical error found in the manual pg. 57

For the Pad track.

midi cc 18 chooses the midi PORT usb, midi all, midi a or b, etc.
Midi cc 19 chooses the midi channel 1-16

In the manual it is currently vice versa.

Stability is improving but still no optimal settings for rock solid operation*.

I’m wondering if it’s data overflow that causes it to choke but it doesn’t make sense due to the comparative modernity of this sequencer to others.

By rock solid I mean performance ready for a festival or concert where 1000+ people paid 20 dollars or more and the sequencer isn’t seen as a weak link in the chain. My vision is to be able to use the octatrack in tandem with the NDLR units to sculpt out of groove based on harmonics and that happens from ground zero(no data) or have saved sets of triggers and p-locks.


Benefits? (Good news)

The octatrack and each NDLR are tempo independent and the NDLR’s can grab their tempo from the octatrack via midi cc or clock or run independent. The octatracks triggers allow for then pad’s to have a precise responsiveness which combines the play/pause with the position. Combined with the strum there are so,e great stabs, runs and glissandos happening with great nuance and not a whole lot of effort. I could use the mv8800 for this but the truth is the octatrack is more efficient and easier to manage space wise.

The midi select channel option is incredibly useful for my setup...because I can have 3 different voices loaded on the dsynth found on the Spectralis. Each having an octave switch, filter setting and an arpeggiator switch. By placing a triggerless parameter lock I can develop an array of extremely rhythmic harmonic tones based on switching the pad’s midi channel from 13-16. The only other way to achieve this would be to manually go to settings and switching it myself...but then I lose the functionality timing and refining the patch settings for each of the d-synths.

I am glad you're finding a little more stability, I am still not sure whether or not what we're dealing with here is a hardware issue, a firmware bug, or if we're dealing with a data bandwidth issue, however I am leaning more towards 1, or 2. I think we need to do a few things to figure that out:
1. we need to check the firmware and make sure you're using the newest available option, and in some cases we've seen instability caused by corrupt save states so I am going to suggest doing a factory reset after the update. (press and hold [shift + menu] while power cycling to enter boot menu then press the PAD play/pause button to reset the eeprom. You will lose save data, but it may be that is the cause of your issues so we have to check.
2. we need to simplify the setup and see if we can get both of the units to fail under the same conditions individually (I know you mentioned coming back to find them both frozen, but I would like to see it happen more than once on unit 2), so crank up that pad voice count and lets see how number 2 does under fire.
3 I still need to test the Octatrack and see if I can get mine to crash under similar conditions, so far I have been using MIDIox to send all the CCs you've listed and no amount of modulation one at a time is causing me any issues, besides an occasional hung note when adjusting polychain live. I should also say that the NDLR shouldn't have bandwidth problems for something like this as it can pass loads of data through without issue in my experience.

I may need to take a stab at it with the OT tomorrow as I have been working now all day and I need some rest.
Best of luck!
Jesse

(03-13-2021, 09:21 PM)Ghostz_of_Moar Wrote:

(03-13-2021, 12:11 PM)Dirk Offringa Wrote: Interesting read... keep it coming. I have a Octatrack too, but I use a Pyramid for midi duties, but never mind , I share your concerns , this thread is useful, thanks

Thanks I’m still hunting down glitches and I have only heard good things about the pyramid sequencer. I have other sequencers as well, but my decision on using the OT is mostly for the arranger/song view.

The key thing to appreciate about the NDLR sequencing strategy is the fact that almost everything is in midi cc’s...and with a bit of coordination and planning we can enjoy a certain degree of tactical improvisation by placing pinpoint parameter locks on the sequencer and then in the case of the OT turn the entire track off, switch to the NDLR , keep flowing and then re engage the octatrack in either song or pattern mode.

So far it’s best when I stay with 5-6 voices on the paid, btwa.

The midi cc solution could be better. It’s not a lot of fun needle nosing midi cc of 1-7 versus having 1-7 averaged across 0-127

---

(03-13-2021, 08:52 PM)Jesse Johannesen Wrote:

(03-12-2021, 10:03 AM)Dirk Offringa Wrote: I noticed that CC#26 changes the chord degree, but also the motif2 midiport. That's a weird implementation. Could that be related?

Dirk it this was an issue it must have been cleared up in a FW update a while back, I just tested it on my unit and it only changes the Chord Degree for me. I recommend taking a second to get updated to the most recent firmware. In fact come to think of it, that should have been my first recommendation for this whole thread. I'm still getting caught up with reading the thread, but Ghostz, if you haven't yet, I would suggest you check if your FW is up to date too.

Jesse

Hello, my NDLR arrived with 1.1.073 

Am I missing an update because I thought I was fully updated...

(03-14-2021, 07:11 AM)Jesse Johannesen Wrote:

(03-13-2021, 09:21 PM)Ghostz_of_Moar Wrote:

(03-13-2021, 12:11 PM)Dirk Offringa Wrote: Interesting read... keep it coming. I have a Octatrack too, but I use a Pyramid for midi duties, but never mind , I share your concerns , this thread is useful, thanks

Thanks I’m still hunting down glitches and I have only heard good things about the pyramid sequencer. I have other sequencers as well, but my decision on using the OT is mostly for the arranger/song view.

The key thing to appreciate about the NDLR sequencing strategy is the fact that almost everything is in midi cc’s...and with a bit of coordination and planning we can enjoy a certain degree of tactical improvisation by placing pinpoint parameter locks on the sequencer and then in the case of the OT turn the entire track off, switch to the NDLR , keep flowing and then re engage the octatrack in either song or pattern mode.

So far it’s best when I stay with 5-6 voices on the paid, btwa.

The midi cc solution could be better. It’s not a lot of fun needle nosing midi cc of 1-7 versus having 1-7 averaged across 0-127

---

(03-13-2021, 08:52 PM)Jesse Johannesen Wrote:

(03-12-2021, 10:03 AM)Dirk Offringa Wrote: I noticed that CC#26 changes the chord degree, but also the motif2 midiport. That's a weird implementation. Could that be related?

Dirk it this was an issue it must have been cleared up in a FW update a while back, I just tested it on my unit and it only changes the Chord Degree for me. I recommend taking a second to get updated to the most recent firmware. In fact come to think of it, that should have been my first recommendation for this whole thread. I'm still getting caught up with reading the thread, but Ghostz, if you haven't yet, I would suggest you check if your FW is up to date too.

Jesse

Hello, my NDLR arrived with 1.1.073 

Am I missing an update because I thought I was fully updated...

Nope, that's the current version, scratch that.

I see what you mean about needle nosing, but changing that now would be complicated (people have put time into creating editors etc). I don't want to try and sell you a solution, but that is one of the things that the MRCC router does, it can scale incoming CCs to a smaller (or larger) range, and map them from one to the other actually too.

I'll get back to you later with my results of my OctaTest.
Jesse

(03-15-2021, 05:56 AM)Ghostz_of_Moar Wrote: Update:

On the Octatrack I experienced more stability by using trigless trigs(the green ones) when I used standard midi note on/off triggers it would invariably freeze up the NDLR, so instead I went with CC automation and avoided the note on off.

there is a bit of lag when sending chord and degree changes. its just not as tight as I would expect out of a normal sequencer. So I can parameter lock a chord type change, but then to change the other chord or pad attributes, I find myself putting those triggers a step before the chord type trigger as a work around. I find this is doable but not ideal...mainly because the sequencers timeline is a bit more cluttered...versus having a neat set of macro cc's sent to automate the NDLR.

this strategy has also resulted in less hung notes on the Spectralis D-synth. so far.

So currently to get cc automation right is to place the not just a midi cc trig to set the desired change in attribute....but also placing it prior to the Chord type and also setting another midi cc trig to return the attribute to its prior setting.

fingers crossed to have a no crash day as I automate the spread, range, and strum attributes.

(03-15-2021, 07:27 PM)Jesse Johannesen Wrote:

(03-15-2021, 05:56 AM)Ghostz_of_Moar Wrote: Update:

On the Octatrack I experienced more stability by using trigless trigs(the green ones) when I used standard midi note on/off triggers it would invariably freeze up the NDLR, so instead I went with CC automation and avoided the note on off.

there is a bit of lag when sending chord and degree changes. its just not as tight as I would expect out of a normal sequencer. So I can parameter lock a chord type change, but then to change the other chord or pad attributes, I find myself putting those triggers a step before the chord type trigger as a work around. I find this is doable but not ideal...mainly because the sequencers timeline is a bit more cluttered...versus having a neat set of macro cc's sent to automate the NDLR.

this strategy has also resulted in less hung notes on the Spectralis D-synth. so far.

So currently to get cc automation right is to place the not just a midi cc trig to set the desired change in attribute....but also placing it prior to the Chord type and also setting another midi cc trig to return the attribute to its prior setting.

fingers crossed to have a no crash day as I automate the spread, range, and strum attributes.

This makes sense, as that is exactly how those changes take place. If you press a chord type button, it waits to execute the change until the next Chord degree is selected. That can be the same chord degree or a different chord degree. You will see the chord shape change appear in blue, then turn white when the chord degree is selected.
I'm just starting to set up my octatrack to test this, would you care to give me some of the parameters of your project so that I can try to get the same setup as much as possible?
Especially interested in making it crash, so not the stuff that's working well please

Jesse