Tag Archive for 'video'

Update on jerky video problem

Following my posts on the problems with Canopus boxes and Pro Tools 8.0.3 here, here, here and here as well as the jerky video problems I have posted on and the video compendium I posted about here and here, there has been another interesting post on the Pro Tools 8.0.3 jerky video thread on the Digidesign User Conference. ‘DigiTech Supt’ has posted….

There are several fixes in 8.0.4 and 10.6.4, but at least one outstanding issue when playing video on a 2nd monitor that appears to be OS related, which we’re working with Apple to implement a fix.
Can anyone on 8.0.4 and 10.6.4 who is seeing jerky/stuttering playback when using a Mojo or Canopus device let us know the specifics of your configuration and the size/codec being used for the video?

Also ‘Anibal’ has posted….

using Canopus, DV and different sizes, very smooth playback but eventually crashing when opening sessions with video in firewire

Video problems on Pro Tools 8.0.3 update with release of 8.0.4

Following my posts on the problems with Canopus boxes and Pro Tools 8.0.3 here, here and here as well as the jerky video problems I have posted on and the video compendium I posted about here and here, there has been another interesting post on the Pro Tools 8.0.3 Big Bug thread on the Digidesign User Conference

‘redj’ posted after the 8.0.4 release…

Thanks Avid for the update ! But thereʼs already a mistake…

For me, this bug happened by two ways :
The first one is now resolved (opening a session).
But the second one is not : when I remove video from firewire (deselect Video Out Firewire) PT crash ! But only if video track is offline. If video track is online, it works. Strange. Does anyone can confirm this bug ?

‘TommyT’ confirmed it…

Damn,,, you’re right, Bug confirmed here…
Guess we should change the Thread name to 8.03 Big Bug & 8.04 Smaller Bug :) ….

DigiTechSupt officially confirmed the ‘small bug’ and the work round…

Ok, thanks for the report – we’ve been able to repro this and are looking into a fix. Not sure whose end it’s on yet – us or Apple, but we should be able to determine that shortly and I’ll reply when I know more. For now make sure to keep the video online when enabling/disabling video out FireWire (stating the obvious, yes..!).
Avid Audio Tech Support

Problem with BlackMagic Intesity and ProTools 8.0.1 LE

‘CEM3387′ asked recently on the Digidesign User Conference about a problem with BlackMagic Intesity and ProTools 8.0.1 LE…..

Whatever codec and resolution, data rate I have tried on the B.M. Intencity card it looks totally terrible when I play the video files back in ProTools thourgh the B.M HDMI out, the files are so pixelated and harsh.
If I play the same files in their own Media Express software it looks decent not good. Better resolution but still harsh.
What kind of codecs do you guys run?
Is there any adjustments I can do apart from the ProTools menu for quick time which does not affect the quality at all at this stage.
It looks like a very low rate QT file for a Cellphone played at 1920 x1080.
MacPro 8core 3.0GHz, 6GB RAM, 10.5.8 ProTools LE 8.0.1 QT 7.6.6 Black Magic 3.6.1

‘JeromeOD’ replied…

I use prores with the same kit and software as you and all is great. I’m not certain about the quicktime version though, is that definitely what it should be?

Gary Nattrass added…

I am running virtually the same system but with QT V10.
Like Jerome Pro res full HD files are no problem.
Have a look at the BM card settings in system preferences there may be something adrift there.

CEM3387 responded…

Thanks for the replies. First of all it the harshness was a “AV MODE” setting on the display I am running. As soon I found that bastard and disable it, it looks more natural. “I am running virtually the same system but with QT V10″
Do you run OS 10.6.x or 10.5.8? “Like Jerome Pro res full HD files are no problem.” OK I´ll see if they can prep that for me. What version HQ, regular or LT? “Have a look at the BM card settings in system preferences there may be something adrift there.” I un-checked the “Remove field jitter when video is paused” that was recomended somewhere else. Other that that I do not know what could affect output. Output is set to HDMI NTSC/PAL and output processing it Off.
Also I cannot get the display the whole picture frame regardless of setting on the monitor setting. The monitor is native 1920×1080 and I have tried with movies at native 1920×1080 and still the picture is a bit cropped.

‘Newpostguy’ suggested…

