Track Input Monitoring 10.3.9 HD broken ?

[WernerF]

Originally Posted by DigiTechSupt

This issue was raised with us a week ago and we are looking into it. A few questions that could help...

1. For C|24 users, does the problem occur with the control surface undeclared?
2. Any HD Native systems with this issue? (Looks like only HD/TDM after reviewing the posts.)
3. Is anyone running Pro Tools HD 10.3.9 software without HD hardware (Aggregate/ASIO4ALL)?

Thanks,
JC

Thanks for the info!

[ripple FX]

Confirming this behavior with PTHD10.3.9 (TDM hardware) OS 10.6.8 and Control24 online.

[Larold]

Same here. TDM hardware.

[Synchrosphere]

Originally Posted by DigiTechSupt

This issue was raised with us a week ago and we are looking into it. A few questions that could help...

1. For C|24 users, does the problem occur with the control surface undeclared?
2. Any HD Native systems with this issue? (Looks like only HD/TDM after reviewing the posts.)
3. Is anyone running Pro Tools HD 10.3.9 software without HD hardware (Aggregate/ASIO4ALL)?

Thanks,
JC

The same Problem, with or without C 24
TDM HD 3, OS 10.7.5

[phil2000]

Thanks for finally chiming in JC,

OS 10.8.5, HD5 (TDM) with Control 8, 192 Digital I/O & SYNC I/O here.

[sirbobnash]

I'm having the same input monitoring problem. I just upgraded to TDM HD 10.3.9 from 10.3.2 (I think it was anyways), and my input monitoring stopped working completely. I'll provide any more info that is relevant if you can think of questions, but you can all see my basic setup in my profile.

Metering/sound does nothing when input monitor activated. Meters show signal when an adjoining track is record enabled, but no signal comes through the input monitored track.

[SunsetLodge]

Same ****** problems here. OS 10.6.8, PT 10.3.9, HD Hardware. The "input" button doesn't work properly as others have posted.

This is such a load of crap. Its hard to not complain and sound like a jerk. But c'mon....

For everyone doing a clean reinstall of 10.3.8, here is a quick link to the AVID download page.
http://avid.force.com/pkb/articles/e...kbase&filter=0

[drvibb]

Yes,

As soon as I upgraded to 10.3.9 I got experienced this problem. No more going to the next version for me until I thoroughly check it out. After the past several problems that have occurred and not fixed, I don't trust Avid anymore… and it hurts me to say that!

I am a very loyal PT user. Having 10.3.9 is UNUSABLE and I have lost several days of work before finding this post. Very frustrating.

Back to 10.3.8 for me.


- Brian

[Firechild]

Originally Posted by DigiTechSupt

This issue was raised with us a week ago and we are looking into it. A few questions that could help...

1. For C|24 users, does the problem occur with the control surface undeclared?
2. Any HD Native systems with this issue? (Looks like only HD/TDM after reviewing the posts.)
3. Is anyone running Pro Tools HD 10.3.9 software without HD hardware (Aggregate/ASIO4ALL)?

Thanks,
JC

No we are all on TDM hardware, the nativeguys are of course on PT 11, no reason to stay on 10 for them.
We are your hardcore fanbase and we appreciate a lot that you are still updating our beloved PT10 HD software. However this input monitor bug is kind of nasty

[metwaystudio]

Yesterday, we went from PT8HD to PT10HD and of course the installer that came with the purchase was 10.3.9. Wow! I can't believe that this update got through the Beta testing phase!!! It took me about two minutes to find the input monitoring bug - Avid, What are you doing!?

Please don't install PTHD 10.3.9 particularly if you are installing the TDM version. If you do, there will be tears. I went down to 10.3.8 without too much grief (using the original 10.3.9 disk image to uninstall) and all seems good.

Tread carefully out there peeps!