H8000fw 5.3 AES clocking problem >48k

Home › Forums › Products › Rackmount › H8000fw 5.3 AES clocking problem >48k

  • This topic is empty.
Viewing 12 reply threads
  • Author
    Posts
    • January 14, 2010 at 2:24 pm #106783
      Siem
      Participant

      I can't seem to clock my H8000fw to sample frequencies over 48k when I clock it via AES. only 44.1khz or 48k seems to work, is this a limitation of the AES protocol?

      I don't remember if it worked on 5.2

    • January 14, 2010 at 3:15 pm #119788
      IDeangelis
      Member

      Hi Siem

      usual details are needed:

      -which routing are you using?

      -how clocking parameters are set?

      -which AES connector(s) are you using?

      thanks

      I

    • January 14, 2010 at 3:17 pm #119789
      IDeangelis
      Member

      …and…

      are you clocking the unit from internal clock….or from external?

      I

    • January 22, 2010 at 9:12 am #131012
      Siem
      Participant

      -which routing are you using?

      AES8 8 Track AB

      -how clocking parameters are set?

      Source: AES 17/18 (does also work with 11/12 13/14 15/16)

      Sample Rate: 44102 / 48002

      ADAT (unlocked)

      FIREWIRE1 (unlocked)

      AES 11/12 OK

      AES 13/14 OK

      AES 15/16 OK

      AES 17/18 OK

      as soon as I go to another frequency that's not 44.100 khz or 48.000 khz it'll be like this:

      Source: AES 17/18

      Sample Rate: a strange number like 47891 or 47887

      ADAT (unlocked)

      FIREWIRE1 (unlocked)

      AES 11/12 unlocked

      AES 13/14 unlocked

      AES 15/16 unlocked

      AES 17/18 unlocked

       

      -which AES connector(s) are you using?

      AES 11-18, the broad 'parallel-port' on the back

       

      -are you clocking the unit from internal clock….or from external?

      external, from one of the AES channels

    • January 22, 2010 at 1:28 pm #131016
      IDeangelis
      Member

      Thanks for details.

      Hard to say what's happening there. AES clocks fine at 96KHz. Try using AES11/12 as source.

      What device is feeding the clock source?

      I

    • January 22, 2010 at 1:42 pm #131018
      Siem
      Participant

      a Lynx AES16e card

    • January 22, 2010 at 1:50 pm #131019
      IDeangelis
      Member

      Have you tried a CLEAR SETUP on the H8000?

      I

    • January 22, 2010 at 2:02 pm #131020
      IDeangelis
      Member

      I have just tried myself here, with 2 units.

      An H8000 connected to an H8000FW (both on 5.3) via AES_EBU on the DB25 connector, the one we advice and have available on the web store.

      The H8000 is running at 96 as internal Master Clock.

      The H8000FW runs on the same routing you reported and clock is derived from AES_EBU inputs 11 & 12- All AES 11>18 are clocked fine.

      So, I can only think of:

      -bad cable?

      -CLEAR SETUP needed?

      -something wrong in the computer/audio interface?

      I

    • January 22, 2010 at 3:46 pm #131021
      Siem
      Participant

      I cleared the settings, it didn't help.

      I suppose it could be the cable, it's not a direct cable, but two digital cables one side connected to the Lynx AES16e and then XLR <-> XLR and then into the AES 11-18 port on the Eventide. I had to do it like this, I couldn't find a Tascam AES to Yamaha AES. I'm going to see if I can find one online.

      I'm going to shorten the cable (these two cables are about 5 meters combined) and make it a single one this weekend, hopefully it'll resolve this.

    • January 22, 2010 at 4:08 pm #131022
      IDeangelis
      Member

      "Did you check it with the latest OS?"

      That's usually my question.

      Yes, both on 5.3 as reported in my previous test reply.

      That cable looks "suspicious".

      best

      I

    • January 23, 2010 at 2:57 am #131025
      zoomex
      Participant

      Hi

      I have the same problem with PT 192 AES/EBU -> Eventide at  96 Ext

      OS 5.3

      error msg   DSP B over Loaded  

      Sad

    • January 23, 2010 at 7:12 am #131026
      IDeangelis
      Member

      Hi zoomex

      we would appreciate details as this means pretty much nothing.

      Do you hav clocking problems?

      DSP x overload usually means the preset is too large or on the verge….running at 96KHz.

      There may be some and we're trying to fix them…..and this is not the same problem reported in this thread.

      So, here we go (again):

      -OS running on the unit?

      -name and number of presets you get this warning from?

      -full description of unit I/Os, used routing and clocking setup

      thanks

      I

    • January 23, 2010 at 11:10 am #131027
      zoomex
      Participant

      OS ver : 5.3

      Preset Name:Omnipressor

      Preset Number:#6517

      Unit I/O Routing:

      Routings:AES8 Track AB

      Source:AES 11/12

      Sample Rate:96 EXT

      external Clock(Digidesign 192 AES/EBU -> connect to eventide H8000fw AES/EBU)

      ProTools 8.3 run on MAC Leopard 10.5.7 (project at 96)

      when i run it on 48 i dont have any error MSG

      so i guess it's not the preset problem

      Cheers,

      Zoomex

  • Author
    Posts
Viewing 12 reply threads
  • You must be logged in to reply to this topic.