---------- Forwarded message ----------
From: Thomas Vecchione <seablaede(a)gmail.com>
Date: Tue, Jul 15, 2008 at 10:21 AM
Subject: Re: [LAU] monitor shot, cables
To: Mark Knecht <markknecht(a)gmail.com>
On Tue, Jul 15, 2008 at 10:08 AM, Mark Knecht <markknecht(a)gmail.com> wrote:
>
> Yeah, sometimes the cost of these cables is just silly. I bought a
> Roku NetFlix player a few weeks ago. when it arrived it turned out I
> hadn't purchased any additional cables thinking I had some extra
> component video cables already. I didn't so I took a drive to Radio
> Shack, the only electronics store here in town, to find out they
> wanted $40.
>
>
NEVER buy from Rat Shack if you value your money and your sanity.
Seablade
Hi All. I'm Cory. Lead on Ubuntu Studio. 1st post to this list. ;)
I have a pickle of a issue for a little app I'm working on. It takes
your FLAC collection and converts the entire thing to whatever format
you want with a couple of simple options.
Anyway, I'm unsure what extension to use for Vorbis audio because .ogg
is legacy and .oga should be used now. Issue is, going .oga might render
HW players that haven't updated to be able to use the extension.
From: http://en.wikipedia.org/wiki/Ogg
"The Xiph.Org Foundation decided to create a new set of file extensions
and media types to describe different types of content such as .oga for
audio only files, .ogv for video with or without sound (including
Theora), and .ogx for applications."
More reference:
http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions
To me, the only way to further adoption is to use the extension by
default. I talked to the oggenc dev and he has no intention of using .oga.
So this is all very vexing to me as to which way to go.
Do I use what is supposed to be the new replacement extension for Vorbis
audio or do I continue to go with respected Xiph devs and continue to
perpetuate a legacy extension with this little app of mine?
-Cory \m/
Hartmut Noack wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Pieter Palmers schrieb:
>
>> You have an o2micro host controller:
>>
>> 04:04.0 FireWire (IEEE 1394) [0c00]: O2 Micro, Inc. Firewire (IEEE 1394)
>> [1217:00f7] (rev 02) (prog-if 10 [OHCI])
>>
>> those are not the best ever.
>
> Thanks for that tipp - the could explain, why the box runs much better
> with my workstation...
>
>
>> To reliably use ffado with this controller you have to use patched 1394
>> kernel modules, you can find them here:
>> http://subversion.ffado.org/wiki/TxSkipPatched
>>
>> The 2.6.22-15-rt file should be good for your setup (2.6.22-14-rt).
>
> I gave it the treat, no errors occured...
>
>
>> After compilation you either replace the kernel modules manually, or you
>> copy them over to the correct place to have them auto-loaded
>> (/lib/modules/2.6.22-15-rt/kernel/drivers/ieee1394 in your case)
>
>
> Thats what I did, copied everything in the build-dir to that place in
> /lib/modules (I upgraded to 2.6.22-15-rt beforehand).
Did you reboot or manually reload the 1394 drivers? The log you give
seems to indicate that the old drivers are still used.
Also, you seem to be using the SVN trunk version. I would suggest that
you use the branches/libffado-2.0 version as that is the one where all
bugfixes are being done. A lot of them have not yet been merged into trunk.
Greets,
Pieter
> >> I think our 17" and 19" Samsungs both do 1280x1024. Certainly you
> >> might have one that only does 1024x768 but that seems like it
> >> would be an older piece of hardware.
> >>
> >> If you can supply and exact make and model number then we can
> >> probably search it out over the net.
> >>
> >> How did you decide it won't do anything larger?
> >>
> >> - Mark
> >
> > Thanks Mark, and also David.
> > The monitor is a fujitsu siemens LCD, model: C384FA-M Rev.01
> > So far I found only either fujitsu or siemens nixdorf.
> >
> > My old CRT was probably my first monitor ever, so it's pretty old
> > and had some problems sometimes. A friend offered me his old LCD.
> > The screen size is the same, 15", but it's a lot lighter and takes a
> > lot less space on my desk. I had my old monitor set to 1280x1024 or
> > 1152xsomething sometimes, which was quite o.k., but I don't manage
> > to get something like that out of the LCD.
> > If it's a hardware-limitation, it's fine by me, someday I'll get
> > myself a bigger and better one anyway.
> >
> > Thanks for help,
> > Philipp
> >
> I suspect it's 1024 max. It's not listed on the Fujitsu-Seimens web
> site any more. That makes it pretty old.
>
> It's probably working correctly.
>
> - Mark
Thanks, then I'll just keep it at that.
Already missing the x-rays 8-)
Best Regards,
Philipp
Hartmut Noack wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Pieter Palmers schrieb:
>> Hartmut Noack wrote:
>
>> There is still a log missing that is requested in the README (ffado-diag).
>>
> .
> oops -sorry :-)
You have an o2micro host controller:
04:04.0 FireWire (IEEE 1394) [0c00]: O2 Micro, Inc. Firewire (IEEE 1394)
[1217:00f7] (rev 02) (prog-if 10 [OHCI])
those are not the best ever.
To reliably use ffado with this controller you have to use patched 1394
kernel modules, you can find them here:
http://subversion.ffado.org/wiki/TxSkipPatched
The 2.6.22-15-rt file should be good for your setup (2.6.22-14-rt).
After compilation you either replace the kernel modules manually, or you
copy them over to the correct place to have them auto-loaded
(/lib/modules/2.6.22-15-rt/kernel/drivers/ieee1394 in your case), and
reboot.
Greets,
Pieter
Hello All,
Jack Audio Connection Kit 0.2.22
Rosegarden 1.5.1
Ardour 2.1
Fedora Core 6 with Planet CCRMA sources.
Using Jack Transport as the control for Rosegarden and Ardour. (This is
my first project doing using Ardour.)
In Rosegarden, I have a BPM of 160. I'm using Rosegarden to send MIDI to
my external Roland Sound Expansion modules. The audio output of the
Roland synths is sent back to the PCM Audigy2-ZS sound card in the
computer. I'm recording into Ardour.
I start recording. Ardour is getting a BPM of 120, not the 160 BPM as
Rosegarden is set to.
The Qjackctl window of Jack shows a BPM of 120.
How do I change Jack to use a BPM of 160? Is this a command line
setting I should be using?
Thanks All,
Stephen.
Folderol wrote:
> I would say stick with ogg until you see a *very* significant number of
> oga's in the wild. I've seen none so far, and there is no point in
> using an extension that nothing recognises. I would guess that players
> will eventuall be produced that will accept both extensions.
>
Well that's the pickle though isn't it? How to you get them out there
unless apps use the extension by default?
I haven't seen any linux/BSD choke on my .oga files so far. Many look to
handle the MIME just fine. Apps on windows did pretty well also though
Winamp was sadly unable to play it. :( No real point in testing iTunes. :P
> Maybe have a switch in your app so it can be changed later.
>
ATM, I have it set to .oga be default with a switch for legacy to use .ogg
So... Still a real pickle. What makes it worse is that even though Xiph
instituted these new extensions they have no intention on pushing them.
Without a push, how can there be adoption?
-Cory \m/
The alsa page says that the E-MU 1820M is supported in version 1.0.14,
so this device should be supported now. Anyone use the device? If so,
how well does it play with alsa?
--
Brad Fuller
www.bradfuller.com
I thought, it would probably help some of you, if I uploaded
my rt-config for a 2.6.25.8 realtime kernel (debian system).
# get my kernel config:
wget http://branwelt.de/download/config.gz
(this is all without any warrenty, use at your own risc)
Below is also a kind of script, that should do the whole procedure
for creating a 2.6.25.8 realtime kernel on a debian based system.
I have not testet this script.
I would recommend, to past command for command, and see if it is
working for you. (it should)
This is how I build the kernel I'm currently using.
Note: The config has the realtime-patch applied, but is not
strictly configured for realtime:
I let enabled acpi and cpu-frequency scaling,
because performance was good enough for my requirements
(2.67ms latency at 48000hz samplerate according to qjackctl).
If you encounter xruns, disable these options with "make menuconfig"
(see bottom)
I tried to keep the config general, so it may be usable on other
systems as well.
It is based on a sidux ~ 2.6.21 configuration, including updates for 2.6.25
start of the command list:
#############################################################
#############################################################
mkdir my_realtime_kernel
cd my_realtime_kernel
# get my kernel config
wget http://branwelt.de/download/config.gz
# get the kernel
wget http://www.eu.kernel.org/pub/linux/kernel/v2.6/linux-2.6.25.8.tar.bz2
# get rt-patch
wget http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.25.8-rt7.bz2
# unpack
tar xfj linux-2.6.25.8.tar.bz2
tar xfj patch-2.6.25.8-rt7.bz2
# create a symbolic link
ln -s linux-2.6.25.8 linux
cd linux
# apply patch
patch -p1 < ../patch-2.6.25.8-rt7
# move config to right place
zcat ../config.gz > ./.config
# now edit the Makefile
# change the line with EXTRAVERSION (without #) to:
# EXTRAVERSION = .8.rt7.em1
# optionally do make oldconfig
# or make menuconfig here
# make the kernel
make-kpkg --initrd kernel_image
cd ..
# finally install the kernel with a command like
# dpkg -i linux-image-2.6.25.8.rt7.em1_2.6.25.8.rt7.em1-10.00.Custom_i386.deb
#############################################################
#############################################################
