Does 'Commit' offer the same quality as 'printing' in real time?
Simple question really. I'm finding the 'commit' feature really useful but just want to be sure that it offers the same quality as printing in real time.
|
Re: Does 'Commit' offer the same quality as 'printing' in real time?
Quote:
Also, you can Commit in realtime as well. Do one each way compare. |
Re: Does 'Commit' offer the same quality as 'printing' in real time?
I have yet to hear any differences at all between printing in real time vs printing offline vs bouncing to disk vs bouncing to session audio track, despite what people say online. The only difference I ever encountered was sometimes mute automation does not happen at the proper location on bounce to disk. But in almost every case, rebouncing again fixes this. This has not happened to me since Pro Tools 10, however.
|
Re: Does 'Commit' offer the same quality as 'printing' in real time?
It really depends on each individual plug-in's code. I haven't noticed any problems myself.
|
Re: Does 'Commit' offer the same quality as 'printing' in real time?
Quote:
|
Re: Does 'Commit' offer the same quality as 'printing' in real time?
Null tests are the only way....ears are too fickle
Way too Subjective......(ears) |
Re: Does 'Commit' offer the same quality as 'printing' in real time?
Quote:
Agree on the null test. C |
Re: Does 'Commit' offer the same quality as 'printing' in real time?
I've always noticed timing discrepancies on longer busier clips. It's very obvious when I line up the midi against the waveform. Strangely, I notice this more on bass, but I haven't investigated to find out if it's frequency related.
|
Re: Does 'Commit' offer the same quality as 'printing' in real time?
Yeah I've heard odd stuff when using warp markers. I was wondering if same for others. It's easiest to hear on bass tracks for me as well.
C |
Re: Does 'Commit' offer the same quality as 'printing' in real time?
Quote:
It's reassuring to hear someone else has this problem. So it's not me or my system. I can understand if that happens with warped audio (after all, elastic audio isn't all it's supposed to be) but these are straight quantized midi/VI tracks. Absolutely no excuse for bad timing here. I always find myself having to warp affected sections of my bass line after using commit, re-committing sections, or realtime bouncing if there's too much of it. It's seemingly random. I haven't had these issues with drums, just bass...which makes me think it's frequency related. Realtime bounce doesn't do that, so the whole purpose of commit is defeated if the results necessitate spending time editing after the fact. Ive had this in all PT releases since commit was introduced. |
All times are GMT -7. The time now is 04:27 PM. |
Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com