Quote:
Originally Posted by tamasdragon What are those editing features which kills Pro Tools? Seriously, so many Nuendo users mention this. What are those features? |
Well, it wasn't me, I didn't say kill...
It's really just two different types of "sound-hammers" but they are very different to bang in nails with. To each his own, but since you asked I'll try to give some examples of what I like.
Short background. I started using 2", then discovered sound tools, then Avid Audio Vision, then onto PT. We still have PT both "fully native" and HD systems. We deal with sound for feature films and drama TV mostly. Five audio editing rooms, two TV mix rooms, one dub stage, big ass foley stage and location recording. Currently building a in house picture department as well.
Started using Nuendo 2005 (at first in paralell with PT). PT gets used less and less these days...
Even though I wrote earlier in this thread part of the difference (the hammering in PT), I'll try:
PT editing is mainly based on the cursor and the range selection. Most things done in PT when editing is dealt with either by selecting a range or where events are in relation to the cursor as the basis of what type of edit is supposed to be done.
In Nuendo its the events that rule the world. You can force Nuendo into working with the cursor and selection pretty similar like in PT, but it is slower.
To give a event a three frame fade in i just hit fade in one frame three times.
For the next event I just want two frames, then one, then eight. Easy.
In PT I have to place the cursor and then fade head, but the exact length of that fade wont be a frame unless you've editied in grid mode or you've manually set your cursor exactly the length from the event start that you want.
Really the editing style difference cursor+selection vs. event goes much further than above, but I find it hard to explain. It IS different and in most ways faster in Nuendo.
Basing editing on events rather than selection has definitely made my chops a lot faster compared to when I was fast in PT.
Events+macros+userdefinable keystrokes=speed
You rarely see Nuendo users having to do awkward "three-finger-salutes" to get something done.
Any sound on any channel regardless of routing, solo state or if it's inactive is always available to preview. Just hit it with the preview tool and see if it's what you need (alt take/alt fx/muted sound etc). This is THE one feature I'm dying for when I have to work in PT. I can make do with PT as well, but replacing the possibility to audiotion anything anywhere with cumbersome solo defeating and shift s is a really crap way to deal with auditioning compared to Nuendo.
Then I might want to remove all muted events, or rename them or unmute them, Ill just use the PLE telling it to do just that. Or name my tracks accoding to my personal naming convention again using the PLE.
Or I'll just select my composite hero-gun and place it on the server as a clippackage, this can be searched and auditioned and re-used by all the other editors at will.
When in the mix I hear the director saying, "I need another style of ambiance for this quiet section, fix that while we continue with the action sequence". I could do headphones laptop in the rear of the dubstage trying to find and rebuild the scene, or I'll just share a copy of those tracks or elements on the network. Go to another studio, work on it, when done commit the changes, have the mixer review the changes and either play the fixes back from the fix tracks or just move them up to the original tracks. No file handling no import export, it's all handled in the background. I'm actually working on a mirror of the fix tracks in the mix room, hit commit and it will all transfer automatically back to the mix.
Of course you also have 32 marker tracks, import of EDL to see all the cuts and scene changes (without having to own expensive AVID gear). CSV import/export for ADR and spotting notes.
Batch process of audio events, where I can store a chain of processing used for a certain type of sound.
Process history so I can undo parts or all applied processing in a series.
And of course non realtime exports...
Nuendo Drawbacks?
AAF import is severly lacking still, easy to work around, just open in PT first and export as a new AAF. PT AAF's always work by the way it's MC that does it's weird things to the AAF's.
No VCA's, I love VCA's but I can work perfectly well without them as well, just another mindset. But I still want them. PT implementation of VCA's is great.
Single selection to process only, process window needs to close to select the next event.
Metadata, lots to do still.
Need better Conform and re-conform tools.
It's not compatible with PT and as long as PT is the elephant in the room that will always be a negative...
Sorry about the long post.
Hopefully that gave you some insight in what we like about Nuendo.