sadly the freezing has returned.
I am fortunate enough to have two NDLR units in close proximity to one another and this allows me to jump the cables from one droid to the other. I have also tried to reseat midi cables and switch out the cables in hopes that the problem was more mundane....no dice.
Akai ME30P is used as a 4 in 8 out midi patchbay.
The Octatrack mk1 is the control sequencer.
Having 2 NDLRs and an octatrack should be a match made in heaven.
T1 and T5 are the CTRL tracks for NDLR A and NDLR B(due to the Spectralis having midi tracks reserved for 13-16, I have opt'd to use keyboard ctrl for track channel 1, and track channel 2 and 3 for the CTRL)
Octatrack's cc assign pg 1(T1, T5) is for cc 85,86,87,88...which provides the on/off switch for the pad, drone, motif1 and motif2
Octatrack's cc assign pg 2(T1, T5) is cc 26(chord degree),27(chord type),73(key/circle of 5th),74(mode/scale),59(humanize),72(tempo)
Octatrack pg 1(T2,T6) is where the Drone's cc CTRL attributes are stored.
cc 20(midi channel assignment), cc 32 drone position, cc 33 drone type, cc 34 drone trigger
Octatrack pg 2(T2,T6) is where the Pad's cc CTRL attributes are stored.
OT knob A - cc 19(midi channel), OT knob B- cc 28(pad position), OT knob C - cc 29(pad strum), OT knob D - cc 30(pad range),OT knob E - cc 63(pad velocity), OT knob F - cc31 (pad spread)
The NDLR receive transport and cc data from midi in B(as per manual/firmware requirements)....which goes to the midi patchbay and then to Spectralis A(NDLR#1) and C(NDLR#2)....from there the Midi thru port is used to send data to Spectralis B(NDLR#1) and D(NDLR#2)....and from there the Spectralis thru(B and D) ports are sending transport data to Roland R8(a and b).
When the NDLR freezes the Spectralis can get a hung note but other wise doesnt care...aside from having to reload the song data.
The Roland R8 sends a "ERROR: midi buffer Full" flag...which cannot be exited until the NDLR has been reinitialized.
Furthermore.
another bug found:
If I saved my settings to a different chord type...i.e. 7th...after saving it reverts to triad...this is happening after saving and rebooting.
and mind you I do not believe the Octatrack is sending an obnoxious amount of data to the NDLR...its not like I am sending ease-in and ease-out automation data or pitch bend data. I am just sending cc pulse data to coordinate the the NDLR as an arranger/conductor.
the good news?
2 NDLRs and an Octatrack have proved to be an ideal format for conducting/arranging harmonic motion theory. I have no problem whatsoever conceptualizing and implementing so many lost concepts in a rather organic and fluid manner. The problem with the Octatrack is that its monophonic sequencer lines are limited but with 2 NDLR's its a becomes a juggernaut. Also being able to CTRL the track assignment of the the sequencer's is also of value because for me I can automate the pad assignments and switch between a string and arpeggio and a horn stab...and that goes for each track...so it becomes pleasing in the same way braids and recursive behavior pleases our sensibilities.
also: regarding the freeze/full midi buffer : I would not so much as mind it lagging/caching and then catching back up versus a full on crash, freeze, please reboot me.
I am fortunate enough to have two NDLR units in close proximity to one another and this allows me to jump the cables from one droid to the other. I have also tried to reseat midi cables and switch out the cables in hopes that the problem was more mundane....no dice.
Akai ME30P is used as a 4 in 8 out midi patchbay.
The Octatrack mk1 is the control sequencer.
Having 2 NDLRs and an octatrack should be a match made in heaven.
T1 and T5 are the CTRL tracks for NDLR A and NDLR B(due to the Spectralis having midi tracks reserved for 13-16, I have opt'd to use keyboard ctrl for track channel 1, and track channel 2 and 3 for the CTRL)
Octatrack's cc assign pg 1(T1, T5) is for cc 85,86,87,88...which provides the on/off switch for the pad, drone, motif1 and motif2
Octatrack's cc assign pg 2(T1, T5) is cc 26(chord degree),27(chord type),73(key/circle of 5th),74(mode/scale),59(humanize),72(tempo)
Octatrack pg 1(T2,T6) is where the Drone's cc CTRL attributes are stored.
cc 20(midi channel assignment), cc 32 drone position, cc 33 drone type, cc 34 drone trigger
Octatrack pg 2(T2,T6) is where the Pad's cc CTRL attributes are stored.
OT knob A - cc 19(midi channel), OT knob B- cc 28(pad position), OT knob C - cc 29(pad strum), OT knob D - cc 30(pad range),OT knob E - cc 63(pad velocity), OT knob F - cc31 (pad spread)
The NDLR receive transport and cc data from midi in B(as per manual/firmware requirements)....which goes to the midi patchbay and then to Spectralis A(NDLR#1) and C(NDLR#2)....from there the Midi thru port is used to send data to Spectralis B(NDLR#1) and D(NDLR#2)....and from there the Spectralis thru(B and D) ports are sending transport data to Roland R8(a and b).
When the NDLR freezes the Spectralis can get a hung note but other wise doesnt care...aside from having to reload the song data.
The Roland R8 sends a "ERROR: midi buffer Full" flag...which cannot be exited until the NDLR has been reinitialized.
Furthermore.
another bug found:
If I saved my settings to a different chord type...i.e. 7th...after saving it reverts to triad...this is happening after saving and rebooting.
and mind you I do not believe the Octatrack is sending an obnoxious amount of data to the NDLR...its not like I am sending ease-in and ease-out automation data or pitch bend data. I am just sending cc pulse data to coordinate the the NDLR as an arranger/conductor.
the good news?
2 NDLRs and an Octatrack have proved to be an ideal format for conducting/arranging harmonic motion theory. I have no problem whatsoever conceptualizing and implementing so many lost concepts in a rather organic and fluid manner. The problem with the Octatrack is that its monophonic sequencer lines are limited but with 2 NDLR's its a becomes a juggernaut. Also being able to CTRL the track assignment of the the sequencer's is also of value because for me I can automate the pad assignments and switch between a string and arpeggio and a horn stab...and that goes for each track...so it becomes pleasing in the same way braids and recursive behavior pleases our sensibilities.
also: regarding the freeze/full midi buffer : I would not so much as mind it lagging/caching and then catching back up versus a full on crash, freeze, please reboot me.