|
Post by spindrift on Sept 14, 2018 12:25:56 GMT -6
What are the PRO differences between using Native and PT HD these days? What makes you crave (or demand) HD vs. Native?
|
|
|
Post by aremos on Sept 14, 2018 12:43:29 GMT -6
HD or HDX? I'm keeping my HD3 Accel & am not craving for HDX, as of now. Unless someone here convinces me otherwise the only thing I might end up doing is stay tracking on existing system (PT HD 10) & maybe buy & mix in PT (Ultimate?) Native.
|
|
ericn
Temp
Balance Engineer
Posts: 15,012
|
Post by ericn on Sept 14, 2018 12:51:18 GMT -6
True generic PT 32 ch I/o lock, lets you use any interface.
HD Native, gives you ultra low latency, higher i/o count but must use interfaces must be PTHDX compatible and you need either the HD Native or PCIE card.
PT HDX ultra low latency plus plugins run on the HDX cards, you can add additional I/O and DSP by adding HDX cards. Must use HDX compatible HDX interfaces. PCIE only or PCIE via TB- PCIE chassis.
|
|
|
Post by drbill on Sept 14, 2018 14:14:12 GMT -6
HD or HDX? I'm keeping my HD3 Accel & am not craving for HDX, as of now. Unless someone here convinces me otherwise the only thing I might end up doing is stay tracking on existing system (PT HD 10) & maybe buy & mix in PT (Ultimate?) Native. HDX has been awesome for me. Glad I finally made the jump from HD to HDX. 96 i/o - flawless delay compensation - flawless unlimited busses - AWESOME (working on a template now that's quickly approaching 1000 internal busses. (500 stereo busses) hardware inserts - flawless AAX - has been stable - if somewhat expensive.
|
|
|
Post by nudwig on Sept 14, 2018 18:11:56 GMT -6
I'm in the process of setting myself up with a second/mobile HDX system. I'm too spoiled working with all the extra power. Mixing native I'm freezing and committing way too much during the last 10% of the mix which is frustrating to say the least.
|
|
kbj
New Member
Posts: 1
|
Post by kbj on Sept 15, 2018 14:36:45 GMT -6
I do Music and Post Production mixing. I went with HD Native. I needed Surround, wanted more that 32 I/O for occasional tracking and I Mix Hybrid so I do use a bit of analog I/O. So I have 32x32 Analog and 8x8 AES. I figured I could always grab an HDX card in the future if I wanted lower latency/DSP. I've been happy with the HD I/O quality so not dying to upgrade interfaces. PT Regular is pretty powerful these days. Most people can probably be perfectly happy non-HD, unless you specifically need some of the features.
|
|
|
Post by matt on Sept 15, 2018 14:41:24 GMT -6
I do Music and Post Production mixing. Welcome to RGO kbj!
|
|
|
Post by Ward on Sept 17, 2018 12:25:09 GMT -6
I'm running a decked out west mere Mac Pro tower and contemplating the move from HD3 to HDX like aremos alluded to and drbill states he has done already. Anyone know the ballpark cost of the upgrade with Avid?
|
|
|
Post by aremos on Sept 17, 2018 12:40:19 GMT -6
I'm running a decked out west mere Mac Pro tower and contemplating the move from HD3 to HDX like aremos alluded to and drbill states he has done already. Anyone know the ballpark cost of the upgrade with Avid? Ward, Since you were last here I "upgraded" to a 12 core/3.46Ghz/64Gb & split the SSD drive into keeping the HD3 (tracking) on Mavericks & the other ready for any of the new Natives (mixing) on Sierra.
If you're going to go HDX, there's still different UPGRADE packages where you turn in your hardware, etc.
|
|
|
Post by cowboycoalminer on Sept 18, 2018 16:53:20 GMT -6
HD or HDX? I'm keeping my HD3 Accel & am not craving for HDX, as of now. Unless someone here convinces me otherwise the only thing I might end up doing is stay tracking on existing system (PT HD 10) & maybe buy & mix in PT (Ultimate?) Native. HDX has been awesome for me. Glad I finally made the jump from HD to HDX. 96 i/o - flawless delay compensation - flawless unlimited busses - AWESOME (working on a template now that's quickly approaching 1000 internal busses. (500 stereo busses) hardware inserts - flawless AAX - has been stable - if somewhat expensive. Explain the difference between native and HDX pertaining to delay compensation. I use PT when sessions come in using PT, but the delay compensation in native sucks. That's why I prefer Cubase.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 18, 2018 17:02:58 GMT -6
HDX has been awesome for me. Glad I finally made the jump from HD to HDX. 96 i/o - flawless delay compensation - flawless unlimited busses - AWESOME (working on a template now that's quickly approaching 1000 internal busses. (500 stereo busses) hardware inserts - flawless AAX - has been stable - if somewhat expensive. Explain the difference between native and HDX pertaining to delay compensation. I use PT when sessions come in using PT, but the delay compensation in native sucks. That's why I prefer Cubase. Some of the delay compensation features are HDX only, PT native doesn't compensate for aux busses and is out of whack without plugins. There are ways around it but it can be a headache.. When I tried other DAW's like Mixcraft, Logic, Samplitude, ADC has never been an issue once setup properly. Hence I dumped PT on it's ass..
|
|
|
Post by cowboycoalminer on Sept 18, 2018 17:05:49 GMT -6
Cubase is automatic with delay compensation. For native guys like me who use a lot of hardware, it’s a must it seems. It’s sad because I do like the new PT release.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 18, 2018 17:17:45 GMT -6
Cubase is automatic with delay compensation. For native guys like me who use a lot of hardware, it’s a must it seems. It’s sad because I do like the new PT release. Most DAW's are across all channels even with HW insert pings.. It's a shame because I love PT for it's ease of use and I even like Sibelius for composing, it's not the only DAW in town though..
|
|
|
Post by matt on Sept 18, 2018 17:38:13 GMT -6
It would be nice if PT Native did automatic hardware insert delay compensation, but it doesn't. No round-trip "ping" measurement function exists so I used the "tick" click to compare timing on parallel busses, one internal, and one with each HW insert- for 16 inserts, with some through Symphony MK1, and some through Apollo Quad Silver. Yeah, my 32x32 I/O is kludged together. It's interesting to see what a HW compressor does to what is essentially a square wave. But the moment of attack is easy to see and easy to line up using HW insert manual compensation (22.58 ms on average). It was tedious and took a few hours, but it is done and now the overall compensation out to all of my HW is in phase and sample-accurate. I also use a lot of internal aux busses for reverbs, delays and such, typically in parallel, and have never noticed phasing or other issues. Maybe I'm lucky though. You never know.
|
|
|
Post by drbill on Sept 18, 2018 17:49:06 GMT -6
HDX has been awesome for me. Glad I finally made the jump from HD to HDX. 96 i/o - flawless delay compensation - flawless unlimited busses - AWESOME (working on a template now that's quickly approaching 1000 internal busses. (500 stereo busses) hardware inserts - flawless AAX - has been stable - if somewhat expensive. Explain the difference between native and HDX pertaining to delay compensation. I use PT when sessions come in using PT, but the delay compensation in native sucks. That's why I prefer Cubase. Sorry. Wish I could. I've always been on DSP PT systems, and DC has always worked well. In HDX it's extremely good. (IMO)
|
|
|
Post by drbill on Sept 18, 2018 17:50:33 GMT -6
It would be nice if PT Native did automatic hardware insert delay compensation, but it doesn't. Actually, it does. At least in HD/HDX.
|
|
|
Post by matt on Sept 18, 2018 18:03:54 GMT -6
It would be nice if PT Native did automatic hardware insert delay compensation, but it doesn't. Actually, it does. At least in HD/HDX. Yeah, that's one of the reasons I'm still considering it for next year- my 2018 budget is blown! I had to resort to calculating it as I describe for non-HD Native. It was no big deal.
|
|
|
Post by seawell on Sept 18, 2018 18:16:50 GMT -6
It would be nice if PT Native did automatic hardware insert delay compensation, but it doesn't. Actually, it does. At least in HD/HDX. Are you using one of the Avid interfaces?
|
|
|
Post by drbill on Sept 18, 2018 20:49:03 GMT -6
Yes multiple AVID HD 16x16’s - 96 i/o.
|
|
|
Post by notneeson on Sept 18, 2018 21:10:13 GMT -6
Explain the difference between native and HDX pertaining to delay compensation. I use PT when sessions come in using PT, but the delay compensation in native sucks. That's why I prefer Cubase. Sorry. Wish I could. I've always been on DSP PT systems, and DC has always worked well. In HDX it's extremely good. (IMO) I found a bug, at least I think I did, going from 12 HD Native to 10 HD ADC would turn off. Yikes, what a difference. I don't know if PT HD DC is perfect, but it sure sounds bad when you turn it off mid mix.
|
|
|
Post by adamjbrass on Sept 19, 2018 9:53:18 GMT -6
What are the PRO differences between using Native and PT HD these days? What makes you crave (or demand) HD vs. Native? When Pro Tools Ultimate Software is required;
-More than 128 tracks
-more than 128 Aux tracks -More than 1 video Track
-Surround Mixing/Panners
-Support for Icon
-advanced audio editing
-advanced automation
-advanced video editing -satellite link
-ambisonics VR support
-Atmos Workflows
-Destructive punch -Clip EFX apply, edit and play
-NEXIS support
-All plug-ins in the Avid Complete Plug-in Bundle, plus HEAT, Pro Tools | MachineControl, and Pro Tools | DigiLink I/O License
When Pro tools Ultimate Native software and hardware interfacing is required
-More than 128 tracks -more than 128 Aux tracks -More than 1 video Track -Surround Mixing/Panners -Support for Icon -advanced audio editing -advanced automation -advanced video editing -satellite link -ambisonics VR support -Atmos Workflows -Destructive punch -Clip EFX apply, edit and play -more than 32 I/O -low latency mixing
-support for Sync HD -NEXIS Support
-All plug-ins in the Avid Complete Plug-in Bundle, plus HEAT, Pro Tools | MachineControl, and Pro Tools | DigiLink I/O License
When Pro Tools HDX is needed
-More than 128 tracks
-more than 128 Aux tracks -More than 1 video Track -Surround Mixing/Panners -Support for Icon -advanced audio editing -advanced automation -advanced video editing -satellite link -ambisonics VR support -Atmos Workflows -Destructive punch -Clip EFX apply, edit and play -more than 64 I/O -more than 256 Voices
-support for Sync HD -NEXIS support
-AAX DSP plug ins -All plug-ins in the Avid Complete Plug-in Bundle, plus HEAT, Pro Tools | MachineControl, and Pro Tools | DigiLink I/O License
-Fixed Low Latency -Fixed PT DSP performance
-More Native CPU power for AAX Native
|
|
|
Post by aremos on Sept 19, 2018 10:05:20 GMT -6
Shouldn't "-AAX DSP plug ins" be listed in the other ones also?
|
|
|
Post by adamjbrass on Sept 19, 2018 10:13:44 GMT -6
Shouldn't "-AAX DSP plug ins" be listed in the other ones also? No
AAX DSP plugs only work with HDX
|
|
|
Post by nudwig on Sept 19, 2018 10:49:09 GMT -6
As part of testing the possible new setup I put the HDX card from the studio computer in a Sonnet chassis and loaded up a mix that was maxing out my laptop. Unfroze/uncommited tracks and even without changing what plugins could be changed to DSP I was easily back in business. I did manage to eventually crap it out again (2015 MBP with 4 cores and 16g RAM vs the studio 12 core 64g RAM is always going to be a disadvantage with using certain heavy load native plugs) but I was still amazed how far I could take this mobile setup. Not really excited about getting another HDX card but I do love the solid system it creates. Only ITB with native so I can't speak on the delay compensation vs HDX when using outboard, no issues with the latter.
|
|
|
Post by drbill on Sept 19, 2018 12:22:05 GMT -6
Going to 2 HDX cards REALLY helped my system out. I needed the extra i/o, but the additional power benefits really amped things up.
|
|