Package Details: radium 4.8.5-1

Git Clone URL: https://aur.archlinux.org/radium.git (read-only)
Package Base: radium
Description: A graphical music editor. A next generation tracker.
Upstream URL: https://users.notam02.no/~kjetism/radium/
Licenses: GPL
Submitter: speps
Maintainer: KenjiTakahashi (J5lx)
Last Packager: J5lx
Votes: 8
Popularity: 0.346601
First Submitted: 2013-05-22 03:41
Last Updated: 2017-05-28 10:56

Latest Comments

J5lx commented on 2017-05-09 13:03

Yeah I use integrated graphics (Intel). I agree that it should not make a difference in theory, but if it does in fact happen I think it can be called a bug, be it in Radium, Mesa, LLVM or somewhere else entirely. It might be a good idea to consult somebody with a deeper understanding of the inner workings involved.

Teteros commented on 2017-05-09 11:53

Do you by any chance have a non-radeon card? When I removed 4.0 libs the radeon/mesa opengl driver stopped working, but radium could start, although it printed an error that opengl is not working which is right of course.

I was thinking of reporting it, but in theory only llvm39 should conflict with llvm, the libs packages are fine without the conflict array as they only provide the extra libs, rather than overriding anything.

Anyway the fix is merged already (!) and in upstream 4.8.0 release, check it out when you can.
EDIT: Merged in master but not in 4.8.0 yet.

J5lx commented on 2017-05-09 11:14

I still don’t quite get why that error occurs for you but not for me, even though I also have installed both 3.9 and 4.0, but if there is in fact some kind of incompatibility between those two versions of llvm-libs you might want to report a bug to the project (i.e. https://bugs.archlinux.org/) (I’d rather not report it myself because I can’t reproduce it and I still don’t really understand what happens). As for the patch, I don’t have the time/calm to review it properly right now so it’ll probably land in a few days or once it gets merged.

Teteros commented on 2017-05-09 03:11

TL;DR I patched radium's bundled faust to work with llvm 4.0, either grab the patch from here:
https://gist.github.com/Teteros/61dfd60f3d2a9216231b97630c0c2401
and add this to the PKGBUILD (and source array)
patch -d bin/packages/faust2 -p0 < "${srcdir}/0001-LLVM-4.0-support.patch"
or wait for my pull request to be merged:
https://github.com/kmatheussen/radium/pull/970

Got the time to track this down, it appears the crash happens when you have llvm-libs from repo installed, which is the 4.0 version, this occurs because llvm39-libs does not seem to conflict with it, so I ended up with llvm39 and llvm39-libs installed (which is intented) as well as llvm-libs (4.0) Of course, this should work as ldd on radium shows it correctly links to libLLVM-3.9.so lib, but for some reason it crashes for me with the 4.0 lib package installed.

I ended up patching radium's faust to work with llvm 4.0 as without it, some important libs like mesa would have to be recompiled to work with llvm39.

Teteros commented on 2017-04-29 08:44

Still occurs with your package build unfortunately. I'll snapshot my current partition, and do a fresh install to eliminate some linking or lingering cache/config from possibly interfering. Though you'd think a chrooted build would help if that was the case.

J5lx commented on 2017-04-29 08:09

Personally I don’t experience that at all. So weird! For now I uploaded my own build of the package at https://repo.j5lx.eu/.radium/, could you try installing it and see whether the error occurs with that build as well?

Teteros commented on 2017-04-29 06:38

Indeed 4.7.6 compiles without errors.
However after I installed the build package and try to run radium, this is the output.

$ radium
JUCE v4.2.4
INIT4
INIT5
Executing -LD_LIBRARY_PATH= /opt/radium/crashreporter L3RtcC9yYWRpdW0uSjEyNjY4 PG5vcGx1Z2lubmFtZXM+ PG5vZW1lcmdlbmN5c2F2ZT4= is_crash&-
QWidget: Must construct a QApplication before a QWidget

Official x64 build runs without this error.

J5lx commented on 2017-04-28 20:18

The commit you mentioned is part of 4.7.6, so I suppose their is nothing special left to do for me. That aside, the package builds perfectly fine for me, both 4.7.4 and 4.7.6, so I’m a little curious as to what exactly you are referring to.

Teteros commented on 2017-04-27 21:15

New master: https://github.com/kmatheussen/radium/commit/6078496bfd480e882a879d49b1f9fb9d7e9b770b

Allows it to build now, but I am getting "QWidget: Must construct a QApplication before a QWidget" on runtime with it, and 4.7.4

Teteros commented on 2017-04-11 20:58

You're right, on investigation: the extra files present in /opt/radium are actually the ones radium creates when it's able to at runtime (the 'warning' file import_midi/mod, python stuff, logs, autosaves...)
Making whole .install file redundant, unless used for documenting.

J5lx commented on 2017-04-11 20:33

To address some of your points:
- The reason I don’t want to see $pkgname everywhere is because one of the most common reasons for changing it is to have something like radium-git or radium-with-custom-patch-xy. In both those cases you're still e.g. installing files of a program called just Radium, and usually they are drop-in replacements for the original package rather than being meant for side-by-side installation, meaning that files would go to the same location (/opt/radium), too. I hope that makes sense the way I wrote it.
- Regarding the user/group thing: Both transmission-cli and mariadb provide daemons running system-wide under their respective accounts via systemd (e.g. `systemctl start mariadb`). Radium however is not a daemon but a program run by end-users on their respective accounts rather than on a system account.
- On my system, removing radium deletes /opt/radium just fine. Maybe you created some files in that directory yourself? Maybe autosaves?
- I am going to test-build 4.6.8 now and if it works fine I'll push an update afterwards.

Teteros commented on 2017-04-11 20:07

Thanks for going through, and scrutinizing my changes rather than just merging blindly:
- Somehow I missed that while researching about changelog() That makes a lot of sense now.As I wasn't sure why pacman/makepkg used the Changelog file before downloading/sourcing the source() array.
- The sed lines were ment to reduce the high amount of one-liner diff .patch files we had in the previous PKGBUILD's. Though as I did them, I noticed they weren't even arch specific issues, so switched to making pull requests instead. I think the remaining .patch'a are matching lines very unlikely to be touched by upstream anytime soon, but I see your reasons.
- Eh $pkgname was supposed to be a practical change thing, but the maintainer will propably vim/sed search/replace the name anyway if upstream changed it. See last point.
- Giving a package its own user/group is standard practice whether it's an official package (transmission-cli: https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/transmission
maria-db: https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/mariadb)
or a popular self-contained aur package (jdownloader2)
I'd agree however that, assigning ACL permissions to have /opt/radium in the 'audio' group is excessive, but there are benefits to have /opt/radium in radium:radium.

