The Vault

The end of Gyes

2011-11-04T11:27:00.000+02:00

-----------------------
NEW FEATURES
-----------------------

All things come to an end eventually so it comes to no surprise that Gyes ends here. The initial goal of Gyes was that would be an addon that could include all my future blender script , but I can see now this is not the best idea. Both RMG and RTG work great under the roof of gyes, but they are only 2 scripts and that keeps the GUI easily and manageable.

However Gyes did not end silently, it ended with a BANG!

The first thing added were a feature to import all material to the history tool that match a specific text filter even partial, making it dead simple to randomly assigne tons of already available material.

Another big addition is the fact that now history is multi-history , the history now has 12 slots each slot is a history or a group of material each material taking one index. Material of course include node materials, texture and node textures. This means that history is ideal if you want to organise your materials into material groups and because of the filter text import you can import all that material even if there thousands of them in mere seconds.

The final BANG and the biggest of all, is the fact that I finally sit down to create a wiki for GYES. I tried to document through videos but it turned out to be a really bad idea, because I keep improving features and that meant that videos had to be redone and that meant also loads of free time lost. Lesson learned from now on youtube video only for demonstration purposes.

This is where the wiki is located

http://wiki.blender.org/index.php/Extensions:2.5/Py/Scripts/System/Gyes

-----------------------
LOOKING BACK
-----------------------

To be honest when I started this project I did not intend to be 1288 lines of code , with a tons of features inside. I did not intent to randomize textures . I did not intend to offer full customisation on the randomization. I did not intent to invent a new tool for blender to store data that will be easier to organise than conventional material lists. I did not intend that tool to be saved with the blend file. And of course I did not intend to import materials based on text filters

I did not intend many things. I was a noob , did not know what the hell I was doing , I was just toying with an idea.

But I managed to do all those things, and loads more that are documented in the wiki. I certainly did not imagine that my first attemp with python and blender addons would be included in the contrib. It was so fun that I could not stop.

The thing is that for me I consider this project to have come far away, I dont want to say that I am a super coder , far from it (though I like to use the term "python wizard" for fun) , I am still very noob. But if you look into the history of blender from version 1 to version 2.6 , there have been some texture and material randomisers but nothing that offered the level of control of GYES. Probably I could go even further, but I dont try to prove how great coder I am, cause I am not . I prefer making addons that people really need and use.

------------------------------------
AND LOOKING FORWARD
------------------------------------

I like to inform people here that I decided to drop the idea of material librarian that can show thumbnails. I had the oportunity at last to look into cycles and draw 3 conclusions

1) cycles is already excellent way to preview materials
2) cycles is the future of blender
3) cycles is not yet matured enough to develop on it an addon

So my next project will be porting lithosphere and updating ANT , or to be more precise I intend to create a Ecosystem builder, starting with a terrain generator. Already speak with developer of lithosphere and I have porting some of the code, it will take some time till I release the new addon but I can promise you it will worth the wait.

By ecosystem I mean that you wont be able just to build terrain , but also river, trees, rock , cities , asteroids, planets and even solar systems

Its an ambitious project that probably will take me years to complete and it will bridge many addons like Plant generators, tree generators, littleneo's city generators, rock generator and any future addon that comes out that is related to my project.

As "taste for things to come" I link screenshots and videos from lithosphere, they are going to impress you

http://lithosphere.codeflow.org/screenshots.html

Have fun and see you soon

Gyes : RTG (Random Texture Generator)

2011-10-02T18:13:00.004+03:00

