Future Audio Forums » Beta Testing Forum

Mac - Intel Core 2 Duo issues with RTAS?

(35 posts)
  • Started 2 years ago by jordanstoner
  • Latest reply from jordanstoner

  1. I'm running a Macbook Pro, 10.5.7, 2.66 GHz Intel Core 2 Duo, 4 GB RAM. I'm experiencing massive problems when running the RTAS version within Pro Tools (version 8.0cs3). It doesn't matter if I dedicate only one or both cores of my processor in the playback engine - I always run into buffer errors during playback / record (DAE error -9127 / -9128, which are CPU related buffer errors). This occurs even on a simple session with only Circle loaded.

    The standalone version works without error - but therein lies the problem. I can't use Circle without Pro Tools as a host in my workflow. I noticed you only list support for Core Duo processors - is there an ongoing issue with Core 2 Duo machines?

    Any help is appreciated.

    Posted 2 years ago #
  2. Additional info:
    When Circle tries committing anything to disk (i.e: recording to a new audio track via a bus or bouncing to disk via the DAW), immediate buffer errors ensue. Performance takes a massive nosedive and I cannot record more than two or three seconds (if I'm lucky). -6101 / -9128 errors.

    I have tested with all combinations of the Digidesign Playback Engine (adjusting to all possible H/W buffers, disk buffers, 1 or both processor cores, et al). I have tried with empty sessions where Circle is the only RTAS plug-in. I've also tried recording to the internal drive as well as an external F/W drive.

    Furthermore, I cannot use JackRouter because of Pro Tools' proprietary driver design. At this juncture, it would appear that there is a compatibility issue between Pro Tools 8, Circle, and Intel Core 2 Duo's.

    Posted 2 years ago #
  3. Ok, thanks Jordan for this info. I will look into it over the coming days.

    Gavin.

    Posted 2 years ago #
  4. Any word on this yet?

    Posted 2 years ago #
  5. User has not uploaded an avatar bootyben
    Member

    SAME PROBLEM HERE !!!

    On Macbookpro intel core 2 duo
    Mac osx 10.5.8 and Pro tools 8.1
    It was working perfectly with tiger and Protools 7.4

    and it's a shame 'cause I LOVE THIS PLUG !!!!
    and i can't use it now ....

    Cheers
    ben

    Posted 2 years ago #
  6. There haven't been any replies to this yet... is it being actively looked into?

    Posted 2 years ago #
  7. User has not uploaded an avatar bootyben
    Member

    Hey FAW people PLEASE ANSWER !!!!
    I bought your plug guys....

    Posted 2 years ago #
  8. Hi,

    We are still looking into this, I will post an update in the coming days on how things are progressing.

    Gavin.

    Posted 2 years ago #
  9. danwilde danwilde
    Member

    same problem here!
    here is the email i sent to FAW.
    o whom it may concern,
    i am having technical issues with CIRCLE v 10.7 in pro tools 7.3.1 on a G5 2.5 GHz PowerPC with 8 GB DDR SDRAM.
    circle seems to be hoggiing all my system resources. and is also making my session crash. this is without and other plugins active.
    even when i increase the CPU usage limit, i still get horrible glitches and then no sound output at all.
    your help in this matter is greatly appreciated.
    thanks
    dwilde

    Posted 2 years ago #
  10. Hi Dan,

    We have your support message and are looking into this.

    Gavin.

    Posted 2 years ago #
  11. Has there been ANY progression with this case? Your support e-mails say that you will endeavor to respond in 24 hours. So far, you've really dropped the ball on giving us ANY information, aside from "we'll let you know in the coming days," which of course never happens. At this point, I've owned a product that I cannot use for FOUR MONTHS, and your support has been non-existent. WTF guys?!?

    Posted 2 years ago #
  12. Hi Jordan,

    Thanks for your patience, we are working on finding out what the problem is right now. We plan to have a beta ready in the coming days, this issue however is proving less trivial than we originally thought. But again, please be patient, we are working on it.

    Gavin.

    Posted 2 years ago #
  13. If you need someone to help you beta test this, please let me know. I have a tech support background with audio applications. If not, please keep us updated on the progress.

    Posted 2 years ago #
  14. Hi Jordan,

    Thanks for the offer of help. We will add you to the beta tester list.

    Gavin.

    Posted 2 years ago #
  15. User has not uploaded an avatar bootyben
    Member

    Guys !!
    still waiting, have lot shit of remixes to do and can't use your plug..
    WE ARE IN 2010 PEOPLE..

    HAPPY NYE and please make that plug work with PT !!!

    CHEERS

    Posted 2 years ago #
  16. Indeed. Even after my fuming in another thread, you have yet to update anyone on the status of Circle. If you've added me to the beta tester list, then you must not be testing anything - no e-mails. And it would appear that you lied to save face in my "FAW Support is dropping the ball - HELP!" thread. Though you said you "replied to this through support@futureaudioworkshop.com," I was never sent an e-mail or any other form of communication.

    At this point, you've really put a black spot on your company and it's support offerings. I think I'm actually more upset that you made such a cool, flexible, and modern plug-in in the first place - I've dealt with the fact that I wasted $200 on software that will obviously not be supported, but to see the potential of what you could have had die like this is just sad.

    I have never seen a company that is so reluctant to respond to paying customers. And I can only assume you lied to shut me up in another thread, and that's just pathetic. Good work.

    Posted 2 years ago #
  17. Hi Jordan,

    We do reply to threads here.

    I appreciate that you do have a problem with Circle and Protools 8. This has proved to be not a trivial bug fix and we are working on it. But if we have been unable to fix it thus far, it is due to the ever moving goal posts of the hosts and not an intentional unwillingness to provide a working protools version.

    It is never our feeling to do what you describe above, but if you feel this way then we take it on board and will communicate better with you.

    Gavin.

    Posted 2 years ago #
  18. To blame the "hosts" isn't a fair bag. This problem has existed continually on one platform for quite some time. Get it fixed, then move forward. I'm sure Avid's 3rd Party developer team wouldn't look too kindly on you placing the blame at their feet. No, the ball has been in your court to get things up and running under PT 8 - and that is a separate issue from Snow Leopard compatibility or any other hot fires you might have on the kettle.

    Regardless the size of your team or the incredibly large workload you may have in front of you for various issues, I take issue with the fact that you have not provided simple *voluntary* updates to your user-base. It takes all of five minutes to type "we've made some progress on the bug today, but uncovered a new issue - expect a new version or beta to be released within the next [few days, week, month, etc]." Your lack of doing so suggests that either you are not working at all on the fixes, or that you simply can't be bothered to tell your users if you are, which makes you seem like you are not interested in supporting your product. Both things have to be in place to be considered a successful software development team - and I would urge you to consider this as you move forward. So far, you have posted reactively, and not proactively.

    Rely on your user-base to help you test by offering beta versions intermittently. This makes your work evident and showcases your level of support, while at the same time letting you off the hook for instability during the beta test cycle. If you don't have the tools to do that, then simply update us on your progress every week or two. Then we don't have to keep coming back angrier and angrier that nothing new has been posted, even though you have made promises to the contrary. Set expectations properly - don't tell us you "plan to have a beta ready in the coming days" and not have anything ready a month later.

    Lastly, offer a level of support that suppresses posts like these. It does nothing for me and only makes all involved look bad.

    Posted 2 years ago #
  19. Hi Jordan,

    We take all you say on board and will improve our communication moving forward. This thread will be now used for updates on the RTAS issue.

    Gavin.

    Posted 2 years ago #
  20. User has not uploaded an avatar bootyben
    Member

    Back to buisness..

    no uptades WE ARE NOW in April 2010 (ok april its tomorow...)

    But still producing WITHOUT your good plugin....
    Pissing me off to wait for it !!!

    Hope you're really working on it....'cause my 1rst post was 5 Fuckin' monthes ago...

    Ben.

    Posted 1 year ago #
  21. FAW certainly has been working at a snail's pace. No roadmap updates, either... I've voiced my opinion on this matter rather loudly in the past, but I do want to let you know that I'm still here and check this board at least twice a week.

    At this point, I would like to ask that the ongoing issue of lack of communication be escalated to someone who has the time and inclination to reply to FAW's customers and give reasonable expectations. That certainly can't be too much to ask for. Sorry, Gavin, but you're just not providing a level of service that one expects from a software manufacturer.

    Posted 1 year ago #
  22. FYI - here's a "time-stamped" rundown of your responses to this issue. The bold text may give you a clue as to why I think your support has been inadequate.

    7 months ago:

    "I will look into it over the coming days."

    5 months ago:

    "We are still looking into this, I will post an update in the coming days on how things are progressing."

    4 months ago:

    "Thanks for your patience, we are working on finding out what the problem is right now. We plan to have a beta ready in the coming days, this issue however is proving less trivial than we originally thought. But again, please be patient, we are working on it."

    Apparently, "coming days" is an apocryphal reference to some distant point in time just before the universe implodes in on itself. Perhaps "End of Days" should be substituted...

    2 months ago:

    "We take all you say on board and will improve our communication moving forward. This thread will be now used for updates on the RTAS issue."

    If improved communication is taken to mean complete radio silence, I could reasonably agree with you on this last point. At least you've not ladled out any false hopes from your seemingly bottomless trough of disappointment. Compliments to your sous-chef for perfecting the bitter aftertaste of buyer's remorse.

    Posted 1 year ago #
  23. Hi guys,

    We monitor the forum everyday, you just need to ask and we will reply.

    The current state of play is that we have been trying to do a build specifically compiled for the Intel Core 2 Duo. However, when we issue the beta for test, while working here on our test system, so far the plug-in fails to load on other peoples.

    Please send a mail through to support@futureaudioworkshop.com and I will forward the download link to the beta.

    Gavin.

    Posted 1 year ago #
  24. "We monitor the forum everyday, you just need to ask and we will reply."

    This is the problem, Gavin. You have promised to post proactively on this issue, rather than as a reaction to us.

    Imagine you take your car into the shop. The mechanic takes a look at the engine and tells you he'll investigate. You don't hear back for a couple days, and you start to get worried. You call the repair shop and they tell you that they're still working on your engine, and that it looks more involved than originally thought. You wait again for a call that never comes - a week later, you call and ask about your car... Still the same answer, but this time you're upset that you've been inconvenienced without word from the mechanic; you tell him to call you as soon as there is news. Again, another week or two go by, and no call. How would you feel? Do you think the repair center is doing their job? Will you ever see your car again? Sure, they pick up the phone when you call, but they don't ever call you - and it's YOUR care in the shop.

    Posted 1 year ago #
  25. Hi Jordan,

    I totally understand you point and again apologize for this.

    What happens at the moment is that we receive support cases to which we reply. In about 95% of these cases, the problem is resolved on the first communication. We however don't hear back if it worked or not, if it is silence then we have to infer that the fix has worked. This process though has led to a problematic situation for yourself, we are in the habit of waiting for you to enquire rather than updating proactively open cases.

    Gavin.

    Posted 1 year ago #
  26. I've downloaded the beta .dpm and moved it to my Plug-Ins folder, but Pro Tools throws this error on launch:

    "Pro Tools could not load the following plug-ins either because no valid authorization could be found, the iLok key was not connected or the plug-in was damaged:

    CircleRTAS.dpm"

    Also sent to support@futureaudioworkshop.com

    Posted 1 year ago #
  27. Same error as above post with second beta .dpm

    Posted 1 year ago #
  28. Beta #3: no error on startup, but plug-in is not listed as an insert.

    Posted 1 year ago #
  29. Haven't heard anything from you in awhile, Gavin. Sent you an e-mail last week... Any progress?

    Also, how's Snow Leopard support coming?

    Posted 1 year ago #
  30. User has not uploaded an avatar bootyben
    Member

    Still waitin' for Snow leopard and PT8

    Posted 1 year ago #

RSS feed for this topic

Reply »

You must log in to post.