Forum Replies Created

Page 8 of 15
  • I was having issues even when tested with 10.6.7 on the same machine. It hated the video card till i put in the debug statements for the gpu fix. But it is working so far fine. in my quick tests of 10.7 prev. 4
    I think i may have gotten a glitch . I know its not supported but thought I would be daring on my NON production machine.
    CJ

  • Christopher Adams

    July 6, 2011 at 4:24 pm in reply to: MacBook Pro

    I am using the MBP 2.93 that way! Works fine with an external HD monitor.
    NOTE to get the system to work without errors I had to do this:
    I added these to debug for my macbook pro 2.93 works fine so far. no more error.
    even on Lion 10.7 For Resolve 8.0.3

    LsManager.3.NumGPUs = 1
    LsManager.3.GPUMapping = 0
    LsManager.3.GPUMappingEnable = 1

    NOTE: You will have to Save and restart Resolve for these settings to take effect.

  • Christopher Adams

    July 6, 2011 at 4:03 pm in reply to: MacBook Pro

    I am using the MBP 2.93 that way! Works fine with an external HD monitor.
    NOTE to get the system to work without errors I had to do this:
    I added these to debug for my macbook pro 2.93 works fine so far. no more error.
    even on Lion 10.7 For Resolve 8.0.3

    LsManager.3.NumGPUs = 1
    LsManager.3.GPUMapping = 0
    LsManager.3.GPUMappingEnable = 1

    NOTE: You will have to Save and restart Resolve for these settings to take effect.

  • Christopher Adams

    July 6, 2011 at 4:01 pm in reply to: 9400m gt? MBP

    I added these to debug for my macbook pro 2.93 works fine so far. no more error.
    even on Lion 10.7 For Resolve 8.0.3

    LsManager.3.NumGPUs = 1
    LsManager.3.GPUMapping = 0
    LsManager.3.GPUMappingEnable = 1

    NOTE: You will have to Save and restart Resolve for these settings to take effect.

  • I added these to debug for my macbook pro 2.93 works fine so far. no more error.
    even on Lion 10.7 For Resolve 8.0.3

    LsManager.3.NumGPUs = 1
    LsManager.3.GPUMapping = 0
    LsManager.3.GPUMappingEnable = 1

    NOTE: You will have to Save and restart Resolve for these settings to take effect.

  • Christopher Adams

    July 6, 2011 at 4:01 pm in reply to: Will this work?

    I added these to debug for my macbook pro 2.93 works fine so far. no more error.
    even on Lion 10.7 For Resolve 8.0.3

    LsManager.3.NumGPUs = 1
    LsManager.3.GPUMapping = 0
    LsManager.3.GPUMappingEnable = 1

    NOTE: You will have to Save and restart Resolve for these settings to take effect.

  • Already had a client like what i did with the new curves in V8 that hes having me redoing all the other clips in V8 just incase i can use them even more.

    Its like having a bit of apple color back. nice new but familiar and comfy.

    CJ Adams

  • Ok Glad it isn’t just me and that I am doing it wrong! This is a nasty bug. Though it seems isolated to key-framing in the color tab. Key-framing of position in the viewer in keyframe mode seems to be fine.
    I have no issues doing a partial track then a manual keyframe with “between”

    Just makes it hard to adjust points on a curve in the color window. Id love it if once you are in keyframe mode in the viewer all options would just keyframe! not just tracking movement.

  • same here no interpolation. also can you confirm in auto keyframe mode that the 2nd adjustment makes the window unstuck and makes it get all whacked out of position?

  • i need to test but those with a wave… can you adjust he width of other windows shapes other then circular?
    i hate having to go to the screen to stretch out rectangular windows for example?
    CJ

Page 8 of 15

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy