-
1. Re: Sluggish Trim Edit on Tracks above V1A1 in CS6
Steven Pribilinskiy Jun 6, 2012 9:52 AM (in response to Steven Pribilinskiy)Please, if you read about that issue, try to reproduce it and reply.
-
2. Re: Sluggish Trim Edit on Tracks above V1A1 in CS6
Steven Pribilinskiy Jun 15, 2012 11:59 AM (in response to Steven Pribilinskiy)Can someone confirm this lag? Jim, please?
After entering Trim mode on Video/Audio 2, press Up/Down to Go to Next/Previous Edit Point.
-
3. Re: Sluggish Trim Edit on Tracks above V1A1 in CS6
RBemendo Jun 15, 2012 3:53 PM (in response to Steven Pribilinskiy)@Steven Pribilinskiy. with a large project open, I tested the bars and tones in trim mode like your video shows, and I don't see the same behavior, everything functions as expected. I also went and tested the same functionality through video5 and audio5, smooth and no crashes. Sorry, perhaps it's a PC bug, I'm testing on a MacPro
-
4. Re: Sluggish Trim Edit on Tracks above V1A1 in CS6
Steven Pribilinskiy Jun 15, 2012 5:26 PM (in response to RBemendo)Thank you very much for testing this. This pushed me to try out the project on a Core i7 920 remote PC (mine is Quad-Core Q8300) - the lag is there, but it's almost unnoticable, and there's definitely no freeze and hangs at all.
I must do a Hardware Upgrade - looks like it is the only way in CS6 to avoid this sluggish behaviour. Core i7-3820 is quite attractive and it's almost 2x times faster than the i7 920 and it's cheap!
What are the specs of your PC, RBemendo?
-
5. Re: Sluggish Trim Edit on Tracks above V1A1 in CS6
Kevin-Monahan Jun 15, 2012 6:03 PM (in response to Steven Pribilinskiy)Long sequences require more system resources, especially RAM. What are your full specs again (especially RAM), Steven?
-
6. Re: Sluggish Trim Edit on Tracks above V1A1 in CS6
RBemendo Jun 15, 2012 7:12 PM (in response to Steven Pribilinskiy)I'm on an dual 2.26 quadcore MacPro 4.1, 32gigs of RAM and quadro 4000 for mac.
-
7. Re: Sluggish Trim Edit on Tracks above V1A1 in CS6
Steven Pribilinskiy Jun 16, 2012 1:55 AM (in response to RBemendo)




