Device Details

Device Overview

Name/Version: J74 V-Module 0.9.1
Author: fabriziopoce  
Description: V-Module is a collection of multiple M4L devices which provides a modular interface to video functionalities in the Max/MSP/Jitter environment, integrated within Ableton Live's workflow.

V-Module is a free tool. If you end up using V-Module and like to keep it alive, please make a donation through the download website:

Required versions (minimum) for version 0.8.1:
- Ableton Live 8.2.6 or later
- Max/MSP/Jitter 5.1.9 or later

Required versions (minimum) for version 0.9.1:
- Ableton Live 9.0 or later
- Max/MSP/Jitter 6.1 or later

Note: V-Module is compatible with VIZZable of Zealtv (

If you like to follow both projects, please visit our development group:

For tutorials visit:

Device Details

Tags video, utility, other
Live Version Used: 9.0.4
Max Version Used: 6.1.2
Date Added: Mar 27 2011 16:43:14
Date Last Updated: May 23 2014 14:08:59
Device Type: midi_device
Download URL (report link)
License (more info): AttributionNonCommercialShareAlike


V-Module is a collection of multiple M4L devices and is essentially a modular, Live-like, interface to Jitter functionalities in Max (along with a few creations of mine).

Excellent, remarquable work... Many thanks to share your efforts.

wow, this is a massive contribution!

would be great if you let the user choose beetween jit.dx.grab and jit.qt.grab(in your v-cam module), since jit.dx is not compatible with osx. I`ve changed it for me, but maybe some other users dont know how to

My view on the V-Cam compatibility issue.

1) To quickly workaround concerns about jit.dx.grab and jit.qt.grab compatibility (Windows vs Mac) I have also included two additional V-Cam-xxx devices in the download package:
- One is called V-Cam-DX and is dx (Windows) based
- The other is called V-Cam-QT ans is Quick Time based (Mac)

The V-Cam is delivered in the live pack as identical to the V-Cam-DX (just a copy with another name).

2) If you open one of my example livesets on MAC, you need either to replace it with the V-Cam-QT or (better) to edit your V-Cam device.

I mean, it is not that complicated and the point is that will make your life set cross-platform (if you do not export the devices with it): if you make a liveset in Mac with "your" V-Cam version and you share it, windows users can open it with "their" version of the V-Cam and would work.

3) There is a try (not done by myself) to make V-Cam self defining the platform you are in and adjusting itself. If I have a workable version of it, I will post it.


thanks, but as i said it never was a proplem for me.
another solution: use cv.jit.grab from the cv.jit lib. , it`s a cross-platform wrpper for jit.dx.grab and jit.qt.grab
greetings from austria

This is fantastic, as it works nicely with the VIZZABLE suite too!!

I'm still trying to get the Video to MIDI working, but otherwise this is awesome.

Thanks so much.

amazing work! thank you!

for anyone unable to use V-Cam on OSX the Grabr module from VIZZable works nicely (

simply label the output :
"video1" to send to "video1"
"voutput1" to send to "stream1"

oh, and yes the V-cam-QT works too!


Robert Jarvis (, the author of VIZZable) and I (V-Module's maker) are trying to start up a community on developing modular Jitter-foucused tools within Max4live.

If you are interested have a look to this post and let us know:


For whoever is interested in the mentioned joint effort (a common modular framework for Jitter processing within Live's workflow), please add yourself to the following Google Group.

Group name:

Group home page:


A new version (0.2.1) has been posted on

- V-VideoRack added
- V-Cam made cross platform
- V-Mixer and V-Out devices with window screen support ESC for existing fullscreen
- V-SliceBeat enhanced
- V-FX-GL-Rota-xxx removed theta issue on Live's undo
- V-FX-Feedback2 added (a backscreen like feedback)


My word, you've gotta chill out man! Your head is going to explode. This is just brilliant. I can't even imagine how much time and energy that went into this. Fantastic. Great work.

Hei anybodyhuman, don't be scared....

All I just updated V-Module to ver 0.3.

- V-VideoRack completely rewritten. Performance and memory usage have increased considerably.
- V-VideoRack supports now 16 pads per device
- V-VideoRack supports chaining of multiple V-VideoRack, by using pad MIDI "offset" (see example08 liveset)
- V-VideoRack tested loading 64 clips in 4x V-VideoRacks
- V-VideoRack supports retrigger/continue options for multiple hits on same pad
- V-VideoRack does not abuse undo list


are there any video tutorials on this topic anywhere? some of these plugs are a bit beyond me, but i wanna get stuck in.


For everybody willing to "learn" the tools:

- Have a look to the PDF documentation on my website (

- If you give the tools a go, open the example livesets in the package. They show you some standard approaches for connectivity and processing. Be curious and dig them out....

- Tutorials are planned (I am working on them). As soon as they'll be completed I will post them on vimeo ( and/or my website ( Please, stay tuned.


looking forward to it. will check pdf.

thanks :)


I posted version 0.4 of V-Module on the usual link:

This time no new devices, but a lot of improvements to V-Module stability in particular against the so called Ableton Max for Live Production Guidelines (v0.6):
- All GUI parameters are labeled in a meaningful way (see info view). Yes, you read it right: ALL GUI parameters.
- The most significant GUI parameters (all type float and/or int, according to M4L constraints) can be mapped and automated for clip envelopes.
- Many devices have useful info view text (thanks M._TriangelKlang for the help)
- All devices behave politely and do not spill into Undo history (no loadbang on live.objects, Max umenu managed through pattr instances)
- All devices are frozen and directly compatibile with OSX and Windows OS
- Other enhancements and fixes on existing devices:
- All V-Input devices have rate which can also go into negative values (thanks ChrisG for the tip)
- All V-Input devices are now efficient with memory and use both drag'n'drop and click-to-read ways to open clips (thanks to ChrisG for the "invisible button").
- V-VideoRack supports Thumbnails creation also if folder is selected while device is ON/playing.
- V-VideoRack, V-SliceBeat, V-Mixer and most V-Effects have full Info View help
- Some effects will see improvement in the use of backread technique (devices type OpenGL or just "GL").

Note: projects made with older versions (<0.4) opened against the new library will not recognize saved parameters. This is due to the new GUI parameter labels.
If you used older versions please backup the old devices within your project folder.


Video tutorial "1" of V-Module can be found at:


Fabrizio, now this is what I would call 'dedication' without the sahadow of a doubt. Merci beaucoup.


V-Module version 0.5 posted:

- Solved some bugs with open GL effects and mixer apparently due to video window automatically pop-up. Note: on V-Mixer devices you need to explicitly set "screen ON" now to have a window.
- Added a V-Mixer version (V-GL-RenderMixer4RGB-Out.amxd) for an additional output stream (useful for instance to do recording to disk by V-Rec)
- Several "video" / non 3D devices (V-VideoRack, V-SliceBeat, V-GL-Rota, V-GL-Slab) support ChrisG auto connect mode (i.e. in combination with VIZZable 0.9.2 or later. See device names with "-auto" suffix.
- LiveAPI LFO modulation supported (and LFO parameter bank removed). Each device shows its parameters (shortnames) for modulation and the V-LiveMod new device allows CVsend to LiveAPI modulation mapping
- V-Effects type OpenGL revised: no additional window required and better backread / readback support.
- V-Control device V-DroidSens2CV and V-DroidCtrl2CV added for Android control in combination with Matt Benatan's Max/MSP control app available at
- V-Control device V-Joy2CV added for support of HID usb devices (such as Joystick, Gamepad) etc. as CVsend (using the V-CV2MIDI you can use these to send MIDI informations).
- Several new OpenGL 3D tools (V-GCoord3, V-FX-GLOpScalar, V-GMove3DWJoy, V-GMove3DWPad)



V-Module version 0.6 posted:

- V-SlabGen instrument introduced for generation of visuals (such as procedural fractals) based on custom OpenGL shaders.
- V-GTexture introduced for texture operations, such as video-to-texture (texture mapping in a 3D object) and texture-to-video (rendering to texture, feedback)
- V-GMulti introduced for efficient cloning of a source 3D object, creating potentially a very large number of 3D clones in space
- Added a V-Mixer version with OpenGL based internal 3D video feedback.
- Added a large number of OpenGL effects and devices for density, proximity, morphing applications
- Added a number of V-AuScope (audio) processing effects for tighter audio to video manipulation.
- Added a range of OpenGL coordinate formula generators (such as V-GCoord3 and V-GCoord4) for more control/customization of 3D objects.
- Added V-Boids instrument with simple fluid simulator.
- Added V-AuEnvelope audio effect for tracking beats and generating envelopes based on Live?s tempo



I just posted a new version of the V-Module plugins (version 0.7). Some features have been requested / talked about so many times, that I got a hold on my GL stuff (where my heart really lies) and did some work on video clip playback again.

Here you go:

- New V-Audio "Instruments" for playback of clips having both video and audio. Audio and video playback is in sync, audio sent through Live's mixer: V-SimAudioPlay, V-SliceAudioBeat, V-VideoAudioRack
- New V-SimAudioLooper an V-SimLooper for Live tempo warp-looping of video clips (ewsepctively with and without audio feed)
- New V-FX-FFWrapper for FreeFrame plugins support
- All previously available V-Instruments (MIDI devices) for QT playback do not spill audio "outside" of Live
- New V-AuBeat based on external op.beatitude~ for Live tempo settings from audio input (even a live feed from external)
- New V-AuBeat2CVEnvelope based on external op.beatitude~ for very tight CV envelope generation from audio input (even a live feed from external)
- All video input devices save file (clips/folder) as part of the liveset
- V-ObjShape expanded for advanced texturing, multi rendering (cloning). It also saves the file as part of the liveset
- New V-ZoomPlay added (for picture zooming)
- Various enhancements to V-GMove3DW devices (3D camera movements) including a toggle for 2d/3d view switch


I have posted a new version of the V-Module plugins (version 0.7.2) with some enhancements and a few new features.

- Enhancement: all V-FX-GL effects rewritten with more efficient chaining (pure GPU). Note: Requires a V-Mixer to be in the liveset in order to work. This is true also for VIZZable users.
- 3D Tools for morphing of OpenGL objects (vertex morphing):
- 3D Tools for movement 3D "recording and editing" (as matrixset/JXF format), useful for planning smooth 3D trajectories: V-GMoveCapture3D, V-GMoveState3D, V-GMovePort3D, V-GMoveEdit3D, V-GMovePlay3D
- 3D Tools for OBJ to OpenGL format matrix conversion and read (nice for 3D morphing and/or physics emulation applied on 3D objects vertices): V-GSnapObj, V-GObj2Matrix, V-G-WriteMatrix, V-GMatrix
- OpenGL-FX on vertex manipulation with simple physics of an oscillator applied on 3D object coordinates (V-FX-GLOscillator)
- New 3D device type: V-OpenGL-Processor for "post-processing"-like effects on top of 3D scenes/objects (based on OpenGL shaders)
- V-GL-RenderMixer4RGBPostFdbk, a new version of the V-Mixer allowing full scene post-processing and recording by V-OpenGL-Processor devices
- More tools for recording of 2D, 3D and both: V-GL-RenderMixer4RGBOut (rewritten), V-GL-RenderOut, V-GL-RenderGrabOut
- V-ZoomPlay modified to easier "still picture scanning"

Notes about capturing a full scene to .MOV: use V-GL-RenderMixer4RGB-PostFdbck + V-GL-RenderGrabOut together.
Settings must be set exactly in the following order (changing the order may disrupt dependencies)
1. Load V-GL-RenderMixer4RGB-PostFdbck (a version of the V-Mixer with render to texture option)
2. Load V-GL-RenderGrabOut (the grabbing device)
3. On the V-GL-RenderMixer4RGB-PostFdbck (middle/bottom section) set the parameter for rendering to texture:
- redirect toggle = "off"
- capture = a free texture name, i.e. "texture1"
- feedback = a free outgoing video stream, i.e. "video1"
4. On the V-GL-RenderGrabOut
- tx/nm = the same texture chosen for capture in the V-GL-RenderMixer4RGB-PostFdbck mixer, i.e. "texture1"
- str_in = the same video stream used by feedback in the V-GL-RenderMixer4RGB-PostFdbck mixer, i.e. "video1"
- render = "mrender1" (context used by the V-GL-RenderMixer4RGB-PostFdbck mixer)
- grab_output = a free outgoing video stream, i.e. "video2". This stream can be picked up by any device as input.
To view the grab: attach a V-Window to the grab_output channel
To record the grab: attach a V-Rec to the grab_output channel
- The definition of the grab is set to automatically follow the format of the V-GL-RenderMixer4RGB-PostFdbck output screen. The best is to have all formats to the same identical size.
- This technique is both CPU and GPU relatively intensive. The best remains to use a GPU based grabber (like Fraps on Windows or Snapz Pro on Mac) or even better an external hardware device (see previous comments on Matrox MXO2 mini).


This is so great.

Question: Are the V-Racks windows only? I can't find them in the OS X version.

All devices (including V-VideoRack and V-VideoAudioRack) are both Mac and Windows. They are respecitvely:

V-Module Project => Presets => MIDI Effects => Max MIDI Effect => V-Module VideoModules => V-Input => V-VideoRack.amxd

V-Module Project => Presets => Instruments => Max Instrument => V-Module Audio Instruments => V-Input Audio => V-VideoAudioRack.amxd

In the example livesets there are a couple of scenario on how to use them.



I have posted a new version of V-Module (version 0.8) with some new features.
This version requires Max 5.1.9 and Live 8.2.6 to work properly. Max 6.0 seems to work, but has not been tested deeply yet (so be careful).

- Added a Syphon-enabled V-Mixer (MAX OS only, V-GL-RenderMixer4RGB-Syphon.amxd) for sending the 4-channel "mixed-down" output to a Syphon client (using servername "MixerOut") (***). Thanks to \\\\ Mike Todd //// for the porting of this device.
- A new wrapper for all V-Module 250+ shaders for video and 3D effects (V-FX-GL-Clab.amxd).
- New Control devices for OSC communication (OSC2MIDI.amxd, V-MIDI2OSC.amxd)
- An efficient video clip player for clip folders (SimPlayList.amxd)
- A wrapper for writing complex 3D scenes as "scripts" (V-GSketchListX.amxd), based on syntax interpreted files with additional functionalities. (***).
- A new wrapper for materials shaders on 3D object (V-GPreShader.amxd).
- Devices for OSC communication between V-Module and vvvv (V-Matrix2VVVV_snd.amxd, V-MIDI2VVVV_snd.amxd) - for the vvvv side have a look to
- Possibility for a secondary/auxiliary window (V-GL-RenderMixer4RGB-FdbckAux.amxd + V-GL-RenderAuxMonitor.amxd).
- 3D camera rewritten in java (old version still available in the legacy sub-map)
- Support for FSAA (antialiasing) in all mixers.
- General code clean up and optimization.


please I want to use your V-module but i need to work whith format 768X576 (75% of 1024X768) and there're only 720X576
why ?
the vid?o clip are in ram ?
how clear the ram ?
so v-module is a great job !!!!

Although 768x576 is not one of the standard resolution modes hard-coded in V-Module mixers/players, this can be easily edited to fit your needs....

Open the device in edit mode, modify the section regarding the format menu and there you go. It is straight forward actually: edit => select the menu object in question => open the object inspector => edit the menu text field to have 768x576 => save.

Gr. Fabrizio

A small update to V-Module package (now on veriosn 0.8.1):

- New V-SimPlayLibrary, with a more compact and at the same time powerful toolset for video clip playback (an enhancement to the SimPlayList earlier device)
- New Audio Analisys devices (V-AuScope-xxx), with much tighter audio signal recognition and Live.API triggering
- Syphon-enabled mixer (MAC OS only) updated to latest version (also on a separate installation directory for direct file copy)
- Some fixes to devices and to the installation pack

Requirements: Ableton Live 8.2.6 (with licence for M4L) and demo installation of Max/MSP/Jitter version 5.1.9.

New tutorial (4) at:


Thanks for the update! This is a really great project.

It took some time to update V-Module visual plugins for proper compatibility with Live 9, but finally here is it.

This new version looks a bit different, specially under the hood. Many devices have been merged/reshaped (and most of all made more efficient) and some parts of the code are now in Java and Javascript (see Boids, Fluids, Sketch, Stokes, API part etc.). Among the new things I added back compatibility to VIZZable 2.x (since it also moved to GPU processing, see note below) and there is also a bunch of new shaders as you find on the new "V-FX-GL-MultiEffect.amxd" and the multipass "V-FX-GL-MultiEffectChain" devices.

Here the release notes for version 0.9.1 in a row:
- Compatibility for Live 9 (Live 8 user should stick to 0.8.1)
- Many device rewritten (and many renamed) with an eye on performance/scale (more use of Java and Javascript)
- New GPU shaders for pixel and vertex shading
- New particle simulations (in Java)
- New extensions to V-Sketch
- Support for Max Materials (as from Max 6.x)
- VIZZable 2.x compatibility, by ability of selecting "VIEWR" as render context in all V-Module OpenGL based devices

Great collection!

Thank you so much Fabrizio for sharing these reliable and cool things with us

Sadly, it appears that as of Live 9.5, V-Module is not working anymore (using either Max 6.1 or 7). Pull-down menus will not display, and many other functions don't work.
If someone is using this successfully with Live 9.5, let me know.
I had put a lot of time into this fantastic suite of devices, it's so powerful the more you dig into it.
Hopefully, Fabrizio will eventually find time to get back to this amazing tool and update it.

- Max

Update (unfortunately, posts here cannot be edited/deleted):

Some of the problems described in my previous post were due to not having the correct audio driver selected at the moment of experiencing these issues. It now runs fine again (Live 9.5, M4L 6.1, Windows 7).

However, I'm still unable to properly run V-Module in Windows 10.
If anyone has been able to get it to work without issues in Windows 10, please let me know.

Well I wish all my problems resolved as easily as this one:

I failed to copy the folders of V-Module Java classes/ Max Externals/ and Max presets to their respective folders when setting up my new laptop.
Now that I've done this, everything is working perfectly again (Windows 10, Live 9.5, Max 6.1 & 7).

I hope, at least, that this may help someone else who may be stuck in getting it all up and running.

Indeed it is fundamental to copy these files and they include "code" not inserted in Max for Live devices (like OpenGL / GLSL shaders). The readme.txt file in the ZIP file explains how to do that.

Thanks for this fanstastic huge package! Just had a rough look at the docu while installing and this promises a lot right from scratch.

Login to comment on this device.

[ browse device library ]