Having said above, consider using the suggested .install file at least for the post_remove() function. The package as it is will leave /opt/radium lingering after package removal which might cause issues for the user when reinstalling the package at a later date.

- The patch for this PKGBUILD was much bigger before my pull requests were merged, so I opted for changing the comsmetics as it looked like a different PKGBUILD either way. Though now that those changes got merged (!) my cut-down PKGBUILD looked weird and out of place compared to the old one.

Having this comment way longer than I wanted... Thanks again for the merge, and I can confirm 4.6.8 builds fine with the current PKGBUILD, could you bump the version please? I'd say it's worth it as 4.6.8 introduces some long awaited features like sample-seek.

J5lx commented on 2017-04-11 18:43

Okay, so I just had a look at your changes and merged… some of them, because of this:
- The $changelog field in the PKGBUILD is for changelogs of the package itself, not for changelogs of the packaged software. Software changelogs usually go into /usr/share/doc
- We specifically opted to use patches rather than sed because sed lines broke on some updates in very subtle ways. Plus, it’s often harder to tell what exactly sed lines do.
- Don’t use $pkgname excessively just because you can, use it when it makes sense – it’s not inherently synonymous with the software name.
- I am absolutely not going to give write access to system directories under any circumstances unless there is a very, very, very good reason for it. Making a warning message disappear is not such a reason.
- Generally, refrain from making lots of cosmetic changes since that makes review much harder
Aside from that, thanks a lot for your efforts in getting those improvements into upstream (!) and integrating them into the PKGBUILD! So far, everything seems to work fine, so good job!

Teteros commented on 2017-04-09 05:30

I've worked with upstream to update this package and make it more user friendly.

Links