Open quicktime pro and convert it. You dont wait for picture department that way and dont look like “oops I forgot I can only run this type of codec” guy.

Convert to apple pro res 442 (mpeg streamclip or QTsync will do this for free almost as good)
Make sure the video is 720p or 1080i if HD (BMI does not do 1080p)
It would be wise to learn about various codecs and why they are used at different times.

CEM3387 replied…

“Newpostguy” THANKS! Im am now tempted to change the the subject of this post to “NO Problem with BlackMagic Intesity and ProTools 8.0.1 LE” Mpeg Streamclip For the win! It can batch convert too!
“Make sure the video is 720p or 1080i if HD” (BMI does not do 1080p)
Ahhh, did not know that I love progressive so 720p it is then.
Thanks a lot for solving my problems!

More on video problems with Pro Tools 8.0.3 – possible work round

Following my posts on the problems with Canopus boxes and Pro Tools 8.0.3 here, here and here as well as the jerky video problems I have posted on and the video compendium I posted about here and here, there has been another interesting post on the Pro Tools 8.0.3 Big Bug thread on the Digidesign User Conference.  ‘zoing123′ has posted….

Gentlemen. Fear Not. It _is_ a known BUG. The work around is to take the video to internal before closing. I went nuts figuring this out, but thats it. Spoke to a real Digi teck and they are working to fix this. I have been flawless after I found this.
8.02cs2 /10.6.3 on an  002 box.

So hopefully this will provide folk with a viable work round until Digidesign can fix it.

The best way to export/bounce to movie

Ian Palmer asked about this on the Digidesign User Conference recently. He asked…

I’ve been exporting mixes for review as a QT for years now. We’ve just upgraded my mix studio to PT8 HD.
Before you would export the QT, set the audio settings and it would stitch the audio onto whichever QT was online in the session. Easy and quick.
Now it’s taking a bloody age as PT is re-encoding the H264 QT into another H264 QT instead of simply copying it. Am I missing something here? The new options window is identical to QTPro (which I have QTPro7 installed).
I’m not using the H264 QT in my session, other than to export to as it’s then uploaded via FTP. Can’t be doing that with a 5Gb DVPAL version.

‘FajitaTone’ replied suggesting the flowing alternative workflow….

  1. bounce to .wav
  2. close Pro Tools Session
  3. open QuickTime with QT Pro
  4. open .wav with QuickTime
  5. select all, and copy to clipboard (from the .wav file)
  6. switch to movie, type (cmd-J) to open the movie properties window
  7. select the audio track and delete it.
  8. then press opt-cmd-V to past the bounced .wav into the movie
  9. cmd-shift-S to save as self contained.
  10. this will save the QT you used in your PT session with bounced audio from the session. Bounce to QuickTime takes too long.
    I hope that was clear.

Audio_Vision added…

+1 to the method explained above. Fast and easy. Only issue is when picture has a leader or slate. I usually trim the picture first so the FFOA is the same for picture and exported/bounced .wav files.

‘nucelar’ responded…

Hmm, in my case bounce to QuickTime takes just as long as bounce to wav, real time that is. It just replaces the audio in the movie without reencoding.
UNLESS you choose Bounce to QuickTime with cmd-alt-ctrl pressed. Then you can specify the codec.
Fajita’s workflow is also very useful, specially when you only need to consolidate rather than bounce. The only thing I may add is that you must make sure that the consolidated or bounced audio is the exact same length as the movie, or at least starts at the same point.

mikevarela added…

Yes, bounce to QT is a BOUNCE (real time), benefits of course are that the audio chain runs through your automation and plug-ins. But, if you’ve already bounced the audio, then the tip above will work fine. Keep in mind though that it’s not always sync accurate, as you’re matching audio to video via command, not by eyes. If the video AND audio are EXACT same length, then you’re good.
(read).. there is also a way to nudge audio in the tip above, but it’s not as easy and accurate as in PT

More on video problems with Pro Tools 8.0.3

Following my posts on the problems with Canopus boxes and Pro Tools 8.0.3 here, here and here as well as the jerky video problems I have posted on and the video compendium I posted about here and here, there has been a couple of interesting posts on the Pro Tools 8.0.3 Big Bug thread on the Digidesign User Conference. Matt Faddy posted….

