Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

4 participants
7502 discussions

Re: [LAU] FIC neo1973 linux mobile

by Marc-Olivier Barre

On 9/18/07, Robert Jonsson <rj(a)spamatica.se> wrote: > Hi folks, > > Lots of talk today about linux mobiles on the internets. Apparently > Trolltech has ported Qtopia to the neo1973 linux mobile. Interesting > news in itself. > Even more so the neo1973 seem to be a very interesting device in itself. > > I only very quickly glanced through the specs on the openmoko site, it > looks to be a very capable device with interesting possibilities. > > Apart from pretty much all mobile devices I know it seems to have USB > host-controller possibilities which should make it possible to connect > an USB soundcard to it. Would make a splendid recording/playback device. > > Also, on this page: > http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem there are some > schematics of the audio hardware which also seem interesting. Possibly > there's both stereo line in and stereo line out, the inputs seems to > route through some "Voice codec" "thing" though... > > Anyone know anything more about this device? Hi Robert, I've been following this project for a while now (I'm waiting the release of the public version of the Neo in October to get one), most of the useful info is on the wiki. I won't recommend the chat room on freenode. It's far from being as interesting as #LAD ;-) Anyways... What I think is that is would make perfect studio remote controle (in addition to a phone) since it has a touch screen. Fact : Did you know that Apple had the idea of the iPhone a few weeks after Sean Moss-Pultz (the project leader at FIC) made a public presentation of the openmoko project ? Funny... BTW, I managed to build a jack package for an emulated Openmoko system in a matter of minutes. I'm sure I've lost the package since then, but just so you know jack runs out of the box on an arm (if compiled without any optimization of course). CCed to LAD since some people might find this interesting... Cheers ! __________________ Marc-Olivier Barre.

17 years, 9 months

Re: wine, vst, 64bit

by Dave Phillips

Marco Milanesi wrote: > By following LAD/LAU lists, I see that you are using pure 64bit >arch, could you confirm that VSTs with 32 bit wine works? > > Hi Marco, I've cc'd this response to the lists because I want to clarify the situation for all who are interested. The short answer is, "Yes". The longer answer is "Yes, with some very specific caveats." Wine can be compiled as a 32-bit binary for running in a pure 64-bit system. I'm running such an arrangement now, with backport packages of Wine and libwine 0.9.34 (Debian, 64 Studio). However, IIRC 64 Studio already has more recent packages available. The biggest problem is latency. In this scenario it's not possible to use the JACK/wineasio combination, so you'll end up using either the OSS or ALSA sound system for Wine (select in winecfg). It may be possible to lower latency with either of those drivers, but I've not worked at it. So far I've only tested Reaper with some VST plugs. It worked, but I wouldn't try using it as a production environment. I haven't yet tested any other hosts. And just to be clear: At this time I would advise anyone who wants to run VST plugins in production to do so with either JAD or 32-bit 64 Studio. They support the wineasio driver, thus greatly improving the latency numbers. Best, dp

17 years, 9 months

[ANN] JAD 1.0 officially released

by Dave Phillips

Forwarded, sorry for the cross-posting: The JackLab Project announces its first public release Promotion association planned The technical manager of the JackLab of project, Oliver Bengs, released the final 1.0 version of the JackLab Audio Distribution (JAD) today after development period of over eight months. JAD 1.0 is based upon OpenSUSE 10.2 with the addition of a real time Linux kernel for fast audio processing with the professional audio server JACK. JackLab 1.0 includes one of the most comprehensive selections of open source audio and multimedia software to date. The Enlightenment D17 window manager (with 'KDE-lite' tweaks) is used by default, with the option of using the full KDE 3.5.7 instead. JAD 1.0 aims to lower the Linux entry barriers, making things as easy as possible for musicians and multimedia content creators, and it offers complete compatibility with openSUSE 10.2. The Smart package manager is included for quickly and easily updating or adding new software and the YaST system tool is included for easy graphical system administration. The system is immediately operational after installation for tasks such as multi-track recording with Ardour 2, real time audio synthesis with ZynAddSubFX , MIDI sequencing with Rosegarden, video editing with KDEnlive, and graphics manipulation with programs such as Inkscape and Gimp. Unlike most other existing Linux audio distributions JAD 1.0 offers complete support for ASIO. Thanks to WINE you can useWindows VST host programs such as Reaper or EnergyXT2 with a very large number of VST plugins, with latency as good as native Linux JACK audio applications. Simply add the wineasio driver to the WINE registry and these applications can then be used as easily as if from native Windows. This is all easily done and well-documented on the JackLab wiki. In addition, native VST for Linux is supported by JOST, a powerful modular host. Some native Linux VST plugins are included with the distribution but there are more that can't be included for legal reasons. JOST also supports LADSPA, the native Linux Audio Developer plugin format. JackLab comes with over 300 LADSPA plugins. JAD 1.0 is the result of a collaboration of musicians and free software developers and enthusiasts. This community was started by musician and media producer Michael Bohle in order to improve and promote the development of pro-audio under Linux. OpenSUSE was selected as the basis of JAD because it is a very user-friendly version of Linux. The project is independent from OpenSUSE but intends to give back to the community by improving SUSE's support for pro-audio and multimedia creation. In order to safeguard JAD and its future development, a registered promotion association [JackLab e.V.] is planned. JackLab e.V. will sponsor activities of the JackLab community such as workshops, participating in shows, and holding developer conferences. Hopefully it will also fund the development of exciting open source audio projects. The project would like to thank all the testers and early adopters for their assistance in creating JAD 1.0, along with all the good discussions in blogs, forums and magazines. The overwhelmingly positive response from musicians was very encouraging. We received feedback from the whole world, where JAD 1.0 is now used in recording studios, schools, workshops and youth centers. Michael Bohle, project-leader www.jacklab.org Screenshots: http://jacklab.net/jacklaborg/english/?JAD_1.0_Screenshots

17 years, 9 months

Re: A common plugin repository (WAS:Re: [LAD] ladspa qa?)

by Stefano D'Angelo

2007/9/13, Krzysztof Foltman <wdev(a)foltman.com>: > Stefano D'Angelo wrote: > > > I'd say package format (.rpm, .deb, etc), OS distribution (Ubuntu, > > OpenSUSE, etc.), CPU architecture (ix86, x86_64, etc.) > > I guess one could think of adding the subarchitecture (as in: p3, p4) > and optimization target too. The difference between subarchitecture and > optimization target would be same as difference between -mcpu and -mtune > gcc options. Well... yes. But I don't know if it would work well with a regular package manager (in terms of packaging work, updates, etc.). Stefano

17 years, 9 months

ladspa qa?

by Tim Blechmann

hi all, i'm not really familiar with the ladspa development process, but is there any quality assurance for ladspa plugins? i have been implementing some of my filters as ladspa plugins, but when trying to compare them with others, i found, that some of the plugins did not do, what i expected them to do (a white noise generator did not generate white noise, a shelf filter was highly unstable when changing parameters) ... of course, all plugins are free (as in speech), without any warranty, but i still think, that there should be a certain amount of quality assurance, if we want people to use the ladspa plugins ... have there been some thoughts of introducing some kind of ladspa qa? best, tim -- tim(a)klingt.org ICQ: 96771783 http://tim.klingt.org Desperation is the raw material of drastic change. Only those who can leave behind everything they have ever believed in can hope to escape. William S. Burroughs

17 years, 9 months

alsa seq client ids??

by IOhannes M zmoelnig

hi in an alsa-seq enabled application i would like to automatically connect to all available "hardware" midi devices on startup. however i have found no way to find out, which clients are real midi devices and which are not. my first attempt just connects to everything except itself and client-0 ("system"), which is rather sub-optimal, as it includes the "midi through" which tends to lead to wild midi feedbacks (our application _can_ do midi through too...) unfortunately i haven't found any documentation. what i have found is: - http://www.alsa-project.org/alsa-doc/alsa-lib/group___sequencer.html (saying that "user clients" have ids 128..191; this is fine, to filter out other applications, but not enough for me) - http://alsa.opensrc.org/index.php/Aconnect (which gives a "simplistic guideline for client numbers": 0..63=internal; 64..127==devicedrivers; 128..?==userapps; this would be perfect, but unfortunately this just seems to be outdated information; e.g. i have 4 hw-midi devices connected and they are assigned the numbers 16,20,24,28) any hints? or iam i totally out of my mind for trying to (optionally) a(uto)connect on the application-side? mfg.asdr IOhannes PS: i guess this question might be more appropriate on one of the alsa lists, but since i am subscribed to lad and not to one of these, .... PPS: sorry if this comes through 2 times; i originally sent this email from an non-subscribed account...

17 years, 9 months

No Timidity Development for the last 3 years

by Carlo Florendo

Hi, Does anyone know the status of Timidity's development aside from the one posted on its sourceforge website (timidity.sourceforge.net)? The Japan URL, timidity.jp seems to be down as well for the longest time I could think of. In any case, it's still great software and I use it a lot (and will most definitely continue to use it for some time). Is the project (almost) dead? Where could we see traces of its life? Thank you very much. Best Regards, Carlo -- Carlo Florendo Softare Engineer/Network Co-Administrator Astra Philippines Inc. UP-Ayala Technopark, Diliman 1101, Quezon City Philippines http://www.astra.ph -- The Astra Group of Companies 5-3-11 Sekido, Tama City Tokyo 206-0011, Japan http://www.astra.co.jp

17 years, 9 months

[OT] assembler guru needed

by Dave Phillips

Greetings, I'm trying to compile Wine 0.9.44 as a 32-bit executable on an AMD 64-bit system (that is, with -m32, not in a chroot). I've done this successfully in the past under 64Studio, but my recent crash & reinstall has introduced something (or left out something) that leaves me unable to build Wine. Here's the problem point : gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -D__i386__ -o interlocked.o interlocked.c {standard input}: Assembler messages: {standard input}:38: Error: suffix or operands invalid for `push' {standard input}:39: Error: suffix or operands invalid for `push' {standard input}:46: Error: suffix or operands invalid for `pop' {standard input}:47: Error: suffix or operands invalid for `pop' make[2]: *** [interlocked.o] Error 1 make[2]: Leaving directory `/home/dlphilp/src/wine-0.9.44/libs/port' make[1]: *** [port] Error 2 make[1]: Leaving directory `/home/dlphilp/src/wine-0.9.44/libs' make: *** [libs] Error 2 Here's the code in question : __ASM_GLOBAL_FUNC(interlocked_cmpxchg64, "push %ebx\n\t" "push %esi\n\t" "movl 12(%esp),%esi\n\t" "movl 16(%esp),%ebx\n\t" "movl 20(%esp),%ecx\n\t" "movl 24(%esp),%eax\n\t" "movl 28(%esp),%edx\n\t" "lock; cmpxchg8b (%esi)\n\t" "pop %esi\n\t" "pop %ebx\n\t" "ret"); And here's my GCC : dlphilp@64studio:~/src/wine-0.9.44$ gcc --version gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) Maybe I need to use a different gcc version ? Whatever, there's nothing on Google that clearly points to a solution, so I turn to the GLAD team (Giants of Linux Audio Development) for guidance. Any suggestions or advice that might move me towards resolving this difficulty ? Best, dp

17 years, 9 months

Re: [LAD] [OT] assembler guru needed

by Dave Phillips

Cedric GESTES wrote: > try pushl/popl , it the 32bit version. but I dont know 64bit asm... Thanks, Cedric, but I still got no joy. :( In fact, I received exactly the same error message, i.e. referring to push, not pushl as I'd expect. Any idea why that happened ? Best, dp

17 years, 10 months

LADSPA Windows OR Effects on all three major systems.

by N. Gey

Hello, my friends and I are developing a Computer Game and it should run on Linux, Mac and Win. Now we're thinking about Audio Effects. Generell reverb, compressor with sidechain (to compress the signal when speech is active, so its clearly heard, no matters how the player has set his audio balance. you know... like in Radio Stations). We are using FMod4 and searching for a platform indipendent effect system. Maybe there is LADSPA port to windows? Or have you other suggestions? greetings, Nils

17 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-dev