Linux public beta (4408)

[Beamboom]

Congrats on choosing Hive, such a fountain of jewels!

Thanks! It's great, I'm really pleased with the purchase, especially at that price.

Did you try minimize/maximize bitwig gui when such a freeze occurs?

How would you suggest I did that when no input device responds? Cause it was the entire desktop environment that was affected, not just this plugin.

Have you chosen a different size Hive gui than default? Perhaps some sizes
are more accurate with your display?

Nope, it was at default size. But I've not yet managed to reproduce this, so as of now I file this under "one of those things". I tend to have a lot of stuff running on my PC so it could just be coincidence.
That's my current theory. Let's hope it remains in the past.

[glokraw]

You catching me in vapid reading mode, inspired me to do some linux freezing studies,
and I found some interesting resolutions to system freezes, many involving
ctrl alt F1 key combo, that leads to a new terminal, where commands can be issued.

I also find http://thelinuxrain.com/articles/gnome- ... nge-update

where a GNOME-shell challenge exists, with some interesting key combos, such as

CTRL + H to minimize an application.
CTRL + Enter on a selected application in the Overview to launch a new instance of an application.

So perhaps a gnome-shell user could do a ctrl alt F1, to avoid the lockup,
and then a ctrl H, to minimize a guilty app (I assume this requires a prior
assignment of the suspect app in gnome-shell settings)
and then revert back to the original X window, more details here:

http://askubuntu.com/questions/157617/r ... trl-alt-f1

Another anti-freeze idea, is to not use the setting
'memlock unlimited' in /etc/security/limits.conf but leave a small portion
of total system memory for wiggle room, in case a project bloat should occur.

Back to Hive, the Celestial preset by Julian Ray, is pretty wonderful.
Making a wonderful tune to use it well, will be challenging
Cheers

[Beamboom]

I found some interesting resolutions to system freezes, many involving
ctrl alt F1 key combo, that leads to a new terminal, where commands can be issued.

Would not work in my instances, it's always the first thing I try whenever the desktop environment misbehaves. The keyboard were really 100% dead. As were the mouse and the midi keyboard. But the system itself ran as usual (at least no visual lockups), it was just like someone unmounted all input devices completely.

But just for the record, I've not managed to reproduce this again.

Another anti-freeze idea, is to not use the setting
'memlock unlimited' in /etc/security/limits.conf but leave a small portion
of total system memory for wiggle room, in case a project bloat should occur.

Interesting idea, but I do not really understand how a memory leak/bloat could cut off all input devices just like that.

Back to Hive, the Celestial preset by Julian Ray, is pretty wonderful.
Making a wonderful tune to use it well, will be challenging

I have to check it out. There's tons of great patches already for Hive, the future looks really bright for this baby.

[Kimuchuu]

Will hive be release at the same time for both windows and linux?

[glokraw]

Another anti-freeze idea, is to not use the setting
'memlock unlimited' in /etc/security/limits.conf but leave a small portion
of total system memory for wiggle room, in case a project bloat should occur.

Interesting idea, but I do not really understand how a memory leak/bloat could cut off all input devices just like that.

Neither do I. I'm resigned to linux being forever beta, and willing to deal with it.
I have an old flaky computer, little memory, faulty design yada yada,
and some kernels have had severe faults leading to freezing. Something
occasionally triggers hal to poll sr0 incessantly, and a command must stop it.
One drive has a very small partition, and error messages can fill up the / disk space
if I fail to delete the huge logs (1.86 gig deleted prior to this session)
Some video drivers are weak, I use the official nvidia3D driver,
but some distros don't have what it takes. I'm ready for the weekend,
and it's only humpday

[StudioDave]

Hey abique,

Any news when we might see updates for the Linux versions ? My ACE is falling behind the times...

Best,

dp

[nonameyet]

Are the versions on the first page the latest? Or is there another place to get the latest version?

[psycha0s]

nonameyet, the versions on the first page are the latest Linux builds.

[nonameyet]

nonameyet, the versions on the first page are the latest Linux builds.

Oh ok thanks!

[kmatheussen]

Hi,

I've got an auomatically generated (and in this case, also anonymous) crash report
for Radium where the Podolski.64 vst plugin crashed. (the name of the currently running
plugin is part of the crash report, so I know it is Podolsko.64 that crashed.)

I don't know if you store debug information separately, but if you do, this might
be useful.

Code: Select all