I know this won’t help your immediate problems but we were using the ADVC 100 and 110 ‘s for years and always had constant issues with them (I have 8 broken ones stacked up in our machine room) – They were unbelievably temperamental and over the years I have grown to despise them but unfortunately they were always a necessary evil. We switched to Black magic intensity pro pci cards a few months ago and they are brilliant. Rock solid, support a few formats and have HDMI as well as component and composite O/P’s – the best thing about them though is they are even cheaper than Canopus ADVC 110′s ! The only drawback is they use an extra slot so if you’re running an HD3 system you’ll need an expansion chassis.

and ‘filmsdunjour’ responded…

Attention PAL users.  I’ve posted a thread here. The Blackmagic cards have a major problem in SD PAL (haven’t tested SD NTSC but I guess it’s working fine, 1080i50 is perfect) using ProTools HD 8.0.3cs(1&2) on Mac OS X.5.8, even with the latest Blackmagic drivers.
Image quality is terrible (jerky and aliased) on both HDMI and SD analog outputs. The outputs are perfect on Final Cut Pro, so it’s a software issue.
I think it’s related to the way Pro-Tools automatically sets-up the output’s resolution. Final Cut Pro works fine because the set-up is manual (you have to change it when going from SD-HD-PAL-NTSC)
Sadly the ADVC110 is the only option (don’t know about mojo) to have a “nice” image in SD PAL…

Clearly this problem still has some mileage to run before it is resolved!

Pro Tools Video Output Options Compendium – Update

There have been a number of additional posts on this thread on the Digidesign User Conference since I posted the main findings here. But this one caught my eye as being in the same vain as the first. There had been some discussion on whether a USB to VGA adaptor might work so ‘Mubeau’ tried it and posted his findings…

I´m on G5, HD3, 2PTs screens, PT 7.4, VVTR and Canopus (on the PT mac and on the VVTR System, depending on the project)

Today i tried a USB to VGA/HDMI external video solutions.
(displaylink). Results:

1. I would not use this for video playback
(even SD has no good playback)
2. it was usable for the PT Mixer or HD content or something similar.
BUT: it also eats up power from the CPU, of course.

WHAT TO DO NOW?:
I have to upgrade my MAC since the G5 dual 2,5Ghz  is getting to slow for me.

HD 3 accel with decklink (my favorite setup) means: PCIe expansion (I really dont want this!) I would also love to use a third video monitor.

Having said this: has anyone of you tried the new 3 x PCIe Expansion Box

I would be very surprised if this expansion bow would work with Pro tools. How many times have we been here before?  Anyone up for an experiment?

Adobe Premiere Transfer – Current Experience?

There is a very interesting, all be it, specialist thread on the Digidesign User Conference about getting audio out of Adobe Priemere Pro into Pro Tools. ‘jeremiahmoore’ asked……

I’m getting ready to start a documentary mix for a project that was cut in Adobe Premiere. (at 25fps, but that’s another matter.) There are mixed messages out there about whether OMF or AAF transfer works. For instance here.
So I’ve contacted the editor and am arranging some tests. I’ve no idea what version they’re on – and I see a new one (cs4/4.2.1) is out since 12/8/09. Does anyone have any recent wisdom or experience to share on this matter?

‘Craig F’ responded with this excellent workflow…

This is what we have our animation department do:

Export an OMF file for Pro Tools
1. In a Timeline panel, select a sequence.
2. Select File > Export > Export To OMF.
3. In the OMF Export Settings dialog box, type a title for the OMF file into the OMF Title field.
4. From the Sample Rate and Bits Per Sample menus, choose the settings needed for your sequence.
5. From the Files menu, choose one of the following:
Encapsulate
With this setting, Adobe Premiere Pro exports an OMF file containing the project metadata and all the audio for the selected sequence. Encapsulated OMF files typically are large.
Separate Audio
With this setting, Adobe Premiere Pro exports individual mono AIF files into an _omfiMediaFiles folder. The folder name contains the OMF filename. Using AIF files assures maximum compatibility with legacy audio systems.

Selecting the Separate Audio option in the OMF Export Settings dialog box

