"Wouldn’t it be cool if…"
We’ve all had that thought about something. How do you get from there to a product you can use and share with others? When I found myself playing with an idea that seemed exciting and new, I decided to capture some notes on the process, from the perspective of an Engineering Manager at a company that’s all about implementing people’s creative visions.
Art+Logic is sponsoring and presenting at Music Tectonics on October 27th and 28th. The virtual conference, with engaging and enticing presenters, promises me the opportunity to slip back into a world I once knew well and vicariously experience the road not travelled.
Last year, I posted here about an animation control framework called ‘Friz’ that works within the JUCE Application Framework.
As I said in that post:
Kim Renard Nazel is best known as Arabian Prince, a founding member of the ’90s rap group N.W.A. whose raw lyrics on police brutality inspired a generation of West Coast rappers. But the producer and artist, who goes by his stage name, has long been a tech geek passionate about closing the digital divide.
This week, the Compton-bred rapper-turned-entrepreneur launched his latest endeavor, Covitech, a platform intended to get people back to work safely. The cloud-based suite of apps provides a protocol plan for small-to-medium businesses, giving them access to COVID-19 screening, testing resources and often hard-to-procure protective equipment. Read more
When designing custom software, designers often need to keep user roles in mind to make an efficient and effective user experience for multiple workflows. By taking a look at the needs of each user, we can design for multiple intuitive user flows while retaining a clean, cohesive look and feel.
One of the most common misconceptions about software testing is that QA does not come into play until the development of a module is complete and ready to test.
In actuality, the earlier QA is involved in the Software Development Life Cycle (SDLC) the better. Studies have shown that up to two-thirds of defects can be attributed to requirements and design.
This Wednesday, a couple of us from Art+Logic will be talking with the folks at rock paper scissors about pivoting creatively through a crisis. Join us.
Like many of you, we’ve been receiving daily suggestions of articles offering advice and insights on how to work remotely most effectively. A lot of these lists offer some great advice, and we’ve even been included in a few such articles ourselves (links below). What struck me, however, was that there was always something in a list that felt like it was missing or that might be overstated for my specific needs. Assuming that might be the case for others out there, I asked members of the Art+Logic team to offer their own insights into tricks, concerns, and changes that help them work remotely while still staying focused and maintaining a high standard. We’ve been working remotely for almost 30 years.
I wanted to share with you an update regarding the current situation with novel coronavirus/COVID-19. As you probably know, Art+Logic is a fully distributed company, which means that everyone, from our sales team, to our designers and developers, works remotely. As a company that has been working remotely for almost 30 years, we are fully prepared to continue to work on your project without disruption.
We are closely monitoring developments and are aware that the impact of the virus could impact your own team and also result in school closures and social distancing recommendations that could impact workflows.
For the immediate future, Art+Logic is discouraging company travel. Unfortunately, that means we were not able to make our presentations at SXSW, which was cancelled, and will not be attending TechDay NY.
If you have a project you would like to discuss with us, please fill out our contact form and we’ll get back to you in a timely fashion. We encourage everyone to stay up to date on the latest Coronavirus information from the World Health Organization (WHO) and the Center for Disease Control (CDC).
After over a decade of work, the final specification documents for MIDI 2.0 have been released to the public!
There’s a fantastic article on the MIDI.org site that explains what the hubbub is all about that I’ll just point you at rather than rewriting — check it here: Details about MIDI 2.0
When MIDI 1.0 was released in 1983, the complete document that detailed all you needed to know about it was eight pages long. Expect to need to read a bit more than that in 2020—the full spec for MIDI 2.0 is five separate documents, each looking at a single part of the system:
M2-100: Overview of the specifications
M2-101: Specification of MIDI-CI, the Capability Inquiry portion of MIDI 2 that’s required to enable devices to query each other and determine how two devices can work together.
M2-102: Common Rules for MIDI-CI Profiles explains how to define and work with MIDI 2 profiles to define controllers and other configuration data to permit devices to automatically adapt to the capabilities present in the currently connected instruments.
M2-103: Rules for Property Exchange, the new provisions for querying current settings and capabilites of connected devices
M2-104: Definition of the new Universal MIDI Packet data structure and the high-resolution MIDI 2 message protocol.
Before you can access these documents, you’ll need to create a (free!) account with The MIDI Association, which is an organization of MIDI users. If you’re not already a member, the link to access the docs will redirect you first to the login/account creation page.
Download everything here and then go make cool stuff with it.