[PD] Gem crashes after relaunching with error: i965: Failed to submit batchbuffer: Invalid argument
Max
abonnements at revolwear.com
Fri Nov 30 11:34:03 CET 2018
me too:
https://github.com/umlaeute/Gem/issues/191
On 30.11.18 05:42, andre rc wrote:
> Hi,
>
> I have the same issue. I tried 3 machines with ubuntu 18.04.1 with a
> self-compiled Pd 0.49.0 and Gem 0.93. cloned from git.
> One machine has an Nvidia Geforce GTX 660 Ti and it has no problems. The
> other 2 machines have an Intel integrated graphics controller and they
> crashed after recreating gemwin only when the text3d is used. With
> text2d there's no problem, same with other gem objects.
> pd -verbose -lib Gem:
> i965: Failed to submit batchbuffer: No such file or directory
>
> Best, A.
>
>
> On Mon, 1 Oct 2018 at 22:38, Csaba Láng <langcsaba at gmail.com
> <mailto:langcsaba at gmail.com>> wrote:
>
> to correct my previous statement, when I wrote metro is slower 3
> times I was wrong, it is not 3000ms but 3333ms but it is due to my
> last project where I used 200fps for the Pylon high speed cameras.
> now everything seems to make sense: when I used those USB3 cameras
> with the correct 200fps, this metro phenomenon did not occur, until
> I changed the cameras to webcams keeping accidentally the 200fps.
> when turned it off Gem went back to 20fps.
> Thanks for solving this mysterious case :)
>
> On Mon, Oct 1, 2018 at 8:50 PM Csaba Láng <langcsaba at gmail.com
> <mailto:langcsaba at gmail.com>> wrote:
>
> yes you are right, once it was 3 times slower, once it was 3
> times faster.
> Gem is on default framerate, I guess you mentioned it is 20fps.
> Monitor is on 60Hz. There is a ratio of 1:3 indeed but I hope it
> has nothing to do with metro.
>
> On Mon, Oct 1, 2018 at 8:43 PM IOhannes m zmölnig
> <zmoelnig at iem.at <mailto:zmoelnig at iem.at>> wrote:
>
> On 10/1/18 6:30 PM, Csaba Láng wrote:
> > Indeed, annoying it is during developing the patch,
> however had a feeling
> > that maybe Gem makes my metro work slower exactly 3
> times, one second lasts
> > 3 seconds in real time.
>
> i'm a bit confused now:
> in your last thread you stated that the metro was exactly 3
> times faster
> (that is a [metro 1000] running a 333ms; now a [metro 1000]
> is running
> at 3000ms).
> while a slower/faster metro is entirely possible and te two
> problems
> might be unrelated, i wonder why exactly the same factor "3"
> occurs in
> both issues.
> could it be that the problem is somewhere else (e.g. a
> simple patch error?)
>
> at which framerate is your Gem-patch running? at which
> framerate is your
> monitor running?
>
>
> > it is in no correlating with the source of the bug.
>
> afaict, this is unrelated to the crasher bug you are describing.
>
>
> > But will never get the answer.
>
> i'm not sur what you mean by this.
>
> fgmsard
> IOhannes
>
> _______________________________________________
> Pd-list at lists.iem.at <mailto:Pd-list at lists.iem.at> mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>
> _______________________________________________
> Pd-list at lists.iem.at <mailto:Pd-list at lists.iem.at> mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
>
More information about the Pd-list
mailing list