Avid will fully support ProHD at DVinfo.net

Tim Dashwood · April 18th, 2008, 02:52 PM

I was looking through my NAB notes and realized that no one noticed this pretty big bit of news.

Here's the JVC press release: http://pro.jvc.com/pro/pr/2008/nab/avid.html

I was seated at the same table as a couple of Avid/Digidesign guys during the JVC press event and they told me that it all seems to work well together in the new version. ETA is sometime in the summer (from memory not notes, so please don't quote me on that.)

Carl Hicks · April 18th, 2008, 08:32 PM

It was very exciting to have an Avid system in our NAB booth, working at all frame rates over firewire, from tape or DRHD100 drive.

Steve Mullen · April 19th, 2008, 02:36 AM

It will be in V3.0 of Media Composer -- the one that will run on 10.5. Due in June 2008.

Now here's a worry I have. This will not be a point release meaning it's not an "update." It's an "upgrade" which will cost $$$.

Frankly, this update to the HDV codec is so small and soooo late, that it really should be a separate download.

Avid will no doubt claim they just don't have time to check the codec with "old" systems. While this is true -- it's true only because they waited almost 3 years to modify the codec. It certainly could and should have been a year ago.

Somehow pressure needs to be applied to Avid to make the codec a simple download to V2.x users.

Peter Moretti · April 19th, 2008, 02:44 AM

Where the heck is 24F support from Avid, is what I'd like them to answer.

Gary Bettan · April 19th, 2008, 07:50 AM

Steve,

Depending on when you purchased MC, the upgrade to 3.0 will have a reasonable upgrade cost. Avid hasn't named the grandfather date, but typically it's from the time of anounce minus 30 or 60 days. So folks who purchased recently have a good shot at the upgrade being a free download (or nominal cast with docs).

As for longer owners of the software, I think that while the upgrade will have some cost, it will be significantly below the current $495 upgrade to MC for X Pro owners which will run at least into the summer. So my guess would be in the $300 range.

This is not for certain, just based on my conversations at NAB.

As for MC 3.0, you will be getting far more then just JVC Pro HD support. The demonstrations at NAB were very impressive. The software becomes multi-threaded and GPU aware. This means it will farm our tasks to all cores and the GPU itself, giving you a big boost in performance and handling - especially with HD footage. It will have both Leopard and Vista support. It will even run under Vista 64, not as a native 64 bit app, but it will let you access huge amounts of RAM.

They've also added some nice user features such as the ability to move stacks of clips together. The responsiveness of the timeline and keyboard controlls are tight.

All MC owners will find the next version a must have upgrade.

Gary

Liam Hall · April 19th, 2008, 03:43 PM

Quote:

Originally Posted by Carl Hicks

It was very exciting to have an Avid system in our NAB booth, working at all frame rates over firewire, from tape or DRHD100 drive.

It would have been exciting three years ago.

Given the hoops we've had to jump through to get this camera working in a professional work-flow I find it quite disingenuous that Avid and JVC should choose now to have this love-in. The party's over, it finished a long time ago and no exclamations of "excitement" will make me think otherwise.

David Parks · April 19th, 2008, 06:29 PM

Better late than never I say. I've vented, shown frustration, and been completey hacked off at Avid. But now that's over.

I'm glad I held on to my HD 100a. I've been through a lot with that camera over the last 2+ years. Funky Avid nonworking workflows, forcing me to learn FCP (which had it benefits), Avid Liquid for 24p and figuring out the funky 720/30p to 30i/1080i open bin dance in Xpress. Dead pixel issues which were fixed by JVC in a very customer oriented way. And so on. But that's in the past.

I just got back from shooting with it today and it stills looks good. I've been shooting some with a Canon XHA1 with my NASA client (their camera not mine) and while it looks very sharp, I really find my JVC looking still more filmic with better color rendition.

Finally, I can edit HDV 24p in Media Composer with my ole camera. Several times I thought about selling my 100a but now I'm glad I didn't.

June can't get here fast enough.

Cheers.

Taylor Brush · July 13th, 2008, 09:03 AM

Anyone else furious about the fact that Avid only supports the 250 camera in Media Composer 3.0? Once again, they have not followed through with promises. Doesn't it worry JVC that their camera has been left in the dust again and again by Avid? I feel totally ignored by the arrogance of a company who deems my camera as a low priority for them. They're shooting major motion pictures with this thing, isn't that enough for them?

Does anyone have any insider info about whether they are done with this 100 and 200 camera's or if they have plans to finally come through with support it in the very near future?

David Parks · July 13th, 2008, 10:50 AM

What do you mean Avid MC 3 only supports JVC HD 250? It supports the 100, 110, and 200 as well as 250. It has supported 30p for some time now.

Are you referring to HDSDI injest vs firewire? I've tested 24p and 30p via 1394 with my JVC 100a and had no issues whatsoever. It works great. And if your saying the 250 works then I'm assuming that 60p works.

As far i as can tell, it supports 24p, 30p, and 60p. Before 3.0 you could only do direct firewire digitize of 30p.

Where are you getting this info???

Bill Ravens · July 13th, 2008, 11:25 AM

I can confirm that MC3.0 will import 24p m2t from my HD110 as recorded onto an FS4HD.

Jeff Cerar · July 13th, 2008, 12:19 PM

Quote:

Originally Posted by David Parks

What do you mean Avid MC 3 only supports JVC HD 250? It supports the 100, 110, and 200 as well as 250. It has supported 30p for some time now.

According to the new Avid Knowledge Base info they ARE claiming support for the 200 camera and all the HDV frame rates...

http://tinyurl.com/5k65c2

However, if you click on the 200 or scroll down that page to the 200 camera you'll see the camera firmware version requirements (and other info concerning audio and video capture offset), then you plug in your camera versions to see if you can get/need the firmware upgrade, here...

http://support.jvc.com/pro/firmwareu...serieslist.jsp

I own a 200U purchased in 2007. I tried plugging in my firmware version numbers and keep getting the message...

"We are unable to determine current version of software you have. Click here to go back and try again."

Avid customer service referred me to JVC about this. I have sent an email to JVC and am currently waiting for a reply.

David Parks · July 13th, 2008, 01:50 PM

So it's a firmware change/conflict on the 200 where JVC changed a few things. That's not Avid's fault. Like I said before it works fine for me on my camera and it's a far cry better situation with ProHD than before.

Cheers.

Taylor Brush · July 14th, 2008, 07:16 AM

David:

Last week on Avid's page I read that there was support only for the 250 and specifically said that MC 3.0 does not support the 110 or the 200. Now that I want to find that page again, I'm having trouble... On Avid's forum, there is a whole page dedicated to it: http://community.avid.com/forums/t/59633.aspx

If this is not the case, then great.

From Avid employee Bob Russo on 11 June, 2008: "Avid Engineering found some issues with the other JVC camera models. Most notably they do not shoot audio and video in sync; the video and audio are off by a certain number of frames depending on the project type. Because of this, only the GY-HD250 is supported at this point.

Additional work is being done to try to add support the other JVC cameras."

If this is wrong or it has been fixed great. I think I may have a workaround, though, so I might just go ahead and purchase Avid anyway. I guess I'm still in the dark.

Taylor

Taylor Brush · July 14th, 2008, 08:37 AM

Investigating furthur, Avid says that the firmware must be updated to:
"the latest version:
SYS CPU C1692 V0109
CAM CPU C1693 V0109
VTR CPU C1694 V424A
ENC CPU C1703
V0103
SD CPU C1695 V0101
SD BOOT C1714
V0100
FPGA5 C1696 V0107
FPGA6 C1697 V0104
FPGA7 C1698 V0101"

My version on my 200U says:

SYS CPU C1720 V0100
CAM CPU C1693 V0106
VTR CPU C1722 V0101
ENC CPU C1703
V0102
SD CPU C1723 V0100
SD BOOT C1724 V0100
FPGA5 C1696 V0104
FPGA6 C1697 V0102
FPGA7 C1698 V0101

When I go to the updating page and enter the info exactly like it says to, I get the message that says they cannot determine my firmware blah, blah, blah...

The ones who have this working, do you have it updated to the firmware Avid mentions, and how do I get the updater to give me the right version?

Taylor

Patrick Synnott · August 8th, 2008, 08:20 PM

Same story - different date.

Avid and NAB made this announcement back in 2005.

I have used the 100 thru to the 200... as well as the HD50.... Avid has listed they support the devices, but there is audio/video sync drift. How can you say you support these devices if they don't actually work correctly?

April 18th, 2008, 02:52 PM	#1
Tim Dashwood Wrangler Join Date: Aug 2005 Location: Toronto, ON, Canada Posts: 3,637	Avid will fully support ProHD I was looking through my NAB notes and realized that no one noticed this pretty big bit of news. Here's the JVC press release: http://pro.jvc.com/pro/pr/2008/nab/avid.html I was seated at the same table as a couple of Avid/Digidesign guys during the JVC press event and they told me that it all seems to work well together in the new version. ETA is sometime in the summer (from memory not notes, so please don't quote me on that.) __________________ Tim Dashwood

