i to usb cable and was able to connect Grasshopper with my digital piano realtime through a simple VB.NET component, no need for any other intermediate software. I used this library http://midiservices.codeplex.com/ (but there are several others).
The VB component outputs a list of 88 values that correspond to the intensity of each piano key at the current time (if the pedal is on and a key is depressed the value is halved, if the pedal is off the value is 0).
The rest of the definition is just to do something with this data. It uses these values to display each note as different floating colors that move with the wind (using Kangaroo). The strength of the wind changes as the music dynamics change.
If there are several devices connected you might have to change the line device.Open(0) to another number.
Definition: piano_midi.gh
…
an be given as 88° and 95°. All three angles must sum up to 180, and we're already 3 degrees over balance. Or maybe the user specifies three edge-lengths: 21, 12 and 8. 21 is bigger than 12+8, so even if the triangle was stretched flat, the two short edges cannot reach the ends of the long edge. The above is easy to test for and I add errors to the component if an invalid triangle is provided. However there are also many angle+edge length combinations which result in invalid triangles.
I could of course test for these as well, but the problem is now tolerance. What if the user specifies a redundant angle of 54.7°, whereas the mathematics tell us that the actual angle is 54.7002°. Is that an error? If so, is the angle wrong or is perhaps one of the edges wrong? Or has the triangle simply been over-constrained? Is there a mathematically robust way of dealing with this? And if so, would that also be the most user-friendly way of dealing with it?…
Added by David Rutten at 2:23pm on August 23, 2014
s are identical to those in Grasshopper so I am getting an ambiguous reference error when loading the OpenStudio.dll into my component and using the Point type hint.
private void RunScript(Point3d pt, ref object os3DVector)
{
OpenStudio.Point3dVector points = new OpenStudio.Point3dVector();
points.Add(pt);
}
Error: 'Point3d' is an ambiguous reference between 'Rhino.Geometry.Point3d' and 'OpenStudio.Point3d' (line 88)
Is there any particular reason the Grasshopper reference to Point3D is implicit rather than explicit Is this something that can be changed on my end as it appears to be locked down.
Would like it to read as follows:
private void RunScript(Rhino.Geometry.Point3d pt, ref object os3DVector)
{
OpenStudio.Point3dVector points = new OpenStudio.Point3dVector();
points.Add(pt);
}
Awesome, thanks!…
d' and no extension method 'AnnotativeScalingEnabled' accepting a first argument of type 'Rhino.Geometry.TextEntity' could be found (are you missing a using directive or an assembly reference?) (line 94)
Along with some warnings:
1. Warning (CS0618): 'Rhino.Geometry.AnnotationBase.Text' is obsolete: 'Use RichText or PlainText' (line 88)2. Warning (CS0618): 'Rhino.Geometry.AnnotationBase.FontIndex' is obsolete: 'Use Font property instead' (line 92)
3. Warning (CS0618): 'Rhino.RhinoDoc.Fonts' is obsolete: 'Use DimStyles table instead' (line 92)
I've downloaded the latest version of FabTools.
I've completely un-installed and re-installed.
I've Googled everything I can think of to find a solution, but most references are circa 2013 which is probably under Rhino 5. Which works totally fine, BTW.
Does anybody know of a solution?
Thanks,
Michael
…
spiring game developers with the necessary tools to bring their creative visions to life. From designing captivating landscapes to coding intricate gameplay mechanics, Game Builder offers a seamless and immersive environment for users to unleash their imagination and craft unique gaming worlds. Moreover, Game Builder supports multiple languages, including Thai, as evident from its phrase ทางเข้า ufabet ภาษาไทย making it accessible to a diverse global community of creators. Whether you're a seasoned programmer or a novice enthusiast, Game Builder offers a dynamic platform to explore the exciting realm of game development.…
to stop referencing the input Lat Lon coord. (36, 86) even though there is no major changes in the input around point 15.
In this specific case 15 is the end of a row of points but the list is flattened and the input window shows no difference before or after 15.
What could be causing this to happen?
…
Added by M11S to gHowl at 5:31pm on January 31, 2016