[Lloopp] lloopp/max/jitter issue

[Tommy Birchett]

one more thing I discovered today...

When launching lloopp for the first time after restart I can simply
close the lloopp host from the lloop host menu once leaving max +
jitter running... and then reopen lloopp-ho_st.pat and everything
works fine.

On 9/26/07, Tommy Birchett <tommybirchett at gmail.com> wrote:
> ok, i did additional testing and got more detailed information...
>
> 1.
>
>  If you only have the MaxMSP Runtime 4.6 you will get the following
> error if you try to install Jitter:
>
> "you cannot install jitter16 on this volume. maxmsp 4.6 or greater is
> required to use this version of jitter"
>
> I discovered chaning the name of the folder from "MaxMSP Runtime 4.6"
> to "Max MSP 4.6" eliminates this problem.
>
> 2.
>
> I have also discovered that the problem I described before with lloopp
> not responding to attempts to initiate acts or environments on the
> first launch is related to Jitter...
>
> What I found is if I restart my mac and open lloopp_ho_st.pat it
> starts MaxMSP Runtime and Jitter16. Once lloopp host is available and
> everything looks ready the lloopp host will not respond to any
> attempts to open an act or environment. Quitting lloopp/MaxMSP Runtime
> and launching lloopp_ho_st.pat again works everytime as long as my mac
> stays up and running. Even logging out of my account and back in does
> not cause any problems. The problem resurfaces the next time I run
> lloopp only after a complete restart of the computer.
>
> As an experiment I restarted and then opened MAXMSP Runtime and
> initiated Jitter without actually opening lloopp. Once I was sure Max
> and Jitter were up and running I started lloopp and I did not
> encounter the problem.
>
> The problem is definitely related to Jitter and I believe that the
> maybe the Jitter initiation that occurs the first time you launch
> lloopp is causing the problem.
>
> Anyway, it is easy enough to work around, but I wanted to make sure it
> was reported.
>
> I hope this information is helpful to someone. Thanks for everything!
>
> Tommy
>
>
> On 9/26/07, o. blaat <oblaten at gmail.com> wrote:
> > hello::
> > i have tested 1.5 w/ both runtime and full install.
> > runtime behaves exactly the same as others claimed.
> > second time was fine. (i'm running osx 10.4.9, max/msp 4.6.3, jitter 1.6.3,
> > on non-intel machine.)
> >  it happens even though i'd launch runtime first and open ho_st from within.
> > i'd need to do it second time around to let it work.
> >
> > 1.5 update also fixed all the problems i had with 1.4 - namely with all jit
> > acts.
> > thanxx to klaus! (i only didn't understand if gl host is not at all
> > interacting with any other jit acts. but i haven't spent enough time with
> > the gl acts yet. maybe i can find something inside the sub-patches.)
> >
> >
> > more report later.
> > keiko
> >
> >
> > On 9/26/07, Clemens Hausch <clemens.hausch at gmx.at> wrote:
> > > hi there,
> > > i have exactly the same problem, though i have a full official license of
> > max- i didn't bother with it since it works flawless after the 2nd start of
> > max- i have an idea though - if i ddo the "close all" command in ho_st
> > before quitting max it seems to me that the next start of lloopp works fine-
> > it worked some times like this, but not always, so i'm not 100% sure about
> > this.
> > > cheers, clemens
> > >
> > > -------- Original-Nachricht --------
> > > > Datum: Tue, 25 Sep 2007 14:39:23 -0400
> > > > Von: "Tommy Birchett" < tommybirchett at gmail.com >
> > > > An: lloopp at klingt.org
> > > > Betreff: [Lloopp] lloopp/max/jitter issue
> > >
> > > > Here is a problem I have run into:
> > > >
> > > > I had Max runtime only installed and wanted to use the Jitter
> > > > functions in lloopp, but the current version of Jitter will not
> > > > install unless I have the full version of max installed. So I
> > > > downloaded the demo and installed it in order to get jitter installed
> > > > and working. Since I do not havea license for the full version of max
> > > > i set lloopp-ho_st.pat to max runtime and applied that change to all.
> > > >
> > > > I now have everything working except I have found that the first time
> > > > I open lloopp after booting my mac i cannot get the host to open
> > > > anything. If I quit max runtime and open lloop again it works fine. I
> > > > have installed and tested this on another machine and I get the same
> > > > results.
> > > >
> > > > I have tested on 3 different macbook pro computers.
> > > >
> > > > it's not a huge problem since i can just start lloop twice to get it
> > > > working, but just wanted to alert you and see if anyone else has seen
> > > > this or if anyone has any thoughts or ideas about what is going on.
> > > >
> > > > Thanks,
> > > >
> > > > Tommy Birchett
> > > > www.broadcastatic.org/tommy
> > > > _______________________________________________
> > > > Lloopp mailing list
> > > > Lloopp at klingt.org
> > > > http://klingt.org/cgi-bin/mailman/listinfo/lloopp
> > >
> > > --
> > > -
> > > http://www.unfinishedbusiness.at
> > > http://www.myspace.com/112310020
> > >
> > > Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
> > > Browser-Versionen downloaden:
> > http://www.gmx.net/de/go/browser
> > > _______________________________________________
> > > Lloopp mailing list
> > > Lloopp at klingt.org
> > > http://klingt.org/cgi-bin/mailman/listinfo/lloopp
> > >
> >
> >
> > _______________________________________________
> > Lloopp mailing list
> > Lloopp at klingt.org
> > http://klingt.org/cgi-bin/mailman/listinfo/lloopp
> >
> >
>