Ran intoTwo Problems with Pro Tools - **FIXED!***

Jack Stoner · Post by **Jack Stoner** » 14 Nov 2011 6:50 am

I've posted on the Avid forum and the gearslutz forum but haven't had any responses.

I've run into two problems with Pro Tools.

1. I have a Frontier Tranzport controller. It works OK in Sonar. I have set it for "Pro Tools(HUI)" which is what Frontier says to set it to work with Pro Tools. I've got it setup in Pro Tools according to Frontier's instructions. From what I can tell it's working as I can change items in Pro Tools using the Tranzport however I keep getting an error message "Pro Tools is unable to communicate with HUI, Power cycle HUI and check for it's communications". I've "power cycled" it, I've reinstalled the drivers, restarted the PC, etc. I can't find what is causing the error.

2. I have an Edirol PCR500 MIDI keyboard. Edirol is not listed in the MIDI devices. Is there any way to still use this?

Tony Prior · Post by **Tony Prior** » 14 Nov 2011 9:29 am

Well, I tried many times to get my Zoom R16 to act as a controller for PT8, the DAW see's it, it just doesn't function, I suspect that I have missed a driver or something, it's not an issue as I doubt I would use it anyway !

I did get my MAUDIO Oxygen 25 key keyboard interface/controller to work right away, I can use that as a controller as well.

Not sure about what Jack's issues are other than we have too much stuff to plug in now !

t

Jack Stoner · Post by **Jack Stoner** » 14 Nov 2011 10:30 am

The Edirol is made by Roland. Roland is listed but not the Edirol or that model number. But, there has to be some way to use it.

The Frontier Tranzport (which is a wireless controller) appears to work, just keep getting the error message. I have checked the box on the error message not to show it anymore, but that doesn't really fix the problem.

The Tranzport is a great unit, I can set it by my steel when recording and control the record, stop, rewind, start, play, track, etc.

Jack Stoner · Post by **Jack Stoner** » 17 Nov 2011 3:07 am

OK, the MIDI with the Edirol PCR500 is solved. It was a "newbie" cockpit error. I was looking at the wrong MIDI setup in Pro Tools. After going through the MIDI introduction in the Groove 3 tutorials for the second time I saw where I "went wrong".

I still have the Tranzport control surface problem. I have checked the box in the error message not to show this again and the Tranzport appears to be working OK, but it still bothers me that the program is seeing some type of error.

Michael Maddex · Post by **Michael Maddex** » 17 Nov 2011 7:51 am

Jack Stoner wrote:. . . I still have the Tranzport control surface problem. I have checked the box in the error message not to show this again and the Tranzport appears to be working OK, but it still bothers me that the program is seeing some type of error.

Jack, I'm afraid that this is going to sound smart-ass, but it's not intended that way. Maybe the underlying error is that an error message is displayed when there is no error. Whew, I managed to get that out. Anyway, it wouldn't be the first time there was a bug in error reporting code. Just my almost $0.02 worth. Have fun with it.

Jack Stoner · Post by **Jack Stoner** » 17 Nov 2011 1:10 pm

Michael, could be a program bug. But as a computer techie and a one time programmer (at NASA) it bothers me that it did come up.

Then again it could be a legitimate error....

Tony Prior · Post by **Tony Prior** » 18 Nov 2011 8:39 pm

I would suggest you not blame PRO TOOLS so quickly but rather Frontier. They are the third party and for all we know they used a basic code from an early release of Pro Tools.

I would use Pro Tools see how it goes and not execute any add-ons at this time. I have been using PT8 for two years, NO ISSUES. Very stable platform. But I did have an issue getting the Zoom R16 to function as a Control surface and of course Zoom advertises it works great out of the box.

There are way too many variables mixing different products and so called functionality features. Of course everyone claims they work great with all DAW's..and all PC's, or MACS...Maybe the Frontier firmware has a bug..who knows...

just my take

t

Jack Stoner · Post by **Jack Stoner** » 19 Nov 2011 3:46 am

The Frontier Tranzport has been around for a long time and from what I find on other forums has been used in Pro Tools for a long time. I can't find any other reports of Pro Tools problems with this unit. But I will agree the Tranzport must work with Pro Tools, not that Pro Tools must work with the Tranzport.

