Re: [Jack-Devel] Odp: Re: Re: Odp: Jack1 && jack_get_uuid_for_client_name
I guess this is need for jack2 as well?
Thanks.
Stéphane
Le 28 janv. 2013 à 01:49, Pawel a écrit :
> Hi,
>
> I made this patch (for master branch https://github.com/jackaudio/jack1). Please apply ASAP.
>
> I have also improved version of two jack tools:
> * jack_lsp
> - add option "-u" for show current clients session uuid's. This code need mentioned patch (because of lack of one API call in current release). For me it is really useful for debug purposes.
>
> * jack_connect
> - fix: jack_get_client_name_by_uuid must be freed by caller (not mentioned by doc, but code return strdup value)
>
> - "-w" option for wait (with timeout) for ports. Because of bug in jack1 which return "inactive ports", if ports are available it try connect hard (i.e. in loop) during this time.
>
> - fix: when ports are already connected then it return success.
>
> Regards
> Pawel
>
> Dnia Czwartek, 17 Stycznia 2013 16:27 Pawel <[hidden]> napisał(a)
>> It is documented here:
>> http://jackaudio.org/files/docs/html/group__JackSessionManagerAPI.html
>>
>> Once again , I not trying to push on you to resolve this problem by own hands. I just expected short (almost binary) answer. If you confirm that this is bug, then I can try provide patch (or maybe someone else give helping hand).
>> If there is no answer then can be mean everything including "don't want such questions" or has been overlooked.
>>
>> In previous message I even offer that I can try support this area in Jack1, well ?
>> Maybe you just give me access to repository. I can also improve Jack tools and try fix "inactive ports" issue - OFC when will be clear how this should work.
>>
>> It's funny because I just need this API for improved jack_lsp which works good with Jack2 and it doesn't in Jack1.
>>
>> Pawel
>>
>> Dnia Czwartek, 17 Stycznia 2013 14:39 Paul Davis <[hidden]> napisał(a)
>>>
>>> On Thu, Jan 17, 2013 at 8:26 AM, Pawel <[hidden]> wrote:
>>>> Thanks for clearing it, but will be much simpler if you can just add this policy to documentation (JackSession is supported only by Torben) then you both with Stephane will not be SPAM-ed by this questions.
>>> that isn't in the docs because it isn't true.
>>>
>>>> If you are main developer of this app then you at least should know there is known bug and (what is worst) it is not compatible with own documentation (lack of one API call).
>>> main developer of what app? jack1? sure .. do you know how many bugs there are in ardour? how do you think i should prioritize my time?
>>>
>>> furthermore, the API for JackSession is documented here:
>>>
>>> http://jackaudio.org/files/docs/html/group__SessionClientFunctions.html
>>>
>>> you will note that it does not include jack_get_uuid_for_client_name().
>>>
>>>> I respect your time and if Torben have no time for this , it's OK and I respect his time too. But please respect my time also , in particular that I want to help. I can try by providing patch or maybe even share maintaining JackSession with Torben (and his bless). As you know I have my own history with sustaining your work (fst case).
>>>>
>>>> For now you just redirect questions to Torben who just not answering ... which actually mean my bug reports and questions are rejected. I lose my time for understand your policy, waiting for answers and can't develop further my Jack based apps.
>>> this is open source. stuff happens when it happens. i prioritize based on a number of factors.
>>>
>>>
>>
>>
>>
>>
>>
>>
>> Jack-Devel mailing list
>> [hidden]
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
> <jack1_lack_ses_api.patch><lsp.c><connect.c>
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
1359349154.4990_0.ltw:2,a <A6B55491-176F-4BA8-822D-29F06B628848 at grame dot fr>