April 18th, 2008, 08:32 PM	#2
Carl Hicks JVC America Join Date: Mar 2005 Location: McKinney, TX Posts: 516	It was very exciting to have an Avid system in our NAB booth, working at all frame rates over firewire, from tape or DRHD100 drive. __________________ Carl Hicks JVC Professional Products Company

April 19th, 2008, 02:36 AM	#3
Steve Mullen HDV Cinema Join Date: Feb 2003 Location: Las Vegas Posts: 4,007	It will be in V3.0 of Media Composer -- the one that will run on 10.5. Due in June 2008. Now here's a worry I have. This will not be a point release meaning it's not an "update." It's an "upgrade" which will cost $$$. Frankly, this update to the HDV codec is so small and soooo late, that it really should be a separate download. Avid will no doubt claim they just don't have time to check the codec with "old" systems. While this is true -- it's true only because they waited almost 3 years to modify the codec. It certainly could and should have been a year ago. Somehow pressure needs to be applied to Avid to make the codec a simple download to V2.x users. __________________ Switcher's Quick Guide to the Avid Media Composer >>> http://home.mindspring.com/~d-v-c

April 19th, 2008, 07:50 AM	#5
Gary Bettan Sponsor: Electronic Mailbox Join Date: Mar 2002 Location: Glen Cove, NY Posts: 758	Steve, Depending on when you purchased MC, the upgrade to 3.0 will have a reasonable upgrade cost. Avid hasn't named the grandfather date, but typically it's from the time of anounce minus 30 or 60 days. So folks who purchased recently have a good shot at the upgrade being a free download (or nominal cast with docs). As for longer owners of the software, I think that while the upgrade will have some cost, it will be significantly below the current $495 upgrade to MC for X Pro owners which will run at least into the summer. So my guess would be in the $300 range. This is not for certain, just based on my conversations at NAB. As for MC 3.0, you will be getting far more then just JVC Pro HD support. The demonstrations at NAB were very impressive. The software becomes multi-threaded and GPU aware. This means it will farm our tasks to all cores and the GPU itself, giving you a big boost in performance and handling - especially with HD footage. It will have both Leopard and Vista support. It will even run under Vista 64, not as a native 64 bit app, but it will let you access huge amounts of RAM. They've also added some nice user features such as the ability to move stacks of clips together. The responsiveness of the timeline and keyboard controlls are tight. All MC owners will find the next version a must have upgrade. Gary __________________ Check out http://www.videoguys.com 800 323-2325 We are the video editing and live video production experts! DV InfoNet members save 5%! Use Coupon Code DVINFO5OFF

