Package Details: vcvrack 1.1.1-1

Git Clone URL: https://aur.archlinux.org/vcvrack.git (read-only)
Package Base: vcvrack
Description: Open-source virtual modular synthesizer
Upstream URL: https://vcvrack.com/
Licenses: custom, GPL3, CCPL
Submitter: mkoskar
Maintainer: dvzrv
Last Packager: dvzrv
Votes: 18
Popularity: 1.524944
First Submitted: 2018-01-09 18:17
Last Updated: 2019-07-06 20:39

Pinned Comments

dvzrv commented on 2019-06-28 08:35

If you are interested in a well integrated vcvrack (eventually in the [community] repository), built with system libraries from a verifiable source tarball, please do voice your concern in this issue and/or this pull request. It seems upstream only considers changing anything, as soon as enough customers complain.

Latest Comments

1 2 Next › Last »

phonky commented on 2019-07-09 04:28

Sorry removing -wayland and installing -x11 fixed it

phonky commented on 2019-07-09 04:22

Man thanks for maintaining this. I had vcvrack-bin at 0.6.2c-1 installed.

I ran yay -S vcvrack which seems to have successfully removed -bin and installed this version.

But when I go to cd /opt/vcvrack and then ./Rack I get

Could not initialize GLFW.

I have glfw-wayland-3.3.2 installed.

I tried reinstalling and also failed. Any idea? Thanks!

dvzrv commented on 2019-07-06 20:52

I've started to devendor vcvrack. If you're interested in helping out, there's a github organization for it, which strives to maintain patches for each release of VCVRack. Furthermore I plan to make Rack more FHS compliant, by introducing absolute paths, instead of the hardcoded relative ones, jailing Rack and its components below /opt.

Most of the plugins need ot be fixed properly, to be build from source. Have a look at vcvrack-fundamental for details. Vendoring Fundamental with vcvrack (imho) makes no sense, as the build would always be from HEAD and thus unreproducible.

dvzrv commented on 2019-07-02 07:07

@pha-qu: yes, the upstream situation is pretty concerning (seemingly using GPL3 as means to get free contributions and to use free services). I will spend the next days doing some devendoring on this package. Sorry, but this might take a little!

I'm fairly certain, that none of my attempts at that will be merged upstream, but we'll see. Worst case, there will be a devendored fork of VCVRack soon, so it can be packaged properly.

pha-qu commented on 2019-07-01 21:15

Upstream have added an application update to the software, it's prompting to update from <help> menu. I suspect this will break/confuse matters, I also suspect Andrew Belt is not being entirely open about where this might be going ... just a hunch

dvzrv commented on 2019-06-28 08:35

If you are interested in a well integrated vcvrack (eventually in the [community] repository), built with system libraries from a verifiable source tarball, please do voice your concern in this issue and/or this pull request. It seems upstream only considers changing anything, as soon as enough customers complain.

dvzrv commented on 2019-06-28 08:32

@klardotsh: I will update the PKGBUILD soonish. There are plenty of other issues with how the software is being built, too.

klardotsh commented on 2019-06-26 11:45

This does not build without a makedep of jq

s-ol commented on 2018-11-15 13:01

Hey everyone, I put @tsujigri's PKGBUILD up as vcvrack-bin, as @mkoskar suggested.

mkoskar commented on 2018-11-03 18:53

I've just disowned this package.

1) I'm not using it often anymore to justify maintaining it. 2) Upstream is now linking all the dependencies statically which would need some hacking of Makefile/s to make it link against Arch's libraries.

Or just package the binary as @tsujigiri did, in that case vcvrack-bin would be appropriate name of such package.