Announcement

Collapse
No announcement yet.

NXe Deck Control - weird behaviour!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NXe Deck Control - weird behaviour!

    NXe with Front Bay. E4.61

    Was connected via rear port to a DSR11 (1) worked without problems.

    Yesterday DSR11 (1) was being used and I patched in my other DSR11(2)usually connected to my Storm system. Both DSR's set to PAL
    Here is what is happening with DSR11(2) which works fine on the Storm system and for every other Firewire app. The Firewire on this deck is working.

    Project set NXE2 50i

    In Capture, select NX DV 50 i - no deck control but picture is seen both in Edius and on Monitor from NX output
    IF I select OHCI 50i Still connected to NX rear then I get normal firewire control.
    I have tried deleting the device from Device Manager/imaging. Cables have been swapped. Other firewire decks seem to be OK- just tried my Sony A1 running DV out. Reconnect DSR11(1) No problem - just DSR11(2)

    Any thoughts?

    DD

  • #2
    I had this happen once with a Sony DV camera, I changed the Firewire lead and it worked OK. At the time I put it down to a faulty FW lead.
    System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
    System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

    Comment


    • #3
      Something else I discovered was that although I do not have deck control, I can still record the signal via the NXe Firewire port by using F9.
      Totally baffled. .......plus it all works fine in OHCI making me think that its time for a VERY Large Southern Comfort.

      DD

      Comment


      • #4
        Me Too DD..................................AND RELAX............Deal with this Monday!
        Asus P5K64WS, Intel Core 2 Quad QX6850 Extreme CPU, Saphire HD 3850 512mb graphics, WDraptor160 OS, Highpoint Rocket raid 2310 4 x 500gig Seagate sata 2 se drives in raid 0, NXe and Edius 5.51 Imaginate 2.
        Procoder 3.06 and various Prodad add-ons

        Comment


        • #5
          Close EDIUS.
          Reboot.
          Run ADVC Mode Controller and verify it's not set to ADVC mode.
          Run EDIUS.

          Comment


          • #6
            Originally posted by Imagine Video View Post
            Me Too DD..................................AND RELAX............Deal with this Monday!
            Tried that and it was set to Edius - however having it open induced a "Green screen" shut the deck don started again and then got back to square 1 no deck controls under NXe with this deck but fine if OHCI selected. Other IDENTICAL DECK still works fine

            DD

            Comment

            Working...
            X