1.0 & Beyond: Cue Points
When we started developing Sonorasaurus we had a clear vision of what we wanted to do and where we wanted to go.
Outside of offering a fully functioning deejay application we had specific ideas for handling the audio output and how music was accessed and managed. We discussed our ideas with Apple early on and learned that there were quite a few restrictions in place. Some of them Apple planned to eventually lift given an increased demand for the functionality. Other restrictions were vague and uncertain.
At that point we had to make a decision. Either put our project and ideas on hold until all the restrictions were lifted (if ever) or revise Sonorasaurus and continue to shape it in the right direction with updates.
At the very least 1.0 could offer people of all skill types a practice and backup solution in addition to a means for casual and non genre deejays to play their sets and record mixes.
So now that we are out in the world and Apple has yet to lift their restrictions we are revising our focus again. Our ideas for additional features and functionality will have to remain on hold but we are still going to find ways to satisfy our users and give them the extended functionality they deserve.
One of the features that will make it into the first update is Cueing.
CUE and SET buttons to facilitate this. Tapping the CUE button will allow the user to jump to the beginning of the track or any new point they set. Holding down the CUE button will play the song from the cue point until the button is release. The SET button will be used to lock in new cue points or reset the cue to the beginning of the song.
We have also been asked a lot of specific questions about certain features and lack of features. Read on to view our answers to some of these questions.
Are you going to release a lite / trial version soon?
We do not have plans for a lite version. A lite version means building a whole other app, even though it appears to be the same app with some features removed. We want to keep our focus on the main app and taking care of the features that the users want.
Why doesn’t Sonorasaurus have a visual mode or display waveforms?
We did come up with variations of our interface that factor in visual representations and waveforms for songs. For the time being we decided not to use these types of interfaces. Displaying a waveform takes additional processing away from other areas that we we feel can be used more consistently; like effects.
Also we felt the screen size was too limiting. Yes you can see a zoomed in portion of a waveform, but you are not able to also see the full waveform and where you are in the track at the same time. Something like this works very well as an additional aid in programs like Serato, but could prove to be cumbersome or misleading when used in a limited capacity on a device like the iPhone.
Will Sonorasaurus have a BPM counter at some point?
We are not sure. We are looking into this, but much like utilizing waveforms a BPM counter and display would require additional processor power on a device with limited CPU and RAM. The BPM counter can also be useful, as it is used on most CDJs, but can also be inaccurate at times. For now we are devoting all the limited processing power to functions that are more consistent.
Why doesn’t Sonorasaurus 1.0 offer a split mode with the Y adaptor?
We were hoping to offer another, currently restricted, option for separating the audio to include in our first update. Split mode for us is plan B.
The buttons are very small, can you make a multi screen mode?
When we revised our focus during the development phase we decided to make 1.0 very clear to new deejays. The layout allows the user to see all of the buttons, input areas and information all at once. This keeps confusion to an absolute minimum and allows the user to familiarize themselves with all the functions before moving on to a more advanced layout with aspects of the set up occasionally hidden from view.
We have other interface designs and will incorporate them in future updates, but to a degree some of our interface ideas are dependent on restrictions being lifted and good workaround solutions being consistently tested and proven.
A special thanks goes to Peter. A lot of our discussion recently helped shape this post.