Pd-list April 2016

pd-list@lists.iem.at

75 participants
106 discussions

pd and HiDPI
by Orm Finnendahl 08 Apr '16

08 Apr '16

Hi, I just bought a Laptop with a HiDPI screen (2560x1440) and the menus and dialogs in pd are unreadably tiny. I searched the web but couldn't find any workaround (there was a thread on the pd-list in 2013 regarding Retina displays and I tried the advice from there but that didn't get me anywhere). Does anybody know how to get this to work better? I'm on Arch linux with a gnome Desktop. Gnome and its Apps upscale all Menus, Dialogs, Fonts etc. well but Tcl/Tk seems to ignore that. -- Orm

5 9

Externals built with MSYS2/MinGW won't load
by Christof Ressi 07 Apr '16

07 Apr '16

Dear list, I tried to compile the test externals in doc/6.externs on Windows 7 from the command line using MSYS2/MinGW. I put everything (source files, m_pd.h and pd.dll) in one folder for the sake of convenience. I compile with $ gcc -c obj1.c -o obj1.o and link with $ ld --export-all-symbols -shared -o test-obj3.dll obj3.o pd.dll compiling and linking works without any errors or warnings. test-obj1 and test-obj2 seem to load and work fine in Pd, but for test-obj3 Pd console tells me: "C:\\Program Files (x86)\\pd vanilla\\extra\\stuff\\test-obj3.dll: couldn't load" The same thing happens when I try to build test-obj4, test-obj5 and test-dspobj~. What could be the problem? I took the source files as they were and built all objects the exact same way... Many thanks in advance!

2 6

Re: [PD] building extras on arm7 (CHIP)
by Peter Nyboer 07 Apr '16

07 Apr '16

> > why do you build Pd in /usr/local/lib in the first place? > > the straightforward way would be: > - extract Pd sources somewhere in your home-directory (e.g. > /home/peter/src/pd-0.46-6) > - cd into that directory and build Pd Yes, that is what I did, more or less. Complete details are here: http://docs.getchip.com/#building-and-installing-puredata-pd-on-chip But in brief: ./autogen.sh ./configure --disable-portaudio --disable-portmidi --no-recursion cd src make clean make -f makefile.gnu sudo make -f makefile.gnu install So I didn’t specifically build such that the pd extras are installed in in /usr/local/lib, that was a result of the make process. "which pd” returns “/usr/local/bin/pd”, in case you are curious. I’m not running it from the build directory. HOWEVER, I now realize the folly of my ways. In order to get the extra objects built I need to run “make install” from ~/pd-0.46-7/extra/ directory, not from the “extra” directory in /usr/local/bin. Anyway, my puredata is now happily working with expr, sigmund~, choice, et al. Thanks for the help! Peter

2 1

building extras on arm7 (CHIP)
by Peter Nyboer 07 Apr '16

07 Apr '16

I’ve built PD vanilla for a small linux computer (Next Thing CHIP) from source. It runs fine, but I don’t have the ‘extra’ objects like expr, choice, etc. I’m having a problem building the ‘extras’. If I cd /usr/local/lib/pd/extra and try “make install” I get an error chip@poch:/usr/local/lib/pd/extra$ make install cd .. && make am--refresh make[1]: Entering directory '/usr/local/lib/pd' make[1]: *** No rule to make target 'am--refresh'. Stop. make[1]: Leaving directory '/usr/local/lib/pd' Makefile:378: recipe for target '../aclocal.m4' failed make: *** [../aclocal.m4] Error 2 This seems like it should be pretty straightforward, but I guess I’m missing something? Peter

2 1

sanity check on workings of pd~
by Jonathan Wilkes 07 Apr '16

07 Apr '16

Hi list,Does [pd~] have a one-block delay? Thanks,Jonathan

5 9

creating an object class with an alias name
by Alexandre Torres Porres 07 Apr '16

07 Apr '16

in the last thread "Name conflicts "class overwritten; old one renamed 'x_aliased'" I was telling how in cyclone you can compile Line~ with alias names such as "line~" and "cyclone/line~", so you can call these two other versions instead. Other files in cyclone have alias name like Scope~ can be called as "scope~". But I don't get how this works. The thing is, as i was also trying to clarify in previous threads, I though you could only call and load an alias after I instantiate the object with the official' name. So, before being able to call "scope~" I'd have to load it as "Scope~". Or load it as "Line~" before "line~" and "cyclone/line~". Or everythiing should have been first loaded as a regular library, then I can call whatever object... I was believing that was the case, and someone like Roman was pending that way as well. but these objects in cyclone prove wrong, there seems to be a way... but it also sees like some ninja trick with some restrictions, cause I tried renaming one of the aliases from "line~" to "pizza~" and it didn't work. Does it have to do with some can anyone shed some light on? thanks

2 1

