Re: Re: Re: Re: raw1394, good right for all during startup ?
On Apr 20, 2009 12:20pm, Eric Hedekar wrote: -- The behaviour you're describing should be fixed as soon as this bugfix hits the repo: https://bugs.launchpad.net/ubuntustudio-controls/+bug/360895 You should already be a member of the "video" group so no further configuration should be needed. -Eric -- ___ http://greyrockstudio.blogspot.com I never had a 'video' group after install. I had to manually create this group and then put myself in it (or else do the 'audio' fix I mentioned earlier). This fixed the permission issues. I should say that I never did install the video packages for Ubuntu Studio, since I do not use them. I use only audio and graphics. Would this make a difference? -Brian -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Re: Re: Jaunty RT testing
On Apr 20, 2009 7:03am, wayne wrote: On Sun, 2009-04-19 at 21:30 +, beej...@gmail.com wrote: On Apr 19, 2009 2:00pm, wayne wa...@jawnee.org> wrote: > maybe it is not jackd that is stuck, but qjackctl, the QT gui for using jack? if so, "killall qjackctl.bin" may work. the nice thing about killall (at least on 8.04), is that after typing "killall", then entering a space, then start typing the name of the process, you can use the Tab key (ala Bash command completion) to finish the process name. when JACK freezes, check with killall if jackd is even running. it may just be that qtjackctl is stuck, which happens to me when the underlying jackd process crashes: jackd dies, but qtjackctl is frozen. also, the qtjackctl process will prob be "qtjackctl.bin", since that pre-script pauses PulseAudio using paususpender before starting jackd... again, at least on 8.04. this way, no PulseAudio getting in the way, while not having to totally remove it. > > > > hope that helps. Thanks, I'll give these different techniques a shot, I'm sure one of them will work. I'm still a bit baffled as to why the GUI for qjackctl was changed at all to remove the ability to force quit. It worked fined in Hardy, but with Jaunty the ability to just hit the 'X' button on the windows and close it is now gone, along with the ability to right click and hit 'force quit'. It's the same for any windows that JACK opens up, such as the message window. Before, you could close it by hitting the 'X' button, but now you must close it by hitting the 'Messages' button on the GUI itself. Did they just want to make sure people were using the GUI to do these things? -Brian not sure about the changes, as i am still using 8.04 Hardy. perhaps it is as you said, making sure the qjackctl program can only be closed certain ways, ensuring better cleanup of underlying jackd processes... or maybe something changed in QT/GNOME/Metacity in 9.10 Jaunty. let us know if it works. peace. Well, I went to test some of these fixes out, and a surprising thing happened. I attempted to push JACK way beyond any reasonable limit in order to cause it to crash. But, instead of crashing, it simply. . .stopped, and allowed me to try different settings until something worked. That's actually very nice, and it eliminates the need to kill JACK in any other manner. Something must've changed in the last few days to cause this. I'll keep testing over the next few days to see if this behavior maintains. If this is the way JACK is going to act from here on out, then I have to say I'm rather pleased. Good job! -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
ISO testing time for the final Jaunty release.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings all Its that time of the release cycle when we are testing madly for the final release, which is in 2 days time. Candidate images for UbuntuStudio are now available from cdimage.ubuntu.com, and you can help us test these images to ensure we have a timely and smooth release. Please head on over to http://iso.qa.ubuntu.com and click on the UbuntuStudio link to find out more on how you can help us test. Luke -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkntH+cACgkQjVefwtBjIM57+ACfc14rG6KVQQXtMM7PMY7mVn0T 20oAoKqE9N7ChBliAt7UtdLqevBRfCZ6 =Dp2L -END PGP SIGNATURE- -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Re: Re: raw1394, good right for all during startup ?
On Mon, Apr 20, 2009 at 10:08 AM, wrote: > On Apr 20, 2009 11:58am, beej...@gmail.com wrote: > > On Apr 20, 2009 11:35am, Luis de Bethencourt lui...@ubuntu.com> wrote: > > > On Mon, Apr 20, 2009 at 5:02 PM, laurent.bellegarde > > > > > > laurent.bellega...@free.fr> wrote: > > > > > > > Cory K. a écrit : > > > > > > >> I /believe/ a fix for Ubuntu Studio Controls was just accepted for > this. > > > > > > >> Can anyone confirm? > > > > > > >> > > > > > > >> > > > > > > >> -Cory K. > > > > Well, it's getting there. . . > > > > First off, I can confirm that on my box, Ubuntu Studio Controls is now > editing /lib/udev/rules.d/50-udev-default.rules. Something a little odd > happened in my case, though. USC removed the line that said "#firewire > device" (or something similar. You know, the comment line that says what > device is affected) and replaced it with KERNEL=="raw1394", GROUP="disk", > which should in theory be fine, except that it did not remove the > KERNEL=="raw1394" line that is there by default, directly below that line, > which places raw1394 in the 'video' group. Whether or not this matters, it > did not work for me and I could not start JACK. So, I went ahead and removed > that default KERNEL=="raw1394" line to see if that worked, and after > restarting the computer, the group for /dev/raw1394 had indeed changed to > "disk". That's a step forward, except that this still did not work, and I > could not start JACK. Is there any reason /dev/raw1394 being owned by 'disk' > would not give me the right permissions? > > > > Anyway, I then just did what I usually have to do, which is to change the > line to say GROUP="audio", put myself in the 'audio' group, and voila, it > works again. > > > > Hope this helps. > > > > --Brian > > > > Hope that helps. > > You know, after reading Eric's response, I'm a bit confused. USC > definitlely added the GROUP='disk' line to my 50-udev-default.rules file, > but it seems like Eric is saying that it is supposed to change the group to > 'video'. Although, maybe it did this when I unchecked raw1394 access in the > USC GUI at some point. So the other question I have is, if you're saying > that USC is supposed to be putting firewire devices in the 'video' group, > does imply that I should just be making a 'video' group and putting myself > in it? As opposed to the 'audio' thing I have been doing (which is, I > believe, what was recommended practice for Ibex)? > > -Brian > -- > The behaviour you're describing should be fixed as soon as this bugfix hits the repo: https://bugs.launchpad.net/ubuntustudio-controls/+bug/360895 You should already be a member of the "video" group so no further configuration should be needed. -Eric -- ___ http://greyrockstudio.blogspot.com -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Re: Re: raw1394, good right for all during startup ?
On Apr 20, 2009 11:58am, beej...@gmail.com wrote: On Apr 20, 2009 11:35am, Luis de Bethencourt lui...@ubuntu.com> wrote: > On Mon, Apr 20, 2009 at 5:02 PM, laurent.bellegarde > > laurent.bellega...@free.fr> wrote: > > > Cory K. a écrit : > > >> I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. > > >> Can anyone confirm? > > >> > > >> > > >> -Cory K. Well, it's getting there. . . First off, I can confirm that on my box, Ubuntu Studio Controls is now editing /lib/udev/rules.d/50-udev-default.rules. Something a little odd happened in my case, though. USC removed the line that said "#firewire device" (or something similar. You know, the comment line that says what device is affected) and replaced it with KERNEL=="raw1394", GROUP="disk", which should in theory be fine, except that it did not remove the KERNEL=="raw1394" line that is there by default, directly below that line, which places raw1394 in the 'video' group. Whether or not this matters, it did not work for me and I could not start JACK. So, I went ahead and removed that default KERNEL=="raw1394" line to see if that worked, and after restarting the computer, the group for /dev/raw1394 had indeed changed to "disk". That's a step forward, except that this still did not work, and I could not start JACK. Is there any reason /dev/raw1394 being owned by 'disk' would not give me the right permissions? Anyway, I then just did what I usually have to do, which is to change the line to say GROUP="audio", put myself in the 'audio' group, and voila, it works again. Hope this helps. --Brian Hope that helps. You know, after reading Eric's response, I'ma bit confused. USC definitlely added the GROUP='disk' line to my 50-udev-default.rules file, but it seems like Eric is saying that it is supposed to change the group to 'video'. Although, maybe it did this when I unchecked raw1394 access in the USC GUI at some point. So the other question I have is, if you're saying that USC is supposed to be putting firewire devices in the 'video' group, does imply that I should just be making a 'video' group and putting myself in it? As opposed to the 'audio' thing I have been doing (which is, I believe, what was recommended practice for Ibex)? -Brian -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Re: raw1394, good right for all during startup ?
On Apr 20, 2009 11:35am, Luis de Bethencourt wrote: On Mon, Apr 20, 2009 at 5:02 PM, laurent.bellegarde laurent.bellega...@free.fr> wrote: > Cory K. a écrit : >> I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. >> Can anyone confirm? >> >> >> -Cory K. Well, it's getting there. . . First off, I can confirm that on my box, Ubuntu Studio Controls is now editing /lib/udev/rules.d/50-udev-default.rules. Something a little odd happened in my case, though. USC removed the line that said "#firewire device" (or something similar. You know, the comment line that says what device is affected) and replaced it with KERNEL=="raw1394", GROUP="disk", which should in theory be fine, except that it did not remove the KERNEL=="raw1394" line that is there by default, directly below that line, which places raw1394 in the 'video' group. Whether or not this matters, it did not work for me and I could not start JACK. So, I went ahead and removed that default KERNEL=="raw1394" line to see if that worked, and after restarting the computer, the group for /dev/raw1394 had indeed changed to "disk". That's a step forward, except that this still did not work, and I could not start JACK. Is there any reason /dev/raw1394 being owned by 'disk' would not give me the right permissions? Anyway, I then just did what I usually have to do, which is to change the line to say GROUP="audio", put myself in the 'audio' group, and voila, it works again. Hope this helps. --Brian Hope that helps. -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
On Mon, Apr 20, 2009 at 8:09 AM, laurent.bellegarde < laurent.bellega...@free.fr> wrote: > Cory K. a écrit : > > sue...@empire.net wrote: > > > >>> I /believe/ a fix for Ubuntu Studio Controls was just accepted for > this. > >>> Can anyone confirm? > >>> > >>> > >>> > >> Speaking of UBStudio Controls, is there doc anywhere that defines what > it > >> does? > >> > >> For example, what files it changes, what parameters it changes? > >> > >> Or even recommendations for memlock limits, etc.? > >> > >> > > > > No. It needs documentation for sure. Anyone is welcome to pick this up. > > Just ask any questions and Andrew or Luis can chime in. > > well, when a user tick the checkbox "enable raw1394", what does exactly > ubuntu studio controls ? > > for a simple user, to be able to get video from a DV camera, he needs > two things, > > - probing raw1394 module with sudo modprobe raw1394 (can be written for > all the startup in /etc/modules) > > - giving the good right to raw 1394 with sudo chmod 666 /dev/raw1394 (i > don't know yet which file i should modify, several ways are in tests) > > Laurent > For the raw1394 checkbox, versions before 0.3 just simply changed the permissions line in /etc/udev/rules.d/40-permissions.rules to be part of the "video" group rather than "disk", version 0.3 (or the 8.10 release) should have done that plus add the raw1394 module (but I think a bug made it only modprobe rather than change permissions too). Versions 0.4 modprobes and adds a line to /lib/udev/rules.d/50-udev-default.rules that gives permissions to the "video" group (provided the latest bugfix is uploaded). I hope that helps explain things - feel free to add this to a new documentation page at https://help.ubuntu.com/community/UbuntuStudio/ubuntustudio-controls -Eric -- ___ http://greyrockstudio.blogspot.com -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
On Mon, Apr 20, 2009 at 5:02 PM, laurent.bellegarde wrote: > Cory K. a écrit : >> I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. >> Can anyone confirm? >> >> >> -Cory K. >> >> > I wish to help and improve ubuntu studio controls to create a simple, > beautifull user friendly package. > > how can I help starting here : https://launchpad.net/ubuntustudio-controls > > by giving ideas in blueprints ? where can I write the command line to > execute, given ideas about icons and interface ? > > Laurent > Thanks!!! Yes, ideas (icons and interface) go in blueprints, new features go in bugs with the "wish" state and problems go in bug reports also. Luis -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
Cory K. a écrit : > I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. > Can anyone confirm? > > > -Cory K. > > I wish to help and improve ubuntu studio controls to create a simple, beautifull user friendly package. how can I help starting here : https://launchpad.net/ubuntustudio-controls by giving ideas in blueprints ? where can I write the command line to execute, given ideas about icons and interface ? Laurent -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
Cory K. a écrit : > sue...@empire.net wrote: > >>> I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. >>> Can anyone confirm? >>> >>> >>> >> Speaking of UBStudio Controls, is there doc anywhere that defines what it >> does? >> >> For example, what files it changes, what parameters it changes? >> >> Or even recommendations for memlock limits, etc.? >> >> > > No. It needs documentation for sure. Anyone is welcome to pick this up. > Just ask any questions and Andrew or Luis can chime in. well, when a user tick the checkbox "enable raw1394", what does exactly ubuntu studio controls ? for a simple user, to be able to get video from a DV camera, he needs two things, - probing raw1394 module with sudo modprobe raw1394 (can be written for all the startup in /etc/modules) - giving the good right to raw 1394 with sudo chmod 666 /dev/raw1394 (i don't know yet which file i should modify, several ways are in tests) Laurent -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
sue...@empire.net wrote: >> I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. >> Can anyone confirm? >> >> > > Speaking of UBStudio Controls, is there doc anywhere that defines what it > does? > > For example, what files it changes, what parameters it changes? > > Or even recommendations for memlock limits, etc.? > No. It needs documentation for sure. Anyone is welcome to pick this up. Just ask any questions and Andrew or Luis can chime in. -Cory K. -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
> > >Original Message: >- >From: Cory K. coryis...@ubuntu.com >Date: Mon, 20 Apr 2009 10:44:36 -0400 >To: ubuntu-studio-users@lists.ubuntu.com >Subject: Re: raw1394, good right for all during startup ? > > >I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. >Can anyone confirm? > Speaking of UBStudio Controls, is there doc anywhere that defines what it does? For example, what files it changes, what parameters it changes? Or even recommendations for memlock limits, etc.? mail2web - Check your email from the web at http://link.mail2web.com/mail2web -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
I /believe/ a fix for Ubuntu Studio Controls was just accepted for this. Can anyone confirm? -Cory K. -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
> > >Original Message: >- >From: Christopher Stamper christopherstam...@gmail.com >Date: Mon, 20 Apr 2009 10:37:07 -0400 >To: ubuntu-studio-users@lists.ubuntu.com >Subject: Re: raw1394, good right for all during startup ? > > >On Mon, Apr 20, 2009 at 10:33 AM, laurent.bellegarde > wrote: >> Hi, >> >> To be able to acquire DV from a firewire camera, an simple user need to >> have enough right over /dev/raw1394. > > >You probably just need to make your user a memeber of a certain group >(maybe 'audio'?). > > I've seen this with jaunty. Everytime I reboot, the permissions and group on raw1394 revert to root. myhosting.com - Premium Microsoft® Windows® and Linux web and application hosting - http://link.myhosting.com/myhosting -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: raw1394, good right for all during startup ?
On Mon, Apr 20, 2009 at 10:33 AM, laurent.bellegarde wrote: > Hi, > > To be able to acquire DV from a firewire camera, an simple user need to > have enough right over /dev/raw1394. You probably just need to make your user a memeber of a certain group (maybe 'audio'?). -- Christopher Stamper Email: christopherstam...@gmail.com Web: http://tinyurl.com/2ooncg gTalk: http://tinyurl.com/6e359r Skype: cdstamper -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
raw1394, good right for all during startup ?
Hi, To be able to acquire DV from a firewire camera, an simple user need to have enough right over /dev/raw1394. at the normal boot, this module hasn't got the good rights and a simple user have to do each boot sudo chmod 666 /dev/raw1394 in a terminal to be able to record DV from the camera with kino, or dvgrab in a command line. is there a file that can be modified to boot this module with the 666 rights, to allowed every user to use the DV camera ? this is an important point that could be package in ubuntu studio controls with the excellent sandie GUI. I've tweaked her GUI a little and i have a button that change it graphically now, but not for all the startup... Thank's for answers, Laurent -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: jaunty, RT, ATI, 3D acceleration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 laurent.bellegarde wrote: > - dual-core Pentium 4-2 Ghz ; 4 Go ram ; ATI radeon HD3470 256 Mo > > So if you need to use 3D acceleration and RT kernel under ubuntu with an > ATI card, Hardy Studio is still the best at this time. > Try the radeonhd driver instead. Let us know how it goes. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknsa/UACgkQwRXgH3rKGfPISwCgmdvq47CPO/tCzZ9TGuqsnLhg wdYAn3SkFeJ4qmBrtKjSryJ5WmFZkClV =GO9o -END PGP SIGNATURE- -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Re: Jaunty RT testing
On Sun, 2009-04-19 at 21:30 +, beej...@gmail.com wrote: > On Apr 19, 2009 2:00pm, wayne wrote: > > maybe it is not jackd that is stuck, but qjackctl, the QT gui > for using jack? if so, "killall qjackctl.bin" may work. the nice > thing about killall (at least on 8.04), is that after typing > "killall", then entering a space, then start typing the name of the > process, you can use the Tab key (ala Bash command completion) to > finish the process name. when JACK freezes, check with killall if > jackd is even running. it may just be that qtjackctl is stuck, which > happens to me when the underlying jackd process crashes: jackd dies, > but qtjackctl is frozen. also, the qtjackctl process will prob be > "qtjackctl.bin", since that pre-script pauses PulseAudio using > paususpender before starting jackd... again, at least on 8.04. this > way, no PulseAudio getting in the way, while not having to totally > remove it. > > > > > > > > hope that helps. > > Thanks, I'll give these different techniques a shot, I'm sure one of > them will work. I'm still a bit baffled as to why the GUI for qjackctl > was changed at all to remove the ability to force quit. It worked > fined in Hardy, but with Jaunty the ability to just hit the 'X' button > on the windows and close it is now gone, along with the ability to > right click and hit 'force quit'. It's the same for any windows that > JACK opens up, such as the message window. Before, you could close it > by hitting the 'X' button, but now you must close it by hitting the > 'Messages' button on the GUI itself. Did they just want to make sure > people were using the GUI to do these things? > > -Brian not sure about the changes, as i am still using 8.04 Hardy. perhaps it is as you said, making sure the qjackctl program can only be closed certain ways, ensuring better cleanup of underlying jackd processes... or maybe something changed in QT/GNOME/Metacity in 9.10 Jaunty. let us know if it works. peace. -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
jaunty, RT, ATI, 3D acceleration
Hi all, This is my last test of jaunty studio. There is still a large trouble with ATI 3D Flgrx driver with Jaunty RT 32 bit kernel. my laptop to test : - dual-core Pentium 4-2 Ghz ; 4 Go ram ; ATI radeon HD3470 256 Mo under hardy - hardy studio 64 - ATI 3D flrgx - RT kernel (production system) : Ok for all, 3D acceleration gives excellents results under jaunty - jaunty studio 32 - ATI 2D open driver - RT kernel : ok for all, very small 3D acceleration, video editing tools are slowest during video effects. - jaunty studio 32 - ATI 3D Fligrx - RT kernel : boot ok, i can hear the first sound of gdm appear but the image is a mid of black and colored square, if i give my user name/password, i can connect the desktop (i can hear the music of opening clearly) but without seeing something, the screen keeps his view. If i tried the CRTL+ALT+F2 to open a terminal, the system reboot suddenly !!! Nothing is possible. - jaunty studio 32 - ATI 3D Fligrx - generic kernel : Ok for all, 3D acceleration gives medium results, video readers are slowed, same thing for video editing tools. So if you need to use 3D acceleration and RT kernel under ubuntu with an ATI card, Hardy Studio is still the best at this time. -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
