So just to update this thread, we still have not found a solution to our problem. I'm now pursuing something I found with the temporary files avid creates when a user saves a bin... These are the .wrt files. On the systems that have slow save times, I'm able to see the .wrt files be created in the respective directories next to the bin that

Yes. We have tried new users, deleting avid settings, bin settings, all that :( On trying to track down any sort of information I came upon the filed labeled "AvidBinIndexer_log" in the error reports directory in the public documents on the computer. This seems to log save activity as you do it. On the systems that work fine we see this (bold

Hi all, We just has 6 new installs of Media Composer/Symphony 6.5 at our business (Avid certified HP z820's). Everything seems great, but we have had a weird issue. 3 of our machines seem to take a really long time to save even a single bin with a single sequence in it. 3 machines will save the bin in about 2-3 seconds, the other 3 machines take

I don't know if this is mainly the gamma issue that was mentioned before. I also cut on Media Composer on a windows system and I had a lot of trouble with levels before I understood how Avid works. Here is what I know that I think fits your case... In the Avid program, video is displayed differently than how Final Cut, Premiere, Media Player, Quicktime

I really really hope Intel doesn't keep with this "cloud" moniker... this will make me believe they WANT people to be totally confused (in this case with 'cloud computing,' the idea of your operating system coming downline from the internet).

[quote user="alleycat"]should use the DNxHD codec to export out from Avid,[/quote] Yes [quote user="alleycat"] as well as out from AE to bring that back into Avid if need be, to have the least amount of quality loss, right? There's no other way to go about it if I understand correctly...[/quote] Yes, this is what I do. You want

[quote user="cls105"]I have a 7d, should one import these as RGB or 601? how about fields? just want to double check, thx -c[/quote] As far as I know it should be RGB, since the pixel values in the h.264 range from 0 to 255. The MKII only shoots 30p at the moment (firmware update pending)... and at least for that, the original is progressive

[quote user="alleycat"]Now, question is, what would be my advantages to import back into Avid? [/quote] You don't have to go back to Avid if you don't need to (like if you just need a digital file as final output). But let's say you need to go back and lay down a master to tape... that would be best done in Avid. [quote user="alleycat"

My workflow is to import the MKII files into Avid as either DNxHD 145 or 220 depending on the project (really 145 is probably fine since the h.264 codec is so crunched anyway). Edit in Avid. Either spit out a DNxHD quicktime file (i'm not all that found of Ref. files if I can help it) or an AAF for use with Automatic Duck (again, depending on the

If you have the storage space, I would recommend keeping the files HD. Personally, I feel I get a better transcode to mpeg at the end of the process with HD material. Plus, if you know you are going to SD, you are able to zoom-in and reframe shots if necessary, or even stabalize shots without having to resize the image over 100%.