Pro tools first not responding

Pro tools first not responding DEFAULT

V-Control Pro – Pro Tools is unable to communicate with HUI

Pro Tools is unable to communicate with HUI

For Users who are experiencing the “Pro Tools is unable to communicate with HUI.” warning, follow these steps for proper setup.

  1. Verify that there is no firewall blocking V-Control Pro from operating properly.
  2. Launch the V-Control Pro desktop application FIRST on the host computer. (Launch in Administrator Mode for Windows users)
    1. To have V-Control Pro automatically launch at Start Up (Mac):
      1. Go to System Preferences>Users & Groups.
      2. Select your User ID.
      3. Select Login Items.
      4. Click the lock icon and enter and admin password.
      5. Click the + button to select V-Control Pro from your Applications folder.
    2. To have V-Control Pro automatically launch at Start Up (Windows):
      1. Press the Windows Logo Key + R, type shell:common startup, and then select OK.
      2. Drag a shortcut of V-Control Pro into the Windows Start Up folder.
  3. Launch Pro Tools on the host computer. (Launch in Administrator Mode for Windows users)
  4. Go into the MIDI Input Devices Setup in Pro Tools and make sure V-Control MIDI Inputs are enabled.
    MIDI Input Enable
  5. Go into Pro Tools Peripherals and ensure that the first row is setup as a HUI device with V-Control designated as the “Receive From” and “Send to”.
    Peripherals MIDI Controllers-Bank 1
    1. If setting up V-Control Pro to control all 4 banks in Pro Tools, ensure the DAW Track count in the V-Control Pro Desktop Preferences is set to 32.
      Preferences DAW Track Count 32
    2. In the Pro Tools Peripherals setup all 4 banks as shown:
      Peripherals MIDI Controllers-Bank 4
Sours: https://neyrinck.com/v-control-pro/pro-tools-unable-to-communicate-with-hui/

Support

Below you will find a list of the standard installation paths for our plugins, preset files and license files:


WINDOWS

PA license folder location:

%USERPROFILE%\AppData\Roaming\

Plugin folder locations:

C:\Program Files\Steinberg\VstPlugins

C:\Program Files\Common Files\VST3\

C:\Program Files\Common Files\Avid\Audio\Plug-Ins

C:\Program Files\Common Files\Digidesign\DAE\Plug-Ins

Preset locations:

C:\Program Files\Vstplugins\Plugin Alliance

%USERPROFILE%\Documents\VST3 Presets\

%USERPROFILE%\Documents\Pro Tools\Plug-In Settings\

%USERPROFILE%\Documents\VST3 Presets\Plugin Alliance\

No preset workaround:

In previous Cubase/Nuendo versions, VST3 presets saved by the user have been stored in these locations:

C:\Users\(Username)\AppData\Roaming\VST3 Presets\Plugin Alliance\(PluginName)\

MAC

PA license folder location:

Go to the Finder, click on the "Go" menu, click on "Go to Folder," and enter the following file path, exactly as written below:

~/Library/Application Support/

Plugin folder locations: 

Go to the Finder, click on the "Go" menu, click on "Go to Folder," and enter any of the following file paths depending on the format that you are after:

/Library/Application Support/Avid/Audio/Plug-Ins/

Library/Application Support/Digidesign/Plug-Ins/

Library/Audio/Plug-Ins/Components/

Library/Audio/Plug-Ins/VST3/

Library/Audio/Plug-Ins/VST

Preset locations:

Go to the Finder, click on the "Go" menu, click on "Go to Folder," and enter either of the following file paths to get to the format that you want:

~/Documents/Pro Tools/Plug-In Settings

~/Library/Audio/Presets

Sours: https://www.plugin-alliance.com/en/support.html
  1. Trusted cvv shop 2020
  2. Fractured but whole character sheets
  3. Graco truecoat 360 vsp

Troubleshooting (and Avoiding!) Common Problems in ProTools

WRITTEN BY KATE FINAN, CO-OWNER OF BOOM BOX POST

