Package Details: dexed 0.9.6-2

Git Clone URL: https://aur.archlinux.org/dexed.git (read-only, click to copy)
Package Base: dexed
Description: A software synth closely modelled on the Yamaha DX7
Upstream URL: http://asb2m10.github.io/dexed/
Licenses: GPL3
Submitter: SpotlightKid
Maintainer: SpotlightKid
Last Packager: SpotlightKid
Votes: 11
Popularity: 0.55
First Submitted: 2018-03-24 00:10 (UTC)
Last Updated: 2021-04-25 18:00 (UTC)

Latest Comments

SpotlightKid commented on 2021-04-25 18:01 (UTC)

@Gimmeapill: you're absolutely right. Fixed.

Gimmeapill commented on 2021-04-25 10:31 (UTC)

Shouldn't the install path be updated to /usr/lib/vst3 ?

SpotlightKid commented on 2021-03-05 16:41 (UTC)

@all: Since JUCE 6 seems not to be forthcoming in the Arch package repos and dexed 0.9.6 is now released, I chose to include JUCE 6.0.7 in the source list for this PKGBUILD.

Note that upstream dropped the VST2 version and so this package now provides a VST3 plugin (and standalone version, as before) instead.

SpotlightKid commented on 2020-10-20 12:41 (UTC)

@all: I'm aware this package is out-of-date. dexed >= 0.9.5 requires JUCE 6.x to build, which Arch does not yet provide. When it does, dexed will be eventually be moved into the community repo, which is now possible because VST2 support was droppped.

So this AUR package will probably not be updated anymore. If you want the latest dexed, you can use the dexed-git package. Be aware, though, that it drops the VST2 version and provides a VST3 plugin instead.

SpotlightKid commented on 2018-08-21 14:00 (UTC) (edited on 2018-08-21 14:01 (UTC) by SpotlightKid)

Notice: the updated package version (0.9.4-4), which I put out last week, now has a functioning plug-in and stand-alone version again!

SpotlightKid commented on 2018-05-31 00:53 (UTC)

@io7m: hmm, that's odd, I get an immediate segfault. I'll try to contact via e-mail, maybe we can sort this out.

io7m commented on 2018-05-30 18:00 (UTC)

I am using JACK, yes. The version I built from GitHub (as opposed to this AUR package) says:

$ /usr/lib/carla/carla-bridge-native vst build/Dexed.so Dexed
libjack.so.0 loaded sucessfully!
JUCE v5.2.1

**********************************************************
DexedAudioProcessor Created
Log started: 30 May 2018 6:59:41pm

DexedAudioProcessor::DexedAudioProcessor() Hi
int Cartridge::load(const uint8_t*, int) valid sysex found!
void DexedAudioProcessor::setEngineType(int) settings engine 1
void Controllers::refresh() controllers refresh>>> amp_mod 0 pitch_mod 0
virtual void DexedAudioProcessor::setCurrentProgram(int) setting program 0 state
void Controllers::refresh() controllers refresh>>> amp_mod 0 pitch_mod 0
virtual void DexedAudioProcessor::setCurrentProgram(int) setting program 0 state
void Controllers::refresh() controllers refresh>>> amp_mod 0 pitch_mod 0

The instrument comes up and I can play notes, load patches, etc. When I close the window, I do see a pile of JUCE assertion errors, but these have always been there as far as I'm aware.

SpotlightKid commented on 2018-05-30 15:50 (UTC)

@io7m: are you using JACK? have you tried the carla command I specified in the Github issue? The command assumes that you have installed the plugin version you want to test under /usr/lib/vst. If you want to test without installing, use:

/usr/lib/carla/carla-bridge-native vst build/Dexed.so Dexed

io7m commented on 2018-05-30 15:17 (UTC)

Suspect I may be missing something incredibly obvious, but if I clone the official Dexed GitHub repository (specifically, git commit 73a266dd70e58e7def14a52bf2a53b5486d083dc) and run:

$ cd Builds/Linux
$ make

... the build succeeds and I get a working VST plugin. I don't use the standalone version. I don't see the JUCE error and I don't seem to get the segfault noted in the GitHub ticket...

