Thanks - yes - they do work in qtractor (and Ardour 3 I think) but I really prefer midi editing/mixing in Muse. Seems like it might be a bug in the Muse implementation so I have also reported it there..glokraw wrote: I have Hive (and the rest of the u-he herd) working fine with qtractor in pclinuxos.
Used an rpm from http://sourceforge.net/projects/qtracto ... tor/0.6.6/
an older one than is currently found.
(I assume the newer qtractor releases at the link are even better, but I don't
often fix what ain't broke )
a CD sized iso to make a live/install CD is available here:
http://www.pclinuxos.com/get-pclinuxos/lxde/
synaptic is the package manager.
Cheers
Linux public beta (4408)
-
- KVRist
- 52 posts since 10 Jul, 2007
-
- KVRer
- 28 posts since 24 Jul, 2007
There are actually at least two bugs in MusE's vst implementation:
1. MusE does not call effSetSampleRate and effSetBlockSize before
effMainsChanged in the plugin activation.
This is the reason for the crashes you mentioned.
2. MusE does not call XInitThreads at the start of main.
This leads to a crash as soon as you try to open Hive's native GUI.
Apart from MusE's bugs, there seems to be a bug in Hive's GUI code as well.
It takes up 60% of CPU power of one CPU cores (in any Host) even if there is no update of the GUI necessary.
Cheers
1. MusE does not call effSetSampleRate and effSetBlockSize before
effMainsChanged in the plugin activation.
This is the reason for the crashes you mentioned.
2. MusE does not call XInitThreads at the start of main.
This leads to a crash as soon as you try to open Hive's native GUI.
Apart from MusE's bugs, there seems to be a bug in Hive's GUI code as well.
It takes up 60% of CPU power of one CPU cores (in any Host) even if there is no update of the GUI necessary.
Cheers
- KVRist
- 417 posts since 27 Mar, 2014
I don't have this issue at least in the Bitwig Studio.Drumfix wrote:Apart from MusE's bugs, there seems to be a bug in Hive's GUI code as well.
It takes up 60% of CPU power of one CPU cores (in any Host) even if there is no update of the GUI necessary.
-
- KVRer
- 28 posts since 24 Jul, 2007
I have the issue with every host, including bitwig (1.1.7)
Hive Gui closed -> xorg 1.0% compiz 0.2%
Hive Gui open -> xorg 45-49% compiz 9-10%
Computer with CPU Athlon II x4 2,6 GHz, ATI onboard graphics
No such behaviour with Diva...
Hive Gui closed -> xorg 1.0% compiz 0.2%
Hive Gui open -> xorg 45-49% compiz 9-10%
Computer with CPU Athlon II x4 2,6 GHz, ATI onboard graphics
No such behaviour with Diva...
-
- KVRAF
- 9123 posts since 6 Oct, 2004
The best linux Hive gui behavior I have seen, is with an nvidia card,Drumfix wrote:I have the issue with every host, including bitwig (1.1.7)
Hive Gui closed -> xorg 1.0% compiz 0.2%
Hive Gui open -> xorg 45-49% compiz 9-10%
Computer with CPU Athlon II x4 2,6 GHz, ATI onboard graphics
No such behaviour with Diva...
using an official nvidia 3D driver. It's the default in pclinuxos,
no compiling to do. The other u-he plugins also do well with that.
Whether in native linux, or various dll's in wine, along with IK, NI, Cakewalk etc
My 2 pennyworth.
Cheers
-
- KVRer
- 28 posts since 24 Jul, 2007
Well i sure not go and get a new graphics card to work around some plugin's
graphics bugs. I also tested presswerk, whose gui has an even higher cpu load (over 60% at normal size). When reducing the size (to anything smaller than normal)
there are drawing bugs (when clicking on a control, additional lines that don't disappear)
After all this is the place to report bugs, isn't it?
And again, with Diva i neither have this high cpu load nor the redrawing bugs..
So i know they can get it right.
graphics bugs. I also tested presswerk, whose gui has an even higher cpu load (over 60% at normal size). When reducing the size (to anything smaller than normal)
there are drawing bugs (when clicking on a control, additional lines that don't disappear)
After all this is the place to report bugs, isn't it?
And again, with Diva i neither have this high cpu load nor the redrawing bugs..
So i know they can get it right.
-
- KVRian
- Topic Starter
- 814 posts since 26 May, 2013 from France, Sisteron
Hello,
I just bumped the latest version to 3462.
- the installer now works with posix shells like dash
- fix for the third party theme support
- improvements to the UI rendering, but it does not fix some drawing issues like those in Bazille
Enjoy!
I just bumped the latest version to 3462.
- the installer now works with posix shells like dash
- fix for the third party theme support
- improvements to the UI rendering, but it does not fix some drawing issues like those in Bazille
Enjoy!
-
- KVRer
- 9 posts since 22 May, 2007
Thanks abique!
-
- KVRian
- Topic Starter
- 814 posts since 26 May, 2013 from France, Sisteron
Yes it is the right place!Drumfix wrote:Well i sure not go and get a new graphics card to work around some plugin's
graphics bugs. I also tested presswerk, whose gui has an even higher cpu load (over 60% at normal size). When reducing the size (to anything smaller than normal)
there are drawing bugs (when clicking on a control, additional lines that don't disappear)
After all this is the place to report bugs, isn't it?
And again, with Diva i neither have this high cpu load nor the redrawing bugs..
So i know they can get it right.
I could reproduce the bug. I have to catch some X11 event which would tell me that the window is not visible anymore. (If you already know which event it is please go ahead ^^).
Also we could do some optimizations for the scaling.
Thanks for the report!
-
- KVRer
- 28 posts since 24 Jul, 2007
@abique: Why would you want to know if the window is visible or not?
Usually all that is needed is to know which parts of the window get visible.
The information of whether the window is visible/partly visible/not visible
you get by checking VisibilityNotify events
But usually what's really important is, which parts of the window get visible.
This you get by checking Expose/Graphics Expose/No Expose events.
For lowlevel X11 programming i recommend reading http://tronche.com/gui/x/xlib/
Usually all that is needed is to know which parts of the window get visible.
The information of whether the window is visible/partly visible/not visible
you get by checking VisibilityNotify events
But usually what's really important is, which parts of the window get visible.
This you get by checking Expose/Graphics Expose/No Expose events.
For lowlevel X11 programming i recommend reading http://tronche.com/gui/x/xlib/
-
- KVRian
- Topic Starter
- 814 posts since 26 May, 2013 from France, Sisteron
Thanks a lot Drumfix,Drumfix wrote:@abique: Why would you want to know if the window is visible or not?
Usually all that is needed is to know which parts of the window get visible.
The information of whether the window is visible/partly visible/not visible
you get by checking VisibilityNotify events
But usually what's really important is, which parts of the window get visible.
This you get by checking Expose/Graphics Expose/No Expose events.
For lowlevel X11 programming i recommend reading http://tronche.com/gui/x/xlib/
So right now I only handle Expose events which tells me which region to update.
I'm checking if I receive the other, because it seems that being embedded into an other window may hide some events right?
-
- KVRAF
- 9123 posts since 6 Oct, 2004
I would get the best graphics card/driver in my budget, regardless of software issues.Drumfix wrote:Well i sure not go and get a new graphics card to work around some plugin's
graphics bugs.
It's not just about perceived bugs in Hive/Presswerk...it's the whole OS gui interaction.
The more plugins and audio apps you open, the more using superior graphics cards and drivers is important, perhaps crucial, to a successful recording session.
If using a certain video card and driver eliminates, or partially eliminates problems,
it would seem the problems are not completely in the plugin code?
Beyond that, not all kernels and kernel maintainers are equal, some distros are
just better than others, for some tasks. Maybe it is easier to code for
beached whale operating systems like windoze and 0sEX,
than the massive pod of leaping and diving dolphins that we know as linux?
Cheers
-
- KVRian
- Topic Starter
- 814 posts since 26 May, 2013 from France, Sisteron
The Visibility thing is done and should save some CPU for the next release.
The other CPU issue seems related to the high quality of the pixmap and the scaling. Something that can be improved
PS: as a workaround, if the UI is taking too much CPU on your computer, you can try to go to the data folder and downscale all the images by a factor of two. Only do it if you know what you're doing
The other CPU issue seems related to the high quality of the pixmap and the scaling. Something that can be improved
PS: as a workaround, if the UI is taking too much CPU on your computer, you can try to go to the data folder and downscale all the images by a factor of two. Only do it if you know what you're doing