Ughhhhh.....

Total disaster tonight with my Octa's. I cannot get my second Octa-Capture to show up at all as a valid audio device to be selected. It makes no sense. I disconnect everything but my keyboard and reboot so that nothing is running. I then connect the Octa captures up and I can only see the main one. The control panel shows them both and I have verified that I can control both of them from the control panel.

I uninstalled and reinstalled the drivers twice to no avail. Did all the things Roland suggested in the readme. Again, no love. I wasted time I was looking forward to spending actually making some music on this nonsense. It had been nice and stable up till now. Last thing I had done before things went haywire was to install Diva. It is an absolute CPU killer with some patches in divine mode and I managed to spike out my CPU and shut down the audio engine a couple of times. I can't see how this would cause such mayhem but I just am out of ideas.

Ideas welcome. I had to give up playing tonight...am just so annoyed!

Ken

Ken...

Sorry, no ideas here but it sounds like your problem is related to linking two Octa's?  Does it work fine with just one?

Jim

jkleban


Ken...

Sorry, no ideas here but it sounds like your problem is related to linking two Octa's?  Does it work fine with just one?

Jim

Yes it is fine with one but I need them both to work. I am going to try to roll back to the original drivers if possible and see what happens. The only issue with this (and a big one) is that the system software on each Octa has to be rolled back also and I don't know how nicely they will take to rolling back firmware.


Just such a drag....the fiance' went out with the girls last night and I was all excited to be left for hours to do nothing but play away. What a buzzkill!


Ken

I found my problem with Sonar (or anything else) not seeing my second Octa-Capture after my update to the V1.5 system code and driver. My situation is not typical but not that unique because I have two Octa-Captures and this was my issue.
 
Turns out I installed the code on the second Octa-Capture but had the VS-Expand option enabled on it. For some reason that only Roland software engineers may be aware of, this causes the driver to not properly update the code so that it can be seen by software other than the Octa-Capture control panel or the master Octa-Capture device.
 
Solution: Turn OFF VS-Expand BEFORE updating your Octa-Capture and then do the update as though it were a standalone unit. Afterwards, turn the option back on and then reboot and things seem to work. Hopefully I won't have additional problems creep up on my but I can finally see all my interfaces again and can get back to playing some music and not being an engineer here.
 
On a side note, the latency settings for my setup do not go below 96 buffers for 96 Khz sample rate. Is anyone else seeing this? This makes no sense. I set my system up at 192 buffers for 10.2 ms round trip latency. This sort of sucks. For comparison, I had swapped in my MOTU 828 MKII on firewire and saw roundtrip latencies of 4.3 ms on my system which makes a lot more sense. I don't need to run that fast but it was a jarring comparison to say the least. My latency is perfectly adequate for real time playing of soft-synths. Just seems silly.
 
Ken
Ken

Ken...

Thanks for the blow by blow update.... I feel bad because I am waiting for your saga to play out before I update.... looks like you have run the gamut though.. maybe this weekend.

Jim

I'm glad you got it going Ken.

So far I'm having great success. what's weird for me though. It works better at 96khz over 44.1. I'll never figure that one out. Looks like I'll have to get a new, larger, HD for the audio disk.

I just ordered an octacapture (it will be here Thursday from sweetwater).  Looks like a mixed bag on the new version software/drivers.  Should I just go with the 1.0 version for a while or jump in with the 1.5?

The USB 3.0 thing was something I found out the hard way which is that it really does not work on a USB 3.0 interface unless it is exactly backward compatible with the USB 2.0 spec. It would have been nice if they had said this in the original documentation cause it would have saved me a LOT of debugging time. That said, at least they are saying it right up front now.

 
FWIW, This isn't specific to Roland.  You'll find this to be the case with most USB audio interfaces (including RME).
They run better on the USB 2.0 controller that's integrated into the chipset.

fireberd


I just ordered an octacapture (it will be here Thursday from sweetwater).  Looks like a mixed bag on the new version software/drivers.  Should I just go with the 1.0 version for a while or jump in with the 1.5?

I can't say I am all that happy with the 1.5 drivers. Roland says they are supposed to be faster. I am definitely not seeing that at least in my setup. My computer is a very fast machine and I am getting dropouts that I never got in the initial driver version. Maybe it is a function of having two Octa-Captures but I have verified this with a single Octa-Capture running standalone. Same latency issues. I just don't get it.


The control panel for the newest drivers is WAY better but I would stick with the V1.0 drivers if I were you.


Ken

According to the instructions on the Roland site you must have the new drivers to use the new control panel software.  I'm going to stick with the original control panel and drivers at first and make sure everything works.   I 've got a second hard drive that I cloned recently that has X1 installed, so I could run a 30 day Pro Tools 10 version and I can install the new drivers and software on there first to see how it runs.  That will also tell me about PT 10 capability.  I have PT MP9 now and going through a groove 3 tutorial, maybe later I'll also add PT10.