Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


danilo2 last won the day on February 21 2016

danilo2 had the most liked content!

Community Reputation

13 Good

About danilo2

  • Rank

Personal Information

  • Name
  1. Hi guys! My name is Wojciech Danilo and I'm one of the early founders of ( https://flowbox.io ), a node based VFX platform allowing for the fastest totoscoping and compositing workflow on the market. If you like Houdini, you should fell in love with the ideology here. Seriously, check out the video: Prior starting Flowbox I've been working for years as senior TD in various motion pictures studios across Europe and was visiting my lovely odforce forum everyday. Right now I'm spending here much less time and tbh, I'm missing you guys a little bit, or maybe more than just a little bit . But putting aside my personal feelings, I'd love to ask you guys for a small help and would be very, very thankful for it. I'm not longer full-time involved in this project (I'm running https://luna-lang.org ), but I love the guys behind Flowbox and I admire their passion to deliver the best tool on the market. They've just released Flowbox 1.7, and its a big release, with integrated Mocha Planar Tacker, a new curve editing tools combining B-splines and Beziers together and a ton of other tools (again, check out the above video). Mikolaj Valencia (Flowbox's CEO) together with Carlos Conceicao (Road To Comp) will have a live facebook webinar tomorrow, so if you are interested in Flowbox technology, its future development or would like to ask us some questions, please join us there. It would be more than awesome to have you guys with us Webinar: 14 of August at 9 PM (WEST time) (1 pm PDT | 4 pm EDT | 10 pm CEST | 1:30 am IST | 3 am CST): https://web.facebook.com/events/666426783714447/ And of course in case of any questions, I'd love to answer them here as well! PS: We've just started a Flowbox discord chat channel here. You are very, very welcome: https://discordapp.com/invite/c7AF6T?utm_source=Discord Widget&utm_medium=Connect
  2. Hi! I find it very interesting so I share it with you. Mikolaj, Flowbox (flowbox.io) founder, tells about their approach: https://web.facebook.com/projroadtocomp/videos/vb.383690282000097/455475341488257/?type=3&theater
  3. Thank you and I'm sorry for overlooking notification about your reply @Nico D.: It would be straightforward to bind Luna to Houdini SDK API, so you will have full power of the API from within the Luna nodes. I think this is one of the most promising ways to do it for me. I'm not sure though if we will focus in short time on doing it, but I would be very interested in this topic personally. @lkruel: Yes, documentation is available for the testers and will be released into the public when we Open Source Luna Are you asking about language interoperability? You are able to easily create binding in Luna to libraries in other languages, like Haskell, C or JavaScript (more languages will be supported in the future). This feature is much better described on our website Did I answer your question? All the best, Wojciech
  4. Hello guys! I've posted a very similar message to sidefx forum, but I would love to post it here too. I was using this forum often in the past and I know that if you're looking for some tech geeks, odforce is the place number one to look at! I'm an old Houdini user. By "old" I mean that I was using it for years, was working as TD in movie studios and have created a ton of assets used until today in some a-class movies around the world. I'm no longer using Houdini at the daily basis (which I miss sometimes), because together with a group of brilliant developers we were creating a completely new visual programming solution. Something that would change visual programming once and for all – and I think we've managed to accomplish that task I'm writing here because: 1) I love you as the community and I feel really strong connection with you guys. 2) We are thinking about incorporating Luna into Houdini one day, so this topic could be also relative to Houdini's development. Some of you might recognize Luna and it's connection to Flowbox (http://www.luna-lang.org You can ask me any questions you want - here or via mail provided at the Luna's website All the best, Wojciech
  5. Flowbox project 

    @marty: you are right - knowing what to expect from new release is very important We will keep that in mind
  6. Flowbox project 

    We have sent a survey for all the people, who signed up on our website. We want to thank you for the great answers and feedback, we get from you! We really appreciate it. Thank you for all great questions In case of any new questions or ideas, feel free to ask them here or write directly to me: wojciech [at] flowbox.io If you did not signed up yet, do not worry - we allow for signing up to the alpha release and we will send surveys to all new people also
  7. Flowbox project 

    @marty: You pointed very important topics again! We also think, this is very good idea. We will probably o with it Sesi model is good, but far from perfect to me. I love the way Houdini is released and we plan to automate our releasing process at some time to create daily builds. It will be not available by Alpha, but we plan to introduce it as soon as possible. We want to provide an issue tracker for you (like Jira, Bugzilla, etc) - to make it clear, what are the known bugs, what we are working at, etc. This brings very good clarifications of what is happening to the project and track status of bugs, you are interested in. We were thinking about creating a place, where everybody would be able to write, what functionality would love to see or vote for existing ideas. The most voted ideas would have priorities over the others and would be implemented first. What do you thing of such idea?
  8. Flowbox project 

    @marty: Hello! This is a very important question. We've got a strong technical team, but as you pointed out - Sales / Marketing is driving the business in the future. We've got some people who made strategies for Forbes 1000 companies, so we are aware of this issue. We want to release Flowbox basing of your needs. We strongly believe in customer based development process. We plan to release Flowbox free for non commercial usage. We are even thinking of releasing some parts of it as Open Source software. We strongly believe in the community spirit. I believe, that one of the most important things for a product to live, is a community of people using it. We love sharing our ideas, knowledge and technology, so we also believe, there will appear some community based high-end tools based on Flowbox, if it will prove, that it is the next level data processing platform. I've used "believe" word too many times, haven't I? This is not a direct answer to your question, but I wanted to share with you my point of view and our beliefs. I do not think this answers your question also. Do you have any ideas or comments? Could you ask more precisely please?
  9. Flowbox project 

    Hello once again! There is some bigger discussion about flowbox on CG Society forum. If anyone is interested in more technical insight into Flowbox, I recommend taking look at it: http://forums.cgsoci...60&page=1&pp=15 @Skybar - I've used there one answer written originally for you, I hope you dont mind it All the best! Wojtek
  10. Flowbox project 

    @thetheo: Flowbox (see no FX here) is made with at all the people in mind, who would like to create custom solutions like 2D tools, simulation tools or sound processing tools. It allows them to create these tools in a visual / textual environment and share with other using an online node repository. Flowbox FX (here is the FX) is Flowbox with nodes aimed at (right now) offline image processing, but we do not exclude possibility, that it will contain in the future reactive components by default (like vvvv or Touch Designer). If there will be more people who will need such functionality, we will add it to the basic version. What I think is very important, if you know Touch Designer or PD and you know how data flows between the nodes, you would be able to create components known from these solutions even if they are not included by default. And if you are even more technical - you will be able to create custom DSP solution based on our platform and distribute it as your own product, allowing end users for visual way of working Does it make sense to you?
  11. Flowbox project 

    @TomRaynor - Thank you If you've got any further questions, feel free to ask me @Skybar - of course you may! Even you should On the beginning, please read my answer above. Our team is focused right now on image processing (including image compositing) in general. I do not think it will allow you to replace your "pure artistic" photoshop workflow at the moment - of course you are free to define nodes, which will allow for drawing with brushesh, applying filters, and anything you're doing in everyday "photoshop life", but we want deliver nodes aimed at general image composition on the beginning, like AE or Nuke but with much greater flexibility. Of course we do NOT want to cover all the Nuke or AE functionality with our Alpha product As you can see, you can using our blocks (read nodes) or using textual Luna (or using them both of course) define custom operations - like brush painting, stencil brush tools, sound or scientific image analysis tools and share them (again, read nodes) with others using our online nodes repository. Your idea is interesting, because it would create a non-breakable node based photoshop operation history, isnt it? The main idea behind the project is, that we want to give more power, flexibility and performance to the user. So the user should be able to easy understand, extend, and share existing and new solutions. Of course if you are interested in developing your own tools for processing data (like creating node based photoshop-like tools with specialized interactive artistic toolset), feel free to contact me at wojtek@flowbox.io or contact@flowbox.io Did I answer your question?
  12. Flowbox project 

    @TomRaynor - please also look at the page http://flowbox.io/landing.php - there is no ipad to distrub you We are randomly showing pages to people - the light and dark one to see which one is "nicer" to you. Answering your question - right now Flowbox allows to process still images, but in the near future (probably up to alpha release) it will support processing sequences of them. It works right now on Linux, Darwin and Windows. We are focusing on these platforms at the moment, but Flowbox is designed to work also on mobile devices (like tablets, etc) - it consists of GUI and a Server, which can be run on the same device or can be distributed - GUI on thin client, like ipad and Server on some "bigger" machine. We have created a new dataflow programming language - Luna - which has got 2 representations - textual and visual one. (Yes, it is a real programming language). While connecting nodes, our compiler is analysing the flow, optimizing it and producing efficient binaries, which are processing images, automatically distributing the computations across available CPU cores and GPU. Flowbox is a data processing platform - it allows you to process any data in a visual way (you can write nodes to process for example sound, 3D graphics, drive simulations etc). Right now we are focused on Flowbox FX, which is Flowbox with nodes allowing for image composition and processing. I hope I've answered your question. If you've got further questions, feel free to ask me
  13. Flowbox project 

    Hello, I'm an "old Houdini user" I was working for few years as senior FX TD and OD FORCE forum was always my favorite one. Because of that I want to share some information with you - I've quit the job and started with a strong programmers team a Flowbox project. You can read more informations about it below: We’re making a new tool for processing images. We believe that our novel approach will speed-up your work and make your workflow more flexible. Flowbox FX refines the node-based approach. It offers a global repository of nodes for image composition, analysis and processing and allows you to fully use the power of your hardware with automatic CUDA/OpenCL acceleration. We’re going to release a closed alpha soon. Everyone who’s interested in our product — please let us know by signing up on our website. Visit: http://flowbox.io Best regards, Wojciech Danilo Flowbox co-founder
  14. Lets do some Lex Systems!

    Hi! Thank you for replies! I'm very happy of such positive feedback Currently you can not test the compiler, because I cannot (like the thesis) make it public. But I'm planning to rewrite this software and then I'll publish it Lex Systems and lex / flex are not related in any way The name Lex Systems stands for "L(Extended) Systems" or "Lexical Systems" (because it is a lot more than simple extension to L-Systems). One of the features that is better could be for example the fact, that you can describe wider range of context L-Systems. In standard implementations, the context of L-Systems could be only one character of an alfphabet, where in Lex Systems you could use an regular expression for context specification
  15. Hi! I dont know If I'm posting it in the right place, so if it's wrong, please move it to the right one A year ago I was writing my Bachelor of Science Thesis "Lex Systems - specification of high-level character processing language". I have been working for a long time on this programming language, which could very efficiently generate L-Systems and is a lot more powerful than standard L-Systems processors. Technically, it allows for definition of almost all languages of Chomsky's Type-2 and 3 grammars. Results I get were really good. I was planning that I would post them in a couple of months, because I wanted to start off with my blog or small website. But the reality was horrible. I am working as technical director in one of the film studios in Poland and in parallel I'm developing several open and closed source projects, so I've got so much work, that probably this website will not be alive for log time The following results are a year old, but this really does not matter Lex Systems is a variant of formal gramma, but more universal, than L-Systems. It even allows for writing standalone programs performing some computation, make some complex algorithms and of course generate L-Systems. The most powerfull feature is its syntax, which is very easy to learn (a lot more straightfoward than L-Systems syntax, but it is simmilar) and gives users a lot more control over the execution and data flow. This syntax is powerful and simple - rules in Lex-Systems could be as short as in L-Systems. What is really interesting is that my compiler of Lex-Systems is a LOT faster than Houdini's one (I tested it against Houdini 9,10,11,12 and 12.1 - almost the same results). It is written in C and it is optimized to get really good results and be stable even for large files. It seems, that my solution have a lot lower computational complexity, that Houdini's solution. I and a lot of people, that were reading and rating my work, have tested if results are correct. They are (we were testing if the resulting geometry is the same. Because of the size of the geometry, the tests were executed on dells workstation with 2*3.2GHz Xeon and 64 Gb of RAM). So lets put some facts in this post! I was testing the generation of L-Systems, not the drawing process in viewport! The tests are running against houdini batch and houdini master (fx) without displaying the results in viewport (for example by telling only the node to cook) some tests: premise: FFFA rules: A -> !"////////B B -> &FFFA for the first 14 generations results are similar, but next generations give us real feedback about whats going on: generation 17 - houdini: 0.84s, Lex-Systems: 0.29s generation 18 - houdini: 10.65s, Lex-Systems: 0.53s generation 19 - houdini: 24.25s, Lex-Systems: 0.87s generation 20 - houdini: 144.61s, Lex-Systems: 1.58s generation 17 - houdini: 345.49s, Lex-Systems: 2.58s generation 21 - houdini: 2,013.52s, Lex-Systems: 4.76s generation 22 - houdini: 3,887.33s, Lex-Systems: 7.28s generation 23 - houdini: crash, Lex-Systems: 14.28s Please notice, that the 22th generation took about 1 hour Houdini to process and only about 7 second L-Systems to get the same results! another example: premise: F+F+F+F rules: F -> F-F+F+F-F+F-F-F+F generation 3 - houdini: ~2*10^(−3)s, Lex-Systems ~2*10^(-3)s generation 4 - houdini: 2.7*10^(−2)s, Lex-Systems 4*10^(-3)s generation 5 - houdini: 1.01s, Lex-Systems 2.4*10^(-2)s generation 6 - houdini: 371.5s, Lex-Systems 0.2s generation 7 - houdini: after 7 hours we get 80% of generation process, Lex-Systems: 1.76s generation 8 - houdini: impossible, Lex-Systems: 15.97s generation 9 - houdini: impossible, Lex-Systems: 145.77s ------------------------------- Additional I created 2 more tools: a plugin for houdini, and pythons translator of L-System language to Lex-Systems language (it has less than 100 lines of code, because the basics of Lex-Systems are simmilar to L-Systems) As a result - all my previous tools that were using L-systems now work A LOT faster and allow for making animation of L-Systems parameters really fast. Due to some limitations in license of my thesis I cannot make it public (I have to talk about it with my university, but I've got not so much time). I would be happy to hear some feedback! If you would like, I will post some more info! Thank you, Wojciech Daniło