Forum Replies Created
thanks for this last post. It reflects my feelings about the arches quite well. After most of the baby bugs were fixed, I never started to really use because it feels so hard to me to understand and set up a working scenario for me. As the limitations of the 1″ OLED user interface are obvious, why don’t you build a small software that can generate and transfer settings via MIDI sysex? It would be much easier to hack in what you want with an quick and easy GUI than to always dive in deep into the programmers menu logic and where everything is exactly on a different place in the menu structure than where you are. My Arches rests here, at the far end of my table.
Any news about the next firmware. We are far from stable/perfect/whatever…
Oh yes! Visual feedback and clear indicators to see that it is working. So much of my clock testing was guesswork. A clear visual feedback like blinking LED for the clock, no matter of internal or received external would be helpful.
Still waiting for a new and improved firmware…
Okay, I tested the MIDI Clock situation in several setups, and the only thing that seems to work reliably is the CKIN out.
I tested it as a Clock out using USB to my Endorphines Shuttle Control which I did not get to work. Also I can not make it work using my Mac. In both cases I was able to receive note on/off via MIDI, but not the clock.
Then I tried to use my Prophet XL to send clock via MIDI DIN to the arches. Did not work.
Then I tried to use my Waldorf kb37 to send clock via MIDI DIN to the arches. Did not work.
Needless to say that the arches is pretty much useless in a larger setup unless it can be integrated as a master clock or as a slave using either MIDI DIN or MIDI USB.
When will be the next firmware release fixing at least all the clock issues? Without a working clock the upcoming arpeggiater functions will be worthless to me, so this is basic functionality that we need to be able to rely on.
I am totally ok when a product I found on Kickstarter delivers late. I am also ok when there are some software quirks and I do some beta testing for a manufacturer.
But I am not ok if the software lacks advertised features, is not even a beta but more an „alpha in progress“ and on top of it all, there are no frequent firmware updates and a non existent communication from side of the manufacturer.
If Kickstarter would allow it, i would like to go for a refund, but unfortunately we all now hang here with an unfinished product that does not meet our expectations.
What now, sound machines? It’s your turn to deliver.
It seems to be that the only thing working reliable is arches sending out the internal clock signal via CKIN.
The internal clock is not transmitted using the MIDI DIN output and not via bluetooth – as they say in the manual.
Clock in is not working at all for me. Not via CKIN and not via MIDI DIN. I have several devices I need to get in sync, like an Endorphin.es Shuttle Control, a MacBook Pro running Cubase, a Prophet XL and an Waldorf kb37. All this gear is talking nicely together as expected, but the arches is not responding to any of these devices.
Hey soundmachines, please get this working asap, your nice device is quite useless for me if it can not sync with other stuff.
I received my arches and it looks great so far. Anyway I am having a huge problem to integrate it in my setup. I connected a Prophet X synth via MIDI DIN cable to the MIDI IN of the arches. Setting the clock source to MIDI, MIDI CLK OUT to ON and MIDI I/F to DIN does not forward my clock information to the CKIN plug. When I switch to INTERNAL, the internal clock pulse immediately appear ar the clock plug. This is critical for me, as I need another device to be the MIDI master clock. Can you confirm this bug?