Diff: https://gist.github.com/Teteros/b6c7bc6d2b60b96b6fe643612cd0c1cf/revisions
Tarball: https://gist.github.com/Teteros/b6c7bc6d2b60b96b6fe643612cd0c1cf/archive/master.tar.gz
Related pull requests: https://github.com/kmatheussen/radium/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3ATeteros%20

Verified to compile on a clean chroot.

KenjiTakahashi commented on 2017-02-02 04:02

The problem reiterated for me and this time I was able to look at this in more detail. @pizzataco was mostly correct with his findings, but instead of crafting another part of a (primitive) package manager within a package (why radium's author is doing this is totally beyond me), I've patched it to use libxcb from [extra], which includes all necessary fixes.

I also see the message about dir not being writable, but it does not appear to do any bad, does it? It would probably be best to check in the code why it might actually want to write into it's own dir, but, honestly, this code is total spaghetti. I kinda adore the guy for being able to keep it in a mostly working fashion, lol ;-].

J5lx commented on 2016-12-17 01:16

@pizzataco If all you want to do is build the package in a clean chroot you should have a look at archbuild: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot That’s what I use whenever I work on this package (IOW, it’s known to work) and I believe it’s pretty much the de facto standard for this task.

KenjiTakahashi commented on 2016-12-16 22:54

@pizzataco: I've written my own after getting annoyed enough by not being able to run makepkg as root anymore :-]. It's still quite hacky on the sides, so I've not released it to the public (yet).

pizzataco commented on 2016-12-14 07:06

So I encountered the same "tabs and spaces" issue when not using a clean chroot, the problem is from python3 I think. If you check out these patches over here:

http://linuxfromscratch.org/blfs/view/svn/x/xcb-proto.html

http://linuxfromscratch.org/blfs/view/svn/x/libxcb.html

It is possible then to patch bin/packages/build.sh from PKGBUILD to include these patches and build without chroot and install the package `pacman -U` style.

However, once you start radium it gives a message that the folder it's in is not writeable by your user.


@KenjiTakahashi what automated build tool are you using? I have always done things according to the AUR wiki page, which does not reference the technique.

KenjiTakahashi commented on 2016-12-01 19:28

I have an automated build tool that always builds in clean chroot :-). But I've triggered it manually to build again and... it went fine. Some transient problem? I don't know, but can't reproduce now, so sorry for the noise.

J5lx commented on 2016-11-30 23:03

That looks weird. For me it built just fine. My best guess right now is that it is somehow related to your system configuration. In that case building the package with archbuild (see https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot) should work just fine. I once had a similar issue where my system refused to build any OCaml packages because hardening-wrapper was installed (FS#42748). If archbuild doesn't solve it we'll have to dig deeper.

KenjiTakahashi commented on 2016-11-30 22:37

Don't have time to investigate right now, but I'm getting

make[1]: Entering directory '/opt/radium/src/radium-4.3.2/bin/packages/libxcb-1.12'
Making all in src
make[2]: Entering directory '/opt/radium/src/radium-4.3.2/bin/packages/libxcb-1.12/src'
GEN xproto.c
File "./c_client.py", line 1937
after_end_of_request = '(((char*)R) + R->length * 4)'
^
TabError: inconsistent use of tabs and spaces in indentation
make[2]: *** [Makefile:1290: xproto.c] Error 1
make[2]: Leaving directory '/opt/radium/src/radium-4.3.2/bin/packages/libxcb-1.12/src'
make[1]: *** [Makefile:788: all-recursive] Error 1
make[1]: Leaving directory '/opt/radium/src/radium-4.3.2/bin/packages/libxcb-1.12'
make: *** [Makefile:455: bin/packages/deletemetorebuild] Error 2

trying to compile the newest version (4.3.0 worked fine).

J5lx commented on 2016-11-12 07:33

Update to 4.2.6 is currently blocked by an apparently missing file: https://groups.google.com/d/msg/radium-music-editor/Mt2-JLA7L0o/p3E8TdmrBQAJ

KenjiTakahashi commented on 2016-11-01 12:38

Thanks a lot for working on this, @J5lx! Unfortunately, my jack installation got buggered somehow, so I cannot test it much ATM, but it compiles and runs, so I'd call it's fine :-).
Using patches is indeed a better idea, but sometimes I'm too lazy to do this. Most times these fixes do not last enough for it to be a problem, but here they often do, as we can see.
Removed the SDK comment as not relevant anymore.

