Skip to main content
D
donjojo-hannes
Inspiring
October 27, 2017
Answered

What does the following Error mean: "invalid graph channel frame type"

  • October 27, 2017
  • 4 replies
  • 3630 views

Hi,

one thing that appears from time to time in the final release is the "invalid graph channel frame type" Error on completing a take. What does it mean?
It seems to be connected to recording a take with webcam + keyboard triggers. If I do them one after the other it is fine. Any way to avoid it? Or any idea what causes it?

Cheers,

Johannes

    This topic has been closed for replies.
    Correct answer Francouz

    Hi, thanks for your response. I actually find the cause. I recorded the quarter right and left face with trigger input and it seem that it was the animation causing trouble. I still have the original file if you want me to send it to you.

    4 replies

    kelbyn
    kelbyn
    Participant
    December 19, 2017

    Ah thanks for the fix! That error message was driving me crazy. Thanks guys. Keep up the good work.

      Francouz
      Francouz
      Inspiring
      November 7, 2017

      Hi, i also have the same problem. I render a first animation in png file, evrything went good, then i wanted to update that first png render and he created a new folder with the exact same name as the first one (don't know how is it even possible). After that the same error message shows up. I tried to save the project in different location but the problem is still the same i don't know what to do.

      Thanks

      DanTull
      Adobe Employee
      DanTull
      Adobe Employee
      November 7, 2017

      Is your project small enough to zip up and send it to me?  I'd really like to see an example of the problem to figure out what is going wrong.

      Thanks -- DT

      Francouz
      FrancouzCorrect answer
      Inspiring
      November 7, 2017

      Hi, thanks for your response. I actually find the cause. I recorded the quarter right and left face with trigger input and it seem that it was the animation causing trouble. I still have the original file if you want me to send it to you.

      D
      donjojo-hannesAuthor
      Inspiring
      October 27, 2017

      Hi Dan, I'm on a slow internet connection in the mountains right now and the project folder is pretty substantial: 1.4 Gigs
      For me it is not a big issue as I don't do live broadcasting and if I'm the only one who can "produce" the error, nevermind.

      But if you would like to investigate here are more details for your investigation:

      In trying to analyze the error I found that it appears when I record from the webcam and call 3 or 4 keyboard triggers (in sequence; some call an animation cycle replacing body and head, one a replacement mouth - no error. If during the same take I later call another animation cycle the error appears). The error pops up only when finished and the the keyboard takes appear in the timeline. But it won't allow playback or any other interaction with CH. It will keep popping up whenever I click something in the window, though I can select the takes individually inbetween clicking away the error message and can then hit "delete" for each one until all keyboard trigger takes are deleted. Then the error message disappears. The take based on the webcam is not affected and can remain in the timeline fully functionally.

      In other news:
      Thanks to the entire team for the final release. I'm really enjoying the new features and look forward to putting out my first big project - a labor that started and grew with the beta version over the last 11 months!

      DanTull
      Adobe Employee
      DanTull
      Adobe Employee
      October 27, 2017

      Looking in analytics, I do see a few other customers have hit this case as well. I wasn't able to reproduce it, but will keep trying.

      Since it sounds like you can reproduce it on demand, one thing we could try is just locating the individual malformed arf file since that should be much smaller and more slow connection friendly. After doing a recording that shows the error and then undoing/deleting so that the  dialog will get out of the way, if you use the File menu command to Reveal the project in Finder/Explorer. Inside the project there's a Ch Media folder, inside that there's a recordings folder, and then there are folders for each day with arf and wav files. An individual arf is often quite small, so if you could zip those up, they might provide some clues.

      donjojo-hannes  wrote

      Thanks to the entire team for the final release. I'm really enjoying the new features and look forward to putting out my first big project - a labor that started and grew with the beta version over the last 11 months!

      Oh, wait. I remember you! Hi again! That reminds me that I did figure out why we use so much RAM when linking long scenes in After Effects. I'll post back on that thread with more information. I'm glad to hear you're finding a lot to like in the new release.

      Definitely let us know when you share it. The team loves to look at things that are created with our product!

      DT

      D
      donjojo-hannesAuthor
      Inspiring
      October 29, 2017

      Hi Dan,

      Here are two arf files. Sorting them by time I chose the two with a creation date before and after the event. There was none produced at the actual time the error occured.

      https://www.dropbox.com/s/oh6f20t4owxwjoc/arf.rar?dl=0

      DanTull
      Adobe Employee
      DanTull
      Adobe Employee
      October 27, 2017

      Hmm. I've never seen that error occur in practice, but it suggests that somehow Ch is writing invalid arf files (that's the extension it uses when saving recorded data for playback). Could you zip up and send a project showing this error to me? I'm hoping a closer inspection of the arf files will reveal some clues as what wires got crossed to create this condition.

      I've done webcam and keyboard triggers before and haven't seen it, but I'll also do some investigating to see if I see anything amiss.

      Thanks -- DT

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices