Pd-list August 2017

pd-list@lists.iem.at

68 participants
100 discussions

Re: [PD] Midi Real Time Active Sensing Message Ignored
by Alexander Connor 21 Aug '17

21 Aug '17

I think the most probable reason active sense is being ignored in the latest version of PD is because I reported this bug (and other midi issues) after fielding and confirming multiple problem reports on the PD web forum: https://lists.puredata.info/pipermail/pd-dev/2017-01/020888.html I agree that this problem (most likely) has nothing to do with the volume of messages; PD internal message bus probably has to handle tons more message volume than anything external MIDI could produce. My main use (insofar as my own patch programming) for PD is modular MIDI control on systems running 16+ ports at a time. I've been working on it for years and believe me, there are numerous problems with the MIDI implementation in PD and I have quite a lot to say about this subject in general. I've been preparing a full list of issues to post here but I want to re-test with the latest version to see where things currently stand. It's really needed, there is a lot of confusion, missinfo and missinformation on this list concerning midi and the state of it's implementation in PD.

1 0

Re: [PD] Midi Real Time Active Sensing Message Ignored
by Dan Wilcox 20 Aug '17

20 Aug '17

I think the reason realtime messages are ignored when receiving is that, by their nature, there are *a lot* of them and they come *really quickly*. Based Pd's architecture, I can imagine a flood of realtime messages might make the GUI unresponsive, so they are left off. I might be wrong on this. > On Aug 20, 2017, at 4:20 AM, pd-list-request(a)lists.iem.at wrote: > >> actually it would be cool if [midiin] would really output all MIDI >> messages! >> > > maybe... try and open an issue on github, or a Pull Request (PR) and make a > case for that ;) > > [midiclkin] doesn't output any clock messages while [midirealtimein] does >> so it's apparently broken. >> > > It is broken, and instead of being fixed, it is actually being removed, so > the idea is to keep using [midirealtimein] for that. -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

3 5

Data in audio / modem
by Max 20 Aug '17

20 Aug '17

Hi list, If I'd would want to encode (sensor) data in an audio signal, how would I go about that? Like a modem sort of. A volume independent solution that's easy on the processor. m.

3 4

conflicting block~ objects in same page
by Jean-Marie Adrien 20 Aug '17

20 Aug '17

Hello Got this error message "conflicting block~ objects in same page » … not very explicit though since i must be using block~ objects without even knowing it "find error" returns big subpatch with no further detail. anyone has a hint ? many thanks JM

2 2

Midi Real Time Active Sensing Message Ignored
by Mario Buoninfante 20 Aug '17

20 Aug '17

Hi All, I noticed that Pd doesn't receive the real time message 254 (0xFE). it's able to generate it, but will ignore it as input. I tried with [midirealtimein] and [midiin]. I'm sure my midi device is generating and receiving this message and Pd is ignoring it. I'm trying sending out the message via midi device, then the midi out of my device is connected to the midi in (loopback). of course I'm monitoring the device in and out with an external software, so I'm sure the message is sent and received. does anyone know something about that? cheers, Mario

3 2

More than one gem_state outlet
by Federico Camara Halac 20 Aug '17

20 Aug '17

Hello, I made a pix_fft2 object that calculates the magnitude of the spectrum [1] based on [2] and [3]. So far, it works pretty much the same as pix_opencv_dft but I want to expand this further: I'm making a different one, and I have problems because I want to output real an imaginary values as images. The code is in [4]. I'm following these instructions [5], but I can't wrap my head around it. How would I go about sending a second gem_state (or image) via a 2nd outlet ? Are there any examples out there? What's wrong with [4]? A solution for this was to output all pixels as a list, but I don't think it's very efficient and it messes around with the pixel order. Thanks! fede [1] https://github.com/fdch/fd_lib/tree/master/pix_fft2 [2] how fftw works from William Brent's recent timbreID [3] how a pix object works with Antoine Villeret's pix_opencv [4] https://github.com/fdch/fd_lib/blob/master/pix_fft/pix_fft.cpp [5] https://lists.puredata.info/pipermail/gem-dev/2011-11/005642.html PS: working on osx10.11.6 with Gem from deken,latest Pd.0.48.0 -- http://fdch.github.io/tv

1 0

Re: [PD] More than one gem_state outlet
by Federico Camara Halac 19 Aug '17

19 Aug '17

Hello list, I made a pix_fft2 object that calculates the magnitude of the spectrum [1] based on [2] and [3]. So far, it works pretty much the same as pix_opencv_dft but I want to expand this further: I'm making a different one, and I have problems because I want to output real an imaginary values as images. The code is in [4]. I'm following these instructions [5], but I can't wrap my head around it. How would I go about sending a second gem_state (or image) via a 2nd outlet ? Are there any examples out there? What's wrong with [4]? A solution for this was to output all pixels as a list, but I don't think it's very efficient and it messes around with the pixel order. Thanks! fede [1] (github dot com) /fdch/fd_lib/tree/master/pix_fft2 [2] how fftw works from William Brent's recent timbreID [3] how a pix object works with Antoine Villeret's pix_opencv [4] (github dot com) fdch/fd_lib/blob/master/pix_fft/pix_fft.cpp [5] https://lists.puredata.info/pipermail/gem-dev/2011-11/005642.html PS: working on osx10.11.6 with Gem from deken,latest Pd.0.48.0 PSS: resending to the list because it did not went through yesterday

1 0

Issue with Midi active sensing message
by mario.buoninfante 19 Aug '17