SpotlightKid commented on 2018-05-25 20:25 (UTC) (edited on 2018-05-25 20:26 (UTC) by SpotlightKid)

Unfortunately I'm stuck on this. I opened an issue about the underlying issue upstream: https://github.com/asb2m10/dexed/issues/132

io7m commented on 2018-05-25 20:05 (UTC)

'ello. Any progress on this?

SpotlightKid commented on 2018-05-02 08:40 (UTC)

@io7m: I was finally able to reproduce the problem building in a chroot. Now to find the cause and a solution ... stay tuned.

SpotlightKid commented on 2018-04-27 15:33 (UTC)

I've tried but I'm having trouble compiling juce in the container. I need to research this more thoroughly.

io7m commented on 2018-04-26 14:08 (UTC)

Have you tried building it in a clean OS install or a container? This install I'm getting the error on is about three days old, barely touched.

SpotlightKid commented on 2018-04-26 13:11 (UTC)

@io7m: Sorry, I can't reproduce the error you get. I reinstalled the normal juce AUR package and rebuild this package with makepkg. I also tried building with trizen. Both times the package was built successfully.

I admit, I don't know much about how .jucer files are supposed to work, so maybe those outdated paths are a problem. I suggest you try commenting out lines 23-27 in the PKGBUILD and see if the build still fails. If yes, this should be reported upstream.

SpotlightKid commented on 2018-04-25 17:42 (UTC)

I just noticed that I have installed a custom PKGBUILD for juce. I'll try to reproduce the error with the normal juce AUR package. In the meantime, if you want, you can try my PKGBUILD: https://gist.github.com/SpotlightKid/a5db04ea9c259ea57b3ea72719b23c57

io7m commented on 2018-04-25 16:58 (UTC)

yaourt -G dexed; cd dexed; makepkg leads to the exact same error, unfortunately.

SpotlightKid commented on 2018-04-25 15:55 (UTC)

@io7m: can you try and confirm whether it builds on your system with plain makepkg (e.g. "yaourt -G dexed; cd dexed; makepkg")?

io7m commented on 2018-04-25 15:07 (UTC) (edited on 2018-04-25 15:09 (UTC) by io7m)

Hello.

Seem to be having trouble building this:

==> Making package: dexed 0.9.4-2 (Wed 25 Apr 16:06:17 BST 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found dexed-0.9.4.tar.gz
  -> Found dexed.desktop
==> Validating source files with md5sums...
    dexed-0.9.4.tar.gz ... Passed
    dexed.desktop ... Passed
==> Extracting sources...
  -> Extracting dexed-0.9.4.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
  -> Building Dexed stand-alone...
JUCE v5.3.0

**********************************************************
Projucer 5.3.0  ---  Build date: Apr 25 2018
Log started: 25 Apr 2018 4:06:18pm

Linux
CPU: 2513MHz  Cores: 4  14010MB
Loading project: /tmp/trizen-rm/dexed/src/dexed-0.9.4/Dexed.jucer
Re-saving file: /tmp/trizen-rm/dexed/src/dexed-0.9.4/Dexed.jucer
Error when saving: At least one of your JUCE module paths is invalid!
Please go to the Modules settings page and ensure each path points to the correct JUCE modules folder.

==> ERROR: A failure occurred in build().
    Aborting...

This is building using trizen. I see some relative paths in Dexed.jucer: Is it possible that the build script is making some assumptions about where things will be (and those assumptions are violated depending on which AUR frontend tool you're using)?

SpotlightKid commented on 2018-03-31 18:26 (UTC)

Heads up: unfortunately the Dexed VST plugin does not work on Linux in release 0.9.4. I've filed a bug in Dexed's Github issue tracker. Until this is resolved I can only recommend to return to release 0.9.3 if you need the VST plugin. The new standalone version in release 0.9.4 seems to work ok, though.

Here's a PKGBUILD, which you can use for version 0.9.3:

https://gist.github.com/SpotlightKid/c0e8abec8af3686d5495b5dfd2b7c399