Can I trade in the 12.7 "loops" for a video engine fix?

[TVPostSound]

Title says it all.
Still an issue.

[TrentWilliams]

I've never had any video engine issues, well none that I haven't been able to fix.

Please explain what you're having problems with.

[mik]

Originally Posted by Trent W.

I've never had any video engine issues, well none that I haven't been able to fix.

Please explain what you're having problems with.

well...
http://duc.avid.com/showthread.php?t=385127
http://duc.avid.com/showthread.php?t=379507

you're lucky !

[TVPostSound]

Originally Posted by Trent W.

I've never had any video engine issues, well none that I haven't been able to fix.

Please explain what you're having problems with.

Please, just because you don't, doesn't mean you have the answer.

There are many with video engine issues.

Ive been in constant dialogue, logging crashes with Avid since last April, mine is due to Protools having two separate video engines, one for internal video, and one for remote Media Composer Video Satellite.

[MusoPro]

Originally Posted by Trent W.

I've never had any video engine issues, well none that I haven't been able to fix.



Please explain what you're having problems with.

Wow, you must be in an alternate universe where the video engine works. Seriously I find that amazing. A day doesn't go by over here without a problem. Usually disabling and enabling works. But I've been in sessions with clients where it just stops working and I need to restart PT entirely...


Sent from my iPhone using Tapatalk

[tom_lowe]

Originally Posted by MusoPro

Wow, you must be in an alternate universe where the video engine works. Seriously I find that amazing. A day doesn't go by over here without a problem. Usually disabling and enabling works. But I've been in sessions with clients where it just stops working and I need to restart PT entirely...


Sent from my iPhone using Tapatalk

Had the odd issue, but generally all is fine. Use VideoSlave 3 anyway as much better with BM hardware, but AVE hasn't been awful.

[TVPostSound]

Originally Posted by tom_lowe

Had the odd issue, but generally all is fine. Use VideoSlave 3 anyway as much better with BM hardware, but AVE hasn't been awful.

If you have no video engine issues, then why are you using VideoSlave.

OH, thats why you have no AVE issues, you don't use it!!!

[tom_lowe]

Originally Posted by TVPostSound

If you have no video engine issues, then why are you using VideoSlave.

OH, thats why you have no AVE issues, you don't use it!!!

Ha, funny.


No, I did use AVE for ages, I just find AVE is more taxing on CPU than VideoSlave and I like the fact VideoSlave can overlay timecode instead of having to burn it in for AVE myself.

I had issues with BM hardware and AVE in PT11 but since 12 (I went straight to 12.3) it's been fine.

I don't think AVE is perfect and Avid certainly could learn lots from VideoSlave, but AVE is by no means unusable.

[TVPostSound]

Originally Posted by tom_lowe

Ha, funny.


No, I did use AVE for ages, I just find AVE is more taxing on CPU than VideoSlave and I like the fact VideoSlave can overlay timecode instead of having to burn it in for AVE myself.

I had issues with BM hardware and AVE in PT11 but since 12 (I went straight to 12.3) it's been fine.

I don't think AVE is perfect and Avid certainly could learn lots from VideoSlave, but AVE is by no means unusable.

One AVE by itself might be fine, but I use a remote Media Composer via Video Satellite, and that instills 2 separate AVEs.
One for internal, and one for VS.
They don't play well together.