When I started my Random Material Generator ( http://blenderartists.org/forum/show...ial-Generator-) ) I knew that no material can look really interesting without some kind of use of textures. The reason is obvious a texture not only adds detail on a material but also brakes its uniformity making it much more interesting and natural. So it was always my intention to implement some kind of texture randomisation inside my material randomisation. However the issue was that RMG grow bigger , more complex and much more powerful I did not want to cram the interface so I decided to implement texture randomisation as a separate tool always from inside GYES.

The big diffirence between RMG and RTG is that the gui in RTG is adaptive to the texture type choosen. That means that GUI changes each time a diffirent type of texture is chosen making sure that only the necessary parameters are displayed keeping the GUI as compact as possible.

The tool is still a WIP but I have finished implementation , for texture types "BLEND", "NOISE", "CLOUDS" ,"DISTORTED_NOISE" and create my own type called "RANDOM" that chooses randomly one of the above 4 texture types and of course it randomises it too.

As in RMG simple mode give you the ability to choose which parameters you want to randomise and percentage mode gives you the ability to choose how much those parameters will be randomised . General percentage is used in case any of the parameter percentage randomisation is 0% , it makes it easy to have the same percentage for any amount of parameters. Percentage means the following : 100% is the full range of available values for the specific parameter, any percentage is divided in half, half going bellow the current value and half going above , so for example 50% of parameter that its minimum value is 0 and its maximum 6 and current value 3 , it will give a random value value in the range of 1.5 to 4.5.

Many things are yet to implemented till this is done, but its no less a released script that should be very useful for you. Bare in mind there is an error each time you change the type of the texture from inside RTG gui, I dont know why this happens but I will speak with blender devs to see if its a blender bug or a mistake from my part. This bug has not crashed my blender or stoped the script from working properly , but caution should be exercised and always save your work before trying this script.

RTG is part of my GYES addon so chances are if you got the latest version of RMG you already have RTG as well. Dont hesitate to ask any questions and here is the link of the download.

https://github.com/kilon/Gyes

GYES -- Random Material Generator (Percentage Randomisation)

2011-07-21T16:37:00.003+03:00

I added percentage randomisation. Now you can control how much random your material is . You can randomise existing material as much you want. GUI update, click on Mode and it will navigate through several pages of the GUI. "Percentage" page will give you even more option to apply specific percentage randomisation to specific parameters, all other parameter not covered by the specific percentages are covered by the general percentage. When a specific percentage is zero, the general percentage is used instead for that area. When a specific percentage is not zero then general percentage is ignored and specific percentage is used instead. If you dont want to randomise that area at all, in "simple" page use the corresponding button to completely disable that area , the percentage slider will also be disable in the "percentage" page.

Percentage randomisation means that the parameter is randomised inside a range of percentage of the full range of the value. For example a 50% randomisation of the specular intensity means the following :

specular intensity start from 0 and end 1 , 1 being the maximum value , 50% of 1 is 0.5 . If your existing specular intensity value is 0.3 then randomisation will range from 0.05 to 0.55 , which mean it can be any value that exists in this range which is a diffirence of 0.5 or 50% of full range. Of course randomisation takes always the current value as starting point so the next randomisation will use the current randomised value. Randomisation is always 50% of the specific percentage bellow the current value and 50% above . If the percentage exceeed minimum and maximum values of the full range, then it will default to minimum and maximum accordingly.

There is a "help" gui page that offers a summary help for quick reminder of the functionality. "Template" page is empty as templates are yet to be implemented. "Simple" page has the old enable disable checkboxes which I have replaced them as enable / disable switch buttons (enable / disable randomisation for a specific group of parameters ) along with a general percentage that for convenience also exists in percentage page.

Did 3 minor updates, one fixes a nasty bug that did not allow the script to load on startup as addon and another one where for some reason the register_module functions fails in future builds from graphicall,org after the official 2.58a from blender.org . I have replaced it with register_class() for each class i use so it should work now and for every future build.

However both problems were critical to the execution of the script so I had to bump the thread.

After a complaint I changed the "mode" button , to a list box to make it more visible and easier to use , blender developers need to fix the menu button (prop_enum_menu()) to make it more visible.

I also reorganised the file structure. Now everything is located in a folder called "gyes" just copy paste the entire folder to your addon folder and you will be fine. Inside gyes/doc you will find gyes.pdf which is the official Gyes Manual. I no longer support wiki as its difficult to work on both (Wiki and Pdf) at the same time , that means that wiki will no longer be updated with latest features. The reason is no longer called "gyes random material generator" is because I decided instead of creating several scripts that do diffirent things, to unite all of them in one add on script that will make installation and activation alot easier, so that means that gyes will be alot more than just a random material generator in the future. I plan to finish a new script every year.

The download link has not changed, remember you can use the same link as it always has the very latest update and I am constantly uploading new updates everyday that I dont report here as often cause I dont want to bump this thread unnecessarily.

Here is the download link => https://github.com/kilon/Gyes

Here is a screenshot of the new mode button

Simple mode :

Simple Percentage Mode :

Help mode :

!! Important Note !!

With the as always helpful guidence of ideasman from #blenderpython I was able to download the source and build the latest blender release. From now on this script will support the latest build release of blender and not just the official release from blender org. So it should work for anyone who wants to use the latest build from graphicall.org . I will keep updating my source and rebuilding blender to satisfy this requirement and will upload the builds to graphicall.org that will come included with my script.

Video Tutorial Random Material Generator - Gyes - Introduction

2011-06-24T14:37:00.002+03:00

Just uploaded a tutorial about my Random Material Generator - Gyes which I described in my previous post, hope it clears up any confusion.

Gyes (Random Material Generator) for Blender 2.5

2011-06-05T00:26:00.006+03:00

There is little doubt that we live in the golden age of computers, with massive power, flexibility , adaptability.

I look back to my old rusty Amstrad CPC 6128 (1988) with its green monitor, its 6mhz cpu. Yeah you heard correctly not 6 ghz , 6 mhz. Thats 3000 times weaker than a Core 2 Duo at 3 ghz. 3000 times, wow , imagine that.

And of course with hardware comes software evolution, as its software that pushes hardware up in the food chain. Yet , I am always suprised to see how more difficult things have become. With my Amstrad it was a question of inserting the disk , typing the run command and i was set to go, nowdays we got just about a million things to remember to get our computers running.

This applies with making 3d graphics as well, extremely powerful but with a gazillion of options enough to make your head explode to a gazillion pieces.

So I thought instead of being one of those guys bringing another new feature why not just make things easier for the tormented user. And thus i started a Blender script.

Gyes is intended to be a collection of scripts not just one, but for the time being the first one is the random material generator. It does what it says on the box, generates random materials. Of course the goal here is to give a meaning to randomisation cause no user likes completely random stuff. Every user has a goal, a dream , a desire. And gyes tries to put that into the equation.

I released earlier a massive update that started giving options to the user to limit randomisation in the way that user defines. As always simplicity is the goal here. Remember when your mother told you that "there is no magic wand" and you have to do things the hard way. Gyes goes against this rule. If the user wants to make a random "oak tree" material , or maybe the surface of the planet , he does need to understand every single detail on the process of making such materials, all he needs is a magic button and maybe some options. Gyes does not care about the "how" or the "why" it is its role to figure those out, it cares only for the "what". What the user wants ?

I wont explain every single detail about this script you can find loads of information together with a link for download in the thread i started in blenderartists. Click the following link.

http://blenderartists.org/forum/showthread.php?218110-Gyes-(Random-Material-Generator)

Now many people have asked what "Gyes" means. Well if you knew a couple of things about me, then you would know I am Greek and that I love ancient greek mythology.

Gyes was one of the three brother , a mythical deity , extremely powerful, capable of even slaying gods and titans. He and his brothers united with greek gods in the epic battle of the TITAN WAR , where greek gods and titans among other deities batlle in a huge civil war. Those 3 brother were called "ecatocheires" , which in greek means , the one with 100 hands. Because as you might have guessed they had 100 hands. Latter the 3 brother were assigned as keepers of the TITANS when the titans were imprisoned in Tarturus , a prison of the underworld where none , no man , god or any extremely powerful creature could go in or out.

For me 100 hands has the the meaning for 100 scripts , that will make life easier for the Blender user and even 2d artists . I know 100 sounds alot , but not all scripts will be as ambitious as random material generator. Sometimes even simple ideas can help alot. Maybe Gyes will be never finished and frankly I dont care. Its a great excuse to code in python, I am having loads of fun with it and I will keep doing it slowly but steadly.

I hope you enjoy using the script as much I enjoyed coding it. Its far from finished but its already very useful.

Vriareon (first Draft)

2010-08-30T16:02:00.004+03:00

Well , I have been coding for fun for more than 20 years now. But I never made any serious app, only messing around, enough to learn the programming languages I wanted. Gwbasic, dbase, clipper, c++, assembly, delphi, java , c# and now python.

So enter Vriareon. Basically its an app for transmiting multipoint envelopes to hardware synthesizers. If you did not understand what I just said, well, its normal if you dont use a synthesizer , software or hardware.

Bottom line is that most synths out there dont ever go being simple ADSR , which is a 3 point envelope , mine will go as much as you want.

Basically an envelops is nothing more than a graph that says to a parameter when to increase and when to decrease automatically. In most cases an envelope is made of no more than 4 points (A,D,S,R for Attack, Decay, Sustain, Release) . Attack is triggerd when a note is played, decays is after the attack, sustain when a not is keep pressed down, and release when a note is released. However in software synths like Absynth, Zebra, Alchemy this restriction is droped, and the user can make envlopes using an almost unlimited amount of points, thus creating incredible deep and complex sounds.

Vriareon uses midi protocol, either CC or NRPN to transmit midi data that makes up the envelope.

Currently the app, implements simple functionality. It support, add , move and delete of points, together with zoom in , zoom out and pan.

This is a video showing the app in action.

The app of course is far from finished, but I am in no hurry either. I want to take my time and make this into a very useful and very impressive app. The ultimate goals is to impement more features than multipoint envelops, but for the time being this is the only goal. Gui is still very crude and it may not seem impressive, but most the basic architecture of the app is almost finished. I have to , as a next step, transmit the midi to the the hardware synth. But its the Gui stuff that will take me long cause I want to build a very felxible gui from zero.

I use python and the python library Pygame, for gui and midi, as pygame has included the pyportmidi library which is very easy and efficient into sending and receiving midi signals.

I will keep you posted with monthly updates of my pogress.

Cython , probably the best programming language in the world.

2010-02-06T15:03:00.006+02:00

1. Introduction

So I guess you have heard all those people saying that there is no such thing as the best programming language in the world, only the right tool for the job. And its true , each language has its advantages and disadvantages.

But Cython , makes me make an exception to this rule.

Why ?

Well because it combines the best a programming language has to offer leaving all the negatives out.

2. What is Cython ?

So what is Cython ?

Well Cython is Python. It will accept any Python code , even Python 3 , subject to some limitation because it is an ongoing project .

However Cython is more than python. The first thing making Cython different is that it converts python code to C code. This code can be compiled with any C compliant compiler and produce either an executable or dynamic linked library (Known as DLL on windows) .

ok so whats the big deal ?

Well this alone offers double the speed for python which is fine but not very impressive if you take a look to tools like ctypes an psyco.

The next cool thing is that it allows you to mix C code with python code, so if you happen to code in C it can be the perfect bridge between C and Python. Again fine but it can be done with other tools as well.

However what makes what makes Cython REALLY interesting is that it expands the Python syntax. It expands it in such way to implement C features. One of these features is statically typed variables.

The key word here is "expands" not "replaces" , which means that you can use dynamically typed variables with statically typed variables.

But why we need statically typed variables in python ?

Well the answer to this is speed. To put it simply Cython code taking advantage of statically typed variables, to increase speed from 2 to 1000 times. Yes you heard correctly there are benchmarks that show Cython run 1000 times faster than Python . Here a benchmark that sho ws Cython being faster than C !!!. And if you think that this requires any major recoding , then think again, it only requires putting the name of the type infront of your variable which is nothing more than on or two words.

Remember that Cython is Python, which means that all you write is 99% python you just add a couple of words here and there with no major editing.

Even the compilation process is automatic taking advantage of the onboard python distribution tools, requiring the usual setup.py script.

Cython Advantages

1) 100% Python syntax, making dead easy to use and code with. You can use any existing python code with no change to your code.

