Linux NATIVE

[osxmidi]

Originally Posted by 4duhwinnn

I double checked, and I have the newest Mint18 dev libraries,
mentioned in your insructions at the GIT page, and the latest g++ 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

/opt/wine-devel/bin has wineg++

but it's not found in

/usr/include/wine-development

/usr/lib/x86_64-linux-gnu/wine-development

But why are those two folders even there,
when staging is in /opt? (I didn't think I ever
installed a 'regular wine' after a recent reinstall,
but I've been a bat in an echo chamber lately,
with all the great new software tools, so maybe I did,
and removed it, rather than purging it.

I'll try the binary shortly, but any suggestions for the build
are welcome. Cheers

I've had a look at my system.

I've got wineg++ in /usr/lib/wine-development and in the various Wine staging and Wine stable install places /opt/wine-staging/bin/wineg++ and /opt/wine-stable/bin/wing++

The wineg++ that will probably be used though is /usr/bin/wineg++ and whatever that points to is it (symbolic link).

Using ls -la /usr/bin/wineg++, I can see that it points to on my system /opt/wine-stable/bin/wineg++ (because I installed wine-stable last)

If I type wineg++ --version then it gives me the g++ version printout.

If I type g++ --version then it gives the same g++ version printout.

They both give the same g++ version because wineg++ (winegcc) uses /usr/bin/g++ or whatever it points to (symbolic link).

Check if wineg++ --version and g++ --version work and that they give the same version printout.

If they don't, check if you have a /usr/bin/g++

[osxmidi]

Originally Posted by kytdkut

I'm not being able to load LSP VSTs (http://lsp-plug.in/), Reaper crashes with this dumped on the terminal:

path=/usr/lib64/vst/lsp-plugins.vst

(reaper5:3354): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'

(reaper5:3354): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(reaper5:3354): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(reaper5:3354): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(reaper5:3354): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(reaper5:3354): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(reaper5:3354): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(reaper5:3354): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplay'

(reaper5:3354): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(reaper5:3354): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(reaper5:3354): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(reaper5:3354): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
zsh: segmentation fault (core dumped) reaper5


Any clues? Did anyone had success trying to load this VSTs?

It's a gdk clash of some sort between Reaper and LSP.

The AmSynth synth vst is the same.

Maybe try Carla and the lv2 versions, I don't know if they work or not.

[snooks]

Originally Posted by brainwreck

Sounds like an issue between unity and wine. Are you running any other windows native applications that maybe have the same behavior?

Nope, it's just native Linux Reaper. I've switched to gnome now since they are killing Unity soon anyway. I remember Unity funnies with Wine though from a couple of years ago that didn't happen on other desktops. It's a shame the Canonical vision was killed by the Linux community, now the stage is clear for Microsoft and Apple.

[Jack Winter]

Originally Posted by snooks

@brainwreck/Garrick: this is on Unity, with Gnome full screen works perfectly. Actually on Unity, full screen leaves the top OS bar on the screen too.

If I understand correctly reaper fullscreen leaves the OS bar visible? If so it's the same on kde/kwin, the video window does fullscreen though. IIRC this was some compromise as it seems very hard to make reaper perform flawlessly with all different window managers. I am sure this will be taken care of in time, as other things probably have a priority.

[Jack Winter]

Originally Posted by kytdkut

I'm not being able to load LSP VSTs (http://lsp-plug.in/), Reaper crashes with this dumped on the terminal:

path=/usr/lib64/vst/lsp-plugins.vst

(reaper5:3354): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'
.
.
.
zsh: segmentation fault (core dumped) reaper5


Any clues? Did anyone had success trying to load this VSTs?

I can confirm the same on archlinux/kde. Started making a buildscript to build from source instead of installing the binaries, but then I realized that the source is not for all the plugins, so I lost insterest...

Interestingly if I build swell with GDK2 support it does open the plugin GUI, and processes audio, but it does leave the reaper GUI completely blocked.

[Jack Winter]

FWIW, I searched a bit about LSP on linuxmusicians.com and came up with this thread: https://linuxmusicians.com/viewtopic...17012&start=15

Looks like the author is considering giving up on using gtk+ and to port the plugins to X11 (Xlib I suppose).

[osxmidi]

Originally Posted by ÄxxlForce

I was finally able to do some testing with Ubuntu Gnome, Reaper & LinVst. I'm amazed how much progress there has been in the past few months and I'm absolutely stoked about it! It's actually a dream come true!

I got everything basically working however I experience a lot of XRuns when using it with Mercuriall Spark guitar amp simulation vst. At first I thought it was because my jackd settings are to aggressive but the XRuns only occur when I insert the amp sim via LinVst. I got a lot of CPU headroom left, so I'm not sure what causes the XRuns. Is it possible to give the WINE layer some kind of realtime priority? I'm already using the low-latency kernel and run jackd in realtime mode.

I've got a workaround for the Spark guitar amp sim and I'll update LinVst within the next few days.

[osxmidi]

Originally Posted by Jack Winter

FWIW, I searched a bit about LSP on linuxmusicians.com and came up with this thread: https://linuxmusicians.com/viewtopic...17012&start=15

Looks like the author is considering giving up on using gtk+ and to port the plugins to X11 (Xlib I suppose).

They look like useful plugins but the gdk issue stops the vst's being much use in Reaper as they are, and there is also a Juce/Tracktion problem (or at least there was when I tried them out) where the GUI comes up but the parameter knobs are frozen.

I checked out some of the LSP source and the gdk stuff is sort of similar to AMSynth's gdk stuff and they both don't work in Reaper because of the gdk window reparenting they both use I think.

They work with Ardour and also Bitwig I think.

[osxmidi]

Originally Posted by Jack Winter

I can confirm the same on archlinux/kde. Started making a buildscript to build from source instead of installing the binaries, but then I realized that the source is not for all the plugins, so I lost insterest...

Interestingly if I build swell with GDK2 support it does open the plugin GUI, and processes audio, but it does leave the reaper GUI completely blocked.

I get the same, a frozen GUI with GDK2 libswell.so

[brainwreck]

osxmidi, have you seen any reports of anyone running Podfarm in Wine/Linvst? I forget the details now, but when I tried to get it up in Wine last year, it was a no go.

[4duhwinnn]

Originally Posted by osxmidi

I've had a look at my system.

I've got wineg++ in /usr/lib/wine-development and in the various Wine staging and Wine stable install places /opt/wine-staging/bin/wineg++ and /opt/wine-stable/bin/wing++

The wineg++ that will probably be used though is /usr/bin/wineg++ and whatever that points to is it (symbolic link).

Using ls -la /usr/bin/wineg++, I can see that it points to on my system /opt/wine-stable/bin/wineg++ (because I installed wine-stable last)

If I type wineg++ --version then it gives me the g++ version printout.

If I type g++ --version then it gives the same g++ version printout.

They both give the same g++ version because wineg++ (winegcc) uses /usr/bin/g++ or whatever it points to (symbolic link).

Check if wineg++ --version and g++ --version work and that they give the same version printout.

If they don't, check if you have a /usr/bin/g++

I only have wine-staging 2.4. There is no /usr/lib/wine-development.
There is a folder /opt/wine-devel ...I've been using synaptic
to install the various devel libraries needed for building these apps.
Shouldn't that folder be somewhere in the wine-staging path?


/usr/bin has g++-5 and a link named g++ that targets the same g++-5

but no wineg++

ls -la /usr/bin/wineg++ reports
ls: cannot access '/usr/bin/wineg++': No such file or directory

/opt/wine-staging/bin has only a link named wineg++ that targets winegcc

(I still think at this point, that problems
exist when only wine-staging is installed, and that the missing
wineg++ would only get there from a non-staging install.)

I think I can piece this mess together, will try later.
-----------------------------------------------------------

I tried the binary version too. Anyone want to rub my hair for luck?

Whenever I add a path containing linvst converted plugins,
when starting reaper, it trudges along repeating this error
over and over (but quite slowly)

/usr/bin/lin-vst-server32.exe: 36: exec: wine: not found
/usr/bin/lin-vst-server.exe: 36: exec: wine: not found


...but both are there, as well as the .so counterparts in /usr/lib

Eventually, reaper opens, but without the converted plugins scanned.

(also, this isn't urgent at all, I have more options than brains.
Have some weekend fun, the win(e) 5.40 works great,
so music making can continue apace, when the sun goes down.)

Cheers

[osxmidi]

Originally Posted by 4duhwinnn

I only have wine-staging 2.4. There is no /usr/lib/wine-development.
There is a folder /opt/wine-devel ...I've been using synaptic
to install the various devel libraries needed for building these apps.
Shouldn't that folder be somewhere in the wine-staging path?


/usr/bin has g++-5 and a link named g++ that targets the same g++-5

but no wineg++

ls -la /usr/bin/wineg++ reports
ls: cannot access '/usr/bin/wineg++': No such file or directory

/opt/wine-staging/bin has only a link named wineg++ that targets winegcc

(I still think at this point, that problems
exist when only wine-staging is installed, and that the missing
wineg++ would only get there from a non-staging install.)

I think I can piece this mess together, will try later.
-----------------------------------------------------------

I tried the binary version too. Anyone want to rub my hair for luck?

Whenever I add a path containing linvst converted plugins,
when starting reaper, it trudges along repeating this error
over and over (but quite slowly)

/usr/bin/lin-vst-server32.exe: 36: exec: wine: not found
/usr/bin/lin-vst-server.exe: 36: exec: wine: not found


...but both are there, as well as the .so counterparts in /usr/lib

Eventually, reaper opens, but without the converted plugins scanned.

(also, this isn't urgent at all, I have more options than brains.
Have some weekend fun, the win(e) 5.40 works great,
so music making can continue apace, when the sun goes down.)

Cheers

I think there is something wrong with your wine installation.

Usually, the wine install puts symbolic links into /usr/bin for wine and wineg++/winegcc and yours seem to be missing.

Maybe if you make the symbolic links then it might be ok.

sudo ln -s /opt/wine-staging/bin/wine /usr/bin/wine

sudo ln -s /opt/wine-staging/bin/wineg++ /usr/bin/wineg++

"/opt/wine-staging/bin has only a link named wineg++ that targets winegcc", that is ok, wineg++ in /opt/wine-staging/bin normally just points to /opt/wine-staging/bin/winegcc.

other optional links

sudo ln -s /opt/wine-staging/bin/wine /usr/bin/wine
sudo ln -s /opt/wine-staging/bin/wineserver /usr/bin/wineserver
sudo ln -s /opt/wine-staging/bin/winecfg /usr/bin/winecfg
sudo ln -s /opt/wine-staging/bin/winepath /usr/bin/winepath
sudo ln -s /opt/wine-staging/bin/wineboot /usr/bin/wineboot
sudo ln -s /opt/wine-staging/bin/wineconsole /usr/bin/wineconsole
sudo ln -s /opt/wine-staging/bin/regedit /usr/bin/regedit
sudo ln -s /opt/wine-staging/bin/regsrv32 /usr/bin/regsvr32

[osxmidi]

Originally Posted by brainwreck

osxmidi, have you seen any reports of anyone running Podfarm in Wine/Linvst? I forget the details now, but when I tried to get it up in Wine last year, it was a no go.

I've got a UX1 http://line6.com/pod-studio/ux1 hanging around somewhere and I might try it out at a later date and see what happens.

[4duhwinnn]

Your link suggestions are correct! The previously converted
plugins are now scanned and functioning. I have 5413 running
with Reaktor 6 hosting the NordRack ensemble,
Synthmaster 2 playing a sequence, Kontakt Elements 5
hosting a drumkit, and NI's Christmas gift freebie Replika,
delaying the works on the master track. Thanks again
for your thorough and accurate support of excellent tools!

For the Reaper team: Docking any of the above
instantly sucks reaper into a black hole,
terminal and all! ...poof...

The gui's can be minimized and raised by using the panel widgets
and the FX button. Moving the gui's around the screen
and resizing them is free from artifacts.
This on Mint 18, nvidia pcie video card,
E21 window manager.

EDIT with the 4 above apps still running, docking/undocking seems to work fine on
Native Linux vsts, checked with Hive and Beatzille.

Cheers

[osxmidi]

Originally Posted by 4duhwinnn

Your link suggestions are correct! The previously converted
plugins are now scanned and functioning. I have 5413 running
with Reaktor 6 hosting the NordRack ensemble,
Synthmaster 2 playing a sequence, Kontakt Elements 5
hosting a drumkit, and NI's Christmas gift freebie Replika,
delaying the works on the master track. Thanks again
for your thorough and accurate support of excellent tools!

For the Reaper team: Docking any of the above
instantly sucks reaper into a black hole,
terminal and all! ...poof...

The gui's can be minimized and raised by using the panel widgets
and the FX button. Moving the gui's around the screen
and resizing them is free from artifacts.
This on Mint 18, nvidia pcie video card,
E21 window manager.

EDIT with the 4 above apps still running, docking/undocking seems to work fine on
Native Linux vsts, checked with Hive and Beatzille.

Cheers

I don't know what happens, but sometimes I've had the same thing where the links in /usr/bin weren't there but usually they are, but I've been installing various wine versions at different times so maybe that's part of it.

[osxmidi]

I've got a new version of LinVst out if anyone is interested, 1.02.

It fixes some GUI thread issues with EZDrummer2 and Mercuriall Spark and probably some others.

[ÄxxlForce]

You're amazing!! Will test as soon as possible.

May I ask how the workaround works? I searched the code base and commits but can't find the corresponding code.

[osxmidi]

Originally Posted by ÄxxlForce

You're amazing!! Will test as soon as possible.

May I ask how the workaround works? I searched the code base and commits but can't find the corresponding code.

I found out what it was by accident trying to work out why the EZDrummer drumkit GUI was stopping the Reaper GUI from updating.

It was a thread priority issue where the audio thread had too high of a priority and the GUI couldn't get the time that it needed and it all ended up doing weird things to Mercuriall Spark and EZDrummer and making Mercuriall Spark run in a rough way.

On my old dual core Dell, the Reaper cpu readout is showing 40% when Mercuriall Spark is playing mono but it's ok with the thread priority changes as it doesn't lock the wine GUI handling out and so it's all ok (hopefully on other systems/hardware as well) and should be even more ok on a faster computer.

Before, the audio thread was not letting the GUI get the time that it needed and the old audio thread priority was ok for a lot of plugins but not for Mercuriall Spark and EZDrummer.

[kytdkut]

Last LinVst pull isn't working for me, I get this on the terminal when reaper tries to load VSTs

❯ reaper5
DSSI VST plugin server v0.986
Copyright (c) 2004-2006 Chris Cannam
Loading /home/mauro/.vst/_LinVst/Diffuse-x64.dll
WARNING: RemotePluginServer::dispatchParEvents: unexpected opcode 350


Happens with every plug (tried by removing them from .vst folder one by one): Voxengo Sound Delay, Surreal Machines Diffuse, Nomad Factory Bus Driver, etc.

I'm using the non-embedded makefile. Reverting back to commit 90e29a7 for now

[osxmidi]

Originally Posted by kytdkut

Last LinVst pull isn't working for me, I get this on the terminal when reaper tries to load VSTs

❯ reaper5
DSSI VST plugin server v0.986
Copyright (c) 2004-2006 Chris Cannam
Loading /home/mauro/.vst/_LinVst/Diffuse-x64.dll
WARNING: RemotePluginServer::dispatchParEvents: unexpected opcode 350


Happens with every plug (tried by removing them from .vst folder one by one): Voxengo Sound Delay, Surreal Machines Diffuse, Nomad Factory Bus Driver, etc.

I'm using the non-embedded makefile. Reverting back to commit 90e29a7 for now

Strange.

That opcode (350) should be ok and should not cause a warning, so somethings going wrong with the compile somewhere or something else.

It's like what happens when the linvst.so is not from the same version as the lin-vst-server.exe (version mix up).

I can't seem to reproduce it, but I'll do some more testing.

What distro do you have and if possible what g++ version?

[Jack Winter]

Originally Posted by osxmidi

Strange.

That opcode (350) should be ok and should not cause a warning, so somethings going wrong with the compile somewhere or something else.

It's like what happens when the linvst.so is not from the same version as the lin-vst-server.exe (version mix up).
What distro do you have and if possible what g++ version?

FWIW, I've built several times from git, but this time I got the same error. However after a make clean && make && make install it appears to work. Who knows maybe I forgot to make clean or make install or something like that.

To the OP, I'd say give it another go.

Edit: Figured out what I did wrong. I had an additional directory where I didn't update the plugin.so properly.

[4duhwinnn]

Originally Posted by osxmidi

Strange.

That opcode (350) should be ok and should not cause a warning, so somethings going wrong with the compile somewhere or something else.

It's like what happens when the linvst.so is not from the same version as the lin-vst-server.exe (version mix up).

I can't seem to reproduce it, but I'll do some more testing.

What distro do you have and if possible what g++ version?

I get the same error, using the binary 1.02.

I over-wrote the 1.01 items in
/usr/bin, /usr/lib, the Convert folder, and the linvst.so

Mint 18

g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

E21 window manager with nvidia video card
Cheers

[kytdkut]

Originally Posted by Jack Winter

FWIW, I've built several times from git, but this time I got the same error. However after a make clean && make && make install it appears to work. Who knows maybe I forgot to make clean or make install or something like that.

To the OP, I'd say give it another go.

Edit: Figured out what I did wrong. I had an additional directory where I didn't update the plugin.so properly.

Ok, so I cloned the repo again and re-did all the steps and it worked. Maybe I just missed something last time? Sorry for the noise

I'm using Arch btw, my gcc version is 6.3.1 (gcc-multilib)

[osxmidi]

I'm pretty sure that that 350 error happens when the new 1.02 linvst.so is used with the older 1.01 lin-vst-server.exe

If the sudo make install is missed out, then the new lin-vst-server.exe isn't installed and linvst.so will be using the older lin-vst-server.exe which is not compatible with the new linvst.so version.

[Jack Winter]

In my case I think I was using an old .so together with new version.

[osxmidi]

Originally Posted by 4duhwinnn

I get the same error, using the binary 1.02.

I over-wrote the 1.01 items in
/usr/bin, /usr/lib, the Convert folder, and the linvst.so

Mint 18

g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

E21 window manager with nvidia video card
Cheers

I think the new linvst.so has to be used to convert all of the plugins afresh.

This new version of LinVst uses different thread/pipe code, so it's not compatible with previous versions and the new linvst.so needs to be used for new plugin name conversion and the older linvst.so name conversions deleted.

[4duhwinnn]

Thanks for the update. I'll take the opportunity
to organize my smaller vsts into a single folder.
Cakewalk, IK, and NI, ...not so much.
Cheers

[ÄxxlForce]

Mercuriall Spark works great with the new LinVst version on my end. Awesome job!

[David Else]

Bug report Reaper 5413:

I installed a fresh Fedora 25 on an old Core 2 laptop. I have plugged in an Audiofire 4 firewire interface. I can select it using the Gnome settings/sound as the output and all is well. It plays in YouTube etc.

I DID NOT setup Jack on this laptop as I want to make it as simple as possible. Everything is just default install for Fedora, it seems JACK is installed, but I did not mod anything or install any extras. I was hoping just to use ALSA.

When I open Reaper it says:

there was an error opening the audio hardware
JACK: error creating client

and the ONLY audio system available is JACK. What has happened to the Pulse and ALSA options?

Reaper now goes into some hissy fit, none of the top menu items will select and when I press play it crashes with a segmentation fault.

[bmarkham]

Originally Posted by kytdkut

I'm not being able to load LSP VSTs (http://lsp-plug.in/), Reaper crashes with this dumped on the terminal:

path=/usr/lib64/vst/lsp-plugins.vst

(reaper5:3354): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'

(reaper5:3354): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(reaper5:3354): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(reaper5:3354): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(reaper5:3354): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(reaper5:3354): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(reaper5:3354): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(reaper5:3354): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplay'

(reaper5:3354): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(reaper5:3354): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(reaper5:3354): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(reaper5:3354): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
zsh: segmentation fault (core dumped) reaper5


Any clues? Did anyone had success trying to load this VSTs?

I am far from an expert on this, but I believe this is a problem with themes/kde/gtk/qt5 rather than the plugins or reaper. This problem (searched for "cannot register existing type 'GdkDisplayManager'" on google) has cropped up with a lot of software and is typically resolved by changing the KDE theme, adding an environment variable, or replacing a certain package.

I found a useful thread here:
https://bbs.archlinux.org/viewtopic.php?id=214147&p=2

[osxmidi]

Originally Posted by bmarkham

I am far from an expert on this, but I believe this is a problem with themes/kde/gtk/qt5 rather than the plugins or reaper. This problem (searched for "cannot register existing type 'GdkDisplayManager'" on google) has cropped up with a lot of software and is typically resolved by changing the KDE theme, adding an environment variable, or replacing a certain package.

I found a useful thread here:
https://bbs.archlinux.org/viewtopic.php?id=214147&p=2

It can be caused by multiple things, and themes are just one cause.

With the lsp and amsynth plugins, they are using gtk for the plugins GUI and it conflicts with Reapers use of gdk and the plugins windows gtk events don't work properly and the plugin window is frozen or whatever and/or Reaper acts strangely.

I've actually got the lsp and amsynth plugins to run ok in Linux Reaper using a modified LinVst that loads a linux vst instead of a windows vst.

I'll probably put it up at the LinVst github when it's ready.

Some Linux vst's suffer from incompatibilities due to toolkits and other things when used in some hosts, so running the Linux vst remotely (away from the host) via a modded LinVst solves quite a lot of the incompatibility problems.

[Jack Winter]

osxmidi, I found work for you

Seeing that reaper works so good already that I'd like to start using it, has prompted me to start beating on linvst instead. There really are a few windows vsts that I'd love to use as I'm used to them by now.

I've been hitting t-racks pretty heavily for a few hours, it seems stable and hasn't crashed a single time, unfortunately it's a bit buggy

Check out this screen shot and see how just closing and opening the GUI makes the plugin revert to it's default settings, but toggling the GUI on/off a couple of times can make it open up with the correct parameters, this is rare though.



Think there might be more issues, but let's take them one after another as in the end they might all be the same bug. Tested with the latest version pulled and built from github.

[osxmidi]

Originally Posted by Jack Winter

osxmidi, I found work for you

Seeing that reaper works so good already that I'd like to start using it, has prompted me to start beating on linvst instead. There really are a few windows vsts that I'd love to use as I'm used to them by now.

I've been hitting t-racks pretty heavily for a few hours, it seems stable and hasn't crashed a single time, unfortunately it's a bit buggy

Check out this screen shot and see how just closing and opening the GUI makes the plugin revert to it's default settings, but toggling the GUI on/off a couple of times can make it open up with the correct parameters, this is rare though.



Think there might be more issues, but let's take them one after another as in the end they might all be the same bug. Tested with the latest version pulled and built from github.

Do all the plugins running under LinVst reset their settings on GUI open/close?

[Jack Winter]

Originally Posted by osxmidi

Do all the plugins running under LinVst reset their settings on GUI open/close?

No not at all. I haven't tested very much, but for instance the stillwell plugins don't. I wonder if you haven't entered the jungle of having to add quirks for different plugins..:S

AFAIK, this applies to the t-racks plugins (though I haven't tested all of them). I can't remember ever having seen something similar when running under Wine.

Amplitube seems to not do it, but when enabling the GUI again, there is a change of tone for a fraction of a second, that I suppose indicates that it opens with the default preset and then switches to the one selected by the user (though this is conjecture).

AFAIK, they have demos, so hopefully you can replicate.

Edit, I've tested more of them now, and they don't all do it... Some seem to retain the user settings, but seem to behave like Amplitube in that there is a short change in the sound reflecting the default setting when you open them up. I'll beat them some more to see if I can find some patterns.

[reddiesel41264]

I found out today that iLok licenses can be activated to the hard drive rather than using an iLok, I would figure that this means you could have your licenses without needing PACE drivers so would that make it possible to run PLAY on Linux with the iLok manager running under WINE?

[David Else]

I just can't seem to run Reaper on my old laptop

I have tried installing and running qjackctl, starting that, and running Reaper from the command line.

I get:

jack: created client
jack: setting TIME CRITICAL = 14
jack activated client
entering message loop

Inside audio device settings there is ONLY JACK available. As soon as I interact with the interface (by pressing play, or trying to access a menu or move a slider) then I get:

segmentation fault (core dump)

This is using a Firewire Echo Audiofire 4 interface

[Jack Winter]

Originally Posted by reddiesel41264

I found out today that iLok licenses can be activated to the hard drive rather than using an iLok, I would figure that this means you could have your licenses without needing PACE drivers so would that make it possible to run PLAY on Linux with the iLok manager running under WINE?

I'd doubt that it works, but possibly sometime in the future. There is constant work being done in wine, including efforts to implement DRM features.

[osxmidi]

I modded LinVst to load the lsp vst plugins and the amsynth vst plugin (maybe others as well) in Linux Reaper.

The new lsp vst plugins have some sort of problem but versions 1.0.15 to 1.0.20 seem to work as far as my testing goes.

Only for 64 bit Linux vst's.

Copy lin-vst-server to /usr/bin

sudo cp lin-vst-server /usr/bin

Use linvst*convert and select the linvst*.so file and then the lsp vst plugins folder and convert them.

Then point Reaper's vst search path to the lsp folder.

The lsp-plugins-vst-core.so file needs to be in one of the fixed paths that the lsp plugins search in such as /usr/lib/vst, otherwise the plugin scanning gets messed up.

In Linux Reaper, load the lsp plugins with a * in the filename.

There is a lsp-plugins-vst-core.so file which is just a core lsp file needed for all of the lsp plugins and it shouldn't be loaded.

[Jack Winter]

osxmidi,

I just had a thought, maybe the ik plugins behave like this if they think they aren't authorized... Don't have the time to test right away, but will do when I get home from band practice. Shouldn't happen, but it wouldn't be the first time that I've had drm:ed software that got confused...

[4duhwinnn]

I think T-Racks and Amplitube both utilize a free Custom Shop
for their main demo, but maybe they still have other options?

The Custom Shops offer a core group of tools for free,
and all the other models that can be purchased ala-carte,
can be tested for 48 hour periods without noisebursts etc,
3 or 4 times a year, and you have to be online when testing.

Purchasing from 3rd parties bypasses their system
of gear credits and jam-points, which do go on sale occasionally
but are not universally acclaimed.

Have you ever tried Sir Elliots preamps and EQ's?
I like the 1977 preamp, but would like to calibrate
my ears a bit, with other opinions, as I'm not very experienced
in that area. Downloads at

https://sirelliot.wordpress.com/download-section/
Cheers