Hi all,
This weekend, starting a midnight (EST), Saturday morning (Mar 9), the
Systems Support Group at Virginia Tech has scheduled storage maintenance.
The storage that supports linuxaudio.org will be unavailable from
midnight until noon Saturday (EST) and hence the server will be offline.
thanks for your understanding.
robin
Hello!
I'm experiencing some weird issues with JACK. I got a new system the other
day, and I'm tweaking it for linux audio only basically. My issues are:
even when dsp load isn't even close to 100%, I get xruns. This only happens
at lower latencies, but still. My setup is as follows :
Kxstudio 12.04.2
3.2 realtime kernel (tried lowlatency and generic aswell)
Usb sound card Lexicon Omega
Realtimeconfig quickscan shows everything green except cpu governors, but
I'm pretty sure I don't have that on this system? It's an Intel i5 3570k
desktop. Or maybe there's some setting in BIOS equivalent of cpu governors?
If so that might very well be the problem.
I use JACK at 48khz 3 periods/buffer. I start it via falktx's Cadence.
Any ideas about this?
Also! When I'm asking for help anyway... I connect my MIDI keyboard via
MIDI in on my sound card, but that suddenly stopped working. The midi out
from the sound card is present in JACK, but it delivers no midi. Any idea
on where to start troubleshooting this?
Thank you so much for taking the time to read this. Cheers!
Hi,
I work with KXstudio and Unbuntu 12.04. Normally I think is on
KXstudio cadence the main tool for start and stop jack, but I like
qjackct. Most of the time I use both tools. Now I have seen that
cadence and qjackct shows different latency. Although both have the
same settings. Cadence always shows exactly the half of the value than
qjackct.
Which latency value of both is right?
Thanks
Chris
On Mon, March 4, 2013 3:26 am, Gabbe Nord wrote:
> Hello!
>
> I don't have hyperthreading, atleast there's nothing about that in bios.
> It's a dekstop computer though.
looking through the output of dmesg or /var/log/syslog should show if the
cpu has hyperthreading and how many cores there are. Hyperthreading should
not be a problem down to running jack with -p64, but it does make a
difference going lower... it may help make -p64 more stable too. If you
have hyperthreading this can be turned off by disabling every second cpu.
That is if you have a single core system with hyperthread, you will have
cpus 0 and 1, disable cpu 1 as it is really just the hyperthread on the
same cpu.
Just to be sure... you are not by chance using a wireless networking IF? I
have one that gives xruns even at -p1024 :P
--
Len Ovens
www.OvenWerks.net
Hi everyone!
Ubuntu Studio is looking for contributors, and there's plenty of room for
new people in all our work areas - Testing, Public Relations, Artwork,
Documentation and Development.
You don't need to be a hacker, or otherwise ordinarily skilled. It's
enough you have a friendly attitude, and the will to help.
I've prepared some pages..
* Our main site: https://ubuntustudio.org/contribute/
* Our wiki: https://wiki.ubuntu.com/UbuntuStudio/JoinTheTeam
So, if you think this might be something for you, don't hesitate to join
us!
Since this is a post to the Linux audio community, it makes sense I
explain a little bit about what you could do to contribute to the audio
side of things.
* Software Selection: Just researching what is out there, new
applications, plugins, etc - since our goal is to be a gateway for new
users coming to the Linux audio world, we want to represent Linux audio
with a nice selection of applications and settings.
* Testing: Of course, always important. We need to know what works, and
what doesn't. If we find bugs, we should report them. And we should try to
work as closely upstream, with Debian and software developers to make sure
bugs get attention and are fixed. Most of everything audio-wise on a
Ubuntu Studio system is directly imported from Debian, and we'd like to
keep it that way, as that means we don't reinvent the wheel, and also, any
improvements will spread throughout the Debian tree of derivatives.
* Performance Testing: Kernel testing, trying different drivers, hardware,
and also designing the tests to be performed. Based on the results, we
suggest and make changes where they seem most logical.
* Public Relations: Posting news, conducting interviews with developers,
musicians, artists who work with Linux platforms. Interacting with users,
etc. As we are probably the most common linux multimedia distro out there,
we have the opportunity to also spread information and experiences to a
large base of users.
* Documentation: What most try to avoid doing, probably, but a very
important part of any organization. Our goal is to reuse as much as
possible of what already exists out there, since that would lessen our
workload. But, we also need to write our own docs. As this is seldom the
first priority, there's plenty to do on this front.
I'm probably forgetting a bunch of stuff, but this is really just meant as
an introduction anyway. Hope to see some new contributors soon!
On 02.03.2013 13:00, linux-audio-user-request(a)lists.linuxaudio.org wrote:
> Hiho, I've only worked with the python2 version, but I may have an
> idea where things go wrong. On Wed, 27 Feb 2013 15:54:42 +0100
> Christoph Kuhr <christoph.kuhr(a)web.de> wrote:
>> I have a python3 app, that calls a class OSC_Communication.
>>
>> address = localhost, port = 9001
> Try for an address 0.0.0.0 instead, then the program will listen on any
> interface, and not just localhost.
> It may be that the program you are using to send is using the
> IP-address connected to one of your physical interfaces as a targer,
> rather than the loopback (localhost) address.
>
> In a sense this difference allows you to make your program more secure,
> by ignoring messages coming from outside of the machine, but
> unfortunately, not all other OSC-enabled programs allow you control
> over how they send the messages.
>
> sincerely,
> Marije
Hi, thanks for the advice, but i already tried that one out earlier
without success.
I switched to pyliblo, which works like a charm!
regards,
Ck
Hi everyone,
yesterday i tried to include pyOSC in a python3 project.
I register my callbacks, the address space is correct.
I connect to the server, it works.
But nothing happens if I send messages from puredata to any address.
Even not the default handlers.
Wireshark captures the packets.
do you have any idea, what might be the problem, where I have to look?
thanks and regards,
Ck
On Wed 27/02/13 5:33 PM , "Len Ovens" len(a)ovenwerks.net sent:
>
> On Wed, February 27, 2013 10:46 am, Grekim Jennings wrote:
> > How difficult or even possible is it to start
> with a server core system> and make it useable for a audio? I don't need a
> GUI/desktop for this.
> Not sure what you mean by a "server core". It could be starting
> with coreserver SW installed. Or be specific HW. Adding Audio Apps to a machine
> setup as a server is not hard, though a new install would be easier. The
> onlyreason to keep the server SW in place is if you want to use the machine
> both ways. In that case I would suggest setting up another run level
> justfor audio. That would make it easy to turn off some of the system
> serviceswhile doing audio or reconfigure some of the core defaults. On the
> otherhand, if you want the machine to run as a server while also using it to
> doaudio work, one of your two uses will suffer. Either the server side
> willbe slower or the audio side will need more latency.
>
This would be for the sole purpose of audio, and GUI-less ones at that. I also like the idea of being able to carry a studio on a flash drive...sort of amazing. Another machine would have Ardour etc. I
came across the "server core" terminology from the Lubuntu alternate downloads area. So, my impression was a server system is a bit more raw and basic than a desktop system and going with a "core"
version of that would be almost as basic as it gets. I know there are distros tuned for audio, but I honestly don't like all the extra stuff I don't need.
> > I installed Lubuntu server core to a usb flash
> drive. I added myself to
> Ok, this looks like just adding audio SW. Take a look at the
> ubuntustudiometas with whatever SW installer you use. (synaptic would be easiest I
> tihnk) You most likey do not want the -desktop, icons or settings, just
> the audio related ones. Though it may be just as easy to choose the
> appsyou want.
>
> > the audio group, but my usb Audiobox does not
> seem to be working,> although it is recognised with aplay -l. Should
> it work without any> additional steps?
>
> Working? Meaning what? Does lubuntu use pulse like most of the other
> *buntus? Have you set your USB card as the default sound device with
> pavucontrol? Which application are you playing audio on? If the machine
> you are using has an internal card, that would be the default, not your
> USB card. Are the levels raised in the alsa mixer? Not muted?
>
I noticed when running my software that the playback variables are set correctly through Alsa calls, but the record ones are not. It's just the first time the (Presonus) Audiobox has not initialized properly
on probably a dozen systems I have tried it on. I'm assuming the kernel should be the same between a server and a desktop. I works fine on the same 12.04 desktop/Unity version. I wasn't sure if we
needed to run modules or set something a certain way to tap audio capability in a server system. Again, doesn't have to be a sever system at all. I just thought it might be closer to what I am after to
begin with.
> So what are you trying to achieve? And how? It would be easy to tell
> thesethings if I was there in person, but I am not and so to help you we
> needas many details as possible.
>
Thanks for the help :) See above about the goal here. But again, I crave simplicity and I like to build a system around a specific task and not have one machine do everything.
> > I suppose I could build an Arch system, but I
> was pleasantly surprised> by the performance of Ubuntu 12.04 (desktop)
> with the particular> software I want to run and thought I would try
> an even more basic> setup. Thanks!
>
> Pretty much all the Linux setups use alsa these days. There is not much
> difference from one to the next at that level. You should be able to
> getsound with any of them.
>
>
> --
> Len Ovens
> www.OvenWerks.net
>
>
>
I'd like to put out a question.
What would seem like the most common channel configuration when using the
module-jackdbus-detect?
module-jackdbus-detect is a module that will detect when jackdbus starts,
and automatically creates a Pulseaudio sink and source for jack. It's a
part of the pulseaudio source, and is separated into its own package on
Debian based distros, called pulseaudio-module-jack.
Currently, it will create as many channels for its sink and source,
separately, as there are channels on your audio device.
Also, it follows the standard model for surround audio, so if you have 8
channels, the module will create a 7.1 interface for the sink and source.
In the case where you have 8 in and 2 out, the module will create 7.1 sink
and stereo source.
In the case where you have more than 8 channels, it will create 7.1 and
add connections named "aux" for each additional channel.
There's now a patch in PA 3.0, written by Peter Nelson, that allows us to
configure how many channels PA should have for both in and out at once.
I'm proposing to have the module be stereo by default. Would this be what
people want?
