gHowl

Information

gHowl is a set of components which extend Grasshopper's ability to communicate and exchange information with other applications and physical devices.

Website: http://www.grasshopper3d.com/group/ghowl
Location: In Between
Members: 976
Latest Activity: Feb 5

Download the latest set of gHowl components:

gHowl_r50 and example files

Check out the gHowl videos page where you can see how people have been using gHowl.

Our users have connected Rhino and Grasshopper to various protocols, platforms, and softwares including:

Processing

Excel

Open Office

RSS

Arduino

Kinect

Reactivision

openFrameworks

Google Earth

Resolume

VVVV

Pure Data

max/msp

Maya

Kangaroo

TouchOSC

iPhone

Android

Components:

UDP:

UDP Components now have the ability to send and receive to a Multicast group. To send or receive to a Multicast group, make sure you use the IP Range of 224.0.0.0 - 239.255.255.255.

OSC functionality is provided by the Bespoke OSC Library by Paul Varcholik.

Network Source - Tests the connection of your machine to a network.

UDP Send - Allows the sending of UDP messages over the network. Also allows the sending of OSC messages to OSC enabled software and hardware devices. (Deleting this component in 0.7.0057 crashes GH / Rhino)

UDP Receive - Allows the sending and receiving of UDP messages. Also allows the reception of OSC messages and bundles (from Reactivision for example).(Deleting this component in 0.7.0057 crashes GH / Rhino)

OSC Channel - This component allows the storage of a single OSC Channel. Change the component's nickname to store that address' data.

OSC Dispatch - This component allows the storage of data from multiple OSC addresses.

Spreadsheet:
The spreadsheet components leverage the OpenXML engine. You must have OpenXMLSDKV2.msi installed in order for these components to work. These components read and write *.xlsx files. Supports numerical values and strings.

Spreadsheet Reader - Retrieves spreadsheet data from a file stored on your computer.

Spreadsheet Writer - Allows you to write a spreadsheet file.

XML:
These components retrieve xml data from local and web sources (such as RSS feeds).

Pachube - Retrieves data from a Pachube feed. Must have a valid Pachube API. (Deleting this component after making a connection in 0.7.0057 crashes GH / Rhino)

Pachube Update - Allows you to update a Pachube Feed. The component has variable inputs to enable streaming to various datastreams. Must have a valid Pachube API.

XML Parser - This component parses an XML file stored on your computer or on the web.

XML Writer - Writes out XML

GEO:

These components aid in the mapping and conversion of coordinates from GPS enabled devices to XYZ coordinates.

Format GEO - Takes NMEA formatted GPS coordinates and converts them to Decimal Degrees.

XYZ -> GEO - Maps XYZ coordinates in Rhino/Grasshopper to Longitude, Latitude, and Altitude.

GPS -> GEO - Maps Longitude, Latitude, and Altitude coordinates to XYZ

Elevation Service - This component returns the elevation at the coordinates you supply as inputs. It queries the Google Elevations API to do this. There are some limitations on usage, so be warned.

KML:

KML Exporter - Exports points, curves, and meshes to a KML File. Breps should be meshed before exporting. Brep support will be added soon. Object attributes such as color, transparency, line width, line color, etc will be added soon.

KML Attributes - Adds Fill Color, Line Color, and Line Width to Exported KML Objects.

Discussion Forum

Android OSCmessage to GHowl. Error Message. 7 Replies

Hello all,I am writing an android interface to communicate with grasshopper. It's the same idea as some of the OSC apps in the app store, but they aren't open source and I need to be able to have…Continue

Tags: java, osc, udp, ghowl, android

Started by Jon Blout. Last reply by Konstantin Markin Aug 8, 2022.

Ghowl xml import /export 10 Replies

Hey againHow does it work if you want to import and export the same .xml file, when the ghowl xml import has 4 output parameters, and the ghowl export has 2 input parameteres ?RegardsContinue

Tags: export, xml, Ghowl

Started by Jesper Hildebrandt Andersen. Last reply by Hannah Stevens Apr 14, 2021.

external real time data/ parse xml 5 Replies

hello, i am trying this for the first time and hoping someone can point me in the right direction. i am trying to use grasshopper + ghowl to read real time data from a weather site's API. i have a…Continue

Started by pwdarden. Last reply by Denis Cox Oct 26, 2020.

