John Pale
Forum Replies Created
-
This might not be practical in your case…
Make a copy of the sequence.
Create a new 59.94 project.
Open the bin that contains the sequence copy in the 59.94 project. Avid will add motion adapters to the sequence to convert it to 59.94. It will play properly on both monitors, but you will be editing in 59.94, which might not be what you want.
-
I have done the 64 bit hack and it works fine. Perfectly stable.
You are using an alternate boot loader for your computer that would normally be used for Hackintoshes. You are essentially turning your genuine Mac into a Hackintosh.There is nothing about the 2006/7 Mac Pro that can’t handle 64 bit operation except That Apple uses an EFI chip to limit Mac OSX to Macs…the chip used in the early Mac Pros can only hold 32 bit code. The rest of the computer is not a whole lot different than later Mac Pros…Xeon processors , fast ram..etc.
Just because it worked for me doesn’t mean it will work for you. There are a lot of variables…and there are only a few hundred people on the planet that have even tried it. Most of them like me and the guy who wrote the blog I link to, learned how to do it via the netkas.org website. I did it as a project to see if I could. The machine I hacked is not my primary source of income.
If you have DX hardware and absolutely need a stable system to make money on, I would stick with Avid 5.x .
Blackmagic quirks….sluggishness in trimming in the trim window, , video unstable when trimming with caps lock audio scrubbing on, no universal mastering. Perfectly usable, but not as good as DX hardware.
-
If it will function with the latest Blackmagic driver, it will work.
I have the Decklink Studio and it works, apart from the kinks that apply to all Blackmagic hardware.
It is possible to hack your 1,1 to boot the 64 bit kernel, but I would only recommend it only if you are very advanced at tinkering. If you do it wrong, you can render your computer unbootable. The hack does work (I’ve done it), and it should allow you to run the kernel extension that will let your DX hardware to work.
https://www.jabbawok.net/?p=47
Honestly, I would stick with symphony 5.5 and run a stable system on the 32 bit kernel…DX hardware is superior to anything by Blackmagic.
-
Quicktime from Avid, DNXHD 1080i/59.94 220 10 bit, interlaced lower field, 29.97″
This is incorrect. All HD interlaced is Upper field first,
This would cause jaggies
-
I live in zone A, right on the East River. We evacuated. This is a pic taken by someone who stayed. This is the boardwalk and playground where my daughter goes to daily.
The waters have receded and we are back home already. My building was miraculously undamaged. Nobody was injured.
-
Not really finding much around the web on this which is surprising, so am i doing something wrong?
Yes. You are not using your help menu which has extensive step by step instructions on how to create multicam group clips.
I know it’s not polite to tell you to RTFM, but really it is the best resource. All I would be doing is cutting and pasting,directions from there
-
Before you give up on QTChange, you should e-mail the author, Bouke, who is very responsive.
The program works well, although the interface is a bit daunting. Its possible that there is some pilot error going on here.
-
They are always yellow in the version of avid software you are using.
Starting with MC6 your AMA clips willl be signified by a new icon…and not colored yellow.
-
Had a major problem with this on MC 5.03 last year.
Realized certain codecs would not transcode in a mixed timeline.
Basically, using “Show Reference Clips” I was able to identify the clips that were not transcoded and did them one by one. Something tar should have been way became an all nighter.
-
Sorry. I did not give a great answer there. I should have read your post more thoroughly.
I should add, I have seen this issue on eSATA, on Windows. Wasn’t a big deal, as it was not a huge amount of footage relinking. Not seen this on my personal system, which is Mac.
Are you Mac or Windows?