6. From the Render menu, choose one of the following:
Copy Complete Audio Files
With this setting, Adobe Premiere Pro exports audio for the entirety of each clip used in the sequence, no matter how many times the clip is used nor how many parts of the clip are used.
Trim Audio Files
With this setting, Adobe Premiere Pro exports only the portions of each clip that are used in the sequence: the clip instances. You can choose to export each clip instance with extra length, handles, added to the start and end of the file.
7. In the Handle Frames field, specify the length of the handles, in video frames. This amount of time is added to the start and end of the exported files when you choose Consolidate Media. The default setting is one second, in frames, at the sequence frame rate. If the length of the handles you specify exceeds the length of the clip instance, Adobe Premiere Pro exports the whole clip instance.
8. Launch Pro Tools, and import the OMF file. For more information on importing files into Pro Tools, see Pro Tools Help.

Tips for importing OMF files into Pro Tools
In the DigiTranslator dialog box:
• Deselect Pan Odd Tracks Left/Even Tracks Right.
• For automatic gain control, select Convert Clip Based Gain To Automation.
• Leave Sample Rate Conversion deselected, unless you need sample rate conversion.
In the Missing Files dialog box:
• Change the default setting to Manually Find And Relink, and press OK.
• Deselect all options.
• Navigate to the <projectName> ExternalMediaFiles folder and select it.

‘jeremiahmoore’ replied…

Just experienced a successful test transferring from Premiere Pro CS4 into Pro Tools using OMF. The key was to use OMF (not AAF) and External Media (not embedded).

Premiere Pro settings used:
Exported from Adobe Premiere Pro CS4 v4.2.1
OMF Title: prem-test3
Sample Rate: 48000
Bits per Sample: 16
Files: separate audio
Render: trim audio files
Handle Frames: 150
Successfully transferred:
- audio media with edits and handles
- crossfades were recreated by pro tools
- volume automation intact
Relink Note:
- Files did not autolink successfully. Instead, “Relink Offline” was used from PT’s Project Browser. I had to search for matches using “Filename Only” and Deselect “Duration” (or whatever it’s called, I’m not in front of the dialog box as I type this.)
Other Notes:
- PT crashed importing AAF. Soundtrack pro failed to import AAF as well.
- OMF with embedded media: region definitions came in, but media could not be linked. (PT could apparently not see the media inside the Premiere Pro OMF.)
We shall see in a few days if the whole hour-long project comes across successfully.

‘lode’ added….

Sounds encouraging. When I read the headline for this post before opening the thread I had already decided to answer that you should run as fast as you can in the opposite direction. We spent a week on importing a session from Premiere. You can find how we solved it here. This sounds like you are on the right track though. Good luck.

However it wasn’t the final answer ‘jeremiahmoore’ replied…..

I was just informed that the editor was unable to EXPORT the OMF from Premiere once they had the full project loaded. If anything develops worth sharing, I will post it here.

‘philiper’ asked….

2Gb file limit?

‘jeremiahmoore’ replied…..

Hi Phil – Maybe it was the 2GB thing, hard to say. I may give the editor a call and see if I can learn more.

Then ‘JWalkerPostAudio’ chipped in….

You may be experiencing difficulties because of the format your media is in. Last year I worked on a project with the same problem, and the media was all MXF. If I remember correctly, since the audio clips in the timeline were attached to the MXF and only referencing the audio, the OMF would not be correctly translated. What the editor had to do was go through every individual audio region on the timeline, manually pull out handles, then “render and replace” the audio to .wav or .aiff, then cut the handles off before the OMF could be correctly translated. A real major PITA. It took a couple months before we were able to do enough research/trial and error/work to get the OMF out. It might take your guy a week or two from here to do all the “render and replace” that needs to be done before the OMF can be made. Good luck and stay away from Adobe!

Noiz2 added…

A few years back I went through hell getting a project from PP into a usable OMF (they ended up going through Avid to do it). So the other week at the FCPU Super-meet in SF I talked to the presenter for Adobe about exactly this work flow. He admitted there were still some issues but that they have been working pretty hard at getting the back and forth with ProTools especially but also with Avid working smoothly. A few years ago it just wasn’t possible so that it works at all backs this up a bit. If they get this working that would be very good because I suspect we are going to start seeing a lot more PP projects. They have really improved the whole suite of apps and I can see it getting a decent piece of the FCP market.

Well it certainly seems to be how an easy process and not to be taken on lightly.

Pro Tools Video Output Options Compendium

