AVCHD, why are some having problems and others not?

Green Hornet said:
Ok so from what I see so far,
PC's can edit and mac's can't when using Premiere CS4.

I have a 2 gig core 2 duo laptop and 4 gigs of ram with Nvida video card running cuda drivers
(both nvidia video card and cuda drivers are said to accelerate AVCHD).
So I guess that is the baseline system that you need to edit this stuff....

When cineform fully supports CS4, then it will be a no brainer to go that route.
CS3 already edits like DV when using cineform.
(That was how i use to do it, but since the cineform presets are not there, I just edit AVCHD, as I can do that too)
Click to expand...
Seen a few of your posts regarding CS4. Do you have it working flawlessly? I recently put together a machine intended for native editing. At first it was chewing up 1080p files with ease, but soon found it randomly hanging when skipping around and just couldn't play certain parts of files. So I'm not concerned so much about speed, just that the program is very unstable for me in vista 64 (the import process hangs, maxing out only one core, seems like a common bug). I have to agree that Premiere doesn't use core when it is installed (but it is GREAT for playback on older machines). I figured there may be a way to hack it, but didn't bother knowing that power wasn't an issue and that Adobe is working on the problems.

Haven't tried Cineform, but was waiting to hear some more comments Neo and this camera (sounds promising). On the other hand, if Adobe can iron out the AVCHD bugs, I probably wouldn't need it for most editing. But I guess I need to pick a solid codec for projects requiring more work anyway. The joy of early adaption ;)
 
Green Hornet,
Did you manage to force premiere to use CoreAVC?

Un-registering/Deleting these files doesn't change a thing.
Premiere talks directly to the mainconcept DLLs, and these cannot be replaced because they are adobe plugins.
 
Green Hornet said:
http://www.coreavc.com/index.php?option=com_content&task=category&sectionid=4&id=21&Itemid=59

Not sure if that will solve all problems, but so far that is the only difference (other than modifiying my graphics card drivers to use cuda) i see from others.
Click to expand...
HI
which sw in your system do you think is written specifically to benefit from CUDA ? I don't think that nVidia drivers (which are done to be comaptible with cuda) would simply speed up the encoding/decoding processes on your system
I believe the NLE or your codec package should be written specifically to use the CUDA API.
I would like to hear about it if you know more. It is an intersting issue :)
THX
CIPO
 
This post seems to suggest that Nvida and cuda drivers can speed up Adobe CS4 applications:
http://www.overclock.net/graphics-c...antly-accelerates-photoshop-cs4-premiere.html

AS for my CS4 working flawlessly, yes I can say that it is working flawlessly for AVCHD.
I have not set it up to work with Cineform, due to them stating that the update for that is just weeks away.

I have unregestered the main concept codecs for CS4 and got it to work that way,for cineform but it is not that way now. When I did that, I wasn't editing AVCHD, only transcoded to cineform files.

Also in CS3 (which I also had on this same machine) worked flawlessly for cineform.

So to recap, Yes My laptop edits AVCHD in Premiere cs4 flawlessly, without crashing, hanging etc.

I am not sure why it is workin, some say it's due to the cuda drivers speeding up CS4,
I thought it was the core codec, but maybe not. Maybe it's the dedicated video card (but that would mean that similiar desktops should do the same).

There does seem to be a pattern that CS4, Nvida vidia with cuda support, and a core 2 duo on windows xp pc, seem to be what is needed to do this.

On other computers set up this way, I have seen it work as well.
 
Chuckf said:
So it isn't possible at this time to edit the 150 in FC2 on a recent Macbook pro?
Click to expand...

Yes, it is.

I and others here have been doing it since the cam is released.

AVCHD is converted to pro res using the log and transfer window and editing is a breeze. Others use Toast 9/10 or other utilities to convert to something else and edit that.

What we are exploring is native AVCHD editing, which few NLEs currently support and even fewer support in RT.
 
Oh, nice. Now it is clear. Is not about "special" drivers then but it is all about CS4 which take advantage of CUDA (it has code specifically written to use CUDA). I can believe your system go faster :) Using the GPU on latest nVidia via CUDA is a HUGE boost compared to CPU only systems. CUDA is an excellent way of improving the performances.
I wonder if other NLE wuld support it :)
THX
 
I was checking more about it. Your nVIdia 8400M GS (for laptops) should be based on the G86M GPU and should delivery about 25.6 GFLOPS of computational capacity. Imagine that a more recent 8800GT/GTS/GTX (for desktop) delivers between 230-416 GFLOPS. Which means almost 10 times (and more) as much as your system. An Intel Core2 probably runs up to 20GFLOPS.
Finally the SW house realized that there is so MUCH POWER in the video card to be used ! ;)
 
i guess the cuda helps. i just updated and it doesnt hang anymore.
however cs4 still needs the 720 24p support. the 1080 24p works realtime

using
8500 gt
c2q 2.4
 
David S. said:
Yes, it is.

I and others here have been doing it since the cam is released.

AVCHD is converted to pro res using the log and transfer window and editing is a breeze. Others use Toast 9/10 or other utilities to convert to something else and edit that.

What we are exploring is native AVCHD editing, which few NLEs currently support and even fewer support in RT.
Click to expand...

so you CAN edit the footage, you just have to convert to pro res? how different is pro res from avchd, in terms of file size and quality?
 
ProRes isn't lossless and I imagine the file sizes would be roughly in the neighborhood of 4-5 times as large as the native AVCHD files. I've been transcoding to DNxHD using VoltaicHD, which has been recommend by users here, and it's approximately 4-5 times as large as the native AVCHD files as well. When I had my HV30 and A1 I'd transcode HDV to Apple Prores and I'd get pretty much the same 5:1 ratio in file size.
 
Last edited:
AVCHD is heavily compressed to start with.

I don't know what is lost by going to pro res in order to edit.

Is it your belief that you are compromising quality by going from 24 mbps AVCHD to 125 mbps Pro res?
 
Yes. It probably does come in about 5 times the native file size so when native editing on FCP becomes a reality, that will greatly reduce my media sizes.
 
CiPO said:
This suggests somthing else:

http://www.fudzilla.com/index.php?option=com_content&task=view&id=9718&Itemid=1

However is a good news for ATI owners. Anyway OpenGL used full power from the GPU ;)
Click to expand...

That is speaking to photoshop, not Premiere CS4.

It is known that Cuda does speed up Premiere, another has posted that it has got rid of his "hangs"

I am editing 1080p AVCHD, with nothing special in my 13.3" laptop, other than the cuda drivers.


IF you really need this to work for you, then try this:

http://www.streamingmedia.com/press/view.asp?id=11153
 
yep but i cant claim its bec. of cuda.. although i didnt experience the hang on render preview like i used to.
 
Whoa I ran into a problem just recently. Does anyone have any avchd 720p60p footage I can use? For some reason, the files I have make final cut crash before they can finish transcoding.
 
yes, it works but due to simple OpenGL which uses GPU at best :) nothing to do with Cuda custom drivers :)
 
No problems here....Macbook Pro 2.6 Ghz Core 2 Duo, 4 Gb RAM, nVidia 512 Mb RAM
Sometimes it does skip/stutters when playing, it could be my Hard drive not fast enough being 5400 rpm but when its on my G-Raid Mini Firewire 800, its no problem playing at all. :)
 
You must log in or register to reply here.
Back
Top