Name conflicts "class overwritten; old one renamed 'x_aliased'
by Alexandre Torres Porres 06 Apr '16

06 Apr '16

howdy, as a remaining extended 0.42-5 user, I'm just now realizing how vanilla works when loading externals with the same name as a vanilla object or some other preloaded library - I have to say it was a surprise to see that it's different that how extended works, and that it doesn't seem like a good idea... Anyway, you see, I got here zexy 2.2.6 (as a library) and cyclone (individual binaries but also has the nettles library) on vanilla 0.46-7 - both external libraries have abs~ (which is also a vanilla object) or an object like [>~] (part of nettles in cyclone). Both zexy and nettles are loaded via startup. So funny stuff can happen... like, vanilla's abs~ is overwritten by zexy's and renamed to abs~_aliased, but if I call cyclone's abs~ specifying its folder as [cyclone/abs~], it overwrites zexy's abs~ and it is never possible to call zexy's abs~ ever again... Ok, in the case of abs~ I think it should be removed from both cyclone and zexy, because it's not only that they share the same name between each other and a vanilla object, but they all do the same thing as the internal object... so it's completely redundanct - but this is another issue. One way or another, it helps illustrating my point. So, moving on to the case of [>~], we see from previous discussions that they need to be loaded as libraries for sanity's sake. But then I can never specify which [>~] I want - if both are via startup or declare, I can never be sure or control which one I'm specifying as either >~ or >~_aliased... The point is: perhaps there could be a better way to force vanilla to load an internal object? Or if not a vanilla object, perhaps that could be a way to specify and object inside one external library or another? The way things are, it's all just really out of control and I can think of many scenarios where patches need to be edited when loaded because of what's going on in that particular machine, such as what patch had been opened before, etc... I know this probably has been discussed for ages and many people had already thought about it... I also know I have NO clue on the technical details and what has already been done, but I would like to ask and suggest things. What would make sense to me is that vanilla objects would always prevail and be called with priority. This is how things were in Extended (and now pd-l2ork I guess) - externals with the same name as a vanilla objects could only be called only if explicitly specified. In the case of cyclone's [line~] it's easy to specify if you wan cyclone's version or not by specifying the folder [cyclone/line~] But the problem is when you're using a library, because you seemingly can't specify a given loaded external library when instantiating an object... such as [zexy/<~] or [nettles/<~] - and yes, they are different, by the way, before anyones asks ;) So, in short, all could be sorted and taken care if: 1- vanilla objects are never overwritten 2- external objects can be specified by a path even if they are loaded as a library with declare or via the startup (ex: zexy/<~ or nettles/<~) cheers

3 10

Re: [PD] Fullscreen, not GEM, just a PD screen?
by Peter Nyboer 06 Apr '16

06 Apr '16

The kiosk TCL plugin works a charm. https://puredata.info/downloads/kiosk-plugin <https://puredata.info/downloads/kiosk-plugin> I also found some things in the hcs externals https://puredata.info/downloads/hcs <https://puredata.info/downloads/hcs> that worked, but the kiosk plugin was a more elegant solution. Peter

1 0

Fullscreen, not GEM, just a PD screen?
by Peter Nyboer 06 Apr '16

06 Apr '16

A simple, somewhat newbie question: Is it possible to display a regular PD window in fullscreen, or position it to fake fullscreen, on Linux? It seems like it should be trivial to hide the application menu bar, but I have yet to find anything - “fullscreen pure data” is polluted by GEM!! Peter

4 3

objects with no alphanumerical names, how to build them?
by Alexandre Torres Porres 06 Apr '16

06 Apr '16

howdy, I know I kinda asked about this before on the list, but now I'm really committed to understanding and building objects with "weird character" names, like [==~]. I built some new objects with alphanumerical names like [equals~] and now I wanna know how to compile them like that. I first tried making a second name - or an "alias" - for [equals~], but it didn't seem to work. I can get [==~] to instantiate as an alias, but only after I first instantiate it as "[equals~]". So, is that because of something I did, or it's just possible for these kind of characters? Anyway, I see that in zexy we successfully have objects like that. So a few questions... I'm specifically talking about the version I found via deken, as: *zexy-v0-0extended-(Darwin-* *i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar* Is this the one available from last released extended (0.43?). If so, is the source code in here? https://sourceforge.net/p/pure-data/svn/HEAD/tree/branches/pd-extended/0.43… I'm assuming so, but I'd like to confirm. And why do you have both 0x3e0x7e.pd_darwin and >~.pd_darwin in the deken download? which is the "real one"? I only see one 0x3e0x7e.c code in the source I link above btw, I'm assuming it generates both. Anyway, I needed to understand what are the issues and what do you have to do to make it happen, and then, well, I guess I can look into this zexy structure to better understand it. cheers thanks

8 27

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 April 2016