Hi!

I am a still newbie who has succeeded in getting Live Slackware Mate running from full install on internal HDs on 2 machines, and from one external SSD in 2 machines (one of them a macbook 2010 w 16 GB ram).

I also run Slackware current from another partition in one of the machines with the full install and Slacckware Live DAW from a USBstick on the 2 machines I have used with the SSD.

The machines I use with SSD are not multiboots -which my other machines are - as I want to preserve their original configurations. The SSD itself is a multiboot. I have used Slackware Live Mate very frequently on all of them for more than a year before attempting to install.

Before and after installing it has solved all my basic needs, with the exception of one thus far: my studies in music.

I am used to have Audacity, Rosegarden, Qsynth , Musescore, Jack and QJackCTL solving all my musical needs. I have still to build my first Slackware package, and I am still scared about it. The more I read the more scared I am, but I am at least aware of the fact that when I have read (and experimented enough) the trend of this development should beguin to invert. I hope.

I believe I have searched sufficiently before posting this and I could not find what I wanted.

My first question is where should I get packages to have a proper install to a fully installed Slackware (Live) Daw. I am not sure it would be right to use the original source from Rosegarden. I found 2 versions of Rosegarden packages for Slackware-based distributions but they were rather old - v.11.x.y and v. 14.x.y.

Would it be safe to try converting from Debian or ArchLinux or perhaps RPM repository?

I would rather stay with Rosegarden since it took me a long time to understand it and I have looked into Ardour which I have installled in several distros, and it is far more scary to me than Rosegarden.

Will be grateful for advice!

So, as I understand it,
1. the Slackware system you want to install Rosegarden on was installed from a "Slackware64 Live DAW" ISO from alienBOB,
2. this system is based on (post-14.2) Slackware64-current.

So the way I would do it is install Rosegarden from the sbo-current git repo. They have Rosegarden 20.12 which should be fresh enough.

A slackBuild is a script that takes (in this case) the source files of some program, compiles it and makes it into a Slackware Package that you can install (and uninstall).
SBo a.k.a. SlackBuilds.org is a community (or a part of the Slackware community) that provides such scripts. The official SBo only does so for Slackware stable (14.2 at the time of writing). There is however, the sbo-current repository, which is unsupported, but which you should use as you're running -current and also has Rosegarden 20.12 vs. 16.02 in the stable sbo.

Caveat: having your -current system up-to-date would rule out some additional sources of error.

1 members found this post helpful.

One easy way to use SBo is with Sbopkg. There exists a development version of Sbopkg that works with the unofficial sbo-current repo (via).

Look at the help for sbopkg.

Likely you will need to resolve the dependencies of Rosegarden, meaning there are other packages that Rosegarden needs to build and/or run. Take care, sqg, included in sbopkg, will build a queue with the dependency information from the sbo-current repo, but this information assumes a clean (and up-to-date) -current system as base, from which your "DAW" system will likely differ. You can find a text file for each of your installed packages in /var/lib/pkgtools/packages/, I would assume that packages added by alienBOB to make the DAW edition out of the official SlackWare64-current will have his "alien" build tag (in the filename).

1 members found this post helpful.

Hey I just made it for you. I have local copy of sbo scripts. You need to build all these packages
requires means that you have to build the packages on the right hand then the one on the left. So to build rosegarden you need to build first dssi and others but before building dssi (see second line) you need to build jack ladspa_sdk and liblo.

1 members found this post helpful.

