Thomas Smet
Forum Replies Created
-
I just tried the update to Lion. Pretty much same exact experience as before.
Phenomenal performance with OpenCL for about 45 minutes. Played with a 3 way CC and all of a sudden OpenCL performance died even at 1/4 resolution. Even raw AVCHD footage would only play at around 10 fps at 1/4 resolution. Delete all clips in the timeline and drag new clips still playback jerky.
Close project and open again with no change. Close CS6 and launch again fixes the problem for awhile until I tinker with some filters again.
Overall OpenCL support is pretty darn slick and is lightyears faster on my 17″ MBP until it stops working. I’m starting to think certain combinations of filters or just tinkering with the settings in the filters are whats killing it for me. Perhaps I should experiment with the filters and see if I can come up with a consistant cause of the problem.
-
I was just thinking here that since my OpenCL seems to be working very well for a X amount of time could my MBP be shifting the gpu to the stupid Intel GPU after awhile which would really mess up gpu acceleration? Only Apple has this annoying feature of switching gpu’s on the fly as they are needed. This may explain why when I first launch CS6 my OpenCL performance is great and then all of a sudden it just drops after a X amount of time.
-
I am having similar problems on my 17″ MBP as well
AMD 6750 1024MB
I however get great playback for a random amount of time and then for whatever reason the OpennCL performance plummets where I cannot get better then 10fps on even 1/4 res display. Switching to software only fixes the problem and I get decent playback again. Restarting CS6 makes the OpenCL work well again for another random amount of time.
When the open CL works it is pretty darn slick although not by as much as our CUDA friends from my understanding. I was glad to get the extra performance however if it can only be stabilized I would be very happy. With OpenCL I can get AVCHD at full quality with two clips using a blend mode, cross dissolve and one gpu filter all with a single title track. Playback drops frames when I use my second monitor for output but thats a lot of junk going on in that timeline.
I’m sure at some point OpenCL support will get better. For now I’m fine using software mode since it even seems to be faster then the software mode in CS5.5.
-
And this is why some companies don’t say anything until a product ships.
We can either have a heads up months ahead of time or stay in the dark. Either way companies end up upsetting somebody.
Honestly I’m glad they are working out the bugs first or again somebody would have complained about releasing beta hardware.
I understand the frustration but it is what it is. Honestly I prefer to wait and dream instead of living in the dark.
-
I should point out I have this exact same problem. 17″ MBP core 17 quad core with hyper threading. AMD 6750 GPU 1 GB VRAM and 8 GB system ram.
I am running Windows 7 64 under bootcamp with Vegas 11. I have the latest version and everything plays great until it gets to a cut. I can even scale AVCHD down to 720×480 add 4 gpu filters and play in RT and render out at super fast speeds. My fps does drop 1 to 4 frames between every cut.
Vegas is using the AMD video card and I have tried many storage devices even up to an empty ESATA drive running at 125MB/S.
To me it seems like the way Vegas seeks the drive to get the next video clip. It just seems to take a frame or two. Once the clip is there it plays fine. I find this bug very annoying as it makes it hard to focus on the timing of edits when the video hickups for a few frames between cuts.
I should point out I have run Adobe CS5.5 under Windows and OSX on this same machine and it does not have the same problem. I have also run FCP and the new FCPX without this same problem on the same hardware.
I would love to know if I’m just doing something wrong but the last three computers I tried Vegas on did the exact same thing.
-
I think too many companies put too much into the whole 64bit thing which on it’s own doesn’t make a program run any faster. I think right now it is actually dragging them down. I’m also not sure why Apple felt slower machines couldn’t handle FCP7. I ran FCP7 on a dual core iMac like there was no tomorrow. Sure the rendering to compressed formats was a bit slow but the actual process of editing was really like slicing through butter. I now have a brand new 17″ MBP quad core that is a dream with FCP7 but is sluggish with FCPX. This is a top of the line Apple system and about the best laptop you can get.
There was nothing wrong with 32 bit software and being limited to 2 GB of ram. FCP7 did just fine and the only thing they really needed to enhance was the render speed. People were editing big budget features on that little 32bit app.
FCPX seems to be taking this new approach of making software bloated and just keep throwing Ram and cores at it to make it run better (cough, Premiere, cough). It is insane to think that a program should have 16GB+ of ram just to do what programs 1 year ago could do with 2GB of ram. Personally I think FCPX is just trying to do too much on the timeline at one time with all the metadata stuff and background processing. Even if background processing isn’t working all the time the program still has to have all those hooks to look out for certain things.
-
I understand CS5.5 cannot capture to ProRes but what about playback of ProRes files in a sequences designed for one of those cards?
I am ok with using an external app to capture but being able to actually edit with the card would be very important.
-
That is because so much takes place when you encode video. The encoding itself is just the process to convert to a new format. All the other processing has to still take place which includes decoding the raw video and rendering each of the effects on the clip. By using gpu enhanced processing it will be the process of scaling, and rendering certain effects that are sped up and not the actual encoding to the destination format. Overall it looks like the encoding is faster but only the effects part of the chain is sped up.
-
Try out my suggestion then and create some footage to test. Use some particle effects in AE to create your own greenscreen footage. Since most cameras have some sort of processing or interpolation going on it really is the only way to see exactly what goes on when you key.
-
just make some in After Effects. Create a green/blue solid in the background and then create some particle effects or animate a few still image layers. Then render out two clips. one at 4:4:4 and then one to a 4:2:2 format. There you go instant footage to test out.
Of course this isn’t the same as shooting with a camera but it is better then nothing.
I find it ironic that for years many of us were so desperately grasping for 4:2:2 color and now today we have people referring to it as not good enough. Considering people can get darn good keys off of progressive 4:2:0 it is really getting nit picky to compare 4:4:4 and 4:2:2.
The other ironic thing about most cameras that shoot 4:4:4 such as Red is that they are single sensor which means every other color pixel is interpolated. So basically it isn’t that was more detailed chroma wise then 4:2:0 with some sort of chroma reconstruction filter or even basic chroma smoothing.
Unless you have access to a 4:4:4 camera it may be best to not get hung up over 4:4:4. You will drive yourself nuts thinking you have to have it when it may be out of your reach for a long time.