2) C speed, cause it supports many of the features of C language making it extremely faster alot faster than psyco and ctypes.There is some overhead because of the conversion but it usually quite small from 40% to 100%. However there have been benchmarks that have show Cython outperform C by 40% which is is not unusual. Usually for statically typed variable except a boost in speed from 50 to 1000 times compared to the same python code

3) you can use any C code any time, just import it and it becomes accessible to your Cython code. Excellent for wrapping C libraries

4) Cython now supports and C++.

5) You never need to mess with C code all happens from inside python syntax.

6) Converts the python code to C code. Well I do not know how useful that is as a few lines of python code turns to thousnads of lines of c code but for those who want to edit code to kingdom come it will be useful. Again I remind you that Cython does not force you to write any C code to take enjoy its advantages.

7) Cython can be compiled to dynamic link libraries that can be imported and used like any python library out there.

8) Has the support of Google , so it is actively developed.

Disadvantages

1) Cython is Python, meaning it will still require python installation and will run from inside a python VM as any python app. I dont know whether this is a disadvantage per se but for those that think that what to consider Cython as a complete replacement to C , must take this into consideration.

2) Its does not offer automatic wrapping for C libaries like Swig , so if you want to wrap Alot of C functions/ Libraries , then Cython is not the best tool for that job , but it may provide support for this in the future.