If you're using Alien Bob's DAW iso, most of that is already there. Lilypond is not. Ponce has an updated slackbuild for it in the stickied slackbuild thread here. In my experience, you want to use the most recent version of lilypond. Older versions would build for me, but segfault when I actually used them. (I'm currently using lilypond 2.20.)

1 members found this post helpful.

Thank you all for much useful information. I will, as usual, need some time to digest it all.

If I download the latest version of Slackware (Live) DAW and install it will it mean it is updated then?

As far as I know I have never downloaded, or needed Lilypond. I do all I need with Rosegarden and Musescore, in various different distributions. My objective now is to establish Slackware as my preferred distro, especially after Sabayon is gone.

I never found - through all my many searches - any link to Rosegarden 20.12 @ sbo-current git repo. This was big news to me.

I will report back as soon as I do some progress or have questions. I would rather wait before marking as solved, although I must admit that I have got very clear answers to my questions. What do you think ?

If memory serves, the only requirements for rosegarden that Alien Bob's DAW package doesn't have are the lilypond ones (so lilypond, fontforge, and guile.) That having been said, I haven't used rosegarden in ages. But if you're doing anything with slackbuilds and current, you absolutely need to be using Ponce's repository, not the SBo one. (That will change once current becomes stable, but that might not happen for a bit.)

1 members found this post helpful.

All scripts for -current are in git ponce repo, I downloaded that repo I think month ago, so is relatively new. Script builds by default rosegarden 16.02. You may try to use the same script for later versions - but it may fail, then go to sticky thread here and post that your build failed. Between versions 16.2 and later may appeared new requirements. Maybe in this month period script was updated. To my experience it is granted that script will build successfully package for default version once all requirements are met. It may not work with different version however. If you want to try build rosegarden 20.12 you need do something like that
if will fail post in thread here or contact script author.

Edit: My mistake. Code above is invalid, this is correct command

1 members found this post helpful.

fredmyra:
As everyone has stated, Rosegarden needs lilypond to work (or build). This is expressed in the dependency tree contained in the metadata from the SBo-current repository, which igadoter extracted for you in post #4 above. However, to reiterate, you will not need some of these dependencies because they are already included in the DAW version, whereas the dependency info in the repo assumes the official Slackware-current release as the base.
As for updating your system, you should read up on that, you can find a lot of info on the web. Configure a Package Manager in the Slackware Beginner's Guide is a good starting point.
It doesn't matter that much for your purpose that you run the DAW version, because what's important to keep up to date is the base system. Just take care to not accidentally remove packages that are not part of the base system. Slackpkg will do that if you just "click" through without taking in what it's about to do. To avoid it you can manually unselect the packages each time, or put them in slackpkg's blacklist. Or maybe they already are in the blacklist. (You can look it up on your systemin the file /etc/slackpkg/blacklist. If unsure, you can post that file here.)

No, Slackware-current's updates moves much faster, alienBOB only releases a new DAW ISO every couple of months, as it looks. The latest Slackware64 Live DAW is from 2021-03-12.
When there's an update to it, you get the latest version of Slackware64-current at that point, plus updates to the DAW package set.
But in the meantime you should keep the system up to date with a method that's not specific to the DAW version but just how every Slackware user does. At least if you go online with that system. Also it could be required to make the SBo-current scripts you need work, but I don't know.

I know this is a lot to take in, so take your time!

igadoter:
SBo-current has lilypond 20.12, as I stated. I actually looked it up on the synced repo on my machine before I wrote that yesterday. (So fredmyra, you can ignore post #9.)

1 members found this post helpful.

I disagree with this. OP shouldn't not update its installation with -current as almost for sure some update will break installation. What OP can do is to update with next AlienBob DAW edition. Updating with -current may end with mass update of size 2GB - which may break all custom builds - and rosegarden too. Shortly DAW version 1, should be updated with DAW version 2, and so on. Till the day when Slackware 15.0 will be released. But of course as well OP may stay all the time with DAW version provided by AlienBob - ignoring both future Slackware stable release and -current.

1 members found this post helpful.

It would not make sense to treat the Live DAW USB stick as a regular Slackware-current with all its package updates.
The Live ISO is a stable snapshot of a Slackware-current and on top, a lot of tools. Leave it at that. It's not meant to browse the internet at your leasure, it's meant as a tool for your musical adventures.

I would usually not refresh such a Live system except when a new version of the Live ISO is released. Then a USB refresh is trivial using the 'iso2usb.sh' script's "--refresh" parameter.

If you want a similar setup to "DAW Live" but then running on your computer equipped with Slackware-current, this is easy to achieve also.
Install the daw_base package from my repository which will tweak your system for real-time audio performance, and read its README file on how to trivially install and update my collection of DAW packages.

5 members found this post helpful.

It's been awhile so I have yet to do this on Current but I do have 2 installs of 14.2, one having most of KxStudio in it, and the other having all of StudioWare in it, which includes lilypond.

Studioware is here - http://docs.slackware.com/studioware:applications_list and may still be useful but like you I'm rather fond of Alien Bob's Live DAW.

Ardour may look scary but it really doesn't take very long to adapt to once one has used just about any other DAW. Just load in a test track copy and follow your nose, or rather ears, and even with minimal reference to docs you'll get a decent feel, certainly enough to WANT to read the docs. Just jump right in, the water's fine

I'm saying that despite taking years to break free from a Windows DAW that I paid over $2000.00 for in 1999. I even tried it in WINE, marginally successfully I should add, before I finally bit the bullet and really gave Ardour a fair turn. That may have worked out well since I first compiled Ardour when it was pre-Alpha and not at all friendly. Modern versions are quite polished and really effective. Looking back I'm glad I didn't "jump right in" in 1999, but by 2009, it was solid.

1 members found this post helpful.

I'll upload packages for rosegarden (Slackware -current only) later today. Also for its dependencies dblatex guile1.8 and lilypond that I did not yet have in my package repository.
Other dependencies like dssi, jack2, ldaspa_sdk, liblo, liblrdf, raptor2 are already present in my repository.

There's also an update for the daw_base package - the slackpkg template file 'daw.template' knows these new packages.
This slackpkg DAW template can only be used if you extend the capabilities of slackpkg to make it work with 3rd-party repositories: for that you need slackpkg+.

6 members found this post helpful.

I decided to try Slackware, a decidedly ambitious goal for someone with my knowledge and experience, because I like what I understand to be its underlying philosophy. Nowadays I am decided to keep trying because of the impressing level of help and support I get here.

I still haven't digested all of the stuff here, but I think I have understood the main points in all of it.

So I will try a clean install of stable - EDIT : oops, I mean current, NOT stable - followed by trying to add the Daw-package and slacklpkg+ and finally try to add Rosegarden.

The Live Daw would certainly solve my musical needs if I could gather the courage to dive into Ardour. But I know I am more motivated to learn Slackware than any specific application, and I still remember how hard it was for me to get the little knowledge of Rosegarden I have got. Once I get Rosegarden working I will be more relaxed and most probably will fell challenged to finally look into Ardour.

It would not be a problem for me to have a dedicated partition with Live Daw to be used only when working with music if I could add Rosegarden to it. And another partition
for the rest of my activities. I have been running multiboots on most of my (all old) machines for many years, so that is not something I am afraid of. Just a thought, but right now I will do as said.

Many thanks again to all of you ! Alien Bob special thanks for supplying Rosegarden !

Last minute question ( I have already downloaded the latest Live current-iso):

could I use Live Mate ? I have a feeling my old computers handle it better then the "big guys".