Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Twitter

CodeGriid Problems

edited February 2013 in Hardware

Hello everybody,

I just got my new code and wanted to combine it with my ipad. The problem is, that on the first time it worked just fine but then code did strange things with the midi-settings. I got just a frame of 4x4 clips in ableton, the rotaries are mapped with no order and sense and the five Buttons on the left side won't work. If i move the frame from griid, the code-frame moves with it, but the rest... In the midi-settings in abletons options i chose griid as controller with the griid-connector and the code with the codegriid-template that i downloaded here.

Do i have to connect the controllers in any special order? Are there some things to add in the python-files? A firmware Update?

Please help. Thanks a lot. Desperate Joshi

Tagged:

Comments

  • It should just work.  It might be helpful to see your log.txt file from Ableton's preferences....I can usually see from that any problems that exist in your setup.


    a

  • edited February 2013

    i can find two log.pyc files in the ableton-programm folder. i don´t know which one do you mean? the one in the _framework folder in the midi-remote-scripts? I am not able to post the text of the file. Do you have to see special lines?

  • ³ò
    0ªõOc           @   s*   d  d k  l  Z  d e f d „  ƒ  YZ d S(   iÿÿÿÿ(   t   DisplayDataSourcet   LogicalDisplaySegmentc           B   sb   e  Z d  Z d „  Z e e ƒ Z d „  Z d „  Z d „  Z d „  Z d „  Z     d „  Z
     d „  Z RS(       sF    Class representing a specific segment of a display on the controller c         C   ss  t  |  t t f ƒ p t ‚ | d j p t ‚ |  } t | ƒ | j oÿ | i d ƒ o | i d ƒ d j } t | i ƒ  ƒ | j o | o | d  } n t | ƒ | j o• x„ d
     D]| } | d j o d n d } xY t | ƒ | j oE | i | | ƒ d j o, | i | | ƒ } | |  | | d } qÚ Wq· W| |  } qIn t | ƒ | j  o | i     | ƒ } n | S(   sª    Brings the string to the given length by either removing characters or adding
            spaces. The algorithm is adopted from ede's old implementation for the Mackie.
        i    t   dBt   .iÿÿÿÿiþÿÿÿt    t   it   ot   ut   et   ai   (   R   R   R   R   R   R       (
       t
       isinstancet   strt   unicodet   AssertionErrort   lent   endswitht   findt   stript   rfindt   ljust(   t   originalt   lengtht   resulting_stringt   unit_dbt   chart   offsett   char_pos(    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyt
       adjust_string   s(    % c         C   s—   | d  j p t ‚ | d  j p t ‚ t | ƒ i d ƒ d j p t ‚ t | t ƒ p t ‚ t i |  ƒ | |  _ | |  _     d |  _
     d  |  _ d  S(   Nt   im_funci   (    (   t   NoneR
       t   dirt   countR
       t   intt   objectt   __init__t   _update_callbackt   _widtht   _position_identifiert   _data_source(   t   selft   widtht   update_callback(    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyR"   8   s    #
                c         C   sC   d  |  _ d  |  _ |  i d  j o |  i i d  ƒ d  |  _ n d  S(   N(   R   R#   R%   R&   t   set_update_callback(   R'   (    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyt
       disconnectH   s
                c         C   sƒ   | d  j p t ‚ t | t ƒ p t ‚ |  i d  j o |  i i d  ƒ n | |  _ |  i d  j o |  i i |  i ƒ n d  S(   N(   R   R
       R
       R    R&   R*   t   update(   R'   t   data_source(    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyt   set_data_sourceS   s        c         C   s8   | d  j p t ‚ t | t ƒ p t ‚ | |  _ d  S(   N(   R   R
       R
       t   tupleR%   (   R'   t   position_identifier(    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyt   set_position_identifierb   s    c         C   s   |  i  S(   N(   R%   (   R'   (    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyR0   k   s    c         C   s   |  i  ƒ  d  S(   N(   R#   (   R'   (    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyR,   q   s    c         C   sC   d |  i  } |  i d  j o" t i |  i i ƒ  |  i  ƒ } n | S(   NR   (   R$   R&   R   R   R   t   display_string(   R'   R   (    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyR2   w   s   
    (   t   __name__t
       __module__t   __doc__R   t   staticmethodR"   R+   R.   R1   R0   R,   R2   (    (    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pyR  
       s       !                            N(   R    R!   R   (    (    (    sb   h:\Jenkins\live\Projects\AppLive\Resources\MIDI Remote Scripts_Framework\LogicalDisplaySegment.pys   <module>   s  

  • Sorry, the file I'm looking for is described here:


  • Ok, now i found it. But the text in this file is too large to paste it in here. Do you need specific lines or is there a way to send you the whole file?

  • I sent you a message with my email address, you can send it there.

  • Looking at your log.txt file, everything looks fine.  I'm guessing that you need to reset the Code back to it's factory default settings via the Code editor application.  Have you tried that?

  • OK, I tried to do that, but the editor seems to have some problems and doesn´t find the controller. I have attached the text of the MaxRuntime window. I can´t understand what that is telling me. Something with Java Runtime which is installed...
    image

    MSP/ad: no ad folder
    ad_mme: No such object
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
        getenv        jasch        Jul 25 2006        ) all rights reserved
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    mxj: could not find Java 2 Runtime Environment.
    Error loading:
    (mxj) mxj_platform_init failed. Could not initialize the Java Runtime Environment.
    Please check your Java installation.  http://java.sun.com
    Unable to create JVM
    Jitter initialized
    text: can't find file dbug.txt
    js: OS and version  windows  259  608
    EXIST?: exists C:/Users/Joshi/AppData/Roaming/Livid

  • The editor shouldn't require JRE....I'm not sure what that is about.  You might try the web-based editor, though, it's a different thing altogether:


  • I tried but it didn't work. I have no idea what to do. Is there anything else i can try? Is it easier to program my own script in Python or with max/msp?

  • It's hard to say re: the choice between Max or Python.  Using max may be simpler if you don't have prior experience with either, but it has it's limitations.  


    In any case, it seems like there's a failure in your Max installation somewhere.  I looked at the errors in your first message again, Jasch Tools is the extension set that is requiring JRE.   It also appears that some other things are amiss.  It might be helpful to try reinstalling Max and see if that helps....no guarantees, but it couldn't hurt.  What OS version are you using?  Which Max version is installed?  Is Max working ok by itself?
  • I reinstalled Max but it didn´t work. But what did work was just loading another liveset... I am not shure how that was possible but it worked and i´m happy again. :-)

    Is it easy to get it to work together with touchable in the same way it does with griid? It has some features that i maybe want to use...

  • Griid is written with direct support for the Code script.  I doubt touchable would work in the same fashion unfortunately, since it doesn't contain the integration that Liine wrote for our Code controller.


    Anyway, glad you got things working :)

Sign In or Register to comment.