This is a reproduction of the first post of a thread on the Digidesign User Conference by the user “Nucelar” who decided to create a thread and outline the options, pros, cons, and costs of all the different options for displaying video with Pro Tools.

Pro Tools video Output options:

1. QuickTime to desktop monitor (1st or 2nd monitor port, with or without DVI-video adapter)
System requirements:
Any Mac or PC with a secondary DVI or equivalent monitor output
PROS: Cheapest solution. Low latency. Good quality when DVI or VGA is used. Handles most codecs Quicktime can play back.
CONS: You only have one monitor left for Pro Tools. Uses CPU for video decoding, thus less power available for other tasks (such as RTAS). Output only. Does not output a native video signal: may cause visible tearing due to refresh rate not equal to frame rate.
PRICE: Adapter 19 US$ from Apple + cable
for example here & here
Note: If you’re on a Mac Pro or G5, you could use a Matrox DualHead2Go on your primary DVI output to connect one more monitor, but it’s not approved by Digidesign.

2. Canopus converter (ADVC110 is the most popular and approved by Digidesign)
System requirements:
Any Mac with Firewire port (Firewire 400). FW 800 to FW 400 adapter cable may be needed. Should be used in a dedicated Firewire 400 bus, not in the same bus as interfaces or audio hard disks.
PROS: Cheap hardware. Controlled latency (about 18 quarter frames) . Captures SD analog video in DV format as a bonus (using third party application). Frees CPU from video decoding.
CONS: Mac only. Video must be available in DV format. SD only. Composite or S-Video output only. Irregular and unpredictable sync
PRICE: about 200 US$
WEB: ADVC family

3. Avid MOJO SDI
System requirements:
Any Mac or PC with Firewire port (Firewire 400). FW 800 to FW 400 adapter cable may be needed. Must be used in a dedicated Firewire 400 bus, not in the same bus as interfaces or audio hard disks.
PROS: Direct Compatibility with Avid video files (MXF). No latency with avid video. Captures video directly into Pro Tools session in sync. Frees CPU from video decoding.
CONS: Quite Expensive. SD only. Struggles with codecs other than Avid’s.
PRICE: 2500 US$
WEB: Avid Mojo SDI

