Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7520 discussions

Re: [LAD] Memory corruption&coredump on Exit in my first vala program spekle

by Niels Mayer

On Sat, Aug 28, 2010 at 6:44 PM, Alexander Kojevnikov <alexander(a)kojevnikov.com> wrote: > You can try running spekle under valgrind [1]. After testing it on a > flac file I already see that spek_spectrogram_put_pixel() is used with > wrong arguments causing an out-of-bounds memory write. Thank you for the clue. I'm especially thankful that I won't have to run valgrind for hours on end with my CPU fans whining at top-speed just to decode a video or mp3 :-) ... I will just go straight to debugging spek_spectrogram_put_pixel(). I've added your suggestion to my issue: http://code.google.com/p/spekle/issues/detail?id=1#c3 > On a side note, feel free to submit patches adding batch support to > Spek, there's even an open issue for it [ http://code.google.com/p/spek/issues/detail?id=6 ] I added the following comment on your issue: http://code.google.com/p/spek/issues/detail?id=6#c5 ........... http://spekle.googlecode.com is a fork of Spek 0.6 specifically designed for batch use and for usage without an X server or GUI. It would be great if the changes for spekle could be incorporated back into Spek. Although down the road, some functionality I plan to add in spekle ( http://vamp-plugins.org ) may be out-of-scope for Spek. It's not something that'll be an obvious patch since I replaced spek.vala with http://spekle.googlecode.com/svn/trunk/spekle/src/spekle.vala and and spek-window.vala turned into http://spekle.googlecode.com/svn/trunk/spekle/src/spek-object.vala and there's a different set of build targets as well http://spekle.googlecode.com/svn/trunk/spekle/src/Makefile.am ... ........... Other code-mangling includes needing to add an extra callback parameter to the Pipeline() constructor: http://spekle.googlecode.com/svn/trunk/spekle/src/spek-pipeline.vala and lots of small changes to http://spekle.googlecode.com/svn/trunk/spekle/src/spek-spectrogram.vala . To recognize what changed, comment-outs of your original 'spek-0.6' code are done with "//" at the beginning of a line, and most of my changes are marked with an "NPM" comment. Since I just got 'spekle' running, and my current changes are a first-pass hacking of your original spek sources, it probably makes sense for me to continue doing development and debugging on 'spekle' and at some point in time in the future, submitting a more definitive patch for http://code.google.com/p/spek/issues/detail?id=6 . In case you're interested in collaborating on spekle, I added you as a committer (akojevnikov). It may also make sense to test out batch-mode ideas in spekle first and then move them back to 'spek' when they've settled down. Let me know how you wish to proceed, and thanks for making Spek available and GPL! -- Niels http://nielsmayer.com

15 years, 3 months

Memory corruption&coredump on Exit in my first vala program spekle

by Niels Mayer

Anybody have any ideas on http://code.google.com/p/spekle/wiki/EvidenceOfMemoryCorruptionOnExit (warning contains large images, http://spekle.googlecode.com/svn/wiki/evidence-of-memory-corruption-on-exit… for error text only). issue: http://code.google.com/p/spekle/issues/detail?id=1 Summary: after successfully writing a spectrogram image in my first Vala programming http://spekle.googlecode.com/ (a displayless-version of Alexander Kojevnikov's http://www.spek-project.org/ ) I get the following error, despite not explicitly calling free() out of my Vala code: Spekle: saving 'j_s_bach-d_minor_invention.ogg.png'... DONE! *** glibc detected *** spekle: free(): invalid pointer: 0x00007fa7e05ca010 *** ======= Backtrace: ========= /lib64/libc.so.6[0x3ac0874ac6] /usr/lib64/libpixman-1.so.0(pixman_image_unref+0x83)[0x3ac9e161b3] /usr/lib64/libcairo.so.2[0x359c016b85] /usr/lib64/libcairo.so.2(cairo_surface_finish+0x36)[0x359c02c9d6] /usr/lib64/libcairo.so.2(cairo_surface_destroy+0x55)[0x359c02ca45] spekle[0x406b1e] /lib64/libgobject-2.0.so.0(g_object_unref+0x15f)[0x3ac380da1f] spekle[0x407d3d] /lib64/libgobject-2.0.so.0(g_object_unref+0x15f)[0x3ac380da1f] spekle[0x403857] /lib64/libc.so.6(__libc_start_main+0xfd)[0x3ac081eb1d] spekle[0x403439] The errors seems to occur intermittently, and more often when using media that is ogg. Retrieving via HTTP seems to reduce the error potential, but it still happens that way too... The relevant libraries and compiler I'm using: vala-0.9.3-1.fc12.x86_64 vala-tools-0.9.3-1.fc12.x86_64 vala-devel-0.9.3-1.fc12.x86_64 libpng-devel-1.2.44-1.fc12.x86_64 libpng-1.2.44-1.fc12.x86_64 gtk2-devel-2.18.9-3.fc12.x86_64 gtk2-2.18.9-3.fc12.x86_64 ffmpeg-0.6-2.fc12.x86_64 ffmpeg-libs-0.6-2.fc12.x86_64 ffmpeg-devel-0.6-2.fc12.x86_64 See http://spekle.googlecode.com/svn/trunk/README for instructions on obtaining by 'svn' and building on Linux. Niels http://nielsmayer.com

15 years, 3 months

mudita24 peaks & peak reset

by David Santamauro

Hi, As I was checking out the new mudita24, I noticed that the peak line on the meters doesn't go to zero after the signal is 'silence'. I have to manually click "reset peaks". Is this on purpose? David PS: nice overhaul, great work, thanks.

15 years, 3 months

Re: [LAD] Mixer GUI for EMU 10k cards

by hermann

Am Samstag, den 28.08.2010, 14:21 -0400 schrieb Camilo Polymeris: > Hi > Sorry. According to that, it seems it's not an EMU 1010 based card. > Probably a completely different beast. > > These are the card this app is intended for: > http://www.emu.com/products/welcome.asp?category=505& > > Is yours one of those? > If so, which version of the alsa drivers are you running? > > Greetings, > Camilo Ah okay, my is this one here : http://en.wikipedia.org/wiki/Sound_Blaster_Live! Sound Blaster Live! Platinum, it's EMU10K1 based. EDIT:// alsa driver is snd-emu10k1 with kernel 2.6.33.6-rt26 #1 SMP PREEMPT RT Tue Jul 27 06:22:24 CEST 2010 i686 GNU/Linux greats hermann

15 years, 3 months

Mixer GUI for EMU 10k cards

by Camilo Polymeris

Hello all, A long ago, I said on this list (I think), I had the intention to write a graphical mixer/router for the EMU 10k cards (EMU 1212m & EMU 1616m). I wanted to make a nice, well-written, full-featured app with routing levels and eventually effects and all, but couldn't figure out all the intricacies of the card's driver. So, over the last two nights I hacked together a simple "Matrix"-style app, very ugly in code, but functional, for me, at least. I won't have time to maintain it, but if you want to try it out, at the end of this message you'll find links to a screenshot, the source package and an x86_64 build. You'll need Qt & ALSA libraries, of course. Be aware that many features are missing, but basic routing works. I'll put up a version control repo when I have time. Any comments welcome. Greetings, Camilo Links. Everything licensed under GPLv3: http://www2.udec.cl/~cpolymeris/emutrix/Screenshot-EMutrix-1.png http://www2.udec.cl/~cpolymeris/emutrix/emutrix-0.1.tar.bz2 http://www2.udec.cl/~cpolymeris/emutrix/emutrix

15 years, 3 months

Whitespaces in jack client/port names / jack_connect

by Philipp

Hi, I have issues with jack client names that contain whitespaces. Example: $ jack_connect MPlayer [19079]:out_0 system:playback_2 ERROR [19079]:out_0 not a valid port Any idea how I can make this work? I tried: $ jack_connect "MPlayer [19079]:out_0" "system:playback_2" ERROR MPlayer [19079]:out_0 not a valid port $ jack_connect 'MPlayer [19079]:out_0' 'system:playback_2' ERROR MPlayer [19079]:out_0 not a valid port So I wonder whether spaces in jack client names and ports are even allowed, since imho jack_connect is a rather fundamental tool, and either the tool or those clients are broken. -- Philipp -- "Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan

15 years, 3 months

Re: [LAD] [LAU] mudita24 1.02 -- improved envy24control mixer/router for ice1712-based sound-cards

by Niels Mayer

On Sun, Aug 8, 2010 at 7:59 AM, Geoff King <gsking1(a)gmail.com> wrote: > I tried the source version of your 1.0.2 mudita release. I'm having > problem with the build step. This is with FC13. Any thoughts? >... > -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 > -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype > -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 > -lasound > /usr/bin/ld: levelmeters.o: undefined reference to symbol 'log10@@GLIBC_2.0' > /usr/bin/ld: note: 'log10@@GLIBC_2.0' is defined in DSO /lib/libm.so.6 Geoff -- thanks for reporting this issue. It is a configuration mistake in this release which doesn't show up in F12, which is what I'm still using. Apparently, Fedora13 wants it to link with "-lm", but F12 links happily without "-lm" ...So I never saw this misconfiguration when I tested my distro build on F12... As a quick fix, you should be able to link successfully by adding "-lm" to the end of the linking command: gcc -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/alsa -g -O2 -o envy24control envy24control.o levelmeters.o midi.o mixer.o patchbay.o hardware.o driverevents.o volume.o profiles.o config.o -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lasound -lm The correct approach is to add "-lm" to the configuration files (i thought i had, but mistakenly modified the generated file rather than the configuration input files -- and "make dist-gzip" didn't of course include my modification) ... I will need to fix this build-blunder in the next release. Sorry. If anybody has a suggestion on the most portable/reliable way of doing this, please let me know. I believe adding a line to configure.in-gtk2 like ENVY24CONTROL_LIBS="$LIBS $ALSA_LIBS $GTK_LIBS -lm" would do the trick, but you never know what happens to a simple line of script out in the wild :-). Is the above an accepted&proper way of adding "-lm" to an autoconf file? -- Niels http://nielsmayer.com

