![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
|
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
![]()
A million features would be useless to 3/4 of a million users, no?
How many of us use ALL the features of PT? Not many I'd say, even if some use almost every single feature.. So, every day I see users on here doing a couple things: 1) Slag on Avid for not implementing a million features with a million options each. 2) Slag on automation and scripting unique solutions to unique use scenarios, for a million reasons. What about the OTHER side, instead of downing on these things in this thread? (You're not welcome in the future, lol, of this thread)! I'd like to hear about how people appreciate tools like SoundFlow and how you anticipate the official scripting SDK to enable and streamline your work. What do you do with automation, since discovering it, that you'll never go back on? What saves you time? What makes automation worth it? What would you like to do that it seems cannot be done yet? What about the learning curve-- do you have time, motivation, cycles for this work? What do you say, after you're into automation for a while, about the mixing of repetitive behaviors and creative energy? For example, some might see the scripting as a cognitive burden, while others see the automation in practice as a creative enabler.
__________________
___ >> me: nednednerB // ||main gig: editing audio voiceovers & testing software | 2nd gig: music software tutoring | hobby: electronic music // ||software: Ventura 13.4 | PT Studio 2023.6 | Ableton Live 11 | iZotope RX, Ozone, Neutron | Arturia Pigments | Auto-Tune | Dubler2 // ||system: iMac (Retina 5K, 27", 2020) 10-Core-i9 | 128GB-DDR4 | 5700-XT-16GB | OWC Thunderbolt Hub and Thunderbolt 3 Dock // ||devices: Focusrite Clarett 2Pre | some AT condensers | SM58 | Ableton Push 2 | 32" 4k LG display | Sennheiser HD 600 HP // ||automation: SoundFlow | Stream Deck+ | Keyboard Maestro | SteerMouse | MacOS Shortcuts // |
#2
|
|||
|
|||
![]()
Mr. Ned Ned
Interesting to consider the implications of a scripting language for PT. Depending on how deep the scripting goes, I could see GPT4.5 (trained on PT Script) fully automating mixes and then producing mixes in the "style of" Al Schmidt for example. Automation will be useful no doubt, but PT as a GPT/LLM plugin will be transformative. If 'Fake Drake' can 'create' music people like, then 'Fake CLA' can certainly 'mix' music people will like. Such interesting times. Anything with deep scripting will be a candidate for LLM training and integration as a GPT plugin. The conspiracy part of my brain thinks that AVID integrated scripting at the request of 'Big Media' so they could radically bring down the cost of Post. Tinfoil hat time. ...but, that's probably not the discussion you were looking for. ejinbc |
#3
|
||||
|
||||
![]()
Regarding AI tools,
Consider GitHub. Are they afraid of software writing software? Nope! They've released "Copilot." The seasoned professional software programmers that REALLY know scripting, and who I work with, are super happy to embrace the idea of telling Copilot: "Okay, I have an object myObject with key pairs and values for name, id, but empty values for color. Can you write a function to iterate through each ID, and when the name is the same, give it the same color, from a range of values in array, myColors. Then, hook that up with the last function I created so based on the color, the function will iterate through this other array myArray." And Copilot practically just DOES it, then the developer goes "ahhh, the boring work is done, now I just do the already necessary troubleshooting part of it!" ![]()
__________________
___ >> me: nednednerB // ||main gig: editing audio voiceovers & testing software | 2nd gig: music software tutoring | hobby: electronic music // ||software: Ventura 13.4 | PT Studio 2023.6 | Ableton Live 11 | iZotope RX, Ozone, Neutron | Arturia Pigments | Auto-Tune | Dubler2 // ||system: iMac (Retina 5K, 27", 2020) 10-Core-i9 | 128GB-DDR4 | 5700-XT-16GB | OWC Thunderbolt Hub and Thunderbolt 3 Dock // ||devices: Focusrite Clarett 2Pre | some AT condensers | SM58 | Ableton Push 2 | 32" 4k LG display | Sennheiser HD 600 HP // ||automation: SoundFlow | Stream Deck+ | Keyboard Maestro | SteerMouse | MacOS Shortcuts // |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
What's New in Pro Tools Scripting SDK Toolkit 2023.3 | rmajors | Pro Tools Scripting SDK Toolkit | 0 | 03-24-2023 10:05 AM |
Scripting in Pro Tools | soundgott | Tips & Tricks | 2 | 05-29-2022 01:28 PM |
Is there a scripting dictionary for Pro Tools? | amyoleary | General Discussion | 1 | 05-07-2005 10:31 PM |
scripting Pro Tools; automation | Bermaster | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 12 | 10-01-2004 12:38 PM |
Fades versus Automation | Johnbearorl | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 6 | 10-10-2002 12:25 AM |