Blog-posts are sorted by the tags you see below. You can filter the listing by checking/unchecking individual tags. Doubleclick or Shift-click a tag to see only its entries. For more informations see: About the Blog.
previously on vvvv: vvvvhat happened in October 2016
so there year is coming to an end and it feels we're only getting started...with beta35 being scheduled for a release soon™ we have a bughunt running at the moment where you can win one of 2 lattepandas. there are not too many reports in yet, so your chances are still very high to win. for all details please see: Find a Bug, win a Panda (latte).
Now check out the completely new NODE website with the NODE17 announcement and save that date!
And then have a look at the fancy new About Dialog we spent beta35 before checking out what more happened last month:
and quite some updates:
Again we have a couple of teasers, that is screenshots of crazy things that hopefully at some point will become available for everyone..
microdee did a proper blogpost: meanwhile-at-microdees-lab-rectpack while others just posed around:
And what is this?
And more gems from:
microdee continued his series of vveekend vvorkshops with two episodes that are ready for you to watch:
To watch those or any of the past workshops head over to the vveekend vvorkshop youtube channel.
Going prettey good. With the feature-freeze in place we're now mostly fixing the buggers we get in via the bughunt and the ones we're still aware of. Also we're now doing a first round of ui-performance tweaks in order to make it a bit more pleasent to work with. Also the networking (udp, tcp) core-library is getting in shape and research is underway regarding all things async..
Read our two recent progress reports here:
Anything to add? Please do so in the comments.
Have a good patch!
previously on VL: vl-progress-report-3
on the way to catch up with what you know and need from vvvv, the first choice for expanding VL core library was to work on file thingies. The following should look extremely familiar and probably quite unexciting for you:
These guys do exactly what you would expect them to do: read from file, respectively write to a file. as a convenience nodes you have string versions, the standard ones give you bytes.
since it's 2016, these nodes do their work asyncronously, hence these output pins, which keep you informed about the working status, giving you the opportunity to draw some nice loading animation.
it wouldn't quite feel like vvvv if the curious ones could not actually peek inside the node to see what's going on
looks a bit overdone for such a simple thing, right?
the motive for the splitting up into File and the actual IO operation has a couple of (imho) good reasons:
no need anymore to load the whole file and then decide what to do with the content. you can for example parse the header of a video file, look up some frame offset and directly do a partial read of just the blob you are interested
there are a bunch of ways to access files. now you can actually control all of that. one reason might be security, since you can decide, whether anyone else can read or write or even delete the file at the same time. you can set it to forcibly create a new file, so you don't accidentally overwrite something existing.
another reason is performance, you are welcome to dive into the deeps of the web to find out which combination of modes causes which thread to do the work. we tried to set the defaults for best performance for parallel reading.
the File node actually returns the FileStream. so all these operations can instantly be used with anything else, that is a stream (which is a lot of things in the .net world)
let's try something different: how about you find a bug in vvvv/vl and you get a LattePanda in return?
We're targeting the beta35 release for end of this year. beta35 will easily be the most feature-rich release of vvvv ever in that it will be coming with a new alternative visualprogramming language called VL, besides quite some other new stuff and bugfixes.
In order to make sure beta35 gets a good start we're on a feature-freeze in the alpha-builds now and are planning to invest the coming weeks for bug-fixing only. And this is where you come in: We'd like to encourage you to give the latest alpha-build a ride and see if you stumble upon anything that we better have fixed in beta35.
Every bug counts, but note that for this bughunt we're specifically interested in bugs that are new in current alpha builds. So either a bug in one of the new features (listed below), or something that did work in beta34.2 but now is broken.
We have 2 prizes to give:
Both are the same LattePanda PC:
We realize it may be harder for you to find bugs in VL since there isn't any proper documentation or demo yet. We hope you can see this as an extra challenge. Use it as you would intuitively use it and see what you stumble upon. You're of course also very welcome to ask any kinds of questions regarding VL on IRC or in the forum and we'll try to guide you to your first bugreport..
To give you an idea of what to look forward to with beta35 and where to specifically check for bugs, here is a collection of the most recent relevant blog-posts introducing new features:
So if all goes well the two of you will own a little LattePanda and we all will have a shiny new beta35 by end of the year. What do you think?
I decided to write a little devblog here for stuff I'm adding to my packs, because as you could notice I'm not too good with keeping you guys updated about what's going on around my contribs, not anymore! so for start:
newest addition to mp.essentials is 2 rectangle packing nodes most obviously used for texture packing to an atlas with 2 different algorithms. RectPack (2d Czachurski) and RectPack (2d ChevyRay). Versions are actually carrying the name of the guys whom I ripped of.
The more advanced and most of the cases better algorithm is provided by Patryk Czachurski here: https://github.com/TeamHypersomnia/rectpack2D I ported his code to C# and you can see the result with 413 random rectangles in the above screenshot. Each rectangle has sides between 250-1250 pixels and the Czachurski node packs them into ~15080×15074 pixels sized space. This algorithm also provides multiple sheets (or bins or slices) of atlasses if the input rectangles wouldn't fit in the desired box size. Here is an example with textures using 8448×8832 pixels:
The other algorithm provided by Chevy Ray Johnston here: https://github.com/ChevyRay/RectanglePacker might be easier to use, less intelligent and you don't have to specify a box size.
However notice it is not at all as efficient as Czachurski in terms of filling the space with lots of rectangles. Same random rectangles are using 22845×24232 pixels. It does a slightly better job at mostly square shaped textures though (here 8448×8704 pixels)
you can get it here: md.ecosystem.mp through vpm. Enjoy!
Immediately after writing this post I've noticed some differences between my results and the results at Czachurski's repo and I've noticed that apparently C++ sort is the reverse of C# LINQ sort. Now the Czachurski node produces results are replaced now they are more similar to the original ones.
Let me introduce you to the new About patch: Spiced up with some usefulness here is what Alt+A can now do for you:
And finally we have this cozy place to feature a listing of all additional contributors. The list is gathered from the "Author" tag in any addon (plugin, effect, module) you have installed and weighted by the number of their occurrences. So if you feel your name is missing or not high enough on the list you know what to do..
anonymous user login