LinuxMusicians

the fact that they differ each time i close, and then reopen the editor, indicates that the host is not just hiding it, but actually destroying it, and recreating it again.. isn't it? Yes, so it must be something different then that. Unfortunately I'll be offline for a week now, because of my work....

skei wrote:be warned, it is "in progress"

development is progress, isn't it?

I can't find your X event loop in the source, could you give me a pointer were it is?

This is a example of Xputty:

System: Host: box Kernel: 5.0.7-rt4 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Cinnamon 3.8.8 Distro: siduction 18.3.0 Patience - cinnamon - (201805132102) base: Debian GNU/Linux buster/sid CPU: Topology: Quad Core model: Intel Core i5-7400 bits: 64 type: MCP arch: Kaby Lake rev: 9 L2 cache: 6...

btw, why does my editor works perfectly the first time i open the editor, with cairo and all, but not after i close and then immediately reopen it? Hard to say, do you host your code public somewhere? Most likely is that the host didn't shot down the interface, but only hide it. Then, on the next r...

I've seen such behave often. First attempt is: Only do drawing to screen in the expose event callback. Never ever call flush. As this will only hide a bug in your source. Send a expose event for to window when needed. Second: When use cairo, use cairo_push_group before draw anything to the surface, ...

i found that when i started using xcb instead of 'pure' xlib, i had to put flushes in a lot of places, as xcb doesn't automatically flush as much as xlib.. haven't gone through it all and tested which of them is actually necessary.. will do later.. When I need to re-draw a widget, I send a expose c...

as i use both xcb/xlib drawing primitives (to blit the backbuffer to the screen/window), and cairo (for drawing into the backbuffer).. I don't do that, I use for drawing a double buffered cairo xlib surface (don't use a cairo image surface to draw operations with xlib !!) and draw only with cairo. ...

the gui is pure xlib (xcb) at the moment (but double-buffered).. i also have cairo graphics support in there already, but i need to squash a few bugs before it can be used.. You may be interested in my damn tiny abstraction Layer to create X11 window/widgets with cairo surfaces It use only plain Xl...

This looks really cool.
I will use it, please do the move to open source.

. . . and now have a example LV2 plugin which shows how to use Xputty to create LV2 plugin UI's.

well, dell is well known for it's linux support. You could select, when order, if you would get your PC with windows or Ubunut:
https://www.dell.com/en-us/work/shop/de ... sc/laptops

A nice review by SuperFunAwesomeHappyTime Pedal Show on the MOD DUO using the ValveCaster by guitarix:
https://www.youtube.com/watch?v=TTiUe1wKj1M

Yes, guitarix work with other buffersizes as well. But the convolver not. So No cabinet, No presence and No ampimpulse.

It is. The magic to Split the dsp over several cores is done in jackdmp, but the bare boone requirment therefor is, well, multiple callbacks.