problem about UDP receiver

Hi, I am using UDP receiver in gHowl. It works well until I packaged everything into a cluster, and the UDP receiver keeps sayting "AddressAlreadyInUse: you might have opened this socket on another…Continue

Started by vapeur Jul 5, 2020.

View All

Comment Wall

Comment

You need to be a member of gHowl to add comments!

Comment by Luis Fraguada on May 1, 2012 at 2:22am: Hello Chan,

UDP // OSC

OSC is a protocol running on top of UPD. A part of the OSC message has information about where the message came from, for example it would tell you which device and which control of the device has just sent you the information.

Both UDP and OSC can be sent or received from the same gHowl components. To invoke OSC, you should change the sending or receiving pattern to 999. To send OSC, you should compose a message where the first element in the list is the device address and the other entries are the data. Check the gHowl examples where you will find OSC examples for VVVV and processing. Let me know if you have any issues and we can help to resolve them!

Comment by Chan on April 30, 2012 at 5:38pm: I think I am getting confuse with the terminology and definition, may some one clarify the difference between osc and udp? Does osc need to be bundle or encode when it sent through udp? I am employing osc when I am sending message vvvv and grasshopper?

Comment by Luis Fraguada on April 27, 2012 at 1:00am: Here is another nice example: http://www.twylah.com/Spatial_3D/tweets/195648004827525120

via @Spatial_3D

Comment by Luis Fraguada on April 27, 2012 at 12:55am: Thanks for the example!

Comment by Constantinos Miltiadis on April 25, 2012 at 3:45pm: added a simple osc method for processing>GH real-time communication sending a 2d point array. Hope it helps. comes with pde and gh files

http://www.grasshopper3d.com/forum/topics/processing-to-grasshopper...

Comment by Bramiozo on February 21, 2012 at 8:51am: Jup, those work fine!

They are sent by the client when an input variable (slider) changes value. In my client app I would like to implement a save function. It would be great if it could send data to multiple addresses in the same go. Sending them after another doesn't work (only the last msg gets across, though as far I can debug, they are being sent by the client) so I figured bundles may be the solution.

I've tried using the single OSC Channel component but it seems to have the same problem.

I'm also having some dropped msgs. It's probably related to a timer that executes _ViewCaptureToClipboard every second is there something I can do to fix that?

Let me know if 'd like me to try something!

Comment by Luis Fraguada on February 21, 2012 at 1:40am: So in the blurred part, these are other OSC channels which are working ok?

Can you try using the single OSC Channel component? You would need to name each one by right clicking in the center of the component and entering the name of the channel (i.e. /5/nr1). You would repeat this for each one. Try this out and let me know how it goes. I might need to rework the dispatch component to better handle bundles...

Comment by Bramiozo on February 19, 2012 at 7:58am: Sure!

I've blurred out the non-relevant part for this test to make it a bit easier to find :).

Also I've noticed that I've been getting some dropped msgges in general when Rhino is occupied with excuting a command I send to Rhino through a VB script _ViewCaptureToViewport.

Comment by Luis Fraguada on February 19, 2012 at 7:43am: Hello Bramiozo, Can you post a screenshot of what is happening?

Comment by Bramiozo on February 19, 2012 at 5:06am: I've been trying to setup communication between Grasshopper and Flash by using ghowl and bubblebird's Flash library (http://bubblebird.at/tuioflash/). So far I've been able to send an OSC message to grasshopper by defining the address and value and it comes across fine. so far so good. However when I want to put together a bundle of messages with different addresses and dito values or when I try to send these messages rapidly after oneanother it doesn't work anymore.

When I rapidly send 3 messages after oneanother the first two get dropped and only the last message (address and value) gets across. When I bundle the three msgs the whole bundle gets across but doesn't 'get parsed' so the output of the UDP component shows out the D output: lines 0 till 5 showing on the even index the addresses and on the uneven indexes the values (I guess this is ok?).

The OSC_Dispatch component doesn't seem to split this bundle message. I input the three adresses in the DispatchObject D input (which works fine with single messages). The D Output shows in the output of address0 the rest of the message : "data1,address2,data2,address3,data3" and the data 2 and data 3 fields are empty. I would like to have data2 in the field coupled to address 2, like it the case when I use single messages.

Anybody have any thoughts on how to fix this ? Thanks!