From emarsk at gmail.com Thu Jul 2 11:19:49 2009 From: emarsk at gmail.com (EmaRsk) Date: Thu, 2 Jul 2009 11:19:49 +0200 Subject: [64studio-devel] Ubuntu: "libasound2-plugins misses alsa pcm jack plugin" Message-ID: <75f5bfa20907020219r40a7a6adk21117aec20a64d5@mail.gmail.com> Hi, regarding going from Debian to Ubuntu as a base for future 64 Studio releases, please be aware of Ubuntu's bug #84900 (https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/84900). libasound2-plugins was migrated to main for pulseaudio, but because jackd's source remains in universe, they cannot build libasound2-plugins with jackd plugin support, according to Ubuntu's policy. This is a serious issue for an audio distro; 64 Studio will need its own custom libasound2-plugins package, or a libasound2-plugins-extra one with just the missing files. -- Emanuele From ralf.mardorf at alice-dsl.net Sat Jul 4 15:47:52 2009 From: ralf.mardorf at alice-dsl.net (Ralf Mardorf) Date: Sat, 04 Jul 2009 15:47:52 +0200 Subject: [64studio-devel] I build a package for Rubberband and wrote a HOWTO compile Qtractor CVS plus Rubberband (not only) for 64 Studio 3.0-beta3 Message-ID: <4A4F5D88.4050700@alice-dsl.net> Hi *developers* :) maybe you want to use my package for Rubberband for the distro, I can copy and paste a description to the package and build it again, but I only know how to compile for amd64. For replies keep in mind, that I don't receive mails from the developers mailing list. Hi *users* :) unfortunately I couldn't build a package for today's [checkout at Jul/04/2009 14:00:00 CEST] CVS version of Qtractor, with complete featured functions, including VST support. You can download the amd64 versions of Rubberband 1.3 as package from here: https://disc.alice-dsl.net/ Username: ralf.mardorf at alice-dsl.net Passwort: 64studio First try to install the package by 'sudo dpkg -i PACKAGENAME' without running 'sudo ldconfig' in addition, if you get trouble run 'sudo ldconfig'. Maybe you will compile Rubberband and Qtractor by yourself, it's recommended to do this at least for Qtractor from time to time, because Qtractor still is elementary, but under heavy development. There's no guarantee that my package and howto are fine and won't damage something, I didn't make tests, but I launched Qtractor and I guess that didn't damage my machine and didn't start eliminating the universe. This is the howto for compiling Qtractor and Rubberband. ------------------------------------------------------------------------ *What is the pitch with Rubberband*? ------------------------------------------------------------------------ Rubberband is a dependency needed by Qtractor. Against all assumptions there seems to be an old version of rubberband in the repositories, that also provides ladspa, that is provided by at least one other package too, anyway, read all about rubberband sources here, so you can chose which way you want to go, to get rubberband. You can get an amd64 (x86_64) version for Hardy here: http://activecom.free.fr/linux/rubberband_1.2-1_amd64.deb Run 'sudo -i', 'cd /path/to/the/downloaded/package', 'dpkg -i rubberband_1.2-1_amd64.deb' followed by 'ldconfig' and then push Ctrl+D. For 64 Studio i386 (x86) you might want to try the i686 executable. Perhaps you want to build it for amd64 or i386 yourself for any reason. Get the executable or source code from here: http://breakfastquay.com/rubberband/ I didn't check if the so called 'executable' (the 'executable' might include the headers too) is all you need, to compile Qtractor or if there is any rubberband development stuff needed in addition. I download source code to /usr/src. To enable this for the user, you need to run one-off 'sudo chown YOUR_USER_NAME /usr/src'. Go another way if your system is used by trustless people too! By using Firefox you can open downloaded archives by the Archive Manager and then only save the extracted source code to e.g. /usr/src. Unfortunately for the .tar.bz2 of rubberband doing it that way only results in getting a .tar, that's why you better save the .tar.bz2, extract it by Nautilus, GNOME's file browser. You only need to click the archive, Nautilus uses the Archive Manager too, but it will be extracted by one step, after that you can delete the .tar.bz2. If you have qtractor and rubberband installed, remove them completely. If you run synaptic to do it, a history can remind you which packages you removed. At the time when I wrote this howto, there were the packages librubberband0 and librubberband-dev in the repositories, librubberband0 only included documents, while librubberband-dev surprisingly seems to include the executable bin too. Launching Qtractor still was fine after removing rubberband_1.2-1_amd64, but with librubberband-dev kept. It might be that it's also possible to use this packages from the repositories, maybe you need to run 'sudo ldconfig' in addition. I guess the executable still was the one from the alien package after this was removed, but librubberband-dev still was installed. Remove librubberband0 and librubberband-dev completely too. If you still have installed versions of Qtractor and Rubberband installed by 'make install', don't expend effort to remove them. I e.g. still had a version of Qtractor installed by this way and didn't remove it. When I wrote this howto, the actual released version for rubberband was 1.3 only the i686 executable was 1.3 too, the alien amd64 package is 1.2 and the package from the amd64 repository is/was 1.0.1, so it can't be bad to compile it, even if the executable bin from the librubberband-dev should be fine too. The repositories provided Qtractor version 0.4.2 at the time of writing the howto. We don't need always the actual version of rubberband, but we very often should get Qtractor's latest CVS version, as I've written before, because Qtractor still is elementary, but under heavy development. If possible don't use 0.4.2! Chose any premade version of rubberband or ... ------------------------------------------------------------------------ *Compile Rubberband* ------------------------------------------------------------------------ Compilers, checkinstall and other development packages are requirements you need all the time, if you haven't installed them, do it now, in addition you need to install the required packages for rubberband, if they aren't already installed: 'libsndfile' for the Ubuntu based 64 Studio this means 'libsndfile1' and 'libsndfile1-dev' 'libsamplerate' for Ubuntu 'libsamplerate0' and 'libsamplerate0-dev' 'FFTW3' for Ubuntu 'libfftw3-3' and 'libfftw3-dev' 'Vamp plugin SDK' for Ubuntu 'vamp-plugin-sdk' 'LADSPA header' for Ubuntu 'ladspa-sdk' 'pthread library' for Ubuntu 'libpthread-stubs0' and 'libpthread-stubs0-dev' As user run: cd /usr/src/rubberband-1.3 ./configure make Compiling is very fast with my dual core 2.1GHz, 1 GB + 896 MB RAM. Try to run 'sudo checkinstall' instead of 'sudo make install', when checkinstall asked me to change something, I changed the architecture from i386 to amd64 to fit to the architecture of my machine and it worked, before I wanted checkinstall not to add dummy documents and I described the package simply as 'rubberband 1.3'. I guess it's possible to run 'checkinstall' without 'sudo'. If checkinstall isn't fine for you, run 'sudo make install' and you are ready. If checkinstall will be fine, this will be the better way, you'll get a packge, install it by running 'sudo dpkg -i rubberband_1.3-1_amd64.deb'. Once you have a version of rubberband installed, in the future you only need to upgrade Qtractor, without compiling rubberband again, now ... ------------------------------------------------------------------------ *Compile Qtractor* ------------------------------------------------------------------------ Again, compilers, checkinstall and other development packages, e.g. CVS, are requirements you need all the time, if you haven't installed them, do it now, in addition you need to install the required packages for rubberband, if they aren't already installed. The requirements are listed here: http://qtractor.sourceforge.net/qtractor-index.html#Requirements For us that should mean, that we need to check if this packages are installed: libasound2-dev (not lib32asound2-dev), libsndfile1-dev, libvorbis-dev, libmad0-dev, ladspa-sdk, dssi-example-plugins, dssi-dev, liblo0-dev, libsamplerate0-dev In addition 'rubberband' must be installed and the versions of 'libjack-dev' and 'libjack0.100.0-dev', that fit to the version of JACK, you have installed. For 64 Studio 3.0-beta3 the repository is broken for (some versions) of JACK, so you need to get it from Quentin's private repository: Type : Binary URI : http://apt.harleystudio.co.za Distribution: hardy Components : main If you want VST support you need to download VST SDK from http://www.steinberg.net/en/company/3rd_party_developer.html, once you are registered you need to download 'VST 2.4 Audio Plug-Ins SDK'. You can also use 2.3 if there is the need for some reason to use this version, but you can't use both versions at the same time and you can't use version 3. After you downloaded it, extract it by using Nautlius, just click on the file and Archive Manager will do it for you, btw. Archive Manage sometimes snag a little bit when choosing the folder. If you won't have some features supported you only need to remove dev packages, e.g. for DSSI dev and VST headers it's fine, you can compile Qtractor without featuring them. Copy the needed VST headers to /usr/local/include: sudo -i cp /usr/src/vstsdk2.4/pluginterfaces/vst2.x/aeffectx.h /usr/local/include cp /usr/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h /usr/local/include Ctrl+D Install 'cervisia-kde4' and 'cvsservice-kde4'. I'm running GNOME, but KDE4 also is installed, maybe you need to add some additional dependencies to run Cervisia, even for me the dependency 'cvsservice-kde4' wasn't installed automatically, when I installed 'cervesia-kde4'. Launch Cervisia by GNOME-menu > Programming > Cervisia. In the menu 'Settings' enable all options. In the menu 'Repository' chose 'Checkout...'. Repository : :pserver:anonymous at qtractor.cvs.sourceforge.net:/cvsroot/qtractor Module : qtractor Branch tag : Working folder: /usr/src Check out as : qtractor [ ] Export only [X] Recursive checkout Finish with clicking the OK button. Now there should be the latest Qtractor source code in /usr/src/qtractor. You can take a look at it by 'File > Open Sandbox...', but there's no need to do this or anything more by using Cervisia. Instead of using Cervisia you can get the source code by running |cvs -d:pserver:anonymous at qtractor.cvs.sourceforge.net:/cvsroot/qtractor login followed by ||cvs -z3 -d:pserver:anonymous at qtractor.cvs.sourceforge.net:/cvsroot/qtractor co qtractor but once you have set up Cervisia you don't have any work to do and you'll simply be able to checkout latest CVS versions. *Compiling and installing* As user run: cd /usr/src/qtractor ||make -f Makefile.cvs| autoconf ./configure Excepted of the version that might differ, the output should end with this: Qtractor 0.4.2.1360 Build target . . . . . . . . . . . . . . . . . . .: release JACK Audio Connection Kit support . . . . . . . .: yes ALSA MIDI Sequencer support . . . . . . . . . . .: yes General audio file support (libsndfile) . . . . .: yes Ogg Vorbis audio file support (libvorbis) . . . .: yes MPEG-1 Audio Layer 3 file support (libmad) . . . .: yes Sample-rate conversion support (libsamplerate) . .: yes Pitch-shifting support (librubberband) . . . . . .: yes OSC service support (liblo) . . . . . . . . . . .: yes IEEE 32bit float optimizations . . . . . . . . . .: yes SSE optimization support (x86) . . . . . . . . . .: yes LADSPA Plug-in support . . . . . . . . . . . . . .: yes DSSI Plug-in support . . . . . . . . . . . . . . .: yes VST Plug-in support . . . . . . . . . . . . . . .: yes XInitThreads() support (DANGEROUS) . . . . . . . .: no Gradient eye-candy . . . . . . . . . . . . . . . .: yes Debugger stack-trace (gdb) . . . . . . . . . . . .: no Install prefix . . . . . . . . . . . . . . . . . .: /usr/local Now type 'make', followed by 'make install' as root. make Compiling isn't so fast, but anyhow it only takes around 5 minutes with my dual core 2.1GHz, 1 GB + 896 MB RAM. sudo checkinstall I tried an alternative version number, e.g.: 0.4.2-cvs1360. Change the name from '0-name-' to e.g. '0-qtractor'. Change architecture from 'i386' to 'amd64' and 'x86_64' but checkinstall always failed. Btw. when running checkinstall as user without sudo, the maintainer will be the actual user and not root. I know from Suse, this will cause a warning when installing the package on another system. Anyway, because it fails here, we need to run sudo make install make clean qtractor --version Qt: 4.4.0 Qtractor: 0.4.2.1360 I can't say if it's fine, but I could launch Qtractor and was able to load a project, VST was listed. Cheers, Ralf From salsaman at xs4all.nl Sat Jul 4 16:54:57 2009 From: salsaman at xs4all.nl (salsaman at xs4all.nl) Date: Sat, 4 Jul 2009 16:54:57 +0200 (CEST) Subject: [64studio-devel] Including LiVES in 64 studio Message-ID: <50030.189.81.96.166.1246719297.squirrel@webmail.xs4all.nl> On Mon, June 29, 2009 19:40, salsaman at xs4all.nl wrote: > On Mon, June 29, 2009 17:18, Daniel James wrote: >> Hi Salsaman, >> >>> I have mentioned this a couple of times before about including LiVES in >>> 64 >>> studio - definately I would think it is something that our users would >>> like to see. >> >> I totally agree, my only reservation has to do with software patents on >> proprietary and MPEG video codecs. >> >> Cheers! >> >> Daniel >> > > > Then worry not. LiVES contains no proprietary codecs - it uses only > external libraries for encoding/decoding. > > - If you have libmjpegtools installed, LiVES will compile against this, > but in fact it uses only some enums internal to the library. > > - dv and ogg/theora are optionally supported by decoder plugins, but > neither of these formats are patented. > > Cheers, > Gabriel "salsaman", > http://lives.sourceforge.net > > > I have just had a report that LiVES 1.0.0-pre1 works out of the box in 64 studio. In fact there will be an article appearing in Linux Journal shortly reviewing LiVES on 64 studio. Cheers, Salsaman. http://lives.sourceforge.net From tickets at 64studio.com Sun Jul 12 19:30:46 2009 From: tickets at 64studio.com (64 Studio) Date: Sun, 12 Jul 2009 17:30:46 -0000 Subject: [64studio-devel] [64 Studio] #499: No disk drive detected error on install for Asus P5Q motherboard In-Reply-To: <031.f2a9964d2cd49668f6d69e90fd3de69a@64studio.com> References: <031.f2a9964d2cd49668f6d69e90fd3de69a@64studio.com> Message-ID: <040.bcbf3a1394de4e02174b1151e4c64eab@64studio.com> #499: No disk drive detected error on install for Asus P5Q motherboard ---------------------------------+------------------------------------------ Reporter: daniel at 64studio.com | Owner: free Type: defect | Status: new Priority: high | Milestone: 3.0 Component: packages | Version: 3.0 beta 3 Severity: major | Resolution: Keywords: | ---------------------------------+------------------------------------------ Comment(by guido at fotocaos.it): Works for me. I own a P5Q Pro and had this problem installing 64studio 2.1. Not 3.0 beta3. If this bug is the one described in this LKML thread: http://www.gossamer-threads.com/lists/linux/kernel/968813 it is solved since version 2.6.27 of the kernel and so it is already fixed in 64studio 3.0. -- Ticket URL: 64 Studio From tickets at 64studio.com Sun Jul 12 19:48:18 2009 From: tickets at 64studio.com (64 Studio) Date: Sun, 12 Jul 2009 17:48:18 -0000 Subject: [64studio-devel] [64 Studio] #479: Garbage in /var/lib/dbus/machine-id In-Reply-To: <029.00b288b3f692b753d034c0c1cf0e02d4@64studio.com> References: <029.00b288b3f692b753d034c0c1cf0e02d4@64studio.com> Message-ID: <038.8783ea5ff692818ff1455a1e20b358c2@64studio.com> #479: Garbage in /var/lib/dbus/machine-id -------------------------------+-------------------------------------------- Reporter: guido at fotocaos.it | Owner: free Type: defect | Status: closed Priority: normal | Milestone: 3.0 Component: build | Version: Severity: blocker | Resolution: worksforme Keywords: | -------------------------------+-------------------------------------------- Comment(by guido at fotocaos.it): I think I found the culprit. /var/lib/dbus/machine-id is not created during installation. It gets created during the first boot. But on my system, the boot sequence ends with gdm trying to start X and totally freezing the system, since I'm the lucky owner of a Radeon X1300 RV515 video card! At that time, the file holds uncommitted data. I managed to install without this problem, still using jfs. I suggest patching /etc/init.d/gdm so it issues a sync command before doing anything. This should save part of the trouble to those with badly supported video cards. -- Ticket URL: 64 Studio From tickets at 64studio.com Sun Jul 12 22:14:34 2009 From: tickets at 64studio.com (64 Studio) Date: Sun, 12 Jul 2009 20:14:34 -0000 Subject: [64studio-devel] [64 Studio] #502: RAID array does not start Message-ID: <029.a8a129511df62ab4b1e5d0ff5407adfb@64studio.com> #502: RAID array does not start -------------------------------+-------------------------------------------- Reporter: guido at fotocaos.it | Owner: free Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: Severity: normal | Keywords: -------------------------------+-------------------------------------------- I fixed my 32-bit install of 3.0 beta3 by replacing a defective installation DVD. Now all is fine except this one (and maybe something with the video card). Shouldn't the kernel automatically create md* devices when it detects partitions which belong to a RAID? I keep data on a mirror of two IDE disks (which I connected after installation), and they are not detected. Moreover, when I issue "sudo dpkg-reconfigure mdadm" I get these errors (after the dialogs): Generating array device nodes... rm: cannot remove `md0-': Read-only file system mknod: `md0-': Read-only file system rm: cannot remove `md0-': Read-only file system rm: cannot remove `md1-': Read-only file system mknod: `md1-': Read-only file system rm: cannot remove `md1-': Read-only file system rm: cannot remove `md2-': Read-only file system mknod: `md2-': Read-only file system rm: cannot remove `md2-': Read-only file system [omissis...] rm: cannot remove `md31-': Read-only file system mknod: `md31-': Read-only file system rm: cannot remove `md31-': Read-only file system done. Removing any system startup links for /etc/init.d/mdadm-raid ... update-initramfs: Generating /boot/initrd.img-2.6.29-1-multimedia-686 Meanwhile, I created a file named /etc/init.d/startraid.sh and linked as /etc/rcS.d/S25startraid.sh: #!/bin/sh test -e /dev/md0 || /sbin/mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1 -- Ticket URL: 64 Studio From gustin at echostar.ca Mon Jul 13 05:26:17 2009 From: gustin at echostar.ca (Gustin Johnson) Date: Sun, 12 Jul 2009 21:26:17 -0600 Subject: [64studio-devel] [64 Studio] #502: RAID array does not start In-Reply-To: <029.a8a129511df62ab4b1e5d0ff5407adfb@64studio.com> References: <029.a8a129511df62ab4b1e5d0ff5407adfb@64studio.com> Message-ID: <4A5AA959.3050401@echostar.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 64 Studio wrote: > #502: RAID array does not start > -------------------------------+-------------------------------------------- > Reporter: guido at fotocaos.it | Owner: free > #!/bin/sh > test -e /dev/md0 || /sbin/mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1 > I can't say how 64Studio handles software RAID yet (this is something I will be testing). Anyway, in this script you are better off using the /dev/disk/by-//