Forum Replies Created

Page 46 of 170
  • Glenn Sakatch

    February 11, 2018 at 5:05 pm in reply to: Fusion 8: rendering cuts the project

    sorry Tom, I replied to this a week or so ago….but I don’t see that posted anywhere.

    (If you copy and paste all that cobledegoop you pasted into a flow area of fusion, you can read it too)

    I took yours, and put my own source sequence in, as I obviously don’t have your source sequences.
    I put mine on loop, as yours were, and set it to 500 frame render range.

    You might want to double check that your render range is set to 500 frames. Since I had to put yours into a new comp, I cant tell that information. I do see your saver is set to 23.97 in the format tab. Is that what you see on your end, or is that also because of my creating a new comp? I would assuming the saver is the same at both ends, as it was pasted from your comp.

    -check your render range, make sure it is set to 500
    -check your saver format, make sure it is set to 25
    -curious to see if your preferences are set to a frame format of 25 as well for this comp.

    If you want to send the two png sequences, I can try a render at my end as well.

    Glenn

    Glenn

    Glenn

  • Glenn Sakatch

    February 4, 2018 at 4:20 pm in reply to: Moving multiple Keys as One

    You can try collapsing your text and graphic layers, and then adding a pic in pic effect to the collapse. In days past, pic in pic could solve the issue of the background moving with the layered element that was caused by using the resize effect.

    I don’t do a lot of this stuff in Avid anymore, so can’t say for sure if it will work.

    Glenn

  • Drag and drop might interfere with spanning of c300 clips, causing 1-15 min file to become 3- minute files.

    Glenn

  • Glenn Sakatch

    February 1, 2018 at 2:43 pm in reply to: Avid 8 Timecode Burn-In Error

    Interesting. If you park the playhead on the frame showing the incorrect timecode, and then step a frame back and then forward again, does the correct timecode show up?

    sounds like the scrubbing is just going too fast for avid to read the information? (I’ve never seen this, but I suppose that is what is happening)

    could this be linked to the power in your system? cpu or ram?

    Glenn

  • Glenn Sakatch

    January 28, 2018 at 6:02 pm in reply to: Fusion 8: rendering cuts the project

    it is surprisingly simple….select all the nodes in your tree and do a copy command.

    Click here and paste.

    to go the other way, select everything from the { at the top to the } at the bottom
    copy it
    go to fusion, and paste into a node area.

    (here is a simple node setup)

    {
    Tools = ordered() {
    Loader1 = Loader {
    Clips = {
    },
    Inputs = {
    [“Gamut.SLogVersion”] = Input { Value = FuID { “SLog2” }, },
    },
    ViewInfo = OperatorInfo { Pos = { 392, 135 } },
    },
    Saver1 = Saver {
    CtrlWZoom = false,
    Inputs = {
    ProcessWhenBlendIs00 = Input { Value = 0, },
    Clip = Input {
    Value = Clip {
    Length = 0,
    Saving = true,
    TrimIn = 0,
    ExtendFirst = 0,
    ExtendLast = 0,
    Loop = 1,
    AspectMode = 0,
    Depth = 0,
    GlobalStart = -2000000000,
    GlobalEnd = 0
    },
    },
    OutputFormat = Input { Value = FuID { “TargaFormat” }, },
    [“Gamut.SLogVersion”] = Input { Value = FuID { “SLog2” }, },
    Input = Input {
    SourceOp = “Loader1”,
    Source = “Output”,
    },
    },
    ViewInfo = OperatorInfo { Pos = { 680, 101 } },
    }
    }
    }

    Glenn

  • Glenn Sakatch

    January 28, 2018 at 4:49 pm in reply to: Fusion 8: rendering cuts the project

    this could be a setting in one or two different areas. Perhaps you can paste your flow into a reply?

    Glenn

  • Glenn Sakatch

    January 27, 2018 at 5:23 pm in reply to: 24 frame project to 30 frame project

    I typically leave it at 23.976 until the very last stage. Master at 22.976, then convert the final program (back in avid).
    I usually want a 23.976 Master on hand anyway, which is handy for 25 frame conversions as well.

    I’ve never done a 29.97 or 59.94 master out of Resolve, so I’m not sure how it handles the conversions.

    Have you tried bringing your 23.976 sequence into a 29.97 project in avid, and creating a list from there? That might help Resolve with the math.

    Glenn

  • Glenn Sakatch

    January 27, 2018 at 5:17 pm in reply to: replacing footage

    If your new clips are the same length as the originals, with the same timecode, then it is easy…even easier if you make them the same name, but put them in a “revised” folder. (Tell Resolve to look in the revised folder for these clips)

    If they have different timecode (which I’m guessing they do) then it becomes much more labour intensive, as you will have to tell resolve which ones go where. If your new renders start at the exact frame you want the new clip to start at..that would be easier. If there is pad on the clips, I think you will be doing them individually, setting in points and editing them in.

    Glenn

  • Glenn Sakatch

    January 27, 2018 at 5:06 pm in reply to: AMA Plug-In Unable to Provide Compressed Sample

    Interesting…sounds like a bug.

    You said you re-installed 8.10. Was that the version that was installed when the original links were created?

    You did download the latest nablet plugins..not just re-install from existing files on your computer?

    If the original links were done in 8.10, but can no longer create a new link, then sounds like something has gone corrupt. If the original avid was an earlier version, it might be a bug with 8.10. Might want to roll back and see what happens.

    Glenn

  • Glenn Sakatch

    January 24, 2018 at 7:28 pm in reply to: Playback lag problem

    you say the frames are cached. Where are they cached to, and in what format.

    (I would not expect great playback from 4k r3ds, or arri from a usb 3 drive, with only 1 GPU)

    Drop your timeline down to HD and see what you get.

    Glenn

Page 46 of 170

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