altmag

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 60 total)
  • Author
    Posts
  • in reply to: Feature Requests/observations #16530

    altmag
    Participant

    Yes – many of us feel justifiably upset. There are issues with Arches which need to be fixed and we haven’t seen any responses for several months now.

    in reply to: Issues reporting #14838

    altmag
    Participant

    Yes – I’ve been experiencing those same instability problems with ‘free mode’ light strips, e.g. they won’t record. They can only be fixed with a power re-cycle.

    in reply to: Feature Requests/observations #13004

    altmag
    Participant

    Your’e right of course about the HOLD statuses – my mistake.

    Really looking forward to the web editor.

    Mick

    in reply to: Feature Requests/observations #12934

    altmag
    Participant

    I bought arches for all of its valuable features, but I’m using it mainly as a controller for my synths. What I really need, for all sliders and buttons which are programmed as FREE, i.e. not part of a keyboard, are these functions:

    1 an arches preset should save the current position/value of all sliders and the status of all HOLD buttons.

    2. when such a preset is loaded, those values/statuses should be recalled, but not immediately sent to the MIDI Out port.

    3. a button which sends all MIDI CC values for all FREE slider/buttons from the MIDI out port.

    Is this possible? It would really increase the functionality of arches as a MIDI controller.

    Thanks, Mick

    in reply to: Feature Requests/observations #12781

    altmag
    Participant

    (current firmware 1.0.10)

    The arpeggiator is still difficult to program. You have tov hold down the central Hold button while holding the notes you want to arpeggiate. However, there’s no way to edit the arpeggiator. Each time you want to make a change, you have to hold down all the notes and start again.

    Why use the central Hold button to record arpeggiation, when you could use the individual Hold buttons for each note? If you did that, we would be able to select and de-select notes independently while the arpeggiator is running.

    Is it possible to program the Play LED to flash (in time with the current internal or external tempo) whenever anything (Arp, Trig Arp or Arpeg) is playing? It would be a great help when working on sequences, etc.

    Whenever you look at a screen for e.g. Sequence or Arpeggiator, it would be really useful to be able to see the current values next to each item, e.g.

    ENABLED Y
    TYPE UP
    CLOCK DIV 1
    GATE LENGTH 16%
    etc.

    When you hit Load or Save, it would be good to see the currently loaded preset number.

    in reply to: Issues reporting #12779

    altmag
    Participant

    Hi Davide – I’ve checked a few items with firmware 1.0.10

    • Tempo, Sequencer and Trigger Sequencer status and data are now saved with each preset – excellent!

    • The problem with the XY pad Hold LEDs coming on randomly seems to have been fixed.

    All good…BUT – Arpeggiator status and data is NOT saved with the presets.

    Firmware 1.0.10 brings some improvements (thanks!) but there’s still a ways to go…

    in reply to: Issues reporting #12774

    altmag
    Participant

    Thanks Davide – if I copy just the archesim.hex file to my micro SD card, it doesn’t load and arches operates under 1.0.7.

    But, if I also copy the autoprog.bcm file, (the one which gives us the crazy lightshow, which I love, by the way) then the firmware loads and I now have 1.0.10.

    Cheers, Mick

    in reply to: Issues reporting #12757

    altmag
    Participant

    Hi Davide – when I unzip the archesim1.0.10.hex file, it gives me the 1.0.7 version of the firmware.

    in reply to: Issues reporting #12712

    altmag
    Participant

    XYZ pad Hold buttons:

    I’ve noticed that, whilst experimenting and re-configuring my presets, the 2 Hold buttons associated with the XYZ pads will occasionally enable themselves – quite randomly, and not while I’m operating other controls.

    in reply to: Issues reporting #12707

    altmag
    Participant

    Selecting Expression CV output for a Keyboard:

    This is unfortunately disabled – if you hit the aux button in order to select an output, it declares that it’s EMPTY.

    So – you have to disable the keyboard group (set the FUNCTION to FREE) then select the aux output to your desired position.

    Then re-select FUNCTION to KB. The aux output selection will be retained.

    This is hardly a slick operation. The aux output parameter should be available whilst KB is selected in the FUNCTION menu.

    I think this qualifies as a bug.

    in reply to: Issues reporting #12705

    altmag
    Participant

    Trigger sequencers:

    The parameters of Trig Seqs 3 4 and 5 are saved with the preset, but not Trig Seqs 1 & 2

    in reply to: Issues reporting #12700

    altmag
    Participant

    My comment above also applies to the Hold function, i.e. some lightstrips hold buttons don’t work occasionally. This is fixed with a power cycle.

    in reply to: Issues reporting #12698

    altmag
    Participant

    I’m finding that a few lightstrips are refusing to record. This is fixed by power-cycling arches.

    in reply to: Feature Requests/observations #12696

    altmag
    Participant

    My comment above also applies to the Hold function, i.e. some lightstrips hold buttons don’t work occasionally. This is fixed with a power cycle.

    (this comment copied to Issues Reporting)

    • This reply was modified 6 months ago by  altmag.
    in reply to: Feature Requests/observations #12689

    altmag
    Participant

    I’m finding that a few lightstrips are refusing to record. This is fixed by power-cycling arches.

Viewing 15 posts - 1 through 15 (of 60 total)