April 19th, 2008, 06:29 PM	#7
David Parks Major Player Join Date: Feb 2006 Location: Houston Posts: 789	Better late than never I say. I've vented, shown frustration, and been completey hacked off at Avid. But now that's over. I'm glad I held on to my HD 100a. I've been through a lot with that camera over the last 2+ years. Funky Avid nonworking workflows, forcing me to learn FCP (which had it benefits), Avid Liquid for 24p and figuring out the funky 720/30p to 30i/1080i open bin dance in Xpress. Dead pixel issues which were fixed by JVC in a very customer oriented way. And so on. But that's in the past. I just got back from shooting with it today and it stills looks good. I've been shooting some with a Canon XHA1 with my NASA client (their camera not mine) and while it looks very sharp, I really find my JVC looking still more filmic with better color rendition. Finally, I can edit HDV 24p in Media Composer with my ole camera. Several times I thought about selling my 100a but now I'm glad I didn't. June can't get here fast enough. Cheers. __________________ David Parks: DP/Editor: Jacobs Aerospace at NASA Johnson Space Center https://www.youtube.com/user/JacobsESCG

April 19th, 2008, 02:44 AM	#4
Peter Moretti Trustee Join Date: Mar 2007 Location: Sherman Oaks, CA Posts: 1,259	Where the heck is 24F support from Avid, is what I'd like them to answer.

