We are happy to announce the latest TC Audio Interface Software release candidate for your preview.
TC Audio Interface Software 3.2 release candidate f10 for OSX, Windows 64bit and 32bit

If you need to submit crash dumps, screen shots or any other files describing failures please do so to [email protected].
[list=*]

OSX:
[list=*]

kernel panic logs can be found at /Library/Logs/DiagnosticReports

application crash logs at ~/Library/Logs/DiagnosticReports

kernel logs at /var/log/kernel.log; 10.8+ kernel logs at /var/log/system.log

Windows:
[list=*]

install logs can be found at \Windows\inf\setupapi.dev.log (XP: \Windows\setupapi.log)

kernel crash dumps at \Windows\MiniDump

application crash dumps can be enabled by following Collecting User-Mode Dumps

Thanks a lot for all your investigations! This is very much appreciated!


Whats new
3.2 release candidate f10
[list=*]

based on TC Applied Technologies DICE driver 4.1.3 with lots of bug fixes and performance improvements
[list=*]

Windows release notes

OSX release notes

Some hints to make a succesful installation: [list=*]

Supported OSX versions are Mointain Lion (10.8) with 64bit Intel kernel, Lion (10.7), Windows Vista/7/8 and Snow Leopard (10.6) with 32bit and 64bit Intel kernel and Windows XP-SP3 with 32bit Intel kernel
it probably also works with Leopard (10.5) with 32bit Intel kernel; but we will not test, nor provide support anymore

Known issues:
[list=*]

OSX[list=*]

Reboot needed after installation (but not enforced by installer)

We are happy to provide an preview on TC Audio Interface Software 3.5
TC Audio Interface Software 3.5 for OSX, 64bit and 32bit Windows

Please find here the latest TCNear related development. Please always keep in mind that you should avoid using this software on a production machine, as regressions are to be expected.



Some advice to fix issues as quick as possible:
[list=*]

Please be descriptive as possible!
What seems to be obvious on your system, may seem completely different in our test setup.
"It doesn't work" is not a bug report.

Reproduce an issue! Include detailed steps on how to reproduce an issue in your report: What happened when your were doing what?

Verify an issue! Please make sure its not an user error or side effect of something. (It takes a lot of time to reproduce bogus issues here! Time we would rather spent in fixing issues.)

Always make sure we know your Konnekt hardware and TCNear software version, OS Version, if its 32 or 64bit, DAW Version (if related to the bug reported) and any other software involved in this bug.
Include all information also if you need to submit additional files to [email protected].

If you need to submit crash dumps, screen shots or any other files describing failures please do so to [email protected].
[list=*]

OSX:
[list=*]

kernel panic logs can be found at /Library/Logs/DiagnosticReports

application crash logs at ~/Library/Logs/DiagnosticReports

kernel logs at /var/log/kernel.log; 10.8+ kernel logs at /var/log/system.log

Windows:
[list=*]

install logs can be found at \Windows\inf\setupapi.dev.log

kernel crash dumps at \Windows\MiniDump

application crash logs can be enabled by following Collecting User-Mode Dumps

Thanks a lot for all your investigations! This is very much appreciated!



Whats new
3.5 f27
[list=*]

Maintenance release for OSX 10.11 "El Capitan" and Windows 10 compatibility

based on TCAT firewire driver 4.2
[list=*]

OSX release notes

Windows release notes

OSX: completely removed PPC targets from the universal binaries of Plugins and all TCNear system software, TCNear system software has been updated and based on latest SDKs and dev tools to ensure compatibility with latest OSX versions

Windows: TCNear system software has been updated and based on latest SDKs and dev tools to ensure compatibility with latest Windows versions

Known issues:
[list=*]

TCAT is currently working on finalising driver compatibility for OSX 10.11 and Windows 10. The final TCNear software update will contain the updated driver version.
The included TCAT driver version 4.2 can be installed on machines running OSX 10.11 and Windows 10. There are however issues with certain setups.

OSX[list=*]

Can only be installed on OSX 10.8.3 or later

Windows[list=*]

requires Windows 7 or later

I noticed yesterday that the UM2 Windows drivers made my Behringer are gone.

Knowing that the UCG102 shares the same driver, I went to it's download page, and it's also gone:

http://www.behringer.com/EN/Products/UM2.aspx
http://www.behringer.com/EN/Products/UCG102.aspx

What's going on here? Did I catch the website during an update gone wrong? Or is something else going on?

Ultimately ... are they coming back?

