However the integration with StreamDeck is way better than KM, so if you have one of those baby's its a no brainer! Having said all that, I found the method of creating shortcuts and transferring them to scripts can be slightly clunky when compared to KM and learning to write shortcuts directly in scripts is a bit daunting. I'd say 'Notes' is worth the price of admission on its own, allowing you to create and use multiple marker sets in Pro Tools.īut the biggest plus is that Christian is a Pro Tools user,Composer, Sound Designer and Mixer and understands what is we are hoping to get the program to do. It seems to me that SoundFlow can do things that are not possible to easily program in KM, if at all and because Christian is so brilliant with support, I've managed to build 2 macros I've been unable to get working for years. I've been using SoundFlow for only a few days now and have already managed to transfer most of my KM shortcuts and macros, with some help from Christian of course. SoundFlow is an entire workflow platform, so our automation part is just a piece of the puzzle. A bunch of apps that we already built for you (check out the Store)īut really as you start using it, you'll notice they are very different apps and that the overlap is relatively minor.A surface designer - build your own touchable surfaces inside SoundFlow, or develop entire apps.All your settings are synced with the cloud so you have access to them at any time from any computer running SoundFlow.Stream Deck integration - use our Deck designer to design your own decks for Stream Deck.Add packages of commands/macros/decks/surfaces that other users built directly inside the app, or publish your own. What SoundFlow offers on top of this is - among other things: This was if you look purely at simple automation. In KM if you want to automate Pro Tools, you'd have to develop the combination of mouse clicks and keyboard actions themselves, in SF you get several hundred built in actions that deeply integrate with Pro Tools, which means we took care of all that for you. In SF you also have the ability to use Javascript, which adds the ability to develop very complex scripts. This means KM has some advantages in making scripting-like things in visual macros, where in SF you can do more simple logic inside of macros, but the actions themselves are much more deeply integrated in Pro Tools. KM has a long history of allowing people to develop macros via a drag and drop editor. Hi short KM and SF have some overlapping features, so lets start there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |