Debugging a Max patch that speeds up arrow keys after you hold a key down for 2 seconds. The metro object was hanging the patch, no matter what the speed. Replacing the metro with qmetro solved the problem
Debugging a Max patch that speeds up arrow keys after you hold a key down for 2 seconds. The metro object was hanging the patch, no matter what the speed. Replacing the metro with qmetro solved the problem
Mac OS frequency control and Max external
update 11/29/2013 – Checked the fcdpp in Mac OS 10.8 – still having issues with sync loss – also noticed that the fcdpp picks up interference from the Macbook trackpad in the shortwave bands – but after further research determined trackpad really does transmit RF.
My notes from September seemed a bit sparse. But I was able to determine that maxsdr5c.maxpat in maxsdr6 and the basicSDR4.maxpat were modified to use the new fcdpp external driver – also, maxsdr5c has the arrow keys mapped to awsd – due to an issue with metro/qmetro – but I will probably map them back again.
Am thinking about giving up on the fcdpp – but should test it out on windows first to make sure its not a hardware issue.
update 9/24/2013 – have written a Max external for the fcdp+ – its called funcubeplus.mxo
Its in the 6.1.3 sdk folder under basic examples. There’s a test patch in Max teaching examples called: funcube-pro-plus-test.maxpat
I have updated the code in tkzic/maxsdr6/maxsdr6 with the new drivers, etc., but have not posted to github – as am awaiting answer to sync issues.
Need to use the ad_portaudio core audio driver – or Max will crash.
Audio sync issues: the fcdp+ produces annoying buzzing artifacts during normal listening and especially right after you change frequency on the device. Have tried every possible Max audio setting to no avail. There have been other postings to the development group – so we’ll see what happens…
= previous post =
I’m listening to the fcdproplus radio in a Max SDR patch on the Macbook. Will need to fix a bug in the maxsdr5 patch with arrow keys – and write a new external for the pro plus – but here are the other details.
Using Alex Csete’s and David Pello’s fcdctrl code – see this post on R-pi
http://www.oz9aec.net/index.php/funcube-dongle/479-the-funcube-dongle-propro-on-the-raspberry-pi
Here’s the hacked fcdctrl code that works with the pro plus:
https://gitorious.org/fcdcontrol/fcdcontrol-proplus/source/d8055cfe4ba2e015a23f2ad8f4a80f4135441e74:
This project was set for linux, so I downloaded the most recent hidapi from here:
https://github.com/signal11/hidapi/downloads
and used the mac hid.c and hidapi.h code.
changed Makefile to use these files and the Mac frameworks…
Code is in tkzic/fcdproplus/mac-fcdcontrol-proplus/
Also added this line to fcd.c – for the pro-plus
#define FCDPP 1
Also in Max, needed to use the ad_portaudio Core Audio driver – it crashed with the regular core audio driver.
By Dan Nigrin, Oli Larkin, and James Howard Young
http://cycling74.com/2012/04/19/get-your-max-standalone-on-apple%E2%80%99s-mac-app-store/
If you look at the vst~ help file. Under the Plugin Names tab – there’s a bpatcher which uses javascript code: get_plugs.js to retrieve a list of all AU and VST plugins on the machine.
There are instructions at http://cycling74.com/wiki/index.php?title=Gen_Code_Export_iOS – which are expanded upon here.
// Create an Audiobus instance self.audiobusController = [[[ABAudiobusController alloc] initWithAppLaunchURL:[NSURL URLWithString:@"genfilter.audiobus://"] apiKey:@"MTM4MDY1ODQzNSoqKkdlbkZpbHRlcioqKmdlbmZpbHRlci5hdWRpb2J1czovLw==:caS8WT1r4OmYz6t89pDq37qNi29hwFba+7+7bP8WubzyKN7Xj+tnU31/Wcaw580zQg8Jz+vC6Ha0H+qDM9JhdBxfQZ7w/R0VHrvsbZYQEJkj1bNpg2h2DfsF1mvFr6jb"] autorelease];
note: 6/2021 – Everything on this post no longer works, except the idea. See Internetsensors posts for current methods
pachube.com and cosm.com have now changed into xively.com. Also Twitter has migrated to the version 1.1 API. The old method of sending tweets with cosm.com no longer works as of of June 2013.
Here are revised instructions for setting up an intermediary program that allows you to send Tweets from Max/MSP using a xively.com “device” (feed). This setup is required by the tweetCurl patches in the Max/MSP internet sensors project:
https://reactivemusic.net/?p=5859
Summary: the Max program will issue an http: put request to your xively.com feed with the Tweet text as data. When the data is received it triggers a request to xapier.com which logs into your Twitter account and sends the Tweet. xapier.com handles authentication using Oauth.
1. set up a xively.com account (self explanatory)
2. add a device. From the xively.com home page select “develop” from the “web tools” menu. You’ll get a screen like this one:
Click on +add device. The following screen will appear:
Fill in the fields. The names and choices can be whatever you want. Then click the “Add Device” box to get the following screen:
Now click on +Add Channel. Fill in the Channel ID field with the name: tweet (as shown below) then click the “save channel” box.
3. Add Trigger. The trigger will link this channel to Twitter. Please follow the instructions here: https://xively.com/dev/tutorials/zapier/
Notes:
A radio experiment
from Texas