In the move to digital 1, and particularly with streaming, the musicians who play on recordings are rarely given credit outside of AllMusic or Wikipedia. A PDF of the liner notes might mention personnel, but I don’t know of any download or streaming service that embeds such information in tracks. For MP3, there is a standard in place for such metadata — ID3 has the TMCL and TIPL for tagging files with personnel credits. There are Apple namespaced equivalents for MP4 (AAC) files. I’ve long used the Comments field for this purpose, but it suffers from limited character length and lack of structure. The only software I’ve found that supports TMCL and TIPL with an interface designed for their input is a Windows application called ID3TagIt. Not wanting to fire up a virtual machine to use an app which has not been updated since 2006, it would be great to see support in Metadatics2. Currently, it handles musician credits only as raw text:
I’d like to see a UI for inputting credits:
The menu button at the right of the name field would give you access to commands to remove the person, the instrument or role, or add another person with the same instrument or role.
Providing a field for the Lyricist would also be nice:
Of course, this is pointless if playback software doesn’t provide some way to use this metadata. I want to be able to start a stream of songs with lyrics by Stevie Wonder, or create a Smart Playlist with all recordings of Pino Palladino on bass. Unfortunately, Apple seems to have lost interest in expanding iTunes’ metadata support and Spotify and Rdio have only the most basic track metadata.
The persistent alignment controls in Sketch could double as a way to add guides around canvas selections. The basic idea is that depressing a modifier key would switch the toolbar into a guide placement quasi-mode, with the icons and tooltips updating to reflect the change. Ideally, the icons in the toolbar would reflect the guide color set in Sketch’s preferences (red being the default).
A few ideas to improve the alignment guides in Bohemian Coding’s Sketch, which I’ve been using more and more since Adobe announced that they pulled the plug on Fireworks — just like Obama will do to your sweet old granny.
In the current version (2.3.1), guide positions are hard to read and you can’t easily space them from each other and the edge of the artboard.
There is also currently no way to position them by numeric input, a feature I found very useful in Fireworks.
Say you’ve decided to change the height (or width) of an element in your design, a change that must propagate. It would be great to be able to move all of the guides on one axis in one pass.
The input boxes for individual and batch position adjustment would of course let you increment their values using the arrow keys and change them using mathematical operations, two features I’ve found really useful in Sketch.
Always focus on good human interface, user interface. Computer apps are not to be judged by what they do or how well they do it. Rather, it is more important that they feel natural to normal humans and they are led to the right actions.
I’d like to see the app switcher’s ability to quit and hide applications extended to allow other commands to be sent to applications without having to exit the app switcher quasi-mode. This could be handy with browsers, writing tools, and media players.
This would work best if the selected application’s windows were presented when using the switcher so you can see what you are acting on. If not, it may be best to limit the additional commands to those that appear in the application’s Dock menu (usually, create a new document or window) and have a keyboard shortcut.
Working with a laptop and large external display reminded me of an interface irritation particular to multi-monitor setups in which the displays are of different sizes. For instance, a stacked arrangement with the menu bar on the large display on top and the Dock on the small one below. You can easily move the cursor to the large display anywhere along the top of the smaller screen. The inverse is not true; there are portions of the large display that will not allow the cursor to move to the smaller display.
I believe an indicator showing just the passthrough zone is the best design, but there are alternatives:
Show indicators for the portions of the display that do not allow the cursor through
Show indicators for both
Keep the existing “mouse around until you find it” implementation
The color of the indicator could be calculated based on the desktop background to ensure sufficient contrast.
Some smarts about determining cursor movement direction (like that used to keep sub-menus open when the cursor is moved diagonally) would prevent the indicator from appearing when the cursor is moved toward a hot corner to activate Mission Control or an Exposé mode.
The indicator is obviously not needed when moving between displays of the same size.
Along these lines, it would be nice if the Google Talk app used a red light when you receive a message while your status is set to Away and green when Available. I feel comfortable waiting to respond to messages when my status is set to Away. You would have to turn your screen on to see which app triggered the light if you have several that use the same color, but it’s no different from every app using the default LED color.