Howdy, Stranger!

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

Sign In with Twitter

Livid Block with Max 6.1.x

edited February 2014 in Software Discussion

Hi,


I use my Livid Block with Max/MSP, using the Max+Livid package of javascripts and Max scripts to recognise and configure the Block. However, on versions of Max later than 6.0.8, the setup procedure no longer works. The Block is still recognised as a MIDI input, but the Max message window show that the scripts stops on a timeout after requesting the channel information. 

This happens even on the unadulterated Livid+Max.maxpat file that is downloadable form the Livid site.

See Max message window content below.

Many thanks for any help with this,

Tom




beginFindCTL: bang
js: trying port  0  of  3  :  AU DLS Synth 1 
js: **timeout  1 
js: moving on (timeout)  block Controls 
js: trying port  1  of  3  :  block Controls  should we check?  1  checking  0  should we check?  1  checking  1  should we check?  0  should we check?  1  checking  3  should we check?  1  checking  4  should we check?  1  checking  5  should we check?  1  checking  6  should we check?  1  checking  7  should we check?  1  checking  8  should we check?  1  checking  9  should we check?  1  checking  10 
js: end of sysex string  1  0 
js: end of sysex msg, moving on  1 
js: **timeout  2 
js: moving on (timeout)  from Max 1 
js: trying port  2  of  3  :  from Max 1 
js: **timeout  3 
js: moving on (timeout)  from Max 2 
js: trying port  3  of  3  :  from Max 2 
js: **timeout  4 
NO_LIVID_CTLR: 2
NoOhm-TryBlock: product 3
js: creating sysex LUTs 
js: searching for  block 
NoOhm-TryBlock: bang
js: trying port  0  of  3  :  AU DLS Synth 1 
js: **timeout  1 
js: moving on (timeout)  block Controls 
js: trying port  1  of  3  :  block Controls 
js: **timeout  2 
js: moving on (timeout)  from Max 1 
js: trying port  2  of  3  :  from Max 1  should we check?  1  checking  0  should we check?  1  checking  1  should we check?  0  should we check?  1  checking  3  should we check?  1  checking  4  should we check?  1  checking  5  should we check?  1  checking  6  should we check?  1  checking  7  should we check?  1  checking  8  should we check?  1  checking  9  should we check?  1  checking  10  should we check?  1  checking  11  should we check?  0  should we check?  0  should we check?  0  should we che
js: end of sysex string  1  1 
js: found  block  on ch  0  on port  from Max 1 
js: REQ count  0 
js: req'ing CH  1 
js: **timeout  3 

Comments

  • Looking again at the above, it appears that the script is identifying the Block successfully, but on the wrong port: it should have found it on port 'block Controls' but instead is sending sysex messages to 'from Max 1'.


    Any thoughts on how to sort this out?

    Thanks again

    Tom

  • That's really weird that it would find the block on "from Max 1". Do you have any other MIDI applications open?

  • No, nothing else open. I wonder if it's a problem with lots of other things happening on a load bang - I've now got it finding the Block on the right channel but it still hangs.


    js: trying port  0  of  3  :  AU DLS Synth 1 
    js: **timeout  1 
    js: moving on (timeout)  block Controls 
    js: trying port  1  of  3  :  block Controls  should we check?  1  checking  0  should we check?  1  checking  1  should we check?  0  should we check?  1  checking  3  should we check?  1  checking  4  should we check?  1  checking  5  should we check?  1  checking  6  should we check?  1  checking  7  should we check?  1  checking  8  should we check?  1  checking  9  should we check?  1  checking  10  should we check?  1  checking  11  should we check?  0  should we check?  0  should we check?  0  should we
    js: end of sysex string  1  1 
    js: found  block  on ch  0  on port  block Controls 
    js: REQ count  0 
    js: req'ing CH  1 
    js: **timeout  2 


    Could I be missing something obvious?
Sign In or Register to comment.