0: crashreporter_posix.c:80     crash()
1: crashreporter_posix.c:97     crash()
2: ??:0 __restore_rt()
3: ??:0 VSTPluginMain()
4: [0x14f0ef] ??() ??:0
5: [0x14e4cb] ??() ??:0
6: [0x1a7b65] ??() ??:0
7: ??:0 _ZN11AM_VST_base20processReplacing3305EPPfS1_i()
8: juce_VSTPluginFormat.cpp:1056        _ZN4juce17VSTPluginInstance12processBlockERNS_17AudioSampleBufferERNS_10MidiBufferE()
9: Juce_plugins.cpp:318 RT_process()

Frame #0, #1, #2, #8, and #9 are from radium, the others are probably from Podolsky.64.

(The crash report also contains some OS-info, CPU-info and gfx driver info, if that is of interest. I can send that privately.)

[kmatheussen]

Hmm, that backtrace is probably very hard for you to use, even if you have stored the debug information, since the start address of the library is not known. However, coincidentally I managed to crash Podolski.64 myself right now. Here's the un-reproducable recipe, from memory:

1. Play some notes
2. Change preset (while playing some notes)
3. Hide gui (while playing some notes)
4. Show gui (while playing some notes)
5. Crash

Backtrace and info about where the plugin is loaded in memory:

Code: Select all

(gdb) bt
#0  0x00007fffcce78885 in ?? () from /home/kjetil/.vst/u-he/Podolski.64.so
#1  0x00007fffccdc70ef in ?? () from /home/kjetil/.vst/u-he/Podolski.64.so
#2  0x00007fffccdc64cb in ?? () from /home/kjetil/.vst/u-he/Podolski.64.so
#3  0x00007fffcce1fb65 in ?? () from /home/kjetil/.vst/u-he/Podolski.64.so
#4  0x00007fffcce70c37 in AM_VST_base::processReplacing3305(float**, float**, int) () from /home/kjetil/.vst/u-he/Podolski.64.so
#5  0x0000000000a2af0b in juce::VSTPluginInstance::processBlock (this=0x26d0af0, buffer=..., midiMessages=...) at ../../JuceLibraryCode/modules/juce_audio_processors/format_types/juce_VSTPluginFormat.cpp:1056
#6  0x00000000009f46ca in RT_process (plugin=0x26c36d0, time=37951616, num_frames=64, inputs=0x2eaa6a0, outputs=0x2e8aa50) at ../../../audio/Juce_plugins.cpp:325
#7  0x00000000006a5dfc in PLUGIN_RT_process (plugin=0x26c36d0, time=<optimized out>, num_frames=64, inputs=<optimized out>, outputs=0x2e8aa50, process_plugins=<optimized out>) at audio/SoundProducer.cpp:244
#8  0x00000000006abb1d in RT_apply_system_filter (process_plugins=<optimized out>, num_frames=<optimized out>, num_channels=<optimized out>, sound=<optimized out>, filter=<optimized out>, this=<optimized out>)
    at audio/SoundProducer.cpp:615
#9  SoundProducer::RT_process (this=this@entry=0x8fd8fa0, time=time@entry=37951616, num_frames=num_frames@entry=64, process_plugins=process_plugins@entry=true) at audio/SoundProducer.cpp:764
#10 0x00000000006a8561 in RT_get_channel (process_plugins=<optimized out>, ret_ch=0, num_frames=64, time=37951616, this=0x8fd8fa0) at audio/SoundProducer.cpp:806
#11 SP_RT_process_bus (outputs=0xf4403b0, time=37951616, num_frames=64, bus_num=<optimized out>, process_plugins=true) at audio/SoundProducer.cpp:907
#12 0x00000000006a5dfc in PLUGIN_RT_process (plugin=0x26d7ae0, time=<optimized out>, num_frames=64, inputs=<optimized out>, outputs=0xf4403b0, process_plugins=<optimized out>) at audio/SoundProducer.cpp:244
#13 0x00000000006aba8d in RT_apply_system_filter (process_plugins=<optimized out>, num_frames=<optimized out>, num_channels=<optimized out>, sound=<optimized out>, filter=<optimized out>, this=<optimized out>)
    at audio/SoundProducer.cpp:615