It may still be something I'm not setting up correctly, as all the functions appear to work, but I can't get any answers on the Avid or gearslutz forums.

This is the ONE control surface device I want to use with Pro Tools. It is a wireless device.

I see many posts about "bugs" with Pro Tools on other forums, so don't assume that it's not a Pro Tools problem.

Tony Prior · Post by **Tony Prior** » 19 Nov 2011 4:16 am

Another factor to not overlook, and the company I work for is seeing this now, very hi tech software with very hi tech analytical Instrumentation.

Some packages that were written to run on XP have '"wild and crazy" issues with Win 7..

Everyone says fully tested but I think what that really means is "fully tested up to where we stopped testing"

The Frontier is a kool device, I'm certain you will get it worked out..

t

Jack Stoner · Post by **Jack Stoner** » 19 Nov 2011 5:31 am

Tony, I have been using the Tranzport for several years with Sonar and Win 7. Frontier had a problem with with Win 7 but Frontier issued a new driver that fixed that problem. The problem had nothing to do with the DAW software and was just a bug that could cause a Windows shutdown problem.

I worked in computers for many years ("BPC" - Before PC) in all phases, maintenance, operations and as a NASA programmer. With the complexity of modern Operating Systems and applications software, I don't think there is a piece of "commercial" software or Operating System around that doesn't have bugs. My last 23 years working (until I retired) was as a LAN/WAN Network and Hardware Help Desk manager (and site engineer) - I've probably saw it all.

Tony Prior · Post by **Tony Prior** » 19 Nov 2011 2:20 pm

Jack Stoner wrote:software, I don't think there is a piece of "commercial" software or Operating System around that doesn't have bugs. I probably saw it all.

Jack , add one more !

I feel we just need to be cautious in stating that errors are PRO TOOLS related, or any other software related,lots of folks reading may get an improper impression. Way too many variables to consider.

let us know when you get it worked out..

t

Jack Stoner · Post by **Jack Stoner** » 20 Nov 2011 3:17 am

Well, I'm not really saying anything that hasn't been said many times on other forums. Problems/complaints that I saw did not cause me not to buy the software.

Back to the original problem, just trying to find out if I missed something in the PT setup or if it's an erroneous error message. It appears to be working properly and I can't find anyone else that reported having this same issue with the Tranzport.

Tony Prior · Post by **Tony Prior** » 20 Nov 2011 6:30 am

I hear ya Jack, if it's any con0solation, I attempted to get the Zoom R16 to function with PT as a controller when I first got it, I read the posts on the forums and tried many of the exotic procedures, still could not get it to function. It's not all that important to me so I stopped trying and started "tracking" instead.

I would be curious however to see what you come up with as the Tranzport is a neat interface, worthy of consideration.

In the meantime I just record in auto loop sections if need be. The fact of the matter is that Clive Davis isn't waiting on a track from me so nothing I am doing has any urgency whatsover!

t

Jack Stoner · Post by **Jack Stoner** » 20 Nov 2011 8:21 am

Tony, it will be a while before I'm completely converted to Pro Tools. I've got several paying sessions coming up before the end of the year, one a live "on site" recording, and I'll use Sonar for those.

As the Tranzport works, I just have to find out why I get the error message.

John Gould · Post by **John Gould** » 20 Nov 2011 8:51 am

Jack, I know you are the man when it comes to computer stuff but have you thought about other wireless devices in and around your system causing a communication problem. Or even other RF flying around causing the problem. Please let us know if and when you find a fix. I use a wired controller but would like to use something wireless.

Jack Stoner · Post by **Jack Stoner** » 20 Nov 2011 10:18 am

I eliminated any wireless around/near the PC and it didn't make any difference. However, the recording program is "looking" at the USB port interface and it's status.

As it works OK with Sonar, it's back to a possible setup in my Pro Tools or a false error message since it appears to function properly in Pro Tools. I haven't used it to control recording in a track but it does start/stop playback, rewind, change other control parameters, etc.

Peter den Hartogh · Post by **Peter den Hartogh** » 20 Nov 2011 10:36 am

I use TranzPort with Cakewalk Sonar.

But, I believe that in order to use TranzPort in Pro Tools, the PT installation must include support for the Mackie HUI control surface.
Some versions of PT require that you copy a special HUI controller support file from the PT installation CD into your PT folder.

