Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • August 13, 2012 at 7:14 pm in reply to: 2880 with MC-505 midi clock error #118000
    JVonD
    Member
    Quote:
    How you configure your esx-1 so that it works?

    Bummer to hear that. I never had any issues with the Korg products when midi syncing. For me I connect the midi from the Korg’s “out” to the 2880’s “in”, set the Korg on “int” for the clock, click the “ext clock” on the 2880, and it works perfect every time.
    The only other time I’ve had issues with the system is when playing outdoor venues and there are voltage issues (not enough power).
    Good luck! ~J

    July 25, 2012 at 7:50 pm in reply to: 2880 with MC-505 midi clock error #117924
    JVonD
    Member

    Hey Flick. Thanks for checking into it. Looks like you found my issue first hand.
    I’ve been testing my MC-505 midi clocks with my Korgs by syncing the delays to BPM. If the clock stutters then the delays will go off time. I haven’t noticed it when slaving off the MC-505.
    At least I’m not the only one. ;)
    Hope your able to find a solution. Thanks again guys! ~J

    July 25, 2012 at 3:05 pm in reply to: 2880 with MC-505 midi clock error #117919
    JVonD
    Member
    Quote:
    Have you considered using something else as the master clock for both devices?

    I have been using my system slaving off the Korg ESX1 but it makes me have to reset the delay on the MC-505 manually every time I change tempo during live performance. Plus running it off the Korg puts extra midi-merge boxes in the line and thus screwing up the beat clock by the time it gets to my Microkorg at the end of the midi routing.

    BTW – I don’t recommend Midi Solutions midi-merge boxes for use with beat clocks. They will screw it up.

    BEATOMATICIIITURBO_small.jpg

    July 25, 2012 at 2:56 pm in reply to: 2880 with MC-505 midi clock error #117918
    JVonD
    Member

    I changed the midi channel on the 2880 and there’s no difference. It still gets jacked from the MC-505.
    I was able to rewire Reason with ProTools and drive the 2880. Ran good.
    If you have any other suggestions please keep them coming.
    Thanks! ~J

    At this point…
    -Every device (Korg ESX1, Microkorg, Computer DAW) slaves good from the MC-505 clock except the 2880.
    -The 2880 slaves good with every device (Korg ESX1, Computer DAW) except for the MC-505.

    Maybe I could do a “midi over ip” and EHX can analyze the MC-505 signal..?

    July 24, 2012 at 10:09 pm in reply to: 2880 with MC-505 midi clock error #117911
    JVonD
    Member

    Slaving my Korg ESX1 from the MC-505 is good.
    I pretty much turned off all transmit messages beside a few synth channels on 5,6,7.
    Put it on a thru to the 2880. It’ll run the Korg good but the 2880 doesn’t like it. Same with direct to the 2880.
    Also just got finished running a test going from my MC-505 to my Reason computer DAW sequencer and that sync was good too.
    Seems like I tried everything you are mentioning.

    Hoping for maybe word on an update for the 2880 maybe..?
    Is EHX coming out with a new looper? How come it’s discontinued?
    Thanks! ~J
    I’ve always contacted Roland’s LosAngeles service center directly and never had a problem.

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)