Badges [ 8 ] [-]
Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 91 ] [+]
Update installed, new session.
Assertion in "/Volumes/Development/212377/ProTools/App/Document/UProToolsWindowPresetMgr.cpp", line 234
XFORM is still SLOW.AS.BALLS. I'm sitting here on a 12core/3.46Ghz machine.. XForming 6 tracks that are 7 minutes long. It's taking FOREVER. What is this? EQing in Sound Tools in the early 90's?? Activity monitor is showing my system is sitting 92% idle. Aka.. Protools isn't taking advantage of the juice aka I'm sitting around WASTING time I could be doing something else. At least, lock out those track regions ...more »
Nothing drives me more insane than forgetting my stupid work ilok if i have to quickly run out somewhere with my laptop.
What would be great is if if your ilok wasn't available, at least let protools open in Protools First mode... and if you launch with the key in, it'll open as Protools or HD depending on the license.
Less, installers, less bullshnit.
I'm finding that if you have a mixer window open, and then have a bunch of floating mixer strips open - the refresh of the meters drops significantly in updating speed. It makes no difference if it's on my primary or secondary monitors, and my Graphicss card is plenty powerful (GT-980TI). Also. meter performance with NO floating meters is totally fluid, even if I have a 1080p video running on the same screen. ...more »
Just like Clip Gain and the Clip Gain line, it would be rad if the result of any clip-based effects would update the clip(s) waveform overview.
Why is the so fiddly - and why is the " db" text a part of the value on occasion? No one is ever going to type it.. it should be a part of the graphics, not the text entry.
It also is pretty dumb in how it handles typing negative numbers sometimes - ... i.e.: -6 for -6db ... but there's no consistency - sometimes it doesn't work.. or inserts it AFTER the stupid db text.
Sometimes Pro-tools isn't remembering upon reload a track's Low-latency mode setting.
For dubbing situations, this not always immediately obvious unless it's visible in the latency header of the mixer..
Can the input monitor button just turn blue instead of green? Then it's IMMEDIATELY obvious in the mixer AND edit windows.
What is up with the Video Engine?? It's an absolutely disaster. If I'm working on my HDX system, Laptop... if I go to a post facility... no matter where... there's always a situation where the Video Engine is "unable to stop".. my system.. clients systems.. 3rd party systems... It's the biggest blunder ever and is absolutely maddening and pretty embarrassing for a company that has an entire division for pro video. ...more »
My setup is a combination of HDX hardware and other MADI gear all clocked from a common source. -SYNCHD, HD MADI x 2, HD I/O -RME MADIFACE XT -RME ADI AES converter -RME ADI ADAT converter -Dangerous DAC-ST -Dangerous DAC-SR For years I've clocked everything from a Big Ben which is in my machine room with this stuff. So, on the odd occasion I want to switch sample rates, I have to go into the machine room, change ...more »
I just got this error today... except I'm running HDX3.
Why can't the error list which card has a problem??
If I changing the meter ballistics on a decent sized session (214 voices) - it takes upwards of 25 seconds to do it..
What's up with that?
System: 12core 3.46 / 128GB ram / HDX3
Video: Radeon 980TI 6GB running 4k and 2560x1080 ultrawide