SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I don't remember it's an old emerald theme I found and edited to match my qtcurve theme. I'd post it but im not on my computer right now (relaxing with my iPad before bed) if you want ill post it when I get up in the morning.
I've been playing around trying to compile dssi-vst and it's surely a pain, but I finally succeeded. I'm not precisely sure of all the steps, but this picture of my desktop is proof, i.e. the output of Rosegarden is streaming through a Windows VST, DSK_Acoustic_Guitars, running on top of WINE via dssi-vst.... Nice!
Pretty Nice!.Have you used Ardour and if so, how u liking Rosegarden?
Edit: Plus VST function is really huge for me. There are a few I just can;t live without. Finally!!!
UPDATE: I WRONGLY installed dssi-vst originally as a 32 bit program via a shell running the 32 bit development environment, i.e. . /etc/profile.d/32dev.sh ...
Do NOT do likewise IF running Slackware 64! With Slackware 32, you can simply ignore this post...
To compile dssi-vst as a 64 bit program, simply ensure you ADD the /usr/bin/32 path to the PATH variable IF the WINE binaries are properly installed in /usr/bin/32 ... * Otherwise, the make file for dssi-vst will abort since it won't find the wineg++ binary... Whew .. now jack-dssi-host (included in the DSSI package) can actually find the dssi-vst.so library in the proper place, i.e. in /usr/lib64/dssi ... excellent, Chris!
BTW, once dssi-vst is built, you MUST rename dssi-vst-scanner.exe to dssi-vst-scanner and dssi-vst-server.exe to dssi-vst-server or the installation will abort when you type, make install ...
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Thanks for Responses
Originally Posted by tpreitzel
UPDATE:<snip> With Slackware 32, you can simply ignore this post...
No worries. I have yet to see a compelling (or compiling) reason to install 64bit Slackware (sorry Eric ). I've tested many distros including 64bit (couple Slamd64 versions, too) and for me the juice isn't worth the squeeze. Presently there are just too many apps that are 32 bit that I depend on and I'm "gun shy" of multi-lib. With a custom kernel set tickless, 1000Hz, low-latency, Athlon64, and PAE @4GB there is less complexity AFAIK and any performance gains seem marginal.
I'll keep an eye on Rosegarden.. I've been using Ardour since it was like pre-alpha when the developer didn't even have installation instructs to minimize the deluge of "I can't get it/It won't.." feedback. It has grown enormously since then and it's nice that gearslutz.com has a whole ardour section habituated by the developer. I guess I just grew complacent with dual-booting back to windoze to use Sequoia for those couple VST/DX plugins for which there is no substitute as yet. That issue is probably of lesser concern than the deplorable state of Linux sound servers which for awhile kept me in Windoze for the whole audio job, but little by little Linux audio improves and once you experience true low latency it is really hard to accept lag since really, that is where the "rubber meets the road", where the precision or lack of it, resides. I still hold out hope that somebody will finally get it and realize that an all Linux, Low Latency DAW distro would almost surely be a profitable venture. Pro Tools... Pffft!
PS - I know about and have used 64Studio and Studio (K)Ubuntu and they're decent but not really ready for serious production IMHO.