Hi...my NDLR x 2 FW 1.073 is crashing alot

[Jesse Johannesen]

So here's what I've done to try and replicate this issue:
Octatrack MIDI out -> MIDI A in NDLR.
OT MIDI track 1 set to send on MIDI Ch 15 (NDLR Ctrl Channel).
OT sends MIDI Clock.
Playing a pattern with notes spaced about 1/8th note apart for the most part, 16 steps long.
4 trigless trigs each with changes to CC#s 27, 29, 30, 31 with different values on each trig.
Set CC 73 (key) to be edited by hand.
Hit play.
NDLR plays fine for 15 min.
Change tempo to 220bpm
NDLR Plays fine for 1/2 hr. but I get a hanging note.
I will leave it playing over night and let you know if I get any crashes, but I think we have established that this is either something else in the chain, (and we really need to simplify things to troubleshoot this, like one midi cable out of OT and into NDLR simplify), or it's a faulty device, or your octatrack settings are doing something we don't understand that mine is not. I encourage you to try the one cable, one connection test, see if it fails, the simpler the test the better.

I am still confused about whether or not you can consistently get both devices to crash or if it's just one. Can you please clarify that for me? I remember you said once you came in and they were both crashed, but I want to know if you can switch units and they both behave the same. If it's just one unit, that would tell us something, so please test that out and let me know.

Jesse

hi Jesse, its Sunday and thank you for taking the time to get back to me.

both NDLRs will lock up if I use trig(red)...and over use trigless trigs(green)...by over use I mean parameter locking several attributes and sending lots of cc over.

so on using the most time accurate method of triggering the pad(which after testing is the note/on off method using the OT(keyboard where it says C4-->B4)...its crashes.

With the green trigs it is not as accurate...and I have to either plant additional triggers to turn the pad off then on and then plant other triggers to modulate other attributes...its just not as accurate....I wish I could say it was a decent work around. I am hoping and praying that using the midi in A port might be the issue(by using the red trigfers) but I don't see why.

I use the out from the Octatrack to the midi in B of the NDLR...(which I will switch to midi input A to see whether not that is the issue)

I have changed midi cables and when the pattern freezes a NDLR I can easily jump the cables to the second NDLR and the same issue happens.

Should I make a video and post this taking place so you can watch this as it happens?

---

Update: using 1 bar of 16th note regular red note on, note off triggers crashes NDLR #1 when parameter locking chord I—> VII on every other trig (ie the eighth notes) at 128 bpm going into midi input A.



NDLR #2 has 1 bar of 16th note regular red triggers with no parameter locks going into midi input A and this one does not crash

---

I will go back and attempt the same effect with the green trigless trig strategy momentarily.

so on using the most time accurate method of triggering the pad(which after testing is the note/on off method using the OT(keyboard where it says C4-->B4)...its crashes.

I don't understand what this means. What does triggering the pad mean? Also what does c4-->b4 mean here? I'm sorry if you explained that elsewhere. 

Video might be good, but I feel like now that I have it set up it might be easier to deal with via a zoom meeting if you have a way to do that. I'm available over the next couple of hours if you would like to do that. PM me your email and when you'll be available and I'll send you some meeting invite info. I'm west coast USA so try to give me either a time in that time zone, or a number of hours/minutes from when you send the message, ie: 2hrs from now, or 1 1/2 hrs. etc.

Jesse