Sum Up

Cython offers C speed from inside python with a tiny amount of recoding, it can be uses . Bare in mind that it offers alot of C features not mentioned here so the best you can do is visit the website and read the excellent documentation .

Here is the Cython website.

http://cython.org/

Links

Links offering cython benchmarks and additional information

http://prabhuramachandran.blogspot.com/2008/09/python-vs-cython-vs-d-pyd-vs-c-swig.html

http://www.behnel.de/cython200910/talk.html

http://behnel.de/cgi-bin/weblog_basic/index.php?cat=11

http://carlo-hamalainen.net/blog/?p=16

This one is a benchmark that show an almost 1000 times speed up over python but it uses pyrex ,bare in mind that Cython is based on pyrex so the same speed should apply. Also note the C speed it 2.15 seconds while Pyrex is 2.5 that is even less than 40% diference.

http://www.scipy.org/PerformancePython

Java vs Python

2009-11-23T23:54:00.002+02:00

There some things that made me conclude that Java is easier than python

1) Good documentation. Yes python has a very simple syntax , while java is more verbose but nothing can make thing any easier than good documentation, especially with third party libraries. Many of them actually require their users to read C++ documentation that defeats the purpose of using python in the first place.

2) Speed. Python is very slow, and even this does not show very often only for CPU intense tasks , that does not mean that python does not consume too much CPU. Again this might not be the problem for non intense CPU stuff, but because I working with midi and audio it makes my life harder.