Or else there is an underlying problem with Win7?
Maybe run things as "WinXP compatible"?

Jack Stoner · Post by **Jack Stoner** » 20 Nov 2011 2:04 pm

According to what I find, on the Avid site, the support for HUI devices in MP9.0.5 (what I have) is the same as other current versions of PT, such as PT10 and PT10HD.

PT9.0.5 runs in native Win 7 64 bit, no need to run in a compatibility mode. Same way with the Tranzport. The Tranzport is set to "ProTools(HUI)" mode.

Scott Henderson · Post by **Scott Henderson** » 22 Nov 2011 7:11 am

Jack I can't help you with the error message but I can tell you that Avid's Customer service is not good...I've had the same response when trying to get help from them. The best trouble shooter/trainer has been you tube....Just my .02cents...

Jack Stoner · Post by **Jack Stoner** » 22 Nov 2011 3:04 pm

The Tranzport appears to be working OK. I've checked the box not to show the error message. But, it still gets back to "did I miss a setting?" or is it just an erroneous error message that I should disregard.

John Gould · Post by **John Gould** » 22 Nov 2011 5:01 pm

Ok it might be something as simple as your operating wireless and every other HUI controller is connected either via usb or midi. Pro tools might not be smart enough to know how it's connected. I can't imagine you missed something in the setup of the software. Let us know if you find out exactly what's going on

Jack Stoner · Post by **Jack Stoner** » 23 Nov 2011 2:38 am

The Tranzport has been around for a long time and has been used with Pro Tools for a long time. Actually the Tranzport was discountinued a couple of years ago (dumb move by the company). I would have thought any problems because it's wireless would have surfaced before now. It has a USB interface/transceiver.

Jack Stoner · Post by **Jack Stoner** » 23 Nov 2011 7:41 am

Frontier Tranzport problem with Pro Tools is FIXED!

The fix is to run Pro Tools as Administrator. I found this burried in the Frontier forum. If it's not run as Administrator, Pro Tools can have a communications problem with HUI devices and the USB connected controller. The thread in the Frontier forum about the problem referred to Pro Tools V7, but it obviously applies to V9 and possibly any version.

I didn't try the run as administrator before as Pro Tools supposedly set itself up so that wasn't needed. There was an info item, as Pro Tools was installing that it was setting itself up so it could be run without the administrator.

Tony Prior · Post by **Tony Prior** » 24 Nov 2011 8:36 am

Jack, is it fair to say that the TWO PRO-TOOLS problems were not actually PRO-TOOLS problems ?

The reason I ask is because there are a few here that are really down on Pro Tools .

Glad you got it worked out, next time I try to hook up the R16 I am going into the administrator mode as well... it makes sense.

t

Jack Stoner · Post by **Jack Stoner** » 24 Nov 2011 9:14 am

The two "Pro Tools Problems" were problems that I had with Pro Tools.

The Edriol PCR 500 was not a "Pro Tools" problem. It was my fault as I was looking at the wrong MIDI setup. But, it took a 3rd party tutorial (groove 3) to find the solution, it wasn't in the Avid documentation or on the Avid support site.

However, the second problem, I would call a Pro Tools "problem" because Pro Tools displayed a message when it was installing that it was setting itself up so Administrator didn't have to be used. But, as I finally found out, with HUI devices, such as the Frontier Tranzport, it needs to be run as Administrator. This was not a program problem as such, I learned that it's the way that Digidesign set up Pro Tools to allow 3rd party surface devices or "HUI" devices and this was not documented in the Pro Tools help or on the Avid support site or forum.

I'll probably have more problems with the program as I learn about it and use it. This is no different than someone learning how to use Windows, or MS Office, or a MAC, or another DAW such as Sonar, Reaper, Fruity Loops or whatever. None of this means the particular program is bad, just that the user has an issue they can't resolve and needs help.

Tony, I know you are set that Pro Tools is the best and nothing else is as good. There are many professional recording engineers that will argue with you on that. It is the predominant DAW software in Nashville but I've been told in some other areas, e.g. L.A. it's not. I'll let you know what I really think after I've had some time to learn more about it and use it in some recording projects.

The Steel Guitar Forum

Ran intoTwo Problems with Pro Tools - FIXED!*

Ran intoTwo Problems with Pro Tools - FIXED!*

Transport problems