J5lx commented on 2016-10-29 22:31

@CrocoDuck Okay, I got the whole thing working now.

@KenjiTakahashi You might want to unpin your comment about manually downloading the SDK now, since it's no longer relevant. I can't do that myself as a co-maintainer.

J5lx commented on 2016-10-29 17:11

@KenjiTakahashi The platform plugin path error was caused by a wrong line number in the sed script in the PKGBUILD. I'm going to replace those sed lines with patches since those are a bit more robust when it comes to line number changes. I'm still looking into the other issues though.

UPDATE: I just noticed that this platform plugin path error also affects other stuff like the crash reporter. I'll include those in the patch as well.

UPDATE 2: argh why did they have to update clang just the moment I was going to finish this now I have to update the clang patch as well and REBUILD RADIUM FROM SCRATCH FOR THE UMPTEENTH TIME

J5lx commented on 2016-10-29 14:30

I have now created the patch and it compiles just fine. However, when I try to run Radium, I get the error message reported by @esclapion. Using the command line provided by @KenjiTakahashi, I get the splash screen, but what follows are an error message and a (probably) unrelated crash. Since I haven't found time to update Radium in a while, I assume that this is not directly related to the system vst patch, but I'm still looking into it.

For reference, the patch can be found here: https://gist.github.com/024c94fcb223bf5ee252b856a648d57d

KenjiTakahashi commented on 2016-10-26 19:11

Yeah, I agree with @J5lx here. The main problem here (and the reason why this package was stagnant for a very long time in the past) is that upstream has refused to change the way he includes this SDK. There were several discussions on github and some ML (or sth, I don't remember exactly).
In fact, I planned to look at patching it on our own as well, but no time now, sorry. If you'll find some time, @J5lx, please go ahead.

J5lx commented on 2016-10-23 17:21

Addendum: From a quick look, it looks like these are the file that we'd need to patch (in git master):

- /check_dependencies.sh, line 130
- /pluginhost/Builds/Linux/Makefile, line 41, and/or /pluginhost/MyPluginHost.jucer, line 19
- /Makefile.Qt, line 195

I don't have the time to actually do the patch and test it and everything right now, but I'll take care of it next friday or earlier if it's still a thing then.

J5lx commented on 2016-10-23 17:08

@CrocoDuck I don't know how @KenjiTakahashi thinks about it, but I'd rather not create any files outside of the build directory as part of the automatic build process. IMHO we should rather go for some downstream patching here, if anything. That would also make this package compatible with archbuild (I think).

CrocoDuck commented on 2016-10-23 14:41

Hi, thank you for your package! Just in case you didn't know, there is a Steinberg SDK package in the AUR:

https://aur.archlinux.org/packages/steinberg-vst36/

You could perhaps include this as a build dependency and link the required files in the prepare() function, like in here:

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=distrho-vst-git

KenjiTakahashi commented on 2016-10-05 00:30

Sorry for a long delay, real life has got me for a while... Should be fixed now (also updated to latest version).

KenjiTakahashi commented on 2016-08-30 01:19

Ah, hell breaks loose again ;-]. I'll work on a proper fix later on, but for now you should be able to run it like this:

QT_QPA_PLATFORM_PLUGIN_PATH=`qmake-qt5 -query QT_INSTALL_PLUGINS` radium

rmdes commented on 2016-08-29 18:44

I really tried to get "xcb" installed before letting a comment here but here it goes : Fatal: This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Read many threads on how to workout this issue with other platforms but I can't get it to work on arch. any hint ?

esclapion commented on 2016-08-29 12:38

Fatal: This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

KenjiTakahashi commented on 2016-08-29 12:03

Moved to Qt5, hopefully everything will work. Let us know if there are any problems.

KenjiTakahashi commented on 2016-03-10 21:35

That's fine by me. Most of the time it's not difficult, just bump the version and it works. But once upon a time it doesn't and the dev will probably not tell you why, so gotta figure that out and things might get strange.
BTW: Already removed the hotfix mentioned earlier, it's fixed upstream.

J5lx commented on 2016-03-07 14:45

