On Tue, May 28, 2013 2:06 pm, Louigi Verona wrote:
> I myself would love to test it. Does anyone know of a PPA for 12.04? It
would be good if I can forgo the compilation process. My quick search
revealed no 12.04 debs.
re: xvidcap PPAs. The last one seems to be for 11.10 (Oneiric). It may be
close enough to run. I will try booting 12.04 later and try it. you can DL
the deb file and run dpkg on it to install.
https://launchpad.net/ubuntu/precise/i386/xvidcap/1.1.7-0.2ubuntu12 Has a
link to the deb file for i386, but there is a 64bit page there too.
--
Len Ovens
www.OvenWerks.net
--
Len Ovens
www.OvenWerks.net
On Fri, May 24, 2013 at 6:25 PM, J. Liles <malnourite(a)gmail.com> wrote:
>
>
> On Fri, May 24, 2013 at 7:52 AM, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
>
>>
>>
>> i'm a (not so happy anymore) owner of a us224 which does all the same
>> path as your us122,,.
>>
>> i am sloppy and the systems i use this lovely piece of h/w is not what
>> you'd call the latest and greatest
>>
>> so (my) the state of things at the time of this writing, is the following:
>>
>> - on 3.4.x-rt it still works but only like a plain usb1 device (-r48000
>> -p128 -n3); good old and awesome, special fast and low-latency rawusb/hwdep
>> mode of operation is dead. or it seems so
>>
>> - on 3.8.x-rt it doesn't work at all; always nagging the device's being
>> used by something else (and no, it's not pulseaudio:); and if you dare to
>> use jack1 then, well, it just crashes the whole show (kernel oops)
>>
>> only tested with preempt_rt though (thus the -rt suffix above)...
>>
>> i know this does not help in anything but at least you're not alone :)
>>
>> cheers
>>
>
>
> This is a known issue with the 3.8 kernel. It's breaks not only tascam but
> lots of other USB audio devices as well. Register your discontent with your
> distro, I guess.
>
>
> Ah - I was about to post a separate thread about this - can't get my
focusrite saffire to start at less than 512 on a 3.8 kernel.. Will go down
to 64 on 3.5. Where do I report/add to this bugreport?
James
Sent from Samsung tabletJoel Roth <joelz(a)pobox.com> wrote:steve wrote:
> Hi guys,
>
> For some time I have been preparing backing tracks using Ardour 2/3 etc. Mixing down to mp3 for live performance. We are having reliability problems during playback.
>
> I have tried my netbook (Tosh nb200) my tablet (Samsung 10.1) & an ipad(not to hand, not mine)Â
>
> The playback fails at random point (if at at) & will often then replay satisfactorily. The mp3s are created on a 64bit machine using Ubuntu studio as the base setup & converted to mp3 in Audacity on the same machine.
>
> I am lead to the belief that it is not the playback machine athough not completely due to the randomness.Â
>
> My thoughts are:-
>
> Â mp3 conversion
> Â mp3.
> Â 64bit conversion
>
> Doesn't need to be mp3. flaac would be my choice. it does need to be fast loading with random access (tablet is ideal). Don't mind spending money.
You don't mention what players are subject to this
stopping.
Since you have all your mp3 material already, why not
try all of the half-dozen mp3 players available?
I've always had good luck with mplayer, but there
is vlc, and even ffmpeg (or avconv as it's being rebranded)
can play mp3 files.
I've always found .wav file playback to be more stable than
mp3, and seeking behavior is better. The processor doesn't have
to do much, at the cost of storing a bit more data (One
hour costs 1 GB, roughly.)
Greetings,
Joel
> Steve
>
>
> Sent from Samsung tablet
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Joel Roth
JACK does not appear to run on this platform (yet). There will be hardware with audio I/O in the not too distant future. It would fantastic to have JACK there too.
Hello everyone!
Just a quick notice: I'm going to sell my Roland XP-30 for reasons of space
and the good old mammon. Bit I'd first like to keep it "in the family".
If someone is interested, please send me an e-mail off-list and we can talk
shop. The instrument is in good condition, it's mostly been in the studio and
I don't smoke in a studio. :-)
Right, I'll be waiting until thursday, maybe friday. If I haven't heard
anything by then, I'll get it up on ebay.
Warmly yours and sorry for the OT
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
Hi all! I installed Aeolus through the Ubuntu distribution, but of course, I can't use the GUI. So far I can't get any sound from it, but there could be several reasons.
I'm using the text mode, and it appears that it is working, unless its not actually controling the organ. Does anyone know if this version's text mode actually works?
I can't access the MIDI settings as they're in the GUI. Can I modify those setting in the ./stops/aeolus/definition file?
Or do I just need to run a different version for some reason? I'm making the jack connections for MIDI and audio, and I'm sending MIDI currently with VMPK. VMPK seems to be working according to amididump, and its connections show up in jack, so hopefully that's not the problem. Any suggestions would be appreciated. Thanks much.
Kevin
If I rip the same CD on two different occasions, would I be right to expect
the two sets of tracks to have the same md5sum, or is ripping not that
precise?
I've been using rubyripper and have a difference between two attempts on
the same CD, though rubyripper doesn't report any problems, and each chunk
is matched twice for each rip.
The CD drive is fairly new.
- Richard.
--
Richard Kimber
Political Science Resources
http://www.PoliticsResources.net/
On Thu, May 23, 2013 5:04 pm, Janina Sajka wrote:
> Hi, Len:
>
> Len Ovens writes:
>>
>> On Thu, May 23, 2013 10:55 am, Janina Sajka wrote:
>>
>> > In any case, I certainly don't want pulseaudio to have access to all
>> my
>> > devices, just as I don't want jack running on the audio devices I use
>> > for Speakup and for Orca (two separate devices, unfortunately, because
>> > of driver compatibility issues).
>> >
>> > In any case, this is a moderate priority project at the moment for me,
>> > so I do spend time on it as I have time. So far I have come to believe
>> > it would be possible to restrict pulseaudio either via its
>> client.config
>> > or in udev, but I haven't tried any of this yet.
>>
>> Really simple with the GUI. I am not sure from the command line.
>> pavucontrol has a configuration tab with device profiles. Setting a
>> device
>> to off tells PA to leave it alone. It is persistent from boot to boot,
>> so
>> it must be stored in a file somewhere... looks like binary though. In
>> ~/.config/pulse/
>
> On a per user basis?
> That won't quite work for me, because I also need to avoid the part
> where pulseaudio doesn't allow sound access for a root login.
>
> I really want to go at this on a system-wide level, but then it's
> possible I don't understand pa architecture, i.e. perhaps any pa is only
> invoked user by user.
The recommended way of using PA is by session. This allows more options
and I think is more secure. To run system wide, PA has to be started at
boot time. Normally, PA is set up to auto find and grab ports, but the
config files in /etc/pulse have some commented out lines that might give
some ideas on only connecting PA to one audio IF.
I would first look at the online docs available for PA about running it
system wide. Then put on your sysadmin hat and play. There are some man
pages included as well that may help. You are going into places beyond
what I have tried to do. You are likely to find more help on the pulse
audio mailing list than here though.
> Ah, yes. Thanks for pointing these out. Looks like pacmd is the one for
> sourcing profiles. But, where do these come from? There must be a set
> somewhere? Or, is the profile what one creates with pavucontrol?
look in /usr/share/pulseaudio/ and subdirectories.
--
Len Ovens
www.OvenWerks.net