• somi

    hi,

    i was wondering whether it is possible to get something like a rotation on individual particles in a particles system.

    this applies to the particlesystem utilizing geos or models. as for now, a model would alway be facing in the exact same position as it is created.

    i don't even need a specific precise rotation, just some (even random) variation.

    can this possibly be done via a gravity or orbit point argument i haven't yet discovered?

    somi

    posted in pixel# read more
  • somi

    hallo,

    i am having problems, when applying a texture onto a model. the texture is never fully visible on the model but bent and only stripy visible in parts (as if highly enlarged an distorted).

    i tried the various options for texturing (repeat, rectangle) as well as [pix_coordinate].

    basically i only get distorted stripes.

    it all works perfectly on native geos but not on loaded .obj models.

    what am i doing wrong?

    i also noticed, that all models i load are way smaller - with the same scaling in pd - as the geos. [rescale 1( didn't help.
    i have to scale them up extremely in any 3d modelling program, to get them to the native sizes of gem. might the problem be here?

    thanks for any help!
    somi

    posted in pixel# read more
  • somi

    @ toxonic & boonier: may i ask what the use of such a timecode would be? i was just fiddling with a small sync patch to get a mini-sequencer inside a pdvst plugin, when it occured to me, that every parameter is already automatable/editable along the timeline within the host.
    ... which then would be a precise timecode for any parameter one would want i n the plugin.

    or are you wondering about a mini timeline within the plugin, like i.e. dblue_glitch has? then, a seq, that rewinds itself on stop is enough? that should be easy.

    i am at a loss though, when it comes to a real timestamp/songposititon being sent from the host.

    posted in technical issues read more
  • somi

    i suppose, a timecode or clocksync would be achieved, just like one would do in "normal" pd. the plugin-patch could start a certain midi-in channel when openend and the host could send its clock out on a certain midi-device.

    this would be a bit of a dirty workaround, since the host sends outside - maybe to midiyoke - and then back into the the host to the plugin.

    i once tried to make a clock with a midi-track in the DAW, which had a note set on every bar, so it would be like a metronme to pd.
    stop and start is received by pd through midiin, so it basically worked.

    unfortunately the latency between both programs was unbareable and i couldn't compensate it.

    posted in technical issues read more
  • somi

    hi,
    i recently wrote a patch on the same approach.
    you have to use "part_render", not part_draw in this way:

    [gemhead]
    |
    [part_head]
    |
    [all the particle related objects of course]
    |
    [part_render]
    |
    [cube]

    naturally, instead of the cube you can use whatever is available in gem.

    greetings from neukölln to neukölln! :)

    posted in pixel# read more
  • somi

    thanks!

    you are right, this http://gem.iem.at/releases/0.92svn (of 0.92CVS20090430) fixes exactly what i meant.

    hooray! :)

    posted in pixel# read more

Internal error.

Oops! Looks like something went wrong!