101 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,599

Re: Release candidate of the Windows driver 3.x (3.013) now available:

If you update the legacy driver you have to reboot the computer...

Regards
Matthias Carstens
RME

MC's Website

102 Reply by panu

  • panu
  • panu
  • AD/DA expert
  • Offline
  • From: Helsinki, Finland
  • Registered: 2010-03-08
  • Posts: 92

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Ok...

sonarmods.com

panu's Website

103 Reply by panu

  • panu
  • panu
  • AD/DA expert
  • Offline
  • From: Helsinki, Finland
  • Registered: 2010-03-08
  • Posts: 92

Re: Release candidate of the Windows driver 3.x (3.013) now available:

3.016
2nd unit's Clock Mode was unintentionally changed after reboot:

Correct values:
Sample Rate: 44100 Hz
Clock Source: ADAT2   | Current ADAT2
Pitch 0.000%

But these values vere changed to:
Sample Rate: 0 Hz
Clock Source: Internal   | Current Internal
Pitch -100.000%

-Panu

sonarmods.com

panu's Website

  • Registered: 2007-05-01
  • Posts: 128

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Hi,

Occasionally (quite rarely actually) when I open new application my FF400 starts to play faster and very grainy.

Application does not have to be audio related, could be notepad or whatever... but generally it happens more frequently if application creates higher CPU peak when started...

I noticed this behaviour with v3.016 drivers. Never had/got this behaviour before v3.016...

Sometimes it will stop on its own when I close something (or close and then reopen the same application), but a lot of times I have to stop and close audio application, and reopen it again.

This could happen with nuendo, foobar or some other media players.

I am not able to reproduce it consistently...

Here is an audio example... I managed to record this in real-time (in loopback mode).
http://www.minimal.si/dl/problem.mp3

Any ideas?

My comp:
ASUS P5K
Q6600 CPU
GF 8600GT
4GB RAM
RME FF400 (rev 1.70, v3.016)
2x UAD1, 2x TC
WIN XP32 SP3


Regards,

     b.

https://granurise.com

105 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,599

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Please go back to an earlier driver to verify it does not happen then. This behaviour is usually caused by a high CPU peak which affects FireWire transmission on a level below our driver, so I think it will show up with other drivers too.

Regards
Matthias Carstens
RME

MC's Website

  • Registered: 2007-05-01
  • Posts: 128

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Thanks for the info Matthias.

I'll try with earlier v3.0x drivers and with last v2.9992 driver and report back.

Regards,

     b.

https://granurise.com

107 Reply by Torniojaws (edited by Torniojaws 2010-08-04 11:45:53)

  • From: Finland
  • Registered: 2008-01-01
  • Posts: 15

Re: Release candidate of the Windows driver 3.x (3.013) now available:

After updating to v3.016, it seems that the front panel potentiometer volume control no longer works fully on FF400. If I select for example L.1, and then turn the knob from 53 to eg. 40, it does not affect the actual output volume at all. If the setting was on ?, and I turn it to 53, the volume will still remain on mute. When I open up Firefacemix, the same channel (AN 1 + AN2) does not change when I turn the knob. It always stays in the same setting. This happens with ALL channels. I cannot adjust their volume through the actual FF400 unit. I can only do it through Firefacemix, which interestingly does change the value on the 7-seg screen of the FF400. If I try to adjust it from FF400 right after this, it still does not change the value in Firefacemix.

Windows 7 64-bit
FF400 firmware v1.70
FF400 driver v3.016

Torniojaws's Website

108 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,599

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Works on my system. Did you cold reboot everything after driver and firmware installation?

Regards
Matthias Carstens
RME

MC's Website

  • From: Finland
  • Registered: 2008-01-01
  • Posts: 15

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Yes.

My previous driver was v2.9992, in case it matters. I installed v3.016 through Device Manager (Fireface -> Driver -> Update driver -> Browse).

Torniojaws's Website

  • From: Finland
  • Registered: 2008-01-01
  • Posts: 15

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Well, rebooting seemed to solve it in any case. Perhaps just some quirk...

Torniojaws's Website

111 Reply by Altiverb (edited by Altiverb 2010-08-08 14:02:59)

  • Registered: 2010-08-08
  • Posts: 2

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Hi,

Recently member of this forum, but ff800 user since 2008.

My hardware :

Apple Mac Pro Octo 2.26Ghz
8 Go RAM DDR3
Nvidia GT120
TI Chipset

Running on Win XP sp3 & Snow Leopard, with Steinberg Nuendo 4.3

Firewire 800 user.

I've recently upgraded to 3.016 on windows XP, 'cause of few BSOD (fireface.sys) happening with 2.9992. Since, i've got big troubleshootings here : Constant BSOD when opening a nuendo session (portcls.sys error).

I'll try other 3.XX releases, and let you know if something happens. EDIT : Well, no other release of the 3.XX. Let's go back to 2.9992 for the moment...

Regards

  • Registered: 2007-05-01
  • Posts: 128

Re: Release candidate of the Windows driver 3.x (3.013) now available:

I had the same problem... (portcls.sys) BSODs with 3.012 and 3.013. Hasn't happened with 3.016 yet (knocking on wood).

Regards,

    b.

https://granurise.com
  • Registered: 2008-01-01
  • Posts: 3,025

Re: Release candidate of the Windows driver 3.x (3.013) now available:

Make sure to either use the "High Performance" power-profile or set the PCI Express energy-saving to "OFF".

  • Registered: 2007-05-01
  • Posts: 128

Re: Release candidate of the Windows driver 3.x (3.013) now available:

MC wrote:

Please go back to an earlier driver to verify it does not happen then. This behaviour is usually caused by a high CPU peak which affects FireWire transmission on a level below our driver, so I think it will show up with other drivers too.

I was able to get the same behaviour with v2.9992 also. But I had to try really hard. The only program that produced that effect was CoreTemp ( http://www.alcpu.com/CoreTemp ) which also creates FW communication errors.

In my case... v2 driver seems to be more robust than v3 driver.

Regards,

     b.

https://granurise.com