Re: [PD] Continuous Integration for Externals

I just updated my pd.build (https://github.com/pierreguillot/pd.build/) repository that facilitate the creation of projects with CMake. I tried to add scripts that also facilitate the use of travis and I improved the documentation. I'll try to do a version of these scripts for Appveyor too and to

Re: [PD] Continuous Integration for Externals

>and to be honest, I have no idea how to test the Windows builds on a Linux >machine. Well probably https://www.virtualbox.org/ will do. Normally not to test audio latency but surely to test the rest. You can host a win7 virtual machine (don`t set up an xp, is pretty old). I'm on Win8.1 and

Re: [PD] controlling a robot arm

hi rolf, >> i guess it comes from the motor's constantly trying to keep there position against the gravity pulling on the arm. yeah we believe thats whats is going on. not sure how to filter. going to work on it this weekend. encoders as sending false positives. either we filter (somehow) in

Re: [PD] [PD-announce] All-in-one 'websocket server + cross-browser multiplayer/multitouch demo' patch for Pd-extended

>> has all the required crypto stuff you talk about (made stricly of vanilla objects) whoa... i didn't realize this could all be done via vanilla and when i checked your code this past summer did not see this portion so thanks for pointing it out! in the end i ended up using python to do crypto

Re: [PD] Continuous Integration for Externals

Hi, On 29.11.2016 09:58, IOhannes m zmoelnig wrote: > On 2016-11-29 02:54, Thomas Mayer wrote: >> Should I use gcc or clang for compilation on OS X? Or both? > > i'd use $(CC). > > i see little merit in using a compiler that is actively being > phased out in the ecosystem (that is: why would

Re: [PD] Continuous Integration for Externals

On 2016-11-29 02:54, Thomas Mayer wrote: > Should I use gcc or clang for compilation on OS X? Or both? i'd use $(CC). i see little merit in using a compiler that is actively being phased out in the ecosystem (that is: why would you want to use gcc on OSX these days?) however, some of my

Re: [PD] Continuous Integration for Externals

[:travis-ci propaganda:] On 2016-11-29 01:09, Dan Wilcox wrote: >> On Nov 29, 2016, at 12:46 AM, pd-list-requ...@lists.iem.at wrote: >> >> Obiously, I would like to set up a Mac build machine as well. What do I >> need to install on a clean system via command line? > Install the build system via:

Re: [PD] Continuous Integration for Externals

> Should I use gcc or clang for compilation on OS X? Or both? On my local machine, I use clang and on travis I use gcc (but you can use both). Here are two other examples if you want: https://github.com/pierreguillot/pd-dummy https://github.com/CICM/HoaLibrary-PD/tree/dev/refactory

Re: [PD] Continuous Integration for Externals

Before PdCon16~ I didn't even know about Travis. When IOhannes explained that it is an online continuous integration tool, my naive idea was 'can we use this to build our Pd libraries on 'all' platforms and route the builds back to us?' Many of us don't have 'all' platforms available at their

Re: [PD] Continuous Integration for Externals

On Tue, Nov 29, 2016 at 12:07 PM, katja wrote: [...] > > From https://docs.travis-ci.com/user/customizing-the-build/, I > understand that Travis CI is also a community build farm (but > obviously bigger and more professional than we could organize in Pd > community): > >

Re: [PD] [PD-announce] All-in-one 'websocket server + cross-browser multiplayer/multitouch demo' patch for Pd-extended

:) thanks ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

[PD] Purr Data rc2

Purr Data release candidate 2! * added delread4~ alias for vd~ * loaded Gem dependencies properly under Windows * added help menu item for list of internal classes * various help patch cleanups and fixes * changed zoom/fit keyboard shortcuts so they work on all platforms * localized the canvas

[PD] Paper about vcf~ implementation?

Hi, I try to understand the code of the [vcf~] filter. Is there any paper or discussion somewhere that could enlighten me about the mathematics used? For instance what kind of filter is it *precisely*. A one-pole resonant filter (as it is noted in the Puckette's book)? Note that i'm not an

Re: [PD] Paper about vcf~ implementation?

Hi, i recently coded it in more 'readable' c++ code. Can share with you if u want, i guess? It's a "one pole complex filter", and miller has suggested previously on this list that it is indeed basically a wrapper for the same code as the cpole~ object, with some other stuff thrown in to

Re: [PD] Continuous Integration for Externals

> Many of us don't have 'all' platforms available at their home or work place and we sorely miss the Pd-extended build farm with its nightly test builds. It seems useful to share knowledge and experience about an existing infrastructure like Travis. One option is "Giblab CI" which comes with

Re: [PD] Continuous Integration for Externals

> On Nov 29, 2016, at 5:28 AM, pd-list-requ...@lists.iem.at wrote: > > Should I use gcc or clang for compilation on OS X? Or both? clang is fine and using “gcc” actually calls clang anyway. I wouldn’t bother with both. If you want to explicitly build with gcc, you’ll need to install gcc via

[PD] Re : Re: Paper about vcf~ implementation?

Yes, I would be very pleased to read your C++ code. And thanks for the helpful link. - Mail d'origine - De: i go bananas À: Nicolas Danet Cc: pd-list@lists.iem.at Envoyé: Tue, 29 Nov 2016 16:53:54 +0100 (CET) Objet: Re: [PD] Paper about vcf~

Re: [PD] Continuous Integration for Externals

On Tue, Nov 29, 2016 at 5:17 PM, Jonathan Wilkes wrote: >> Many of us don't have 'all' platforms available at their home or work > > > place and we sorely miss the Pd-extended build farm with its nightly > test builds. It seems useful to share knowledge and experience about >

Re: [PD] Continuous Integration for Externals

> It seems that with Gitlab CI you can configure 'runners' on your own hardware for the project(s) that use it, right? Yes.  I could install gitlab-runner on my rpi2, get the "token" from gitlab, and have it sit there waiting to build. In that case, however, I'd essentially be letting remote