19 Aug '17

1 0

Issue with MIDI "active sensing" message
by mario buoninfante 19 Aug '17

19 Aug '17

1 0

Compilation - errors, options and questions
by Yoann Le BORGNE 17 Aug '17

17 Aug '17

Hi! First of all, congrats for the 0.48 release and thanks to everyone involved in Pd development! I've already successfully compiled previous versions of Pd in the past using: ./autogen.sh ./configure make (by the way I'm building for Linux Mint 18.2 64bits) but this time I set some options, namely: ./configure --disable-locales --enable-fftw --enable-jack --disable-portaudio --disable-oss Compilation stops with libtool: link: g++ -g -O2 -o pd pd-d_arithmetic.o pd-d_array.o pd-d_ctl.o pd-d_dac.o pd-d_delay.o pd-d_fft.o pd-d_filter.o pd-d_global.o pd-d_math.o pd-d_misc.o pd-d_osc.o pd-d_resample.o pd-d_soundfile.o pd-d_ugen.o pd-g_all_guis.o pd-g_array.o pd-g_bang.o pd-g_canvas.o pd-g_clone.o pd-g_editor.o pd-g_graph.o pd-g_guiconnect.o pd-g_hdial.o pd-g_hslider.o pd-g_io.o pd-g_mycanvas.o pd-g_numbox.o pd-g_readwrite.o pd-g_rtext.o pd-g_scalar.o pd-g_template.o pd-g_text.o pd-g_toggle.o pd-g_traversal.o pd-g_vdial.o pd-g_vslider.o pd-g_vumeter.o pd-m_atom.o pd-m_binbuf.o pd-m_class.o pd-m_conf.o pd-m_glob.o pd-m_memory.o pd-m_obj.o pd-m_pd.o pd-m_sched.o pd-s_audio.o pd-s_entry.o pd-s_file.o pd-s_inter.o pd-s_loader.o pd-s_main.o pd-s_midi.o pd-s_path.o pd-s_print.o pd-s_utf8.o pd-x_acoustics.o pd-x_arithmetic.o pd-x_array.o pd-x_connective.o pd-x_gui.o pd-x_interface.o pd-x_list.o pd-x_midi.o pd-x_misc.o pd-x_net.o pd-x_scalar.o pd-x_text.o pd-x_time.o pd-x_vexp.o pd-x_vexp_fun.o pd-x_vexp_if.o pd-s_audio_alsa.o pd-s_audio_alsamm.o pd-s_midi_alsa.o pd-s_audio_jack.o pd-d_fft_fftw.o -Wl,--export-dynamic -lm -lasound -ljack -lpthread -ldl -lrt -lfftw3f pd-s_file.o: In function `glob_loadpreferences': /home/yoann/Sources/pd-0.48-0/src/s_file.c:624: undefined reference to `sys_close_midi' pd-s_inter.o: In function `glob_quit': /home/yoann/Sources/pd-0.48-0/src/s_inter.c:1378: undefined reference to `sys_close_midi' pd-s_midi.o: In function `sys_putnext': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:118: undefined reference to `sys_putmidibyte' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:119: undefined reference to `sys_putmidimess' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:118: undefined reference to `sys_putmidibyte' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:119: undefined reference to `sys_putmidimess' pd-s_midi.o: In function `sys_get_midi_devs': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' pd-s_midi.o: In function `sys_putnext': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:118: undefined reference to `sys_putmidibyte' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:119: undefined reference to `sys_putmidimess' pd-s_midi.o: In function `sys_pollmidiqueue': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:479: undefined reference to `sys_poll_midi' pd-s_midi.o: In function `sys_putnext': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:118: undefined reference to `sys_putmidibyte' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:119: undefined reference to `sys_putmidimess' pd-s_midi.o: In function `sys_open_midi': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:582: undefined reference to `sys_do_open_midi' pd-s_midi.o: In function `sys_get_midi_devs': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' pd-s_midi.o: In function `glob_midi_setapi': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:646: undefined reference to `sys_close_midi' pd-s_midi.o: In function `glob_midi_dialog': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:796: undefined reference to `sys_close_midi' pd-s_midi.o: In function `sys_get_midi_devs': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' pd-s_midi.o: In function `outmidi_byte': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:250: undefined reference to `sys_putmidibyte' pd-s_midi.o: In function `sys_get_midi_devs': /home/yoann/Sources/pd-0.48-0/src/s_midi.c:813: undefined reference to `midi_getdevs' collect2: error: ld returned 1 exit status This happens only when I try to disable OSS (that I don't need as I use Alsa and Jack). After reading src/makefile.gnu, I could however compile with OSS disabled by using: make -f makefile.gnu JACK=true PA=false OSS=false But doing this compiles Pd without working Jack support API 5 not supported, reverting to 1 (ALSA) Anyway I simply went with OSS enabled but wanted to give some feedback on this behavior. While browsing makefile.gnu, I saw # You can add compiler flags using CODECFLAGS, MORECFLAGS and/or MORELDFLAGS. # For example, you can turn off optimizing and enable debugging: CODECFLAGS=-g # or *compile with native double precision: MORECFLAGS=-DPD_FLOATSIZE=64* Is this flag enabling double precision as explained here -> http://www.katjaas.nl/doubleprecision/doubleprecision.html ? If yes, is it supported/experimental/deprecated? If no, what is the current state on this topic? In a more general way, what are the best compilation options to get the most out of Pd on one side, and my computer on the other side? Thanks and happy patching! Yoann

2 2

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list August 2017