Any help would be appreciated,
Seth

For anyone who might be interested, the X Air iEQ App for iPhone and iPad is available in the App Store:

https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/app/1106383513



The App permits remote control of the DEQ racks in the X Air series of consoles, and also allows Auto-EQ of FOH and Monitors.

This release is not maintained by TC. Please don't bother support if anything is not working! TC is not involved in any of the development anymore. TC kindly offered this place for sharing.

unofficial PowerCore 4.5 beta 72
macOS, Windows 64bit, Windows 32bit
(by downloading pre-released PowerCore software you agree to the conditions outlined at welcome!)

If you need to submit crash dumps, screen shots or any other files describing failures please do so solely to [email protected].
[list=*]

macOS:
[list=*]

install logs at /var/log/install.log; uninstall logs at /var/log/powercore_uninstall.log

kernel panic logs can be found at /Library/Logs/DiagnosticReports

application crash logs at ~/Library/Logs/DiagnosticReports

kernel logs:
[list=*]

prior macOS Sierra: at /var/log/system.log

from macOS Sierra on: issue log stream --predicate 'senderImagePath contains "PowerCore"'

Windows:
[list=*]

install logs can be found at \Windows\inf\setupapi.dev.log

kernel crash dumps at \Windows\MiniDump

application crash logs can be enabled by following Collecting User-Mode Dumps

Thanks a lot for all your investigations! This is very much appreciated!


Whats new
4.5 b72: (P/OS 4.4.0f46)[list=*]

macOS[list=*]

fixed regression in b71 leading to instability and sluggish behaviour

Windows[list=*]

no changes - same as b71

Some hints to make a successful installation: [list=*]

Backup any separately installed TC plugins! They might get overridden

Supported OS versions are macOS 10.8.3 and later (with 64bit kernel) and Windows 7 SP1 + KB3033929 and later (with 32bit and 64bit kernel)

macOS: If updated from a previous PowerCore 4.5 installation a reboot is required!

Windows: Please ensure that you have recently updated your system (otherwise certificates needed to check if the driver is correctly signed could be outdated leading to "device cannot start").

All PowerCore Firewire versions are supported, PCIe, PCI MkII and Classic PowerCore PCI are supported.

Known issues:
[list=*]

PowerCore/PCIe and PCI MkII do not work with Apples thunderbolt update to the PCIFamily.kext included in macOS 10.8.4 and later

I've been having this problem since I switched to Win7 x64 about a year ago using beta drivers, but now with the v2.5 drivers out, it's time to get this fixed.

The problem is that WDM simply loses all sound sporadically. ASIO continues to function when this happens. To fix it, I have to either unplug/reconnect the FireWire cable to the computer or restart the Windows Audio system service.

Here's a description of the setup:
- My device is a Konnekt Live.
- The TC software package is version 2.5.0.6906, control panel is 2.5.0 r3583, and 1394 driver is 3.5.3.8786.
- My motherboard is an Abit IP35 PRO(P35+ICH9R).
- The FireWire chipset is an on-board TI TSB43AB22.
- I have no DPC latency problems or other sound cards (on-board is disabled).

I'm convinced this is a driver error, because:
- The exact same hardware did not have this problem under 32-bit Windows XP.
- The problem seems to occur more frequently when programs which make heavy use of sound are left open, such as webpages with Flash, video games, iTunes, etc.
- Restarting the Windows Audio service is a temporary fix.
- ASIO continues to work while WDM dies, indicating that it's not a FireWire problem.
- I have a friend with the exact same problem on a different computer with an Impact Twin.

My current work around is a bat file that restarts Windows Audio, it looks like this:

net stop "Windows Audio"
net start "Windows Audio"

The Event Viewer only has one type of recurring error which seems interesting, though I can't confirm if it correlates 100% to my audio loss problems:

Windows Audio Device Graph glitch threshold count exceeded 
                              Count   : 0x0x33

As a programmer by trade, this is exactly the kind of thing that frustrates me the most. I know it's a programming error, and I know that I would fix it if it were open source. But instead, I have to rely on TC to get it right. I think this is about all of the useful debugging information that I can provide, and I hope someone (preferably a developer) at TC will reply to me and tell me what the status of this bug is.

If TC can't fix this, I'm not sure what to do about it. It looks like I could either get a new audio device (which I do not want to do, since this hardware is fine, if it just had proper drivers), or I could start disassembling the TC driver and learn some kernel hacking to try and fix it (which I'd love to be able to do, but I just don't have the time).

