[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-users] MKtl description issue



I talked too soon

It works in Windows.The description can be downloaded here:
http://gilfuser.net/akai-mpkmini2.desc.scd
But it doesn't work in Linux. If the device is disconnected from the computer it works as a virtual device though.

The error I get in Linux is:
ERROR: Message 'connect' not understood.
RECEIVER:
Instance of MIDIOut { (0x7f24d41ddcf8, gc=58, fmt=00, flg=00, set=02)
instance variables [3]
port : Integer 0
uid : Integer 0
latency : Float 0.200000 9999999A 3FC99999
}
ARGS:
nil
PATH: /home/gil/.local/share/SuperCollider/downloaded-quarks/Modality-toolkit/MKtl_utils.scd
CALL STACK:
DoesNotUnderstandError:reportError 0xc21b878
arg this = <instance of DoesNotUnderstandError>
Nil:handleError 0xcd919c8
arg this = nil
arg error = <instance of DoesNotUnderstandError>
Thread:handleError 0x5d78488
arg this = <instance of Thread>
arg error = <instance of DoesNotUnderstandError>
Object:throw 0xd4a2d98
arg this = <instance of DoesNotUnderstandError>
Object:doesNotUnderstand 0xcce88f8
arg this = <instance of MIDIOut>
arg selector = 'connect'
arg args = [*1]
MIDIMKtlDevice:initMIDIMKtl 0xbd658c8
arg this = <instance of MIDIMKtlDevice>
arg argName = 'midi_3_mpkmini2'
arg argSource = <instance of MIDIEndPoint>
arg argDestination = <instance of MIDIEndPoint>
Meta_MIDIMKtlDevice:new 0xcc6b528
arg this = <instance of Meta_MIDIMKtlDevice>
arg name = 'midi_3_mpkmini2'
arg idInfo = "MPKmini2"
arg parentMKtl = <instance of MKtl>
arg multiIndex = nil
var lookupInfo = <instance of Event>
var foundInfo = <instance of Event>
var foundSources = <instance of MIDIEndPoint>
var foundDestinations = <instance of MIDIEndPoint>
var newDev = <instance of MIDIMKtlDevice>
MKtl:openDevice 0xde99738
arg this = <instance of MKtl>
arg lookAgain = false
arg multiIndex = nil
var protocol = 'midi'
MKtl:finishInit 0xc866d58
arg this = <instance of MKtl>
arg lookForNew = false
arg multiIndex = nil
MKtl:init 0xdce99b8
arg this = <instance of MKtl>
arg argDesc = <instance of MKtlDesc>
arg argLookupName = nil
arg argLookupInfo = nil
arg lookForNew = false
arg multiIndex = nil
var specsFromDesc = nil
< closed FunctionDef > (no arguments or variables)
Interpreter:interpretPrintCmdLine 0x7f24d40c7e78
arg this = <instance of Interpreter>
var res = nil
var func = <instance of Function>
var code = "n = MKtl('mpk2test', "akai-m..."
var doc = nil
var ideClass = <instance of Meta_ScIDE>
Process:interpretPrintCmdLine 0x6f019c8
arg this = <instance of Main>
^^ The preceding error dump is for ERROR: Message 'connect' not understood.
RECEIVER: a MIDIOut

adc <alberto.decampo@xxxxxxxxx> schrieb am Sa., 12. Dez. 2015 um 12:48 Uhr:
oi gil,

if you send me the APC mini 2 desc file, I can commit it to modality, so modality officially supports this device :-)

Also, it should usually not be necessary to edit the cache file text -
One can always update the cache file by doing:
MKtlDesc.writeCache;

I thought it does that automagically, but it seems not, so I will look into that.

best adc


> On 11/12/2015, at 18:38 , Gil Fuser <gilfuser@xxxxxxxxx> wrote:
>
> Oi Alberto, tudo bem?
>
> Problem solved!
> But I needed to do a (maybe dirty) trick.
> In the MKtlDescriptions folder there is file called _allDescs.cache. I putted the description I did there manually. That's all. It worked. Cool.
>
> Thank you all
>
> Schönes Wochenende,
> Gil
>
> adc <alberto.decampo@xxxxxxxxx> schrieb am Fr., 11. Dez. 2015 um 14:12 Uhr:
> oi gil,
>
> can you send the APC mini 2 desc file ?
> then we can check whether it works at least for making a virtual device.
>
> best a
>
> > On 11/12/2015, at 12:36 , Miguel Negrão <miguel.negrao-lists@xxxxxxxxxxxxxxxxx> wrote:
> >
> > On 11-12-2015 11:07, Gil Fuser wrote:
> >> Hi Miguel.
> >> I forgot to say. I did it.
> >> I used the MIDIExplore for that.
> >>
> >
> > In linux, what does MKtl.find(\midi) post ?
> >
> > You should explicitelly pass the description name as the second argument:
> >
> >  k = MKtl('mynano2', "korg-nanokontrol2");
> >
> > From the documentation:
> > -------------
> > The first step is to discover which devices are available for use
> >
> > MKtl.find;
> >
> > This will find all currently available devices, info on them, and example lines of code that can generate an MKtl for the device.
> >
> > Each line is MKtl('a_shortname', "a_desc_filename").
> >
> > Copy the MKtl(...)-line of the device you want to use from the post window to your document and assign it to a variable.
> > -------------
> > Best,
> > Miguel
> >
> > _______________________________________________
> > sc-users mailing list
> >
> > info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
> > archive: https://listarc.bham.ac.uk/marchives/sc-users/
> > search: https://listarc.bham.ac.uk/lists/sc-users/search/
>
>
> _______________________________________________
> sc-users mailing list
>
> info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
> archive: https://listarc.bham.ac.uk/marchives/sc-users/
> search: https://listarc.bham.ac.uk/lists/sc-users/search/


_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/