Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[b00ter]

The latest update for MC 20 seems to have created a TBIA error now and no audio playback. Can I just uninstall the update?

[glynor]

You can almost always just install older builds of MC "over top" of the current one without first uninstalling.  If needed, though, yes, you can uninstall and then reinstall whatever build you want.

When you uninstall, you can choose to preserve your Library and Settings.  For this kind of thing, you almost certainly should do so.

Before you do this, though: Make a Library Backup first.  That will let you restore all of your settings if you accidentally remove something you shouldn't have.

[glynor]

Also... I don't know what a TBIA error is, and it would probably be most effective at solving the issue if you explain what is happening.  It is unlikely that it was the update that is causing the problem, or if so, there may be something just misconfigured.

[b00ter]

I searched TBIA and found this:

http://yabb.jriver.com/interact/index.php?topic=92936.msg640917#msg640917

Here is a sequence of events.

1. JRiver MC 20 notified me of an updated, so I installed update.

2. PC rebooted

3. After logging back into windows 7 64 bit, it prompted for a driver install, I clicked yes and everything went fine.

4. Opened MC 20 and noticed no audio on anything I played, so I rebooted the PC and now every time I log into windows I get this TBIA error.

[glynor]

Do you have an M-Audio sound device?

[b00ter]

I have an m-audio torq Xponent midi controller with built in sound card. I haven't used it in over a year.

[glynor]

That is caused by your M-Audio device or its drivers, not by MC.  The reason it happened when you upgraded MC is that MC now includes the WDM driver feature, and apparently the bug in M-Audio's drivers is triggered by changing your active audio device or attaching new devices.

https://www.google.com/search?q=m-audio+tbia+the+data+is+invalid&ie=utf-8&oe=utf-8&aq=t

You could have triggered the same thing by plugging in a USB headset or anything else like that.

[b00ter]

Thanks for clearing that up