Hi Wretch,

thanks for the reply, I don't think this function exists for the Mac version of Cubase. But if it solved you problem, I hope there is an equivalent!

all the latest.

Hi Timur,

I would start a new project, work for about 15 min, computer starts to fan hard, I continue, suddenly the ASIO bar from the performance monitor in Cubase starts to move back and forth and every spike gives a glitch. Even-though I thought I had fixed the kernel problem, I checked the Activity Monitor while this was happening and kernel was up 214%. Now if I do the same thing with my Mbox, I'm having no problems what so-ever.

I made a little screen-video of it, I don't know if I can upload that.

Thanks for helping!

ruben

Does it happen when you are only using Nuendo/Cubase internal effects? Is there a way to reproduce your issues in a step-by-step manner?

TM usually does not change its state. Can you please explain in detail what is happening.

Your explanation mirrors what you wrote before.

> Totalmix goes to it's opening state

I have no clue what that means.

and how about the other questions,

thanks!

Driver: v1.72
Firmware: v115
Totalmix (no FX) 0.972

It does the same thing.
all the faders in the 3rd row go back to 0

very cool, will try that later, Thanks!
How about the other questions, are those also cubase related?

Official Support only reacts on the easy questions.
Fireface UC is unusable, still having massive issues with it.
My computer has brand new HD, clean OSX install, 8 gig of Ram, Latest drivers etc. it's fine, also works with other interfaces, but with Fireface Kernel goes nuts Asio goes nuts.

the facts:

MacbookPro 2.66 GHZ intel Core i7
8 GB 1067 MHz DDR3
7200 RPM HD
Osx 10.6.8
Computer checked all the way by Tekserve in NY, all good they say.
Driver: v1.72
Firmware: v115
Totalmix (no FX) 0.972

Cubase 6.5.1

Problems:

1. After 15 - 30 minutes of (light) use, clicks, pops on recording and playback, Kernel pretty high:
    http://www.youtube.com/watch?v=K5O1JGZlzQo

2. I can do bigger mixes on my internal audio on 2048 then on RME on 1024,  RME starts to sputter very soon. (official reply: sorry, there is no higher setting. This should not affect the software, though.) well it DOES!

I'm selling my device if I'm not getting some real replies within this week.

Official support: If you don't know an answer AT LEAST ACKNOWLEDGE me asking a question, don't answer the easy stuff and pretent that was it!!
Would be easy if there would actually be a person you can call of skype with!

Thanks,

Ruben

Since there is no ASIO in OSX, what exactly does this refer to?

If there were an issue of the FF, it would likely turn up straight away, there is really nothing that can "build up" over time here. On the other hand, within your software or specific plgins, there could be several things like memory leaks or so

Please realize it is not the audio interface that "sputters", nor does it actively cause this. The signal that is being sent to the driver from Cubase already contains these dropouts, they occur when the software can no longer handle its tasks within the set latency time. This points to a performance issue of some sort.

While we can help tracking down issues, it is apparent that the actual issue is taking place on the side of the computer and software. The FF is in no way involved in rendering plugins or instruments inside your software. Higher latency would not likely help here, it might delay this specific buildup and subsequent dropouts, but won't likely prevent it.

Since there is no known issue or common problem here, please do not expect an immediate solution, this will require some research on your part. Sometimes the cause of similar mysterious issues turns out to be some software or hardrdware component that was never mentioned.

Regards
Daniel Fuchs
RME

@Timur,   bought my mac in 2011 but just found out with the serial it's a halfway 2010 Macbook, I can get you a simple cubase project but I also have these problems just when I'm tracking with nothing on it, no VST's no plugs, nothing, even while just recording one track, after a while the kernel starts to act up.
I do appreciate your help though!

@Daniel Fuchs,

the ASIO I'm referring to you can see in the Youtube video, in Cubase: VST Performance, it's the amount of CPU used I guess, all jerky because the Kernel is eating all the CPU.

Maybe there isn't a problem with the device but I can't explain why I only have these problems with the RME unit and not with my mBox, firepod or a Duet2. To me that seems like the Device is not working or the Drivers are bad. Also I'm not sure how I can find out what leaks.

I understand the Buffer size problem but again, I can't explain why I can do bigger mixes on my mbox/Duet/Buildinaudio etc on 2048 than on the Fireface on 1024. if it's in the computer shouldn't it be a problem with all Devices?