3) Lack of a good IDE, IDEs is an essential part of RAD and none of the IDEs that support python works in a way that is hassle free. Especially in the GUI design department these IDEs leave alot to be desired.

I love the python syntax, it is surely the best of the best, that is why I have jython close at hand , but overall, at least for me what killed python is bad documentation and fragmented cross platform availability of libraries ( I have even experienced severe problems into making python work on macos).

I dont see python conquering the universe, the best language is yet to be invented. Its a great language however and alot of fun to use.

I do understand that the 3 above may not apply in all cases. Some people do not use IDEs, their python libraries have very good documentation, and do not real need speed.

My issue with python are quite old, but it was now that I decided to make an app that via MIDI protocol will control external hardware synthesizers ( I make music as well -> www.soundclick.com/kilon ) . Problem one , finding the right GUI. Qt is not free, GTK need X11 to work in mac, and Wxpython has non existent official documentation. Problem two, finding the right MIDI library, again the documentation is non existent.

Also I did not like the pure python ides or the IDEs that support python via plugin. I ended up that I would had to use several programm to do what I want and that is not good.

Java already solved the above problems.

Another motivation is jython. Java developers hate it beacause it inherits the slowness of python. Python developers hate it because it does nto allow of the use of cpython libraries unless they are already implemented in jython and thus is tied to java library and thus is not really pythonic. And other people love it ,like me, because it unites easy python syntac with the power and popularity of java libraries.