@KenjiTakahashi FYI, I'm a bit occupied with school work right now, so if packaging really is as difficult as you say I don't know whether I'll be able to actively contribute before March 17th (my deadline). But anyway, thanks for adding - I'll try to get up and running ASAP.

KenjiTakahashi commented on 2016-03-02 01:07

Updated and fixed symlink problem.
@J5lx: I've added you as a co-maintainer. As, like I said earlier, the upstream maintainer cares little about us, he can change deps/building scripts/whatever without notice, so please make sure that a new release still works before uploading. Just saying :-).
There is also a little compilation fix back ported from current master that should be removed with next version (provided that he doesn't break it again...).

KenjiTakahashi commented on 2016-02-24 00:11

FYI: The package currently cannot be built due to a bug in binutils package (see https://bugs.archlinux.org/task/48317). I'll come back to it when it's fixed (hopefully soon, Allan is on it already).

J5lx commented on 2016-02-14 21:21

3.6.3 is out. @KenjiTakahashi, if you feel unable to keep up with the release "cycle" of Radium, I'd be willing to jump in as a co-maintainer (or even adopt the package).

FreeFull commented on 2016-02-11 19:44

freefull@freefull-asus ~/A/radium> ls -la /usr/bin/radium
lrwxrwxrwx 1 root root 54 Feb 11 19:27 /usr/bin/radium -> /home/freefull/AUR/radium/pkg/radium/opt/radium/radium*

/opt/radium/radium does exist, but /usr/bin/radium ends up linking to the wrong place

KenjiTakahashi commented on 2016-02-08 23:14

Updated. Sorry for the delay and for not keeping it up to date, the upstream guy is spitting new number almost every day, it's not possible for me to keep up. Especially with him caring very little about info useful for packagers...

vasisualiy commented on 2016-01-20 13:27

The version is too old. 3.5.5 is actual one.

Nareto commented on 2015-01-27 11:53

working pkgbuild for 3.0.rc3

http://pastebin.com/Cch23f52

the package() is quite a hack, unfortunately "make install" is no longer supported, not sure why. Read the warning - you'll need to get the vst sdk version 2.4 from steinberg for compilation to work (see https://github.com/kmatheussen/radium/issues/196 )

totalchaos commented on 2014-05-05 18:09

After reading the comments i guess the PKGBUILD needs to be rebuild anyway?

totalchaos commented on 2014-05-05 17:39

Will it be an issue if i use 'calf' as dependency instead of 'calf-kxstudio-git'?

Animtim commented on 2014-04-23 20:19

Here it didn't compile as I also have Qt5 installed, I added an extra "export QT_SELECT=4" before the make packages line and it works.
Please add this to the PKGBUILD (or if there's a better way to do it..)

lievenmoors commented on 2014-04-17 19:07

Maybe the 'lsb-release' package should be added as a dependency, because radium is using /etc/lsb-release to decide for the name of the moc binary. There is a check for arch linux, but it didn't work because i didn't have that file.

Gimmeapill commented on 2014-01-11 10:23

1.9.35 is out:
https://github.com/kmatheussen/radium/blob/master/Changelog

DanielD commented on 2013-11-30 12:21

It crashes each time I try to open a PD patch. Anyone got this ?

DanielD commented on 2013-11-19 22:06

Error here :

Qt/Qt_PluginWidget.cpp:44:1: erreur: ‘PluginWidget’ does not name a type
PluginWidget *PluginWidget_create(QWidget *parent, struct Patch *patch){
^
Makefile:1087: recipe for target 'Qt_PluginWidget.o' failed
make: *** [Qt_PluginWidget.o] Error 1

With the depends as specified by frat

frat commented on 2013-10-23 05:41

depends=('calf' 'liblrdf' 'libxaw' 'qt4''lsb-release')

this will fix it.

frat commented on 2013-10-23 03:00

……
Makefile:1001: recipe for target 'qcolordialog.o' failed
make: *** [qcolordialog.o] Error 1
……
Makefile:1006: recipe for target 'Qt_Bs_edit.o' failed
make: *** [Qt_Bs_edit.o] Error 1

can not work out.

neuromancer85 commented on 2013-10-22 08:34

The build fails for me with this error:
which: no moc in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/core_perl)
Can not find moc. Make sure QTDIR and/or MOC is set correctly in the Makefile.