I understand your reasoning about the problem being a software/computer issue and I'm aware of the fact that I need (and have done so) to do research, it's all I've been doing in the past 2 weeks instead of all the work I need to finish. I've brought in my computer twice for check-up, I've been all over the web trying to find a solution for this problem but I can't find one. Besides that I'm glad you are answering these questions, I know we've been in contact over the mail and I've asked different questions at different times but if there are a few days between answers that means a few days of work lost and stress added, besides that I've had a thread on here where I was "sort of" getting some response from Matthias Carstens but he was ignoring some of my questions while answering others, this made it even more frustrating as you might understand.
Also, because there is no phone-number to call there really isn't any way of knowing if anybody is actually reading your mails or working on it.

I do appreciate the fact you're answering all the questions and I hope to figure this out soon!

Ruben

@esteban, I haven't had the time to do so, I know I should give it a shot, just need to find one I can install everything I use on to simulate my workflow with the Device.

@Daniel and Timur, Just got Kernel problems with the Duet2, I borrowed it and worked well the first days, now it's doing the same thing as the fireface, Mbox still works fine, could it be a usb2 problem in my computer? Mbox is usb1 and Firepod is Firewire.

@daniel,  I've just been running some tests, and right now it seems like its all going crazy!

both usb ports give the kernel spikes up to 200% after a while if I plug the RME or the Duet in and use it with Cubase,
crazy enough if I just play the project, it's O.K.
but as soon as I start to move things around while audio is playing, Kernel goes nuts.
If I then change driver to build-in audio it still Spikes, BUT if I unplug the device and close totalmix, everything is normal and I can use cubase without a problem. If I use the Mbox it is also no problem but that's not USB2
I only have an ilok and a cubase dongle connected through a little usb powered hub, I have a few, changed them but that doesn't seem to matter.

SO WEIRD!

@ esteban,

I spend a lot of money on a product that didn't work with my set up, I didn't (and still) don't know why, my first thought was that my computer was not working properly, so I brought it in, got it back with an "all good" label, so my next thought would be "the device" since my other device worked. Now I know the RME is not the issue here but if you don't know why something doesn't work and you are not getting the right support, that is very very frustrating, especially since I'm not using this for a hobby, it's for my work, I don't have 2 weeks to just wait and hope for an answer tomorrow or the day after or the day after.

Daniel Fuchs has always replied to my mails with full answers and I'm grateful for that but sometimes it took a while which means I don't know when I'll get a reply, which means I'm still in the dark and unable to work, so I posted on the forum, this other guy from RME has structurally ignored some questions which meant days and days of not being able to work or at least figure out a cause. He didn't even say, "I'll get back to you", or even acknowledge that I asked him a question. That means I'm lost and don't know what to do or expect. Maybe there is a reason you've read tons of angry posts like this and maybe there is something to be done from the Support side of it to make sure that you feel like your not just talking to a wall because after a while you will scream.

Again, I know now that the Device is not the problem here and reading all the rave reviews + the times I was able to work the Device I know it's a killer piece of equipment, but I think, with the right help, I could've found that out sooner and that would have saved me a lot of stress.

and just "Too bad" doesn't cut it, I hope you've never been in a deadline situation before with malfunctioning equipment and I hope you'll never will, but without offering help here it seems quite redundant to post a message.

Ruben

@ Timur, When I started having the issues, besides having my comp checked out all the way, I bought a new internal HD because I wanted a faster HD and I'm having the same problems on the new HD with a clean install. I'll try it with an external today though! Is it possible that my USB ports are just not working well anymore? In the past I've had problems with having to plug-in external HD's a few times before my Mac would recognize them, this never happened with the RME but it does with the DUET which is bus powered.

Thanks!

AFAIK there are no problems if one does a clean install (i.e. from DVD to a blank drive) and then uses the migration assistant to copy programs and settings from a previous installation. Works fine here on two different installations of 10.7, with imported 10.6 software.

Regards
Daniel Fuchs
RME

I totally agree on ruben's moment, same case here. Computer is not the probelm. I do bigger mixes on mbox/ even m-audio firewire 1814 handles better on 1024 (not to mention 2048, which i like to use for bigger projects) because that i personally hope for my RME UCX to have 2048 option available on the future driver update beacause of that.

48khz both cases same buffer lenght. different behaviour. Btw im not an expert that can pinpoint the problem, if i knew i wouldn't be begging for the expert opinion and driver update on the forum.