The Red Dragon (part 4)

2009-03-14T19:18:00.000+02:00

Here is a viewport real time rendering with no aa and light. AA destroys my muscle tone, still too noobish with it.

The Red Dragon (part 3)

2009-03-14T19:17:00.000+02:00

Another update, the 4 feet are almost done , created several muscle tones for the torso as well, fined tuned the head abit , have not touched yet wings, neck and tail. Replaced the light , included AA and changed background for easier viewing.

I am open to any suggestions. Enjoy !

Next step

* Finish minor details of feet
* Work with wings , neck and tail

The red dragon (part 2)

2009-02-16T00:20:00.000+02:00

a new update. Nothing is finished here, I love to jump around and give detail or change general shapes until satisfied.

The Red Dragon

2009-02-12T10:08:00.002+02:00

Title : The Red Dragon
Tools Used : Blender 2.48a
Time Spent : 1 hour 10 m
Total Time Spent : 1 hour 10 m
Purpose : To build a red dragon jumping out of a cup, to be used as a logo for the programming language JYTHON (a unification of JAVA and PYTHON)

Jython Speed vs Java

2009-01-06T21:56:00.006+02:00

I have created a small benchmark , to test the speed of Jython when calling swing components and JAVA2D methods. I was aiming to 5x times slower speed in JYTHON but JYTHON proved me very wrong. IT was only 3 times slower than JAVA.

The benchmark was not only for speed reasons but also a way to learn Jython .

I share with you the code of both JAVA and Jython. You may run the test in your computer and share results.

The app is building a window and draws 1 point lines and then displays a very large button with the amount of nanoseconds it took to execute the program.

I run the test in a ACER ASPIRE ONE with 1.GHz Pentium Atom Processor, 500 MB RAM, 8 GB SDD HD and WINXP.

------------------------------------------------------------------------------------

JAVA CODE

------------------------------------------------------------------------------------



/*
 * To change this template, choose Tools | Templates
 * and open the template in the editor.
 */
package speed;

import javax.swing.JFrame;
import javax.swing.JButton;
import java.awt.color.*;
import java.awt.geom.Line2D;
import java.awt.*;
import java.util.Observable;
import javax.swing.JComponent;
import java.util.Observer;

public class Central {

   

    public static void main(String[] args) {
//Toolkit theKit = aWindow.getToolkit();
//Dimension wndSize = theKit.getScreenSize();
        long StartTime = System.nanoTime();
        JFrame aWindow = new JFrame("This is my window");
        CentralView view;
        view = new CentralView();

        aWindow.getContentPane().add(view, BorderLayout.CENTER);

        aWindow.setBounds(0, 0, 800, 500);
        aWindow.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        aWindow.setCursor(Cursor.getPredefinedCursor(Cursor.CROSSHAIR_CURSOR));
        aWindow.getContentPane().setBackground(Color.PINK);
        aWindow.setVisible(true);
        long EndTime = System.nanoTime();
        long TimeExec = EndTime - StartTime;

        aWindow.getContentPane().add(new JButton("Time of Excution in nano seconds:" + TimeExec));


    }
}

class CentralView extends JComponent implements Observer {

    /**
     *
     */
    private static final long serialVersionUID = 1L;

