Gustin Johnson | 1 Jun 2009 02:31
Picon

Re: [64studio-devel] Rtirq


Ralf Mardorf wrote:
> Hi :)
> 
> I still try to fix the trouble with sync on my machine. Does anybody 
> have experiences with http://alsa.opensrc.org/Rtirq? As I reported 
> yesterday, unfortunately Rui's site still is off-line.
> 
I have been in the field without internet access for two days, but as of
right now the site is alive and kicking.

> I see that the script is installed to 3.0-beta3 by default. Is there 
> anything I can do, to check if everything is optimized?

Optimization is a deep rabbit hole, make sure it works first.
Optimization is also not going to solve your problems, crappy and buggy
hardware is still crappy and buggy even after optimization.

Gustin Johnson | 1 Jun 2009 05:07
Picon

Re: [64studio-users] Rtirq


Ralf Mardorf wrote:
> Ralf Mardorf wrote:
>> Hi :)
>>
>> I still try to fix the trouble with sync on my machine. Does anybody 
>> have experiences with http://alsa.opensrc.org/Rtirq? As I reported 
>> yesterday, unfortunately Rui's site still is off-line.
>>
>> I see that the script is installed to 3.0-beta3 by default. Is there 
>> anything I can do, to check if everything is optimized?
>>
>> Best,
>> Ralf
> 
> PS:
> 
> I'm confused about the rtirq package, because I can't find the script.
> 
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/rtirq
> /usr/share/doc/rtirq/copyright
> /usr/share/doc/rtirq/changelog.Debian.gz

Obviously these are documentation.

> /etc
(Continue reading)

Ralf Mardorf | 1 Jun 2009 10:20

Re: [64studio-users] Rtirq


> In the future, the "file" utility is pretty handy:
> file  /etc/init.d/rtirq
> /etc/init.d/rtirq: Bourne-Again shell script text executable
Hi Gustin :)

before I wrote my request I tried to run it, but it didn't work :(, but 
it might be because I made typos, similar to the one I did some seconds ago:

spinymouse-sudo <at> 64studio:~$ /etc/init.d/rtirq ststus

  Usage: /etc/init.d/rtirq {[re]start|stop|reset|status}

:D

Maybe the RTPRIO of the USB MIDI DEVICE is bad?

spinymouse-sudo <at> 64studio:~$ /etc/init.d/rtirq status

  PID CLS RTPRIO  NI PRI %CPU STAT COMMAND   
  411 FF      90   - 130  0.0 S<   IRQ-8   RTC
 2349 FF      85   - 125  0.0 S<   IRQ-21  PCI SOUND CARD
  971 FF      80   - 120  0.0 S<   IRQ-16   
 1366 FF      80   - 120  0.0 S<   IRQ-19   
 1370 FF      79   - 119  0.0 S<   IRQ-17  USB MIDI DEVICE
 1399 FF      78   - 118  0.0 S<   IRQ-18   
  403 FF      75   - 115  0.0 S<   IRQ-1   
  402 FF      74   - 114  0.0 S<   IRQ-12   
  104 FF      50   -  90  0.0 S<   IRQ-9   
  995 FF      50   -  90  0.0 S<   IRQ-22   
(Continue reading)

Ralf Mardorf | 1 Jun 2009 10:31

Re: Rtirq

Or is the IRQ of the timer bad? What does the sync the RTC or the timer?

Ralf Mardorf wrote:
>> In the future, the "file" utility is pretty handy:
>> file  /etc/init.d/rtirq
>> /etc/init.d/rtirq: Bourne-Again shell script text executable
>>     
> Hi Gustin :)
>
> before I wrote my request I tried to run it, but it didn't work :(, but 
> it might be because I made typos, similar to the one I did some seconds ago:
>
> spinymouse-sudo <at> 64studio:~$ /etc/init.d/rtirq ststus
>
>   Usage: /etc/init.d/rtirq {[re]start|stop|reset|status}
>
> :D
>
> Maybe the RTPRIO of the USB MIDI DEVICE is bad?
>
> spinymouse-sudo <at> 64studio:~$ /etc/init.d/rtirq status
>
>   PID CLS RTPRIO  NI PRI %CPU STAT COMMAND   
>   411 FF      90   - 130  0.0 S<   IRQ-8   RTC
>  2349 FF      85   - 125  0.0 S<   IRQ-21  PCI SOUND CARD
>   971 FF      80   - 120  0.0 S<   IRQ-16   
>  1366 FF      80   - 120  0.0 S<   IRQ-19   
>  1370 FF      79   - 119  0.0 S<   IRQ-17  USB MIDI DEVICE
>  1399 FF      78   - 118  0.0 S<   IRQ-18   
>   403 FF      75   - 115  0.0 S<   IRQ-1   
(Continue reading)

Ralf Mardorf | 1 Jun 2009 10:46

Re: PS: Qtractor wishlist

Hi :)

I guess this mail also belongs to the 64 Studio lists, but not to other 
lists.