July 13th, 2008, 09:03 AM	#8
Taylor Brush Regular Crew Join Date: Mar 2008 Location: Jurbise, Belgium Posts: 29	AVID has abandoned us once again... Anyone else furious about the fact that Avid only supports the 250 camera in Media Composer 3.0? Once again, they have not followed through with promises. Doesn't it worry JVC that their camera has been left in the dust again and again by Avid? I feel totally ignored by the arrogance of a company who deems my camera as a low priority for them. They're shooting major motion pictures with this thing, isn't that enough for them? Does anyone have any insider info about whether they are done with this 100 and 200 camera's or if they have plans to finally come through with support it in the very near future?

July 13th, 2008, 10:50 AM	#9
David Parks Major Player Join Date: Feb 2006 Location: Houston Posts: 789	What do you mean Avid MC 3 only supports JVC HD 250? It supports the 100, 110, and 200 as well as 250. It has supported 30p for some time now. Are you referring to HDSDI injest vs firewire? I've tested 24p and 30p via 1394 with my JVC 100a and had no issues whatsoever. It works great. And if your saying the 250 works then I'm assuming that 60p works. As far i as can tell, it supports 24p, 30p, and 60p. Before 3.0 you could only do direct firewire digitize of 30p. Where are you getting this info??? __________________ David Parks: DP/Editor: Jacobs Aerospace at NASA Johnson Space Center https://www.youtube.com/user/JacobsESCG

July 13th, 2008, 11:25 AM	#10
Bill Ravens Join Date: Nov 2001 Location: santa fe, nm Posts: 3,264 Images: 10	I can confirm that MC3.0 will import 24p m2t from my HD110 as recorded onto an FS4HD.

July 13th, 2008, 01:50 PM	#12
David Parks Major Player Join Date: Feb 2006 Location: Houston Posts: 789	So it's a firmware change/conflict on the 200 where JVC changed a few things. That's not Avid's fault. Like I said before it works fine for me on my camera and it's a far cry better situation with ProHD than before. Cheers. __________________ David Parks: DP/Editor: Jacobs Aerospace at NASA Johnson Space Center https://www.youtube.com/user/JacobsESCG

July 14th, 2008, 07:16 AM	#13
Taylor Brush Regular Crew Join Date: Mar 2008 Location: Jurbise, Belgium Posts: 29	David: Last week on Avid's page I read that there was support only for the 250 and specifically said that MC 3.0 does not support the 110 or the 200. Now that I want to find that page again, I'm having trouble... On Avid's forum, there is a whole page dedicated to it: http://community.avid.com/forums/t/59633.aspx If this is not the case, then great. From Avid employee Bob Russo on 11 June, 2008: "Avid Engineering found some issues with the other JVC camera models. Most notably they do not shoot audio and video in sync; the video and audio are off by a certain number of frames depending on the project type. Because of this, only the GY-HD250 is supported at this point. Additional work is being done to try to add support the other JVC cameras." If this is wrong or it has been fixed great. I think I may have a workaround, though, so I might just go ahead and purchase Avid anyway. I guess I'm still in the dark. Taylor

July 14th, 2008, 08:37 AM	#14
Taylor Brush Regular Crew Join Date: Mar 2008 Location: Jurbise, Belgium Posts: 29	Investigating furthur, Avid says that the firmware must be updated to: "the latest version: SYS CPU C1692 V0109 CAM CPU C1693 V0109 VTR CPU C1694 V424A ENC CPU C1703 V0103 SD CPU C1695 V0101 SD BOOT C1714 V0100 FPGA5 C1696 V0107 FPGA6 C1697 V0104 FPGA7 C1698 V0101" My version on my 200U says: SYS CPU C1720 V0100 CAM CPU C1693 V0106 VTR CPU C1722 V0101 ENC CPU C1703 V0102 SD CPU C1723 V0100 SD BOOT C1724 V0100 FPGA5 C1696 V0104 FPGA6 C1697 V0102 FPGA7 C1698 V0101 When I go to the updating page and enter the info exactly like it says to, I get the message that says they cannot determine my firmware blah, blah, blah... The ones who have this working, do you have it updated to the firmware Avid mentions, and how do I get the updater to give me the right version? Taylor

August 8th, 2008, 08:20 PM	#15
Patrick Synnott New Boot Join Date: Jan 2007 Location: Edison, New Jersey Posts: 13	Old news Same story - different date. Avid and NAB made this announcement back in 2005. I have used the 100 thru to the 200... as well as the HD50.... Avid has listed they support the devices, but there is audio/video sync drift. How can you say you support these devices if they don't actually work correctly?