Saturday, August 4, 2007

Video Vendors

One of the problems I've found with trying to sell jewelry is that, especially for the finely-detailed pieces, a static image on a vendor doesn't really do it justice. You want to give the customer the ability to see it from all angles, and close up. Even worse - if you're selling a scripted object, how do you show it in action?

So today I wrote a simple "video vendor" system for my store - individual vendor boxes which, when touched, communicate with a video screen. The screen sets the parcel's video media URL, resets the texture repeat and offsets on the main face to match the video's dimensions (so that "Auto scale content" doesn't need to be enabled), and starts the video in looped mode.

Maybe one day I'll even get to see it in action. The 1.18.1(2) release of the viewer purportedly added streaming video support for Linux users, but many of us can't get it to work.

(Next, multi-vendors and networked vendors! Muah ha ha ha ha!)

2 comments:

Dalien said...

Great idea!

The video integration seems to be a bit slacky even in windows - while playing with my vnc2sl hack, I noticed that frequent setting of the media URL was correlated with the much higher frequency of crashes, and the very action of setting the URL was causing a 1-2 second "hiccup" on the windows client.

But nice to read that media is coming to linux (finally), hopefully it works eventually :)

Johanna Hyacinth said...

Thanks!

This whole client seems very unstable; among other things, if my camera goes through a wall, it freezes for several seconds, and I can no longer drop an attachment; I have to detach it and then drag it to the ground, otherwise I crash every time. And there's a memory leak in this one that's worse than any I've ever seen in previous clients; the memory shoots up to claim all my available memory within a couple of hours, and when I quit, it almost always includes a "double free or corruption" message when deallocating memory.

But by far the cruellest thing in this viewer was that when I ran it the first time, it took me through the voice configuration process - raising my hopes that Vivox had finally got their library ported to Linux - and yet despite that, the voice component still isn't present.