We all have technical difficulties from time to time, especially when using software are intricate as ProTools.  But, after years of making what seems like every mistake in the book, hanging out on Avid DUC, and stalking Gearslutz.com, I pride myself in my ability to overhear frantic technical freakouts and supply solid advice on the best course of action.  Here are a few of the problems I see most often, and and how to get through them while salvaging as much of your work and sanity as possible.

This happens all the time.  And as a supervisor, nothing is more annoying to than sitting down to review work and then finding that not everything links up.

How to Solve It

When you open a session with this issue, a dialogue box will pop up tell you that you have missing files.  Always choose “Manually Find & Relink.” Letting your computer automatically do so will take forever. Select the files you wish to relink (hopefully, all of them), and check out the path.  This will tell you where the session believes that the files live. Most likely, this will be on another drive or another computer. Once you see where the files are, you have a few options:

  1. Plug in the drive that contains the files, select that drive in the area to search, and choose find links and then commit links once the files have been found.  At that point, any files which were missing will still be missing from your audio files folder. They will only be linked to the session when the drive is plugged in.  So, you will then need to “Save Session Copy In” to save a session which does include all audio files.

  2. If you know that the files also live somewhere else on your local computer (such as a library drive), relink to that drive. Again, you will need to Save Session Copy In if you would like the files to be saved into your audio files folder where they belong.

  3. Find all of the missing files manually, and then drop them into your session’s audio files folder.  Then, relink to that folder. You may need to choose to relink be file name only if it does not work to use file name and ID.  There is no need to Save Session Copy In.

  4. If the files ARE in fact in your audio files folder, but ProTools isn’t recognizing them, you may need to search your audio files folder and relink by file name only instead of file name and ID.  Every once in a while, the file IDs become corrupt and ProTools mistakenly can’t use them to locate your audio files.

How to Avoid It In the Future

When saving your work to give to another person or to take to another computer, always use either Save Session Copy In or Export Selected Tracks as New Session.  Doing so gathers all audio files that are linked to your session from locations other than your audio files folder (like if you didn’t have “copy on import” selected or chose to import tracks by linking to files instead of copying) and copies them into the new session’s audio files folder so that they live in one place.  If you simply click and drag your working session’s folder, any files which are linked from other locations will not be copied and will be missing once the session has been moved.

This is one of the most aggravating things that can happen and always seems to occur at the end of a really long day. But, there’s hope!

How to Solve It

In my experience, the most likely culprit is that your drive is near capacity.  Check the drive to which you are attempting to save, and make sure to clear off enough space.  Even if you technically have just barely enough space, this can cause the bits to be written in every tiny nook and cranny on your drive, which makes it take forever to process the request.  

If drive space isn’t the issue, then you’re probably dealing with a corrupt file.  Here are your options:

  1. Close your session, open the most recent backup in your Session File Backups folder and save it off with the correct name (if you can). Then, you’ll need to redo any work between that backup and where you ended.  

  2. If the above does not work, then there is probably a corrupt file somewhere in your session.  The next thing to try is to close your session, create a whole new session (checking that all of your settings such as frame rate, sample rate, etc. are the same), and then import all of your tracks through the Import Session Data file menu.  Make sure to copy all audio files instead of linking.

How to Avoid It In the Future

Keep track of your available drive space at all times.  Have a system in place for archiving old work onto separate drives to make sure that you project drive always has space.

If you’re working on a mac, you will need to disable the function key features in order to select your tools/modes with the keyboard function keys.  

How to Solve It

Open System Preferences, and click on Keyboard. Then, check the box that says “Use F1, F2, etc. keys as standard function keys.”

How to Avoid it in the Future

Once you check this setting, you won’t have to think about it again until you purchase a new computer or reinstall your operating system.

This is the result of using the audio zoom in function when you are not showing all tracks.  Clicking on the audio zoom in/out button only affects clips which are visible in your current display of tracks.  When you show all tracks, the newly displayed tracks will have non-zoomed waveforms. Yet, the audio which was visible when you zoomed in/out will continue to display the new size.

How to Solve It

