header image
 

Cntrlr Hardware Problem?

Home Forums Livid Scripts Cntrlr Hardware Problem?

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #895
    nannivr
    Member

    Hi,

    I have just bought a CNTRL:R and I am having major issues, the controller is constantly sending MIDI messages.

    I have installed the latest Live Script downloaded from: https://github.com/aumhaa/m4m8 and I am currently using macOS Mojave 10.14.16 and Live 10. Does Mojave supports this script?

    Here’s a link to download a video to easily help you understand the issue: https://wetransfer.com/downloads/b99eb5fa5363a10e26f696cbe0a560fa20200322143507/e6b2ea752130c047f1a1db0555247b6f20200322143527/a109f0

    – I have flipped all the dip-switches up and then back down.
    – Used different USB cables.
    – I reset the controller in the offline editor.
    – The expansion jacks are properly tightened.

    I have also ran a third party Midi testing package (https://www.snoize.com/MIDIMonitor/) as shown in the second part of the video, which shows all the MIDI CCs sent from the controller.

    I love the layout of this controller and I have been waiting a very long time to find one on the market. I thought this was speeding up the creative process but during these past 3 weeks it has actually blocked it completely…
    I really hope you can help me out because this is getting quite frustrating.

    #896
    amounra
    Participant

    Hey nannivr, welcome to the forum :)

    Unfortunately, I don’t have much in the way of good advice for you. I’ve had similar problems in the past, but it was always due to improper grounding of the expansion port. It sounds like you’ve done some good research, and taken the most common precautions to prevent the issue. The only other thing I might recommend is taking the controller apart and disconnecting the internal cable to the expansion jack, or trying to reseat or replace that cable? You might also try to update to the most current firmware for the CNTRLR, as I think some of those problems got ironed out over the life of the hardwares development. Hope that helps, unfortunately I’m more of a software guy than a hardware guy (I know enough just to be dangerous ;) )….

    a

    #897
    nannivr
    Member

    Hi Amounra,

    Thank you fur such a fast reply. I have updated the CNTRL to both of the firmwares available on Livid Wiki (CNTRL:R v123 and CNTRL:R v127) but still having the same issues..
    I don’t have much experience disassembling equipment but I’ll give it a try at this point…
    Do you have any suggestion on how to contact Livid Support ? I have tried on the Livid Forum without any luck yet.
    Thanks,
    Nanni

    #830
    amounra
    Participant

    This discussion was created from comments split from: Livid instruments Cntrl-R.

    #974
    rahmsc
    Member

    Hey Nannivr,

    Have you resolved this issue?

    I was suffering from this same issue for a while. The thing that seemed to fix it for me is playing with the switches on the back of the hardware unit (the red thing with white switches – potentially the expansion port?). I flicked them all down and have not had the issue again for a couple of weeks now.

    Are the MIDI messages being sent CC 33 and 34??

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.