Vsynth Package

    Aug 23 2016 | 9:12 pm
    Hi everyone! I'm opening this thread in case any of you have questions, doubts, suggestions, etc, related to the Vsynth Package. Remember I'm uploading almost everyday info, screenshots, videos here: https://www.facebook.com/vsynth74/ https://www.instagram.com/vsynth74/ Cheers!

    • Aug 26 2016 | 11:16 am
      Hi Kevin,
      Many thanks for the vsynth package, I'm enjoying it a lot, great work. One thing I would like to see is the capability to automate effect parameters, eg on the rota object. Is this something you are considering?
    • Aug 26 2016 | 6:33 pm
      Hi Paul, thanks for your words. Taking into account we are inside Max and there are a lot of snippets out there to automate things, I won’t develop them myself (at least not for now). I’m focusing on the oscillators, cv_ins, envelopes, filters, that is, all that has to do with video synthesis. However, for the next update, I’m adding a control inlet in every module so you can externally control them in a Max-style way with whatever you want! Here is a screenshot that exemplifies this better. You can see I’m controlling parameters with Beap and Vizzie (but this can be whatever you want) by adding just one or two simple Max objects.
    • Aug 27 2016 | 11:53 am
      Hi Kevin,
      That's great news - being able to control vs parameters with standard Max objects will be even better. I think I had - incorrectly - assumed you were aiming for a fully self contained system. This will be much better.
      I look forward to the new version.
    • Nov 02 2016 | 2:29 pm
      v1.0 was released yesterday fellows, go grab it through the package manager! Lots of new features!
    • Nov 02 2016 | 9:50 pm
      Hi . First of all thanks for this brilliant tool. I tried your beta and was loving it ! im dying to try the new version ,but the max package manager doesnt like me today. any manual way of installing it? otherwise i will just wait THANKS , great job!
    • Nov 02 2016 | 10:15 pm
      Thanks Carlo. Yes, I uploaded the package to gumroad for those with an older version than Max 7.1. Place it under /Documents/Max 7/Packages.
    • Nov 03 2016 | 8:59 am
      Thanks a lot. Working really smooth this new update. Thanks for all that examples !
    • Nov 06 2016 | 7:47 am
      Hey just passing by to say this is amazing, lots of thanks, having loads of fun, and it's useful to learn a bit about jit.gl.pix too :) One question about the feedback though, i'm not sure i understand when it can be connected, like what are the conditions and the logic behind it ? As i'm a noob in graphic generation and trying to use my little knowledge from audio synth to transpose it to this world.
    • Nov 23 2016 | 6:17 am
      Hi Kevin,
      Thanks so much for making this and sharing it with the community! I starting playing with V Synth about a week ago and I really love it! It’s so nice to have access to this process of image making without the insane price of modular hardware or their restrictions, especially fixed NTSC resolution!
      I have a couple of questions that probably relate to the same issue:
      1. Sometimes after building up a patch with many wave generators, I'll decide to unplug/delete one or more from either an FM path or mixer path but their feed continues to affect the generator or mixer it was previously connected to. Is this normal? I wonder if this happens because I am often copying module chains (alt-dragging) and the copied modules have overlapping named contexts by not being instantiated from the V Synth menu bar? Do VSynth modules have to be instantiated from the VSynth Menu Bar in order to function properly?
      2. I've been trying to use Snapshots with my V Synth patches. I feel like Snapshots is a huge feature to be able to take advantage of within Max7, especially when compared to equipment based modular analog video synthesis, in which preset making is impossible. Many of the V Synth modules aren't natively visible by Snapshots but I have been able to make them visible by modifying controller objects within the original bpatchers. For example, in the CLRIZER module I've ticked 'Parameter Mode Enable' to ON for the 'swatch' object within the bpatcher and now it seems to work fine with Snapshots.
      The big problem I had is that the native VSynth Menu Bar will create/instantiate a bunch of new modules every time I change presets in Snapshot. Often times these modules include new R3NDER modules which then create huge conflicts with the VSynth output window, sometimes even crashing Max7 in the process. Initially I tried to fix this within the V Synth Menu Bar by disabling 'Parameter Mode Enable' for the ‘coll’ object in that bpatcher. It seemed like it had worked until I tried to create a new VSynth module from the VSynth Menu Bar and I was no longer able to instantiate new modules at all. Reactivating the 'Parameter Mode Enable' for that coll didn’t work ( I now understand why) and I had to start again by completely reinstalling the VSynth Package.
      Now I think I’ve figured out how to fix the issue with the VSynth Menu Bar. In the bpatcher for all of the ‘live.menu’ objects I have changed their ‘Parameter Visibility’ to ‘Hidden’.
      I guess I’ve probably solved my problem here, but perhaps I can make a feature request out of this? Could all of the VSynth modules be made compatible with Snapshots in a future update? I’d be happy to give you notes or copies of my patches that I’ve fixed for this use, if you’d like.
      Thanks again for such an awesome set of tools!
    • Dec 03 2016 | 7:23 pm
      Hi there. Really enjoying V Synth! Are the control parameter names for each module documented anywhere? Some are obvious, but others are not & having trouble guessing. For instance, on WFG_Shapes and WFG_2, the time parameter does not respond to the message "time x". Also, several parameters on XYZ.Displace are a mystery.
      thanks! //jake
    • Dec 07 2016 | 8:41 pm
      @VICHUG: you are doing feedback when you displace (frequency - position in the screen) or mix (amplitude - brightness) the video signal with itself (or with itself+process). Here an image of two simple feedback chains to illustrate. I’m working on a patch-book at the moment but in the meantime, you can also try with the cam_2 or a lumakey+framedelay among others. There are a lot of possibilities actually!
    • Dec 07 2016 | 8:58 pm
      @TYSON: sorry for the delay and thanks for taking the time to write all this, really appreciated!
      1. Is normal, is happening to me too and that's the reason why I didn’t add more ‘cv’ inputs to the modules. I think I found a way to solve this but I need to work and test it more before release it. I always alt-drag, thats not the problem!
      2. I've started a preset system with the pattr familly objects but using the new Snapshots system sounds promising and easier/faster to develop. I will look at it and yes, of course I wanna see patches! Does Snapshots allow to morph between presets?
    • Dec 07 2016 | 9:06 pm
      @JAKE RODRIGUEZ: they aren’t. I will post them in the next update. To control time you should write "/time 0”, “/time 1”, etc. You can always open up the bpatchers, is really easy to add your own control params!
    • Dec 07 2016 | 9:10 pm
      thank you--i don't know why it didn't occur to me to open up the bpatchers at first. i have since added controls everywhere i need them, and spied on the ones already present.
      cheers! jake
    • Dec 07 2016 | 9:35 pm
      Perfect Jake, just remember to backup before downloading the next release!
    • Feb 11 2017 | 10:22 pm
      Am interested in learning more about the Patchbook. I don't have Max, just use M4L inside Live. Will that limit what Vsynth/Patchbook can do? Is there a syphon out or other video out option to use with Live, or the ways to save your work?
    • Feb 12 2017 | 3:57 pm
      @JCRYSTAL You can use the Patchbook without having the Vsynth Package installed. The difference is that you won't have the entire modular environment to build your own configurations but some configurations I came up with to produce certain visuals. Both configurations from the Starter Kit of course comes with Syphon Output. You can load them in your Live set and turn them on and off to have different 'scenes' with presets.
    • Jun 16 2017 | 12:28 am
      do vsynth modules support custom midi mapping for a midi controller?
    • Jun 16 2017 | 1:47 pm
      @BYOU, you can control all the modules externally by sending messages to the most right inlet. For midi mapping check the 'external_connection' tab on the Launcher and to see the complete list of the public variables go to the 'sync_time' tab.
    • Aug 03 2017 | 8:51 pm
      Hi everyone! I'm gonna leave here some of the patches I sent to the students that attended my Vsynth workshops.' Hope they are useful to you too! You should have the latest Vsynth version installed (v1.2.1), so if you didn't update now its good time to do it!
    • Aug 04 2017 | 9:39 am
      Thanks Kevin! Is the latest version the one in the Max package managet?
    • Aug 04 2017 | 1:49 pm
      yes @foldh, also available here for the ones still in Max 7.0
    • Sep 05 2017 | 9:09 pm
      Vsynth v1.2.2 I've just uploaded a little update that brings some new features and bug fixes. They are all detailed in the changelog file. As usual, you can grab it through the Package Manager or from here.
      Stay tuned!