To reset all waveforms to their actual size, use the quick key Control+Option+Command+[ on a mac.

How to Avoid It In the Future

If you want to avoid this issue all together, only zoom your waveforms while all tracks are visible. Otherwise, the key command is a very quick fix.

This is most likely the result of having your session set at an incorrect frame rate.

How to Solve It

  1. Open your video in QuickTime and hit Command+i to get info.  This will display the video’s frame rate.

  2. In ProTools, open your Session Setup window and choose the corresponding frame rate.  

  3. Re-spot your video into place.

How to Avoid It in the Future

Always check the frame rate of your video in Quicktime before importing into ProTools. If you prefer not to do this, your video track in ProTools displays the frame rate below the track name. If your video’s frame rate does not match your session’s frame rate, the number will appear red. Change the frame rate in your Session Setup window to match the video.

This issue is known as drift and is the result of having your session set to an incorrect frame rate.

How to Solve It

  1. Open your video in QuickTime and hit Command+i to get info.  This will display the video’s frame rate.

  2. In ProTools, open your Session Setup window and choose the corresponding frame rate.  

  3. Re-spot your video into place.

How to Avoid It in the Future

Always check the frame rate of your video in Quicktime before importing into ProTools. If you prefer not to do this, your video track in ProTools displays the frame rate below the track name. If your video’s frame rate does not match your session’s frame rate, the number will appear red. Change the frame rate in your Session Setup window to match the video.

If you have already begun working on a project with your session set to the wrong frame rate, you cannot fix the problem by simply setting your session to the correct frame rate.  You must perform a sample rate conversion to re-sync your work.

How to Solve It

  1. Open your video in QuickTime and hit Command+i to get info.  Check the correct frame rate of the video.

  2. Open a new ProTools session with the correct sample rate and bit depth.  

  3. Open the Session Setup window and choose the new (correct) frame rate to match your video.

  4. Go to File > Import Session Data, and navigate to your project which was done at the wrong frame rate.

  5. Select all of your tracks, and make sure you are copying all audio (not linking).  Click the Apply SRC checkbox, and choose the correct pull up/pull down from the Source Sample Rate dropdown menu. To do this, choose your sample rate from the bottom of the list and then choose which direction you need to adjust.

  6. Click OK.

  7. Import your video, and re-sync it to your session.

  8. Check that the timecode burn-in matches the ProTools timecode window.  Your audio should be in sync.

How to Avoid It in the Future

Always check the frame rate of your video in Quicktime before importing into ProTools. If you prefer not to do this, your video track in ProTools displays the frame rate below the track name. If your video’s frame rate does not match your session’s frame rate, the number will appear red. Change the frame rate in your Session Setup window to match the video.

Your session has crashed.  You will need to force quit and open one of your backups (and pray that it was set to back up fairly recently).

How to Solve It

  1. Use the key command Control+Option+Command+Esc to bring up the force quit window.  

  2. Force quit ProTools and any other applications that are listed as not responding.  If you still cannot click on anything, you may want to force quit the Finder as well.  

  3. In the event that that does not work, you will need to “hard restart” your computer by holding down the on/off button on the computer until you hear it restart.

  4. Once you are able to use your mouse again, navigate to your Session File Backups folder and choose the most recent version. You will need to redo any work that was accomplished after that copy was saved.

  5. Re-save this as your original file name and it will replace your previously saved session.

How to Avoid It in the Future

Crashes are unavoidable. But, you can usually get used to which actions in ProTools are most likely to bog down your system. Take note of what you were doing each time this happens, and try to avoid it in the future. If a particular file is causing the crash, try to save a new copy of the file, or revert to an old version which doesn’t cause the issue.

Do you have any technical advice for common ProTools issues? If so, share in the comments below!


7 Comments

Sours: https://www.boomboxpost.com/blog//1/28/troubleshooting-common-problems-in-protools
iLok Services Not Running - Troubleshooting (Pro Tools)

Avid Pro Audio Community

DefaultPro Tools regularly freezing + 'Not Responding'!!

Pro Tools is absolutely killing me at the moment.

Am running PT Ultimate, up-to-date (), on Windows 10 (again, fully up-to-date), and the past days or so have been running into very frequent problems of PT freezing, completely at random, but on average perhaps every 15 minutes or so.

It could just be as simple as muting a track in the mix window, tweaking a dial in a plugin, clicking on a clip in the edit window, or selecting an option from the main menu - PT will just randomly freeze.
If a track is playing, the audio will keep playing, however PT will just lock up & completely freeze, & then 'Not Respond', leaving me with no other choice but to force close the entire program, & then I have to reboot my PC every time.

Just wondered if anyone else has been experiencing this recently??

I have paying clients both in person & connecting remotely for both audio & film work, and this is killing sessions & professionalism.

Our PC is incredibly hi-spec, so there's absolutely no risk of running out of memory etc.

I guess I could try trashing PT preferences yet again, but the past week or so have been an absolute joke.

Sours: https://duc.avid.com/showthread.php?t=

Responding not tools pro first

Here for the gear

Pro Tools Quicktime Server (Not Responding) Mavericks


Pro Tools on a brand new Macbook Pro (mavericks)

When booting up Pro Tools for the first time in Activity Monitor I see
two issues:
Pro Tools Quicktime Server (Not Responding)
and
Avid Video Engine (Not Responding)

After a minute or two Avid Video Engine returns to normal but the Pro Tools Quicktime Server remains as (Not Responding)

If I kill the process the Pro Tools becomes non-responsive as well and has to be restarted. Re-installing Pro Tools does not fix the problem.

Anyone else having this problem? Does anyone know exactly what the Pro Tools Quicktime Server process is doing? Pro Tools does seem to run fine if I don't mess with it, but I'm still curious as to what's going on.

Here for the gear

Same problem


Here a similar problem on a Win 7 machine.

Since 1 week i own Pro Tools

Unpredictable unresponsive, very similar to Timusic7 his problem.

Landed at Gearslutz (and became member ) through Google search for this specific problem.

Please note that is crashing upredictably too, so I am NOT convinced that both versions 10 and 11 (very unlikely) are the cause of this problem.
However I'm at at stage that I am kinda lost and don't know what to do anymore.

One time running , the internal program watch dog recognized a problem and has sended a report to Avid.

Any tips? If you need more info, please let me know

Lives for gear

Quote:

Originally Posted by Timusic7➡️

Pro Tools on a brand new Macbook Pro (mavericks)

When booting up Pro Tools for the first time in Activity Monitor I see
two issues:
Pro Tools Quicktime Server (Not Responding)
and
Avid Video Engine (Not Responding)

After a minute or two Avid Video Engine returns to normal but the Pro Tools Quicktime Server remains as (Not Responding)

If I kill the process the Pro Tools becomes non-responsive as well and has to be restarted. Re-installing Pro Tools does not fix the problem.

Anyone else having this problem? Does anyone know exactly what the Pro Tools Quicktime Server process is doing? Pro Tools does seem to run fine if I don't mess with it, but I'm still curious as to what's going on.

Same here. Pro Tools Quicktime Server (Not Responding) always in red in Activity Monitor. Maveriicks /latest PT.

Lives for gear

 
gainreduction's Avatar

Quote:

Originally Posted by Marsdy➡️

Same here. Pro Tools Quicktime Server (Not Responding) always in red in Activity Monitor. Maveriicks /latest PT.

Same here, same system specs. Exactly what is the quicktime server, what is it doing?

Gear Nut

Lives for gear

 
KevWind's Avatar
 


My Studio

🎧 15 years

Gear Maniac

 
thebri's Avatar
 


My Studio

🎧 15 years

Looks like this is an old issue. Reviving the thread to see if it the same for other people today as it was then.

I have noticed this for several versions of Pro Tools now for me, and was wondering if others had a similar experience. As shown in the screenshot below, the quicktime Server for protools reports in the activity monitor as not responding, in red.

In a similar head scratcher, my CPU overall meter will read 60%, but only one processor is being used, and it will be under Even with all of these processors, I still get overload errors under K buffers.

So, anyone else get similar results?

Lives for gear

 
lionheart's Avatar
 


My Studio

🎧 15 years
I also get the cpu spike all of a sudden.
Did you solve this ?

Quote:

Originally Posted by thebri➡️

Looks like this is an old issue. Reviving the thread to see if it the same for other people today as it was then.

I have noticed this for several versions of Pro Tools now for me, and was wondering if others had a similar experience. As shown in the screenshot below, the quicktime Server for protools reports in the activity monitor as not responding, in red.

In a similar head scratcher, my CPU overall meter will read 60%, but only one processor is being used, and it will be under Even with all of these processors, I still get overload errors under K buffers.

So, anyone else get similar results?

Sours: https://gearspace.com/board/
iLok Services Not Running - Troubleshooting (Pro Tools)

Herein you will  find a list of Pro Audio developers we&#;ve been tracking as they release information about compatibility with Windows If you know of something we do not have listed here, please contact us!

For our findings on Windows 10 for Pro Audio, look here: https://pcaudiolabs.com/windowsfor-pro-audio/

For information on how to upgrade to Windows 10, look here: https://pcaudiolabs.com/how-to-upgrade-to-windows/

AVID Pro Tools and AVID products

Avid products are not yet compatible with Windows  In our tests, Pro Tools 12 works well, although Avid has not yet released full compatibility.

Ableton

Ableton is compatible with Windows

https://www.ableton.com/en/help/article/windowscompatibility/

Cakewalk

http://blog.cakewalk.com/sonar-performance-with-windows/

http://blog.cakewalk.com/windowsmusic-production/

PreSonus

All PreSonus products are compatible with Windows

http://support.presonus.com/entries/PreSonus-WindowsCompatibility-Statement

M-Audio

M-Audio is testing many of their devices with Windows 10 and reporting no issues.

http://m-audio.com/kb/article/

Novation

Novation products are compatible with Windows

http://us.novationmusic.com/answerbase/windowscompatibility

Steinberg

Steinberg products are not yet compatible with Windows

https://www.steinberg.net/nc/en/support/knowledgebase_new/show_details/kb_show/product-compatibility-info-regarding-microsoft-windowshtml

Sours: https://pcaudiolabs.com/windowspro-audio-compatibility-list/

Similar news:

Pro Tools Keyboard Shortcuts Not Working? Get a fix! Let’s dive into the 5 Most Common Issues and get them working again in no time.

Why are Pro Tools Keyboard Shortcuts Not Working - 00 Featured - Sound Mixing Stage

Shortcuts are a blessing, a gift from heaven. But shortcuts are a curse when the right keys are pressed… and nothing happens at all. Hey, don’t panic, the answer might be just around the corner. Keep on reading!

So Why Pro Tools Keyboard Shortcuts aren’t Working?

In this guide, we’ll be covering the most common issues and how to fix them.

Generally, shortcuts fail to work correctly due to the following causes:

PRO TOOLS SPECIFIC SHORTCUT ISSUES

AZ Commands Keyboard Focus

Pro Tools has a great set of Single-Key shortcuts, which are extremely practical and fast. You can perform rapid actions such as Zoom In/Out by pressing R and T, or Cut, Copy or Paste using just  XC, V.

On the other hand, Pro Tools also has a ton of Combination Shortcuts. These shortcuts additionally require the use of a modifier key such as Control, Option, and/or Command. Take for example Option+Shift+3 to consolidate a clip.

If combination shortcuts are working fine but single-key shortcuts are not, check the Command Focus first.

Use the Commands Focus to get your Pro Tools shortcuts back!

Pro Tools keyboard commands can be focused on 3 different sections:

  1. The Edit Window
  2. The Clip List
  3. The Groups pane

The “letters” on your keyboard will trigger the shortcuts where the Focus is set to. For editing purposes, you definitely want the Commands Keyboard Focus to be active on the Edit Window, as shown below.

Click on the tiny AZ icon. It will turn yellow, indicating where the Focus is active. 

Why are Pro Tools Keyboard Shortcuts Not Working - 01 Command Focus - Sound Mixing Stage
Why are Pro Tools Keyboard Shortcuts Not Working - 02 AZ Edit Keyboard Focus - Sound Mixing Stage

You will now be able to use one-key editing shortcuts normally.

Keyboard Command Focus Shortcuts

As a bonus, you can alternate the Focus using the following combination shortcuts:

  • Edit Window: Option+Command+Numeric keypad 1
  • Clip List: Option+Command+Numeric keypad  2
  • Group List: Option+Command+Numeric keypad  3 

Mix Window Command Focus

The Mix Window has its own keyboard focus AZ icon.

Why are Pro Tools Keyboard Shortcuts Not Working - 03 AZ Mix Window Focus - Sound Mixing Stage

This keyboard focus indicator will be active when you have the Mix window selected, having an effect on the Group List. If you click anywhere in the Edit window, your editing shortcuts will become active again.

CLASHING SHORTCUTS BETWEEN PRO TOOLS AND THE OS

Function keys (F1-F12) not working on macOS

Pro Tools does not respond to Function Keys (F1F12).

Switching between editing modes (Shuffle, Slip, Spot, Grid), or editing tools (Smart Tool, Selector, Grabber, Trimmer, Pencil, etc.) doesn’t work. Instead, you end up changing the screen brightness or adjusting the volume?

This is because Function Keys are acting as special Feature Keys. This mode enables you to quickly dim the display, advance iTunes tracks, mute the speakers, etc.

You can get away by using the Fn key in combination with the desired F key. You can find the Fn on the lower-left corner of your keyboard.

This will enable the function keys, and momentarily solve the issue. But it’s a bit cumbersome to rely on this workaround if you are serious about editing.

A better option is reversing the OS default behavior of these “special” feature keys into standard functions keys. This is far easier than it sounds. Just follow these simple steps:

How to enable F1 – F12 as standard function keys

1.  Click on the Apple menu, left on the top bar

2.  Go to System Preferences…

3.  Click on Keyboard > Keyboard

4.  Check the box “Use F1, F2, etc. keys as standard function keys”

Why are Pro Tools Keyboard Shortcuts Not Working - 03 Function Keys - Sound Mixing Stage

Checking this box will make your life much easier when using Pro Tools. It’s far simpler to use one hand to toggle the Smart Tool than to reach out for the  Fn key in combination with  F6+F7+F8.

If you eventually need to change the screen brightness, adjust the volume or skip a song in iTunes, just use the Fn key in combination with the desired feature key.

If your Mac has a Touch Bar

> _You can always show function keys (F1, F2, and so on) in the Touch Bar for specific apps. In Keyboard preferences, click Shortcuts, select Function Keys in the list on the left, then add the apps on the right._ (from the macOS user’s guide)

How to disable macOS shortcuts that conflict with Pro Tools

Pro Tools has a whole bunch of keyboard shortcuts that make editing more comfortable and fast. But, many of these shortcuts are already taken up by macOS by default.

For example:

  • To Expand/Contract a Track’s Height: Control+Up/Down arrow are actually the same macOS’ shortcuts for Mission Control and Application windows respectively.
  • To Record:  Command+Spacebar, shares the same shortcut with Spotlight Search.

Luckily, disabling those native shortcuts is a piece of cake, and I strongly suggest you do so. Turn off everything except functions that are quite useful and don’t clash, such as Show Desktop, Dashboard, some Screen Snapshot functions, and Custom Pro Tools Shortcuts.

To disable system shortcuts conflicting with Pro Tools, follow these steps:

  1. Click on the Apple menu, left on the top bar
  2. Go to System Preferences…
  3. Click on Keyboard > Shortcuts
  4. Uncheck every checkbox on every category, except the ones listed
    1. Launchpad & Dock: Uncheck all
    2. Mission Control: Uncheck everything, except&#;
      1. Show Desktop [F11]
      2. Show Dashboard [F12]
    3. Keyboard: Uncheck all
    4. Screenshots: Uncheck everything, except&#;
      1. Save picture of selected area as file
      2. Save picture of selected area to the clipboard
    5. Services: Uncheck all
    6. Spotlight: Uncheck all
    7. Accessibility: Uncheck all
    8. App Shortcuts: Of course, don´t disable any previously added Pro Tools Custom Shortcut.

MacOs Keyboard Shortcuts: This is how everything should look like&#;
(Click on the arrows for Next/Previous image)

Once you have unchecked the suggested options, Pro Tools shortcuts functionality should be restored.  Try any key combo. For example, select any track in Pro Tools and press Command+Up/Down. The tracks should expand or contract in height. If not, continue reading.

Fix Conflicting Keyboard Layouts and Input source languages

If you live in a non-English speaking country, it’s very likely that your keyboard is localized. It has special characters and a different key layout. Having a non-US keyboard can really whack your shortcut mappings.

  • For example, on a Spanish Latin American keyboard, the shortcut to switch between Edit and Mix windows [Option+=] doesn’t work.

Also, having a standard US English keys keyboard with the Operating System Input Source language set to other than US English can yield unpredictable results.

If you are serious about using Pro Tools professionally, I encourage you to use an English version of Pro Tools along with a full-size US English keyboard (with numeric keypad).  

  • Your keyboard mapping will be exactly as that shown on the Pro Tools users guide.
  • You’ll internalize finger movements for each shortcut, preparing you to work in almost any studio around the world. This reason alone is worth the investment.

When you need to work with audio, plug your US English keyboard and switch the input source from your default language to English [Command+Space]. You’ll be ready to edit and make use of all available shortcuts. Very simple and effective. 

Note: By enabling the Input Source toggle [Command+Space], you will override Pro Tools’ shortcut for recording. Anyway, I always record using the alternate shortcut, reinforcing the idea of a so-needed keypad. Preferred recording shortcut -> Number  3 on the Numeric Keypad.

OTHER ISSUES

Notebook Keyboards Shortcut Limitations and Workarounds

When editing or mixing dialogue, you continuously rely on actions that are easily accessible from the numeric keypad. Take this few examples:

  • [+/&#;] to move the Cursor or nudge selected clips forward or backward 
  • [*] Asterisk & Numeric Enter for jumping to timecodes
  • [.] Period to access Marker Locations.
  • [Return] for adding new Markers
  • [Option+6] Show/Hide Clip Effects. So useful for mixing dialogue and sound fx.
  • [3] For Recording
  • Various Jog/Shuttle functions

If you are using a notebook, I would strongly suggest that you get yourself a full-size external keyboard. Pro Tools is not designed to work with skimmed notebook keyboards, and that’s the hard truth. The Numeric Keypad, in my opinion, is such an integral part of a great Pro Tools workflow. Also, a good external mouse with a scroll wheel is an excellent idea.

You could use QuickKeys App to remap the shortcuts. But you’ll find it’s much easier and way more comfortable in the long run to plug an external keyboard.

Be aware of external keypads: Most of them will get the job done right out of the box. But some won&#;t work when combining shortcuts on both keyboards, such as pressing Command and a numeric key! 

Recommendation: I love Mac keyboards, both USB or Bluetooth. They are very sturdy yet lightweight. They have a very shallow profile and an amazing mechanical action, which makes them ideal for long editing sessions. The USB version has the benefit of including 2 USB ports for plugging in removable media or any other compliant device. Unless you spill a cup of sugary coffee over them (I sadly witnessed that), they will last forever.

Notebook workarounds: Anyway, if you are working with your notebook, here are a few tips you can benefit from:

  • Adding Markers. You would typically add a marker using the enter key on the numeric keypad.
    • On a notebook use: Fn+Return
  • Nudging Clips: The most common way of moving clips back or forward in time is by using &#;/+ on the numeric keypad.
    • On a notebook use:  <, > (Link Edit and Timeline must be enabled)
  • Entering Timecodes: Normally, you would hit the star key [*] on the numeric keypad, fast and effective.
    • Alternative: Click on the main counter or big clock to manually enter timecodes.

Conclusion

We’ve seen five of the most common causes of why Pro Tools shortcuts might stop working and how to fix them.

In a nutshell, 

  • The first thing you should check is theCommands Keyboard Focus. To make one-key editing shortcuts available, make sure the AZ icon is active in the Edit Window.
  • If the Function Keys are not working [F1 &#; F12], they are likely set to work as Feature Keys, to control volume, screen brightness, etc.Check this section toenable Function Keys

Do you have any other issues or can share any solutions that might help others? Please comment below!

Next Step

Now, are you interested in adding your custom shortcuts for launching your favorite plugins with the press of a key combo? I’ve written this article explaining how to do it in just a few simple steps.

Sours: https://soundmixingstage.com/why-are-pro-tools-keyboard-shortcuts-not-working/


994 995 996 997 998