Tempo mapping is an important and major advancement in most modern DAWs that dramatically opens the door for freely recorded music (not strictly recorded/quantized to a tick/grid) to be both enhance with loop based sounds and quantization.
The problem: It takes depending on the song anywhere from 5-20 minutes to map a song manually in Studio One. Unfortunately, this is too big of a hurdle and learning curve for most of your customers.
Competitive analysis: Although Studio One has made good advancements in transient capabilities, you are behind your competitors in tempo capabilities. ProTools, Logic, Cubase and Sonar can (and have been for several releases) detect tempo changes for an entire song to a least a beat level. Thus there is a real market for this capability for tempo tools. Please see the video for examples of the competition.
Benefits: 1. By improving your tempo detection capability you will attract more ProTools, Cubase and Sonar customers that heavily rely on this capability.
2. Many more existing customers that have never attempted tempo mapping due to the difficulty and time required to make it work will get more value from your product.
3. You will greatly improve work flow of existing customers that already attempt to tempo map with existing capabilities.
Feature Request 1: Tempo detection algorithm for an area or event. 1. It should have a dialogue box to set resolution to beat or bar.
2. It should transients threshold adjustability
3. It should be able to handle different meters ( although not necessarily changes in meter with in an event, none of the competition can do this either)
4. It should be able to detect beat one.
5. (Suggest adding it to the existing bend marker view)
Feature Request 2: Manually/visually align beats to transients. 1. It should support drag and drop grid beat lines to actual transients to allow for quickly beat to transient visual alignment.
2. Note: Yes I know that it can be done by manually inserting tempo marks and then dragging tempo marks. (Please see my Audio timing video if needed). The point here is Presonus is well known for its superior ease of work flow. At a minimum it should work as easy as or easier than for example Logics approach to dragging the time line marks to a transient.
Feature Request 2a:
The new cross hair alignment capability should extend the cross hairs across the tempo track and audio/MIDI tracks. It currently only work exclusively in one or the other making it useless for manual tempo alignments
I know it has been requested many times in the past but please seriously consider this request.
Thanks
Jeff
This message was edited 2 times. Last update was at 05/11/2013 18:28:32
Joined: 20/10/2011 04:33:34
Messages: 1111
Location: California
Offline
I hate to bring up PT, but I do miss this feature. Count this as a .
Dan
All the cool kids hang out in the middle of their meters, you should too.
S1/2 Pro
***Lenovo i5 @ 3.1ghz running Windows 8.1 x64 with Syba Low Profile PCI-Express 1394b/1394a (2B1A) Card, TI Chipset, SD-PEX30009
*** Levono E520 with SYBA SD-EXPC34-2F 1394A Firewire 2-Port ExpressCard *** Win 7 64 Pro
*** Firestudio Mobile
*** Presonus Studiolive 16.0.2
*** Digidesign Eleven Rack, PT 10
Sold my PTHD system to someone who didn't mind paying $8000 for an upgrade to 11
I really need this feature. I like it a lot better to just playing sample drums, keys whatever without any restrictyion of a loop or click track. In whatever tempo feels natural. Then cut the looppoints and then match up the tempo to the loop.
An easy command as set tempo to loopselection would be a really great feature allowing S1 users to play from the groove that feels natural to them instead of recording to a clicktrack or loop.
Musicmakerr wrote:Agree! But I would prefer something simpler, like this:
Agree with you both.
That would be a natural place for a detection button if the Event wast a consistent tempo..
But just to be clear detecting tempo of a naturally played track results in many tempos, as the tend to shift measure by measure or beat by beat. The results thus needs to be displayed in the tempo track. So most likely they would need to implement a toolbar like the quantize toolbar, that would allow for setting options like tempo sensitivity measure/beat, meter settings and over all detection sensitivity.
In my experience no DAW maker has a perfect detection algorithm so once the process is done, you need a very simple manual override to fine tune the tempos (I like Logic's drag the measure to the actual beat solution)
S1 has already detect transient (attack) it might already be used to calculate the BPM .. Or add an option or you must manually place the markers, after which it can calculate the average BPM.
sambosun wrote:Cant you set midi to time base rather than beat based in the inspector?
Wow! This is one of the best tips I've learned on this forum! Thanks a lot Sambosun.
It's one of those simple things that I seem to overlook. Hahaha, I've been thinking last two weeks to find a macro workaround for this. Bouncing down the midi file, loop selection etc....
Thanks!
This message was edited 2 times. Last update was at 04/05/2012 01:35:17