If anyone else has a clue as to what might technically be wrong (in case I go the driver hacking approach), please pitch in your ideas to this thread.

Hi Everyone,

The X32 features a comprehensive Scene Management system that allows all parameters and settings to be instantly recalled at the touch of a button. The 100 scenes on the X32 can be imported and exported via USB Stick and parameters can be eliminated from Recall using the SAFE options. In this Tech Talk we will go into detail about how to use the SCENES menu on the X32.

Scenes vs. Shows: Know The Difference
Scene - A scene is a single file containing a snapshot of the settings of the X32. When saving a scene, all parameters are ALWAYS saved. Upon recall, you have the options to "Safe", or prevent, certain parts of the scene from being recalled.

Shows - A Show File contains the 100 scenes that fill the slots of the X32's scene memory. Only a single show file can be loaded on the X32 at a time.
*NOTE: When recalling a SHOW from USB, ALL scene files on the X32 would be overwritten with the scene files from that show.

Import / Export from USB:
The X32 allows you to import and export both individual scenes and entire shows. Individual scenes can be saved to USB directly from the SCENES menu. To export a whole show, or to import a scene or show, press UTILITY while viewing the SCENES menu. You can also Copy, Paste, and Delete Scenes while viewing this UTILITY menu.

Using XControl for Enhanced Scene Management:
Aside from easy setup and greater control of your mix, XControl software expands the scene capabilities of the X32.
There are 2 main benefits to using XControl for Scene Management:
1. 100 More Scenes: When using XControl as an online editor with the console, you have access to a second page of 100 scenes. This means that while using XControl you have 100 internal scenes labeled “Console” PLUS the 100 scenes labeled “XControl” bringing the total scenes available using XControl to 200.
2. XControl has the ability to insert a scene between two scenes. This allows you to go back and create a space for a new scene at the beginning of the show without having to move all the following scenes down manually. This is particularly useful for theatre use with the X32.

Scene Safes:
As stated earlier, Scene Safes will EXCLUDE that parameter from being recalled. For example, when walking into a new venue that has an X32, you could bring in your USB stick and recall your scene but "safe" the routing so that you would not overwrite that venue's routing configuration.
This means that if you want to recall ALL parameters, all of these boxes need to be unchecked (not orange).

Descriptions of Safe Parameters:
"Home" Screen Scene Safes: The safes on this menu are on a scene-by-scene basis. This means that you need to check the desired safe on each scene you plan to recall individually.

Routing I/O - All settings in the ROUTING menu
Output Patch - Only the output pages of the ROUTING menu
Preamp (HA) - Mic Gain and Phantom Power for inputs
Configuration - Any recallable settings in the SETUP menu such as link preferences, panning mode, and bus pre-configuration
Chan Process - Channel Strip processing for INPUT channels (starting with phase flip)
Mix Buses - Mix Bus "Channel Strip" processing
Effects - All settings within the EFFECTS page
Talkback - All settings within the Talkback Settings

The settings on the following pages are global and will apply no matter which scene is recalled:

"Param Safe" Screen Scene Safes: Allows you to globally safe certain parameters across all input channels and mix buses. Global console safes such as routing and configuration are also found here. For example, if you choose Preamp (HA), then all mic gains would be safe from recall across all input channels.

"Chan Safe" Screen Scene Safes: Safes all parameters for a specific Channel, AUX / FX Return, Mix Bus, Matrix, DCA Group. This screen also allows you to individually safe any FX slot. One use for this could be the MC's mic at an event featuring multiple acts. You could safe his channel so that as you move through different scenes his mic would be unaffected, even if the scenes you are recalling have different settings for this input channel.

A Note About Presets vs. Scenes:
In addition to Scenes, the X32 also features preset libraries. These "presets" are completely independent of scenes and allow you to save your favorite channel strip, routing, and FX settings. These are really handy because they can be loaded at any time and in any scene. This would allow you to save your favorite vocal EQ or routing setups without having to use a scene slot.


Things to remember when using Scene Management:
1. If you want to recall all settings, make sure all safe options are UNCHECKED.
2. The Safes on the Home Screen are set individually, scene by scene. For global safes, use the “Param Safe” and “Chan Safe” pages.

The X32 as you can see has great flexibility in Scene Management. We hope this Tech Talk will help you better understand and take advantage of these features. As usual, feel free to post your questions here. We will be back next week with another edition of Tech Talk.

Best,
John DiNicola
Senior Specialist, Product Support
MUSIC Group
BEHRINGER