4. Digidesign Video Satellite LE
System Requirements:
Main system must be Pro Tools HD. Needs a second computer dedicated exclusively to video output. Connects to the main PT system via Ethernet.
Secondary computer could be a Mac Mini, but then you’re stuck with the drawbacks of desktop video quality. For best performance, secondary computer should be a Mac Pro with a Decklink HD card. (see Post #2)
PROS: Dedicated, stable, scalable and flexible solution from Digidesign. Frees main CPU from video decoding.
CONS: Relatively Expensive, hassle of second computer
PRICE: Mac Mini+ Mbox micro + Video Satellite = aprox. 1200 US$
PRICE: Mac Pro + Decklink HD +Mbox Micro+ Video Satellite = aprox. 4200 US$
WEB: More info on the Video Satellite LE

5. Avid Video Satellite
WEB: More info on the Video Satellite

6. Chase video deck
System requirements:
Pro Tools System with Machine Control ability and of course a pro video deck.
PROS: You can use professional deck for direct playback and layback. No capture or conversion needed.
CONS: Very specific workflows. Tape-based, linear. Additional wear of deck heads. Downside when editing: forward-selecting to picture is not possible because PT only outputs positional info when selecting backwards.
PRICE: You don’t want to know the price of a digibeta deck.
Notes:The Rosendahl Bonsai Drive can be used as a standalone non-linear VTR, eliminating the drawbacks of tape-based decks. SD only.

7. Blackmagic PCI Card
System Requirements:
Any Mac Pro with a free PCI-e slot
PROS: Very good price/performance. Digi approved solution. Accepts all Quicktime-playable codecs. Very good video quality. Controlled latency.
CONS: It uses CPU Power for video decoding. Does not capture into Pro Tools or handle Avid video, unlike Mojo.
PRICE RANGE: from 200 US$ (Intensity) to 1000US$ (Decklink HD Extreme)
WEB: More info the Blackmagic web site

8.Virtual VTR
Third party software installed on a secondary Macintosh computer for dedicated video playback and recording.”Can be externally controlled via Midi, Sony 9-Pin protocols or TCP/IP, and can also synchronise playback, chasing timecode, even in multi-channel configurations.”
PROS: Basically the same as Video Satellite LE
CONS: Basically the same as Video Satellite LE, Mac Only
PRICE: Software is around 1000 US$
WEB: More info on Gallery web site

“Nucelar” has done an excellent job in producing this compendium and it provides an excellent resource to help all those who need to display video within Pro Tools sessions to choose the option that suits them best. I have gone for a Canopus ADVC 110.

What is the best QuickTime codecfor working with Pro Tools

Recently there have been two threads on the Digidesign User Conference on this subject.

One asking about the best codec to put the least strain on the host CPU

usastra asks

I have a session for a live concert with a quicktime movie using the H264 codec. When the movie is online it crashes very often, especially if I set the cursor to a new place in the timeline.
If the movie is offline PT is way more stable (though still with the occasional crash)..
I was wondering if the session could be made more stable if I render the movie with a different codec and which codec would be best so I would have the least CPU strain?

The other commenting on the load playing an mp4 file has on the host CPU.

Roger Stauss asked…

I’ve been using an Mp4 vid to ease the up/download time. The PT session runs with some latency. It’s very smooth with a QT DV. Is there a way to smooth out the session operation? (I run Video on separate drive)

I have compiled the best responses from both threads below…

Chief Technician advised simply…

Use the DV codec.

c.evans agreed…

Agreed. The DV codec works well on my system, but what really helped is adding the Canopus ADVC 110 and sending my video out to an external monitor. Also, it is very important that your video is playing from a separate drive than your audio. I even use the internal SATA buss for my video when using firewire for video. It also helps to have a third party PCI firewire card to add some beef and options to your system.

Craig F chipped in…

mp4 is a intraframe codec same as h264 hence heavy CPU usage.

José Luis Díaz explained…

Always choose intraframe codecs (DV, Motion JPEG-A, Photo JPEG, etc).
Always avoid interframe codecs (H264, Sorenson, etc).
Interframes codecs demand much more brute force from CPU than intraframe codecs.
Intraframe codecs only compress the data of one frame regardless any adjacent frame.
But to decode a simple interframe stream of frames (like H264) the CPU of your computer will dedicate a lot of its cycles just for that simple moving image because it must to compute differences and similarities between frames.
Check all this with Activity Monitor App.
Play a PT session with an interframe movie. Them the same with a intraframe movie.

Jon_Atkinson added….

Digidesign Technical Support have gone on record here a few times saying that H264 has been the root of many PT related QT problems. “A can of worms” was, I believe, the phrase used….

usastra responded…

Thanks for all the replies! For now, I have converted the videos to mjpegB and the session runs much smoother! I will experiment with other codec later.

philip888 asked….

What are you using to convert with?

usastra replied….

Quicktime Pro

Rick Sanchez confirmed….

A couple of solutions I found that worked well for me.

1. Once you’ve downloaded the video, use Quicktime Pro to transcode it to DV. If you have a fast computer, it’s pretty quick to do. Usually much quicker than the download time.

2. Tell the editors to send you Motion JPEG A video instead of MP4/H.264. It’s still very small and plays well with ProTools.

One of the falsehoods about H.264 is that it is not a frame accurate format. This is not really the case. It can have a variable frame rate, but that is a setting when you do the original encode/capture. What it is, is a long GOP (Group of Pictures) format. Much like Mpeg2. In the first frame, all of the pixels are captured. In between the first (key) frame the next (user selectable) key frame, the computer looks for differences between the the Key frame and the next frame and only encodes anything that has changed. If the pixels (say a non-moving background) stay the same from frame to frame, it just fills in the blank with already captured pixels. Then when the next Keyframe comes around again (I think the default is 24) it captures all of the pixels and starts over. It’s much like creating an audio ambiance fill track for a scene. You only need a few seconds of fill and then you loop it until there is the next change in ambiance.

I take no credit to the advice I have quoted here but do confirm it from my own experience.



About Me

You are currently browsing the Pro Tools for Media weblog archives for 'video' tag.

Donate

If you have found something useful here, please consider having a donation so I can keep this going. Thanks.

Pro Tools For Media Archives

  • 2010 (118)
  • 2009 (264)

Groove 3 advert

Flux Advert

MacProVideo advert

For UK readers

For US Readers