Log in
Register
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Christian Nöding" data-source="post: 67740" data-attributes="member: 2637"><p>Re: X32 discussion</p><p></p><p>Hello Joe,</p><p></p><p></p><p>I'm using the X32 for about two weeks now. It is a great board which is working fine - when I'm using it without a computer. When I'm using it with my Cubase 64-Bit I've got strange driver-problems. Here some details about my computer:</p><p></p><p>Windows 7 64-Bit (German) with all updates (at least it should have all )</p><p>Steinberg Cubase 6.0.7 64-Bit</p><p>Behringer X32 Archwave Driver v5.25 (both Firewire and USB)</p><p>Behringer X32 with Firmware v1.09 (it had v1.02 on delivery)</p><p>Intel Core i7 processor</p><p>NEC Firewire-Card (PCI) or VIA Card (onboard) [Windows 7 delivers "NEW" and "OLD" firewire drivers. I've tested both]</p><p></p><p></p><p>some background:</p><p>I'm using digital recording-interfaces for several years - so I'm not completely new to this. I've used a TASCAM US1641 (USB) and two Alesis MultiMix 16 Firewire for recording with Cubase 4 and Cubase 6 (the Alesis were daisy-chained to record 32 channels). I've never had problems with the drivers even at very low latency. So my computer-setup should be OK.</p><p></p><p></p><p><strong>Problem with Firewire:</strong></p><p>The first time I've connected the X32 by Firewire. I've got a good signal input but suddenly I've received strange noise on top of the signal. I've made a recording of this: you can download the file from here, because I'm not allowed to attache ZIP-files or MP3s here: <a href="http://www.pcdimmer.de/X32_problems_fw.zip" target="_blank">noisyrecording</a>. I had to increase the buffer-size to 40ms for each Input and Output - so I had 80ms turnaround-latency - but the noise is not the standard clicking, when the latency is too low so that the computer cannot manage it - it sounds like the board and the XUF has slightly different samplerates. OK, with this high latency it seems to work most of the time, but sometimes I have to change the buffersize several times to get the Firewire connection working. I've tried the firewire connection with an old Pentium M Notebook and everything was working - so it seems to be a problem with the 64-bit driver? I've tested with 32 in/32 out, 32 in / 8 out - same problem.</p><p></p><p>In the old(!) behringer-forum someone has written about the problem I've figured out with firewire, too. He had this after flashing firmware version 1.09. Is this possible? Is this a known problem and is someone working on it? Can I help you in some way?</p><p></p><p></p><p><strong>Problem with USB:</strong></p><p>Then I've tried the USB-Connection. Here the latency can be much lower, but sometimes I've got strange readings within Cubase in the field "Clock source" (please have a look at the attached pictures). But the board was working. Strange, but OK if it is working, but: yesterday I tried to record our band but suddenly cubase showed me 64 inputs instead of 32. The Archwave drivers seems to be able to manage multiple X32, but here the driver seemed not to reset the list. I did not have time to check everything - I simple rerouted the cubase-inputs to input 33 to 64 and it worked, but this is not a solution.</p><p></p><p>Some pictures of my setup (sorry for the german text):</p><p></p><p>Here with strange characters within the field "Clock source". The characters (here "t - g") are changing if I change something within the driver-dialog:</p><p>[ATTACH]151613[/ATTACH]</p><p></p><p>and suddenly here it is working ("Computer" as Clock-Source) - until I change something in the setup-dialog of the driver:</p><p>[ATTACH]151610[/ATTACH]</p><p></p><p>and here some pictures of the 64-inputs. As you can see, the clock-source is now "( - i":</p><p>[ATTACH]151611[/ATTACH][ATTACH]151612[/ATTACH]</p><p></p><p></p><p><strong>Minor Issue with XControl:</strong></p><p>I'm from Germany and I'm using a german character within my username. XControl starts with "IO ERROR" because it cannot access my home-directory which is name with a german "ö". I've solved this by creating a new username with only US-characters, but maybe it is easy to fix this for the next release <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile :)" data-smilie="1"data-shortname=":)" /></p><p></p><p></p><p><strong>Issue with Latency-Compensation on Cubase:</strong></p><p>On dub-recording I've figured out some problems with the latency-correction. Cubase automatically corrects the latency of the recorded material and moves the recorded audio on the timeline. For this Cubase takes the transmitted latency-information of the driver. I recorded some audio with lower latency, but Cubase moved the audio to much to the left, so it "over"-compensates the recorded audio. Maybe this problem is related to the problems above? I used the USB-connection for recording.</p><p></p><p></p><p>Thank you very much for any help!</p><p></p><p></p><p>kind regards,</p><p>Chris</p><p></p><p></p><p></p><p>PS: in the new behringer forum someone posted a problem about the 64-bit firewire-drivers, too. Maybe it is related to my problem? Here is the link: <a href="http://forum.behringer.com/showthread.php?352-x32-firewire-problem" target="_blank">Firewire-Problem</a></p></blockquote><p></p>
[QUOTE="Christian Nöding, post: 67740, member: 2637"] Re: X32 discussion Hello Joe, I'm using the X32 for about two weeks now. It is a great board which is working fine - when I'm using it without a computer. When I'm using it with my Cubase 64-Bit I've got strange driver-problems. Here some details about my computer: Windows 7 64-Bit (German) with all updates (at least it should have all ) Steinberg Cubase 6.0.7 64-Bit Behringer X32 Archwave Driver v5.25 (both Firewire and USB) Behringer X32 with Firmware v1.09 (it had v1.02 on delivery) Intel Core i7 processor NEC Firewire-Card (PCI) or VIA Card (onboard) [Windows 7 delivers "NEW" and "OLD" firewire drivers. I've tested both] some background: I'm using digital recording-interfaces for several years - so I'm not completely new to this. I've used a TASCAM US1641 (USB) and two Alesis MultiMix 16 Firewire for recording with Cubase 4 and Cubase 6 (the Alesis were daisy-chained to record 32 channels). I've never had problems with the drivers even at very low latency. So my computer-setup should be OK. [B]Problem with Firewire:[/B] The first time I've connected the X32 by Firewire. I've got a good signal input but suddenly I've received strange noise on top of the signal. I've made a recording of this: you can download the file from here, because I'm not allowed to attache ZIP-files or MP3s here: [URL="http://www.pcdimmer.de/X32_problems_fw.zip"]noisyrecording[/URL]. I had to increase the buffer-size to 40ms for each Input and Output - so I had 80ms turnaround-latency - but the noise is not the standard clicking, when the latency is too low so that the computer cannot manage it - it sounds like the board and the XUF has slightly different samplerates. OK, with this high latency it seems to work most of the time, but sometimes I have to change the buffersize several times to get the Firewire connection working. I've tried the firewire connection with an old Pentium M Notebook and everything was working - so it seems to be a problem with the 64-bit driver? I've tested with 32 in/32 out, 32 in / 8 out - same problem. In the old(!) behringer-forum someone has written about the problem I've figured out with firewire, too. He had this after flashing firmware version 1.09. Is this possible? Is this a known problem and is someone working on it? Can I help you in some way? [B]Problem with USB:[/B] Then I've tried the USB-Connection. Here the latency can be much lower, but sometimes I've got strange readings within Cubase in the field "Clock source" (please have a look at the attached pictures). But the board was working. Strange, but OK if it is working, but: yesterday I tried to record our band but suddenly cubase showed me 64 inputs instead of 32. The Archwave drivers seems to be able to manage multiple X32, but here the driver seemed not to reset the list. I did not have time to check everything - I simple rerouted the cubase-inputs to input 33 to 64 and it worked, but this is not a solution. Some pictures of my setup (sorry for the german text): Here with strange characters within the field "Clock source". The characters (here "t - g") are changing if I change something within the driver-dialog: [ATTACH=CONFIG]151613.vB5-legacyid=5185[/ATTACH] and suddenly here it is working ("Computer" as Clock-Source) - until I change something in the setup-dialog of the driver: [ATTACH=CONFIG]151610.vB5-legacyid=5182[/ATTACH] and here some pictures of the 64-inputs. As you can see, the clock-source is now "( - i": [ATTACH=CONFIG]151611.vB5-legacyid=5183[/ATTACH][ATTACH=CONFIG]151612.vB5-legacyid=5184[/ATTACH] [B]Minor Issue with XControl:[/B] I'm from Germany and I'm using a german character within my username. XControl starts with "IO ERROR" because it cannot access my home-directory which is name with a german "ö". I've solved this by creating a new username with only US-characters, but maybe it is easy to fix this for the next release :) [B]Issue with Latency-Compensation on Cubase:[/B] On dub-recording I've figured out some problems with the latency-correction. Cubase automatically corrects the latency of the recorded material and moves the recorded audio on the timeline. For this Cubase takes the transmitted latency-information of the driver. I recorded some audio with lower latency, but Cubase moved the audio to much to the left, so it "over"-compensates the recorded audio. Maybe this problem is related to the problems above? I used the USB-connection for recording. Thank you very much for any help! kind regards, Chris PS: in the new behringer forum someone posted a problem about the 64-bit firewire-drivers, too. Maybe it is related to my problem? Here is the link: [URL="http://forum.behringer.com/showthread.php?352-x32-firewire-problem"]Firewire-Problem[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!