Rui Nuno Capela wrote:
> On Sun, May 31, 2009 23:15, Ralf Mardorf wrote:
>   
>> I guess that you're still busy by programming some 'standard' features,
>> so I won't write to you 'please add this, please add that'.
>>
>> I wrote that it's a PITA, to do settings, because of seg faults. It's
>> not too hard, it's able to work relaxed, so don't worry about this.
>>
>>     
>
> laetst qtractor 0.4.1 has a nasty bug that makes it crash half of the
> times you load a session with midi tracks. it is even more probable to
> crash if  you have a multi-core machine (cpus > 2). this nasty has been
> already squashed in cvs.
>
> you're welcome to check out and build from qtractor cvs (current version
> as 0.4.1.1339) where bugs get nailed on a daily basis. you can also
> experience a few new features as well ;)
>   

The 64 Studio beta version don't makes the jack.h available by it's 
repositories and because I read about troubles when compiling Jack, I 
won't compile Jack myself and that's why I can't compile Qtractor at the 
moment. I'm running Qtractor using jackdmp on a dual-core machine.
(Continue reading)

64 Studio | 1 Jun 2009 15:28
Favicon

Re: [64 Studio] #488: Add Tascam US 122 & US 122L support (was: Add Tascam US 122 & US 122L support (to kernel))

#488: Add Tascam US 122 & US 122L support
-----------------------------------------+----------------------------------
 Reporter:  rosea.grammostola@...  |        Owner:  free
     Type:  enhancement                  |       Status:  new 
 Priority:  normal                       |    Milestone:  3.0 
Component:  build                        |      Version:      
 Severity:  normal                       |   Resolution:      
 Keywords:                               |  
-----------------------------------------+----------------------------------
Changes (by daniel@...):

  * milestone:  => 3.0

Comment:

 The bug for the US 122 is simply that the udev rules for this device are
 not present in the udev package. The U122L has a different chip inside and
 is probably harder to support.

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/488#comment:1>
64 Studio <http://trac.64studio.com/64studio>
64 Studio | 1 Jun 2009 16:07
Favicon

Re: [64 Studio] #488: Add Tascam US 122 & US 122L support

#488: Add Tascam US 122 & US 122L support
-----------------------------------------+----------------------------------
 Reporter:  rosea.grammostola@...  |        Owner:  free
     Type:  enhancement                  |       Status:  new 
 Priority:  normal                       |    Milestone:  3.0 
Component:  build                        |      Version:      
 Severity:  normal                       |   Resolution:      
 Keywords:                               |  
-----------------------------------------+----------------------------------

Comment(by rosea.grammostola@...):

 "that the udev rules for this device are not present in the udev package"

 ok, so how to fix this?

 AFAIK US122L does work in Jaunty now:

 http://ubuntuforums.org/showthread.php?t=1127282&highlight=tascam+jaunty

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/488#comment:2>
64 Studio <http://trac.64studio.com/64studio>
Michael Alexander | 1 Jun 2009 16:14

Re: [64 Studio] #488: Add Tascam US 122 & US 122L support (was: Add Tascam US 122 & US 122L support (to kernel))

Way Cool!

Looks like I'm drivin' down to Bakersfield today to pick one of these up, and I can now FINALLY start recording my stuff using Linux instead of windows!!!





On Mon, Jun 1, 2009 at 6:28 AM, 64 Studio <tickets-ljUBoSVpJTpWk0Htik3J/w@public.gmane.org> wrote:
#488: Add Tascam US 122 & US 122L support
-----------------------------------------+----------------------------------
 Reporter:  rosea.grammostola-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org  |        Owner:  free
    Type:  enhancement                  |       Status:  new
 Priority:  normal                       |    Milestone:  3.0
Component:  build                        |      Version:
 Severity:  normal                       |   Resolution:
 Keywords:                               |
-----------------------------------------+----------------------------------
Changes (by daniel-ljUBoSVpJTpWk0Htik3J/w@public.gmane.org):

 * milestone:  => 3.0


Comment:

 The bug for the US 122 is simply that the udev rules for this device are
 not present in the udev package. The U122L has a different chip inside and
 is probably harder to support.

--
Ticket URL: <http://trac.64studio.com/64studio/ticket/488#comment:1>
64 Studio <http://trac.64studio.com/64studio>

_______________________________________________
64studio-devel mailing list
64studio-devel <at> lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel
64 Studio | 1 Jun 2009 17:20
Favicon

Re: [64 Studio] #488: Add Tascam US 122 & US 122L support

#488: Add Tascam US 122 & US 122L support
-----------------------------------------+----------------------------------
 Reporter:  rosea.grammostola@...  |        Owner:  free
     Type:  enhancement                  |       Status:  new 
 Priority:  normal                       |    Milestone:  3.0 
Component:  build                        |      Version:      
 Severity:  normal                       |   Resolution:      
 Keywords:                               |  
-----------------------------------------+----------------------------------

Comment(by daniel@...):

 You could file a bug against Debian's udev package for US122 support. The
 US122L has a completely different driver, see:
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/329437

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/488#comment:3>
64 Studio <http://trac.64studio.com/64studio>
Daniel James | 1 Jun 2009 17:20
Favicon
Gravatar

Re: [64 Studio] #488: Add Tascam US 122 & US 122L support

Hi Michael,

> Looks like I'm drivin' down to Bakersfield today to pick one of these 
> up, and I can now FINALLY start recording my stuff using Linux instead 
> of windows!!!

If you buy a US122L you will probably have some tweaking to do, see:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/329437

Eventually I hope we will support both models out of the box. As an 
alternative you could look at getting a class-compliant USB audio 
interface, there are many to choose from.

Cheers!

Daniel

Gmane