Blok

[GeorgeZ]

Well, it's all moving in the right direction at least

[S-N-S]

i am just starting to demo the demo version of BLOK in renoise,and i really like the look and the concept,but it still needs to "grow"alot before i would buy it especially at the current price tag.and besides i already own plogue bidule

some things i noticed while messing with it is

the GUI is a bit glitchy at times

and the sounds also got a tendency to glitch/slow response time

but i will test it some more,and looking forward to see where this will go

[Zephod]

The GUI glitches I am aware of (hence the current GUI rewrite), but can you please elaborate on the audio glitches/response time?

About the gui rewrite - here is a small (standalone, no audio) preview of my current progress: http://www.blokmodular.com/dev/blok-wit ... test-6.zip

This would be r312

changelog since last svn post:

Code: Select all

r309 - Small redraw fix for selection rectangle.
     - Small coordinate fix for selecting while screen was scrolled.
r310 - New cpgui control: ParamButtonStrip (for mode-selection.. like arp modes
     - Arp ticker display now works in cpgui
     - Small event handler changes for cleaner redraws in cpgui RootControl
r311 - Small site update (long overdue)
     - Site news works again
r312 - Small stability fix for RootControl (OnClose message handler changed)

[Zephod]

whoops.. wrong file ended in the zip..
http://www.blokmodular.com/dev/blok-wit ... test-7.zip would be the correct one.

[todd_r]

...here is a small (standalone, no audio) preview of my current progress...

Thats a million times better under wine

[Zephod]

I have updated my build scripts and the blok homepage.

Now my latest development betas are also available for download on the homepage.

Registered users can get the beta for the latest full version in the userarea.

http://www.blokmodular.com

Please note that the current betas still have some instabilities due to the massive gui-library switchover (and some minor graphical anomalies.. still pixelhunting to make it 1:1 with what I had)

The new betas should
1) be much smoother/directer in their interaction
2) no longer have any scrollbar-rendering glitches
3) look fine on wine (no more dependency on GDIPlus which is really badly supported on wine)
4) have some more blocks to play with

Please check the changelog to see what has been changed since the last stable version.

[Zephod]

http://blokmodular.com/changelog.php which is available here.

[Ingonator]

I have updated my build scripts and the blok homepage.

Now my latest development betas are also available for download on the homepage.

Registered users can get the beta for the latest full version in the userarea.

http://www.blokmodular.com

Please note that the current betas still have some instabilities due to the massive gui-library switchover (and some minor graphical anomalies.. still pixelhunting to make it 1:1 with what I had)

The new betas should
1) be much smoother/directer in their interaction
2) no longer have any scrollbar-rendering glitches
3) look fine on wine (no more dependency on GDIPlus which is really badly supported on wine)
4) have some more blocks to play with

Please check the changelog to see what has been changed since the last stable version.

I just installed the new beta version of Blok (v314 beta) and tested it in Ableton Live 8.2 (latest version, published this week). Seems to be stable and new features like e.g. the improved legato, the Modwheel module and the Aftertouch module seem to work nicely. I have added all three features to one of my lead sounds so i could control the cutoff with the Modwheel and the vibrato with aftertouch now.

The only "bug" which i found is that i could not open the editor window of a patch from the bank by double-click like before but only by clicking on "open patch". I guess it's not a bug but just a change.

UPDATE:
One "real" bug. When i open the GUI of Blok beta in Ableton Live 8.2 (on Windows 7 32-bit) the CPU load stays at 18% all the time (at my Core 2 Quad Q6600 CPU), even when not playing notes. This disappears when closing the GUI.
18% on a Quad Core would mean about 70-80% on a single core system.

[Zephod]

Can you send me the patch you were displaying when the GUI peaked at that amount of cpu?

I might be overdoing it a bit with the animation-update-rate, also need smarter handling of dirtyrects... still tuning it all

btw - if your audiohost is set up correctly, GUI cpu usage is not an issue.. the update rate will degrade from "REALLY DIRECT" to a bit slower when audio is peaking, but it should never interfere with the audio. Nevertheless I'll still spend quite some time optimizing before the blok version with the new gui lib is "not beta".

Thanks for the tip about the doubleclick, I nearly forgot to add it back in in the new gui library!

I have uploaded a new beta that adds the doubleclick back in. (v 316)
The animation rate in this version is also a bit lower to mitigate the cpu problem until Ive really optimized it.

[Ingonator]

Can you send me the patch you were displaying when the GUI peaked at that amount of cpu?

I might be overdoing it a bit with the animation-update-rate, also need smarter handling of dirtyrects... still tuning it all

btw - if your audiohost is set up correctly, GUI cpu usage is not an issue.. the update rate will degrade from "REALLY DIRECT" to a bit slower when audio is peaking, but it should never interfere with the audio. Nevertheless I'll still spend quite some time optimizing before the blok version with the new gui lib is "not beta".

Thanks for the tip about the doubleclick, I nearly forgot to add it back in in the new gui library!

I have uploaded a new beta that adds the doubleclick back in. (v 316)
The animation rate in this version is also a bit lower to mitigate the cpu problem until Ive really optimized it.

I found that it doesn't matter which patch but the CPU load is related to the amount of modules used. Depending on the complexity of the patch the CPU load is between 17% and 75% on a Core 2 Quad Q6600 CPU !! This is just by opening the GUI, without playing notes. While playing notes the additional CPU load is in "normal" range, around 3% with one voice of a middle complex patch.
When i close the GUI the CPU goes back to normal but when i play notes it's again at that high CPU load.

I'll test the new beta you have uploaded and send you my current patches by email.

[Zephod]

I've done my first rough guess of the problem (I was not able to reproduce that excessive cpu usage here yet.. ) but lets see if this improves matters -> beta v317 uploaded!

[Ingonator]

I've done my first rough guess of the problem (I was not able to reproduce that excessive cpu usage here yet.. ) but lets see if this improves matters -> beta v317 uploaded!

I just sent you a link for my patches as a PM. I'll try that new version too.

[Ingonator]

I've done my first rough guess of the problem (I was not able to reproduce that excessive cpu usage here yet.. ) but lets see if this improves matters -> beta v317 uploaded!

I just sent you a link for my patches as a PM. I'll try that new version too.

The CPU problem seems to be fixed with the beta v317 and double-clicking works too now.
Always impressive how fast you are at fixing problems. Sometimes faster than i could write a reply here...

[Zephod]

Thanks a lot! Nice sounds in there + nice case to optimize

r317 is not yet the fix. (i can already tell you that)

I'll try and come up with something.

[Zephod]

ah, our replies crossed

glad to know this already fixes your case, but I still think I can do much better *still optimizing*