#14 SoundProducer::RT_process (this=0xf440320, time=37951616, num_frames=64, process_plugins=true) at audio/SoundProducer.cpp:765
#15 0x00000000006c7e4b in Mixer::RT_thread (this=this@entry=0x331ad20) at audio/Mixer.cpp:644
#16 0x00000000006c7f9b in Mixer::RT_rjack_thread (arg=0x331ad20) at audio/Mixer.cpp:685
#17 0x0000003b564163fd in Jack::JackClient::Execute (this=0x32f5ee0) at ../common/JackClient.cpp:565
#18 0x0000003b56435910 in Jack::JackPosixThread::ThreadHandler (arg=0x32f6050) at ../posix/JackPosixThread.cpp:59
#19 0x0000003b49c07d14 in start_thread () from /lib64/libpthread.so.0

(gdb) info sharedlibrary
From                To                  Syms Read   Shared Object Library
...
0x00007fffccd20210  0x00007fffccee4c11  Yes (*)     /home/kjetil/.vst/u-he/Podolski.64.so
...

It could of course be caused a bug in Radium, but since the crash is happening inside Podolski,
and VST plugins seems stable othervice in Radium, it's not unlikely to be a bug in Podolski.
Hope this can be of any help to you.

EDIT: Oh, and I haven't updaed the u-he plugins in a long time:

Code: Select all

[kjetil@ttlush Podolski]$ ls -la
total 10160
drwxr-xr-x  7 kjetil kjetil    4096 2015-02-08 19:03 .
drwxrwxr-x 13 kjetil kjetil    4096 2015-02-08 19:04 ..
drwxr-xr-x  5 kjetil kjetil    4096 2015-02-08 19:03 Data
-rwxr-xr-x  1 kjetil kjetil  739464 2015-02-08 19:03 dialog.32
-rwxr-xr-x  1 kjetil kjetil  741816 2015-02-08 19:03 dialog.64
-rw-r--r--  1 kjetil kjetil    2552 2015-02-08 19:03 license.txt
drwxr-xr-x  2 kjetil kjetil    4096 2015-02-08 19:03 Modules
-rwxr-xr-x  1 kjetil kjetil 2925608 2015-02-08 19:03 Podolski.32.so
-rwxr-xr-x  1 kjetil kjetil 3226896 2015-02-08 19:03 Podolski.64.so
-rw-r--r--  1 kjetil kjetil    1657 2015-02-08 19:03 Podolski readme.rtf
-rw-r--r--  1 kjetil kjetil 2718022 2015-02-08 19:03 Podolski user guide.pdf
drwxr-xr-x  3 kjetil kjetil    4096 2015-02-08 19:03 Presets
-rw-rw-r--  1 kjetil kjetil     387 2015-02-08 19:03 README-Linux.txt
drwxr-xr-x  3 kjetil kjetil    4096 2015-02-08 19:23 Support
drwxr-xr-x  2 kjetil kjetil    4096 2015-02-08 19:03 Tunefiles

[bmrzycki]

This isn't strictly a u-he question so I hope this isn't too far off topic...

I'm toying with the idea of buying an inexpensive chrome box, reinstalling Ubuntu on it and setting up Linux to boot straight into Zebra. I'd like it to respond to midi via USB and ideally operate headless and without X. Does anyone know an open source vst host for Linux that doesn't require X or loading the plugin GUI? I'm very comfortable in Linux but am new to the plugin audio world on it.

I saw there is a dssi-vst bridge but it uses wine and isn't for native vst like these. Any help or insight from others would be greatly appreciated.

[psycha0s]

VST shared library (.so) is linked to the Xlib:

Code: Select all

ldd -d ~/.vst/ZebraHZ.64.so | grep X11
        libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f7370c9c000)

In other words, you cannot use it without libX11 (and many others)

[bmrzycki]

VST shared library (.so) is linked to the Xlib:

Code: Select all

ldd -d ~/.vst/ZebraHZ.64.so | grep X11
        libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f7370c9c000)

In other words, you cannot use it without libX11 (an many others)

Good to know. Even so, you don't have to necessarily display the GUI, just meet the lib dep. I'll dig in more over the weekend when I have time.

[glokraw]

fst is a command that runs .dll
as a standalone, utilizing wineasio, routed with qjackctl.
I think it is fst-host or fsthost in ubuntu.
All the u-he plugins should run that way, cpu requirements allowed for.

Using reaper also works, if some daw functions are desired.
The linux versions should work in the latest qtractor and carla,
so adding kxstudio repos would make them available, or use git.
The devs have sorted the linux issues of having multiple plugins
under one vst shell.

I wouldn't recommend an autoboot on a laptop, for theft security reasons.
Unless alone on a tropical island, or no personal details are aboard.
Cheers

Radium is a linux daw related to trackers, I know nothing about it,
except the dev is probably a genius, and he has had success with the u-he herd.