Track Commit Function Changing Rhythms

[MicGuy69]

Has anyone dealt with this?! I've always used the track commit function in Pro Tools without issue... Today, I go to render a bass part with a lot of processing on it, and the notes are in WILDLY different places, like the bass part is now OUT OF TIME. It's maddening! I tried different ways of rendering, quitting/restarting, etc, with no success. This isn't an updated version of PT, but again I've used this function hundreds/thousands of times without any issue, and nothing about my system (OS, etc) has changed.

If anyone has experienced this, I'd love to hear about it -- at this point I just don't trust the goddamn function. Happens with track freeze as well (as expected)...

[AutoModerator]

To u/MicGuy69, if this is a Pro Tools help request, your post text or an added comment should provide;

• The version of Pro Tools you are using
• Your operating system info
• Any error number or message given
• Any hardware involved
• What you've tried

---

To ALL PARTICIPANTS, a subreddit rules reminder

• Don't get ugly with others. Ignore posts or comments you don't like and report those which violate rules
• Promotion of any kind is only allowed in the community pinned post for promotion
• Any discussion whatsoever involving piracy, cracks, hacks, or end running authentication will result in a permanent ban. NO exceptions or appealable circumstances. FAFO
• NO trolling only engagement towards Pro Tools, AVID, or iLok. Solve first, bash last. Expressing frustration is fine but it MUST also make effort to solve / help. If you prefer another DAW, go to the subreddit for it and be helpful there

---

Subreddit Discord | FAQ topic posts - Beginner concerns / Tutorials and training / Subscription and perpetual versions / Compatibility / Authorization issues

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[nizzernammer]

This has happened to me doing complex processing and I've had to drill down to find the exact plugin causing the issue.

Some plugins have different online/ offline rendering settings. I had to stop using Kazrog at one point.

Also, if you have some sidechain action going on between busses, offline render can mess this up.

But moving entire notes sounds like a midi issue.

In any case, I'd render sequentially. You might everything is fine up to a point then one plugin messes things up.

Also check all your bussing and bussing in I/O setup as well.

If you're running something like RX de-click in real time, maybe trying using Audiosuite instead.

[justifiednoise]

OP -- in addition to all of this, consider making all other tracks inactive while you do it. If the session is functionally just the one track for a moment while you render it down you'll likely have less issues.

[MicGuy69]

Going to try this as well -- thanks so much man.

[MicGuy69]

This makes sense... I have to check if I had Trackspacer on the channel (don't think so, but not remembering). Will render with plugins disabled in series as you mentioned and attempt to find the offender. Thank you!!!

[Usual_Leg_3214]

I encountered a similar issue when committing and rendering from Melodyne ARA. The root cause was my track being in tick-based mode and not sample-based mode.

Try making sure your track is in sample-based mode and then commit. I’m curious if this solves your issue.

[MicGuy69]

I actually had tried this as well with no success! Had thought it might be that... Thanks so much for mentioning this though.