    public void paint(Graphics g) {
        Graphics2D g2D = (Graphics2D) g;

        for (double x = 0; x < 801; x++) {
            for (double y = 0; y < 501; y++) {
                Line2D.Double l1 = new Line2D.Double(x, y, x, y);
                g2D.setPaint(Color.BLUE);
                g2D.draw(l1);
            }
        }

        g2D.setPaint(Color.RED);
        g2D.draw3DRect(50, 50, 100, 100, true);

        g2D.drawString("A Speed Test ", 60, 100);


    }

    @Override
    public void update(Observable arg0, Object arg1) {
// TODO Auto-generated method stub
    }
}

-------------------------------------------------------------------------------------

JYTHON CODE

------------------------------------------------------------------------------------



# This line will import the appropriate swing library for your system (jdk 1.1 or 1.2)
from java import awt
from java import lang
from java import util
from javax import swing

class CentralView(swing.JComponent, util.Observer):
    def paint(self, g):
        for x in range(0, 800):
            for y in range(0, 500):
                l1 = awt.geom.Line2D.Double(x, y, x, y)
                g.draw(l1)

        g.setPaint(awt.Color.RED)
        g.draw3DRect(50, 50, 100, 100, 1)
        g.drawString("a nice square", 60, 100)

StartTime = lang.System.nanoTime()
view = CentralView()


aWindow = swing.JFrame('This is my window ')
aWindow.getContentPane().add(view, awt.BorderLayout.CENTER)
aWindow.setBounds(0, 0, 800, 500)
aWindow.setDefaultCloseOperation(swing.JFrame.EXIT_ON_CLOSE)
aWindow.setCursor(awt.Cursor.getPredefinedCursor(awt.Cursor.CROSSHAIR_CURSOR))
aWindow.getContentPane().add(view)
aWindow.setVisible(1)
EndTime = lang.System.nanoTime()
TimeExec = EndTime - StartTime
aWindow.getContentPane().add(swing.JButton("Time of Execution in nano seconds:" + str(TimeExec)))

A Christmas Song

2008-12-31T16:39:00.003+02:00

I wanted to make a Christmas Song about a Child looking at the window early in the morning and watching the snow fall slowly.

It is a way for me to wish Merry Christmas and a Happy new year to you and your family. Don't forget to smile , cause life is beautiful even at its worst.

The song is called "First Christmas Snow" and it is made solely on a YAMAHA MOTIF ES6. You can listen to it with the player on the right.

XSI-> TheShark -> Unfinished

2008-12-24T14:30:00.008+02:00

In case you are wondering what happened to my reptilious shark , it was left ufinished of course. But it turned out well. The reason I did not finished is because i tried to sculpt scales on its body resembling a crocodile but it was a bit difficult. It required a high detail mesh and my computer did not allow it (only 2 GHz at the time and a low spec graphic card) and that was my excuse for quiting.

But I managed to sculpt properly the model , so I share it with you now , some people may find it worth their time.

This is the model , sculpted in Zbrush and rendered in XSI

and this is the wireframe

Click the photos for a larger view.

Blofeld Editor VST with JAVA

2008-12-24T12:41:00.003+02:00

I have already started making a blofeld editor using the VST framerwork from JAVA with the help of the jVSTwRapper . The editor will probably implement the basic functionality of Waldorf Blofeld synth and will exclude any sysex related features like the arpeggiator and utility parameters which can be unstable in some hosts. Building a very good looking GUI is the purpose as well. But for now a non GUI version is the highest priority which will control alla CC controllable parameters of the Waldorf Blofeld synthesiszer.

I have already made a first version which can control the cutoff of the first filter but I experience problems with making midi pass thru the editor. As soon as I solve this problem , then the non gui editor will be just a matter of time ;)

Watch this space for all updates.

XSI->The Shark->Step Two

2006-02-18T13:49:00.000+02:00

As I promised i finished the general shape and added fins and tail. Here is the render region of the right side.

XSI -> The Shark -> Step One

2006-02-18T01:12:00.000+02:00

I have finished the general shape of the shark and added the fins. I will try to add some pictures tomorrow.

Genesis

2006-02-18T00:51:00.000+02:00

This is the first post. I will post here my progress with XSI and other hobies...