Loopy Masterpiece: What bugs you?

[@larryseyer]

What bugs me the most is crashes - at the most inappropriate time.

[@gavinhowe9897]

Thank you for asking this question, workflow is important, and touch screens introduce new problems that we've never seen before. I will just leave a few that pop to mind now 1. SCROLLING: scrolling in music apps is about the most annoying thing ever, I go to tap something or move a knob and instead move an entire interface, one app (sampletank) is even so bad at it you can start scrolling even when you are already controlling a knob, it then disables that knob, this is death to workflow (preset menus and file browsing are an exception) 2. Floating menus & difficult navigation: if there is a menu for anything and it floats above the main interface it might as well just fill the screen, there's no need for a frame of unusable space. tabbed interfaces are much easier to browse than rolling modules (aka animoog and loopyHD metronome/beat menu) make it easy for me to navigate settings. 3. Touch and hold functions that should just be touch functions: there's not too many examples of this, but many times when you are required to touch and hold to activate something I'd much rather just have a separate activation area or be able to use a 2 finger tap as an alternative 4. fine tune and lock, adjusting parameters on a touch screen precisely does not need to be impossible, 2 simple features will make this much easier. For one allowing a two finger touch for fine tune control and second having a lock area. The lock area could be in the upper left corner so when you adjust a parameter with right hand you can lock it with your left and safely remove your right hand. I've noticed removing my finger from the surface always adds or decreases a parameter value. also a simple [ - ][ + ] icon that adjust maybe the last parameter would be useful I plan on writing a full post with examples and solutions on this very topic at some point. these complaints are mostly based on touch devices but can even translate to hardware and software, thank you for taking consideration.

[@rossfenmore4366]

Good suggestions. Number 4 especially drives me crazy.

[@FleksiTV]

You already know this because I had a short back and forth with you on loopy forum about the multiple outputs. What bugs be the most is the difficulty in integrating the sequenced electronic instruments with their electro acoustic counterparts. ;)

[@redjupiter2]

I know this is very old, however, I have got to commend you… I believe you have created a cornerstone in iOS music, making with LoopyPro. I am just now going through your KZbin archives and found this. Having spent my entire life behind turntables and decks starting at age 17 in the late 1970s, and still very active in production, I have fallen in love with the iOS, devices and you are a visionary

[@SevrinK]

The one thing that bugs me with creating music on an iPad at the moment is the lack of an auto save to iCloud or Dropbox while I am working on a session. I was working on a song for a few days when my iPad decided that I needed to plug it into iTunes and do a factory reset. I lost all of the work I had been working on since I last backed up to iTunes. A function like Time Machine on the Mac for chosen apps would be ideal.

[@FleksiTV]

Regarding the undo function, could there be an undo history list somewhere where one could choose how far back to go? This is of course if there are enough levels of undo. Happy Holidays to you to!

[@joefry22]

I think Dropbox integration is an important feature. Anything that eliminates the need to physically connect my iOS devices to my PC for transferring files is a real time-saver. On a more general topic, I find it annoying when users complain that certain app functions are "buried" within pages and sub-menus. This applies to desktop programs too, not just mobile apps. Sometimes that IS a legitimate complaint, but it seems that just as often it's a case of the user just not wanting to spend any time to really learn the apps they use. From a developer's perspective, this must be really frustrating. It's as though some users expect there to be red flashing arrows pointing at a button, with the label "This Is The Button You Need To Click To Perform The Exact Function That You Want To Do Right Now!" And those same people would be complaining about an interface being TOO cluttered if a developer tried to minimize sub-menus and option tabs. Most good developers spend a lot of time and put a lot of thought into providing a detailed, well-thought-out User Manual for customers who buy their apps. Before complaining that a certain function isn't obviously labelled or is too hard to locate - read the User Manual! And ask yourself if it's really THAT big of a deal if it takes you an extra 2 seconds to navigate to a sub-menu, if the benefit is a less cluttered main interface? If that extra 2 seconds is enough to cause you to lose focus or disrupt your creative workflow so badly, maybe the problem is with the USER, not with the app.

[@GlobalOffense]

Is it too late to request midi looping/? Okay, I will have a melody in my head, I'll play/rec it, and have a lot of extra variations (and progression) of that melody. I would like to (easily) use the progressions for intro/outtro, breakdowns, and pushes in the song. This means I'll manual cut out all the junk, trying to chop and arrange hoping to timing will fit (matching the recorded drum loop or midi loop). If I had something that allowed mey to keep my original melody without some stretching, auto beat fit, or quantizing. This is the same problem on my DAW. It seem all programs treat audio and midi like neighbors, not friends. :)