15 years, 3 months

guitarix-0.11.1 Bug fix release

by hermann

On behalf of the guitarix team I'm proud to announce Guitarix Version 0.11.1 Bug fix release Guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. Guitarix uses the Jack Audio Connection Kit as its audio backend and brings to the jack audio graph a mono amplifier input/output port, and a FX mono input with two (stereo) output ports. Guitarix provides a jack midi input port to connect a midi controller (midi learn) and a (3 channel) jack midi output port, feed by a (scalable) mix of the tuner and a beat-detector. Release 0.11.1 comes with following changes : * fix Bug Echo/Chorus/Delay/Slooper don't work * add pre/post processing switch to all mono Effects We put the Guitarix widgets into a library, with the goal of making them usable independently from Guitarix. You can build it as shared library and there's a c++ (gtkmm) wrapper, a python wrapper and glade support. Check it out and look for examples in those directories, or just build a nice looking display with the glade editor, and of course ask in our Guitarix forum (it's still alpha). As a side note, Guitarix is now in debian(sid/squeeze/Experimental) , have fun _________________________________________________________________________ guitarix is licensed under the GPL. Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ please report bugs and suggestions in our forum here: http://sourceforge.net/apps/phpbb/guitarix/ ________________________________________________________________________ For capture, guitarix uses the great 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the zita-convolver library, and, for up/down sampling we use zita-resampler, both written by Fons Adriaensen. If you don't have it installed, get it here: http://www.kokkinizita.net/linuxaudio/index.html We use the marvellous faust compiler to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ ________________________________________________________________________ For faust users : All used Faust dsp files are included in /guitarix/src/faust, the resulting cc files are in /guitarix/src/faust-generated The tools we use to convert (post-processing and plot) the resulting faust cpp files to the needed include format, stay in the /guitarix/tools directory. ________________________________________________________________________ regards Hermann Meyer, James Warden, Andreas Degert

