» Player (EX9.Texture)
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

Player (EX9.Texture)


after quite some months in development and testing we are happy to announce the availability (in alpha builds) of Player (EX9.Texture). It was developed in collaboration with and initiated and sponsored by eno | nsynk.

The idea was to have a professional/highperformance alternative of playing back videos based on stacks of images instead of video files. The node is quite versatile/spreadable and does the heavy datahandling a background thread. Check its helppatch for instructions.

joreg, Tuesday, Dec 18th 2012 Digg | Tweet | Delicious 10 comments  
unc 18/12/2012 - 05:28


u7angel 18/12/2012 - 12:27

lovely eno and elias !

joreg 18/12/2012 - 12:54

forgot to mention: all actual coding-credits go to elias

sebl 18/12/2012 - 15:01

so cool!

bo27 18/12/2012 - 15:19

thank you))

Noir 18/12/2012 - 16:52


patrick 18/12/2012 - 23:54

Ah, the end of endless wasted hrs searching for the vvvvriendliest codec! Applaus!

casinowilhelm 14/01/2013 - 21:18

love it.

Is it quite reliable at syncing to audio?

tonfilm 14/01/2013 - 22:16

depends on how you play the audio and whether you use the timebased version or how you calculate the frame number.

timpernagel 13/08/2013 - 15:28

How can I determine the IO buffer size, which fits best for my PC? And what is the difference between Texture and IO threads?

I'm trying to play 4 streams simultaneously and change one stream without stopping the other three. I presume, that those pins are the key, right?

  • 1

anonymous user login


~10d ago

SuperflysiNZ: Thanks

~13d ago

sebescudie: @Superfly : ApplicationPath

~13d ago

SuperflysiNZ: How do you get the path of the current patch in VL?

~13d ago

SuperflysiNZ: How do you get the path of the current patch in VL?

~14d ago

joreg: reminder: first #vvvv online meetup after the summer break: tomorrow, tuesday 7th, 8pm CET 13.-worldwide-vvvv-meetup