15 years, 4 months

monobristol 0.60.1 & System.NullReferenceException

by APO33

Hi There, Working on new version of APODIO http://www.apodio.org & wiki of the work in progress http://www.apodio.org/wiki (please add ideas there if you feel like!!) I compiled monobristol (bristol GUI) and met the same problem as falktx which to be around here. the erro when starting monobristol is : Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object at MainWindow..ctor () [0x00000] at monoBristol.MainClass.Main (System.String[] args) [0x00000] I followed this message : http://old.nabble.com/Is-anyone-using-monobristol-0.60.1--td29132285.html (which seems to be the same everywhere) I uptaded it with the repository of kxstudio... but same error... did I missed something? I used ubuntu 10.04 thanks for the answer Julien -- APO33 space of research and experimentation http://www.apo33.org info(a)apo33.org

15 years, 4 months

what does "full range" mean with regard to ambisonics and speakers?

by "Bearcat M. Şandor"

Folks, I'm a recovering audiophile. When i was reading the magazines and reading about over priced (in my now opinion) speakers, the words "full range" tended to mean that a speaker was reasonably flat from 20 Hz to 20 kHz. Granted those were unusual. I have read that speakers in an ambisonic set up should be "full range". I'd like to set up a ambisonic speaker system (8 channel to start), and the prospect of 8 full range channels is daunting. Since it seems they would be stand or wall mounted (at least some of them) that means monitors and subwoofers. Since all channels must be the same, that means 8 subwoofers...somewhere in the room. So what does "full range" mean usually and what does it mean in terms of talk on this list? Thanks, Bearcat

15 years, 4 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