Bugs, problems, setup and fixes

Re:Bugs, problems, setup and fixes (smoochy)

Wed, 11 Nov 2009 00:09:44 GMT

i have the 700r and c , running sonar 8.5 with all curent updates, and a widi cme lif 80 keyboard and that's about it other then they computer hardware neccisary to run a pc.

asus p6td mother board socket 1366
i7-920 chip
12 gig ocz platnum ddr3
sata drive 1tb x2
sata opticle dvd drive x 2
radion hd4850 video
on baord audio disabled in the bios
nothin out of the ordinary

Re:Bugs, problems, setup and fixes (madfloyd)

Mon, 09 Nov 2009 17:31:54 GMT

I noticed something. The 'select' light (that is supposed to show which track is active) doesn't always match the selected track. If you select tracks via the controller it does, but you can load up a project that has a different track selected - or use the mouse - and the controller doesn't match.

This is with Sonar 8.31 - I haven't installed 8.5 yet. Win 7 64 bit

Re:Bugs, problems, setup and fixes (jzl)

Mon, 09 Nov 2009 14:44:36 GMT

Thanks Brandon,
I did add a new usb connection. This must be what changed the settings.

I'm running many things through usb - 2 midi inputs, keyboard, wacom tablet, Vienna key, etc....) will other usb devices effect the audio performance of the v700r since it is a USB device?

Re:Bugs, problems, setup and fixes (Crg)

Sun, 08 Nov 2009 20:17:17 GMT

You've definitely got an interuption going on somewhere. The stopping time bar is a dead give away. What all do you have hooked up to your system?

Re:Bugs, problems, setup and fixes (smoochy)

Sun, 08 Nov 2009 14:28:07 GMT

another anomaly that i forgot to mention that seems to have croped up since installing sonar8.5 is that occasionally now bar stops tracking wile in play. it doesn't seem to affect any thing and goes away by closing and reopening the program... that's weird.

we should start a "that's weird thread"....

Re:Bugs, problems, setup and fixes (Brandon Ryan [Roland])

Fri, 06 Nov 2009 20:35:34 GMT

jzl

I guess the good news is that rebooting seems to help with a lot of these little anomalies.

In regards to my console behaving strange: I've now discovered that the midi out was change (not by me) in the control surface settings. This just showed up this morning. Yesterday I had confirmed all the setting while trying to trouble shoot my console acting strange. It seems to change itself now and then in sonar 8.5. Would locking ACT data help?

Get the ports setup for the VS-700C and then try re-starting SONAR. It should keep the port assignments unless you change USB ports or ins some cases if you add another USB interface of some kind.

Re:Bugs, problems, setup and fixes (Crg)

Fri, 06 Nov 2009 20:35:06 GMT

jzl

Hi Craig,

Thanks for your reply.

Under "options", "audio", the box that you can normally select the default bit depth is grayed out and cannot be changed. It is stuck at 24 bits but when running Sonar the lower right hand section of sonars window indicates that it is running at 48000 16 bits. Is there a different area in sonar where the bit depth of a project can be altered? Could it be that i should completely disable the mobo audio so it doesnt interfere at all?

By rca I meant spdif, sorry about that.

and as far as the console acting strange goes -- it seems to be back to normal (without me changing anything other than doing a series of reboots)
Initially I installed 8 on the new system, updated to 8.31, installed the vstudio, updated vstudio drivers and firmware, configured it in 8.31 then installed 8.5, then configured vstudio for 8.5. I was taking a guess that the faliure in 8.5 might have been driver related because the vstudio worked fine in 8.31 after it failed in 8.5. I am using 32 bit plug ins so maybe the 8.5 bit bridge isnt too solid yet, but I was also loading a blank project to try to get the console to work. I guess I'mn going to cross my fingures and hope that it doesnt happen agian.

I'm not sure since your using a SPDIF connection. That could be the reason why your bit depth is greyed out.
Study the SPIDF rates, I'm not up on them. You can go to options- global- Audio Data-File bit depths and set them there. If those are greyed out also it might be the SPDIF connection. Loading a blank project shouldn't affect the console as a controller if it is selected as your controller. It should come right up on the blank project.
The onboard sound thing can do it to you also. If you're not using it disable it. But a word of caution: sometimes you have to leave their drivers installed and running. There are alot of different setups and sometimes the MOBO needs those circuits for any audio. You'll have to give some details on the onboard sound and try a few variations of what works and what doesn't. On board sound cards can be a real PITA when comes to DAWs.

Re:Bugs, problems, setup and fixes (jzl)

Fri, 06 Nov 2009 15:50:13 GMT

I guess the good news is that rebooting seems to help with a lot of these little anomalies.

In regards to my console behaving strange: I've now discovered that the midi out was change (not by me) in the control surface settings. This just showed up this morning. Yesterday I had confirmed all the setting while trying to trouble shoot my console acting strange. It seems to change itself now and then in sonar 8.5. Would locking ACT data help?

Re:Bugs, problems, setup and fixes (Westside Steve)

Fri, 06 Nov 2009 13:03:20 GMT

Here's a weird bug.
In Direct Mix screen sliding fader 2 and the cursor freezes.
It will slide fader up or down but will not leave that fader.
Had to reboot.
Twice.

Odd eh?
WSS

Re:Bugs, problems, setup and fixes (smoochy)

Fri, 06 Nov 2009 04:00:30 GMT

I UPDATED FROM SONAR 8.31 WITH NO ILL EFFECTS.... PRETTY MUCH EXACTLY WHAT YOU'VE DONE. ALTHOUGH I WILL SAY THE FIRST TIME I LOADED SONAR 8.5 THE CONSOLE THOUGHT IT WAS A KEYBOARD... IT WAS KIND OF FUNNY FOR ABOUT THIRTY SECONDS TILL I COULDN'T MAKE IT STOP.... AND DAMMM IF I COULDN'T EVEN FIND MIDDLE C ON THE SILLY THING.... AFTER A QUICK REBOOT ALL WAS BACK TO NORMAL. NO PROBLEMS SINCE.

Re:Bugs, problems, setup and fixes (smoochy)

Fri, 06 Nov 2009 03:41:01 GMT

YA MY CONSOLE HAS DONE THAT A FEW TIMES BUT USUALLY TURNING THE CONSOLE OFF ALONG WITH THE 700R AND TURNING IT BACK ON CORRECTS IT. HASN'T HAPPENED IN QUITE A WHILE.

Re:Bugs, problems, setup and fixes (jzl)

Thu, 05 Nov 2009 23:42:19 GMT

Hi Craig,

Thanks for your reply.

Under "options", "audio", the box that you can normally select the default bit depth is grayed out and cannot be changed. It is stuck at 24 bits but when running Sonar the lower right hand section of sonars window indicates that it is running at 48000 16 bits. Is there a different area in sonar where the bit depth of a project can be altered? Could it be that i should completely disable the mobo audio so it doesnt interfere at all?

By rca I meant spdif, sorry about that.

and as far as the console acting strange goes -- it seems to be back to normal (without me changing anything other than doing a series of reboots)
Initially I installed 8 on the new system, updated to 8.31, installed the vstudio, updated vstudio drivers and firmware, configured it in 8.31 then installed 8.5, then configured vstudio for 8.5. I was taking a guess that the faliure in 8.5 might have been driver related because the vstudio worked fine in 8.31 after it failed in 8.5. I am using 32 bit plug ins so maybe the 8.5 bit bridge isnt too solid yet, but I was also loading a blank project to try to get the console to work. I guess I'mn going to cross my fingures and hope that it doesnt happen agian.

Re:Bugs, problems, setup and fixes (Crg)

Thu, 05 Nov 2009 21:13:37 GMT

jzl

I updated the firmware and ran all the updates possible when i installed the vstudio a week ago. I'm now having a curious problem in addition to my other ones. When running sonar 8.5 the v console stopped responding like it should and used to. No time code, fakers unresponsive , no lights when selecting a track etc... After turning sonar off and on and a couple of reboots later it is back to normal. Even though it now works fine, this kind of instability worries me. My only guess is that I installed sonar 8.31 updated drivers, installed v studio, then installed 8.5 and that because of this order of installation, I've created 2 sets of drivers in my registry maybe?? are you using 8.31 and 8.5?

thanks for your response.

Are you using any plugins that are 32 bit in your 64 bit environment? As far as the 8.3.1 upgrade verses 8.5 disc thing goes,...? there are some different glitchs going on there. Are you refering to Sonar drivers or V700 drivers?
I think I would have installed the Sonar upgrades first then the V700, but I just don't know if it's the order of installation causing your problem. No lights where when selecting a track? on the console select button? No time code, no faders indicates you've lost your Console drivers in Controllers / Surfaces. I'm completely 32 bit on my system so I I'm not sure if it's a 64 bit problem, but go through all the Options and check to see if all the right drivers are selected.

Re:Bugs, problems, setup and fixes (Crg)

Thu, 05 Nov 2009 20:50:07 GMT

3. The bit depth in sonar is disabled will using the v700. It seems I'm stuck at 16 bits. Is there a way to change this?

That shouldn't be happening because you're using the V700. Sonar controls the bit depth as well as the bit depth of the project if you imported it at 16 to 16 bit or recorded it at 16 bit. Which is the case here?

I tried to sync the vstudio to the ax fx (it runs 48000 and 24bit) unit via rca (its hooked up through digital io 1) can clock syncing only happen if its a AES/EBU connection? I know this isn't so much a v700 question but thought I'd throw it out there.

It could be a V700 question, have you set the knob on the front of the V700R to 4800 and changed the bit depth to 24 in Options - Audio? By RCA do you mean SPDIF? Looks the same but isn't. Clocking is possible through all the digital connections.

Re:Bugs, problems, setup and fixes (smoochy)

Thu, 05 Nov 2009 20:19:30 GMT

unless they have come up with a fix in the last couple of hours... yup... that's right... ark board only works with 32 bit... their fix is to run 32 and 64 sonar.... kind of defeats the purpose of it ey? system would be much better with dedicated pcie card system for plugs rather than ark. i keep checking for a fix on the vstudio help sight from cakewalk and as of this afternoon nothing had changed. i'm starting to get the feeling it's something they don't really like to discuss....

Re:Bugs, problems, setup and fixes (jzl)

Thu, 05 Nov 2009 17:45:22 GMT

I updated the firmware and ran all the updates possible when i installed the vstudio a week ago. I'm now having a curious problem in addition to my other ones. When running sonar 8.5 the v console stopped responding like it should and used to. No time code, fakers unresponsive , no lights when selecting a track etc... After turning sonar off and on and a couple of reboots later it is back to normal. Even though it now works fine, this kind of instability worries me. My only guess is that I installed sonar 8.31 updated drivers, installed v studio, then installed 8.5 and that because of this order of installation, I've created 2 sets of drivers in my registry maybe?? are you using 8.31 and 8.5?

thanks for your response.

Re:Bugs, problems, setup and fixes (madfloyd)

Thu, 05 Nov 2009 16:51:37 GMT

smoochy

i've been running the v on vista 64 bit since it came out... had the first one issued in Canada. i trust that you've updated the firmware... that's the first thing it should clear up the driver problem. made a big difference with the drivers. next... i hope you weren't planning on using the v synth.... unless you want to load the 32 bit software and run both. other wise it's a boat anchor. other than that the v has performed pretty good. also unless it's an audio track the meters on the console won't indicate. it's apparently a bug their working on so don't be surprised if you don't see any activity on the meters when it's a midi track.... to tell you the truth they could have fixed it already and i just haven't noticed... i don't really look at the meters that much anyways. the surround features of the the v studio where awesome i definitely recommend you set up for surround... the console and software excelled in that department. your going to dig it.

Can you eleborate on "hope you weren't planning to use the v synth" ? I just received my 700 package, which I bought along with an ARX expansion card and Win 7 so I can go 64 bit... so I'm kind of alarmed here...

Re:Bugs, problems, setup and fixes (jackn2mpu)

Thu, 05 Nov 2009 16:12:47 GMT

jzl

Hi,
I've just built a project studio based around a v700. I think generally we should get a thread going on things that aren't working as I have a vested interest in getting the v700 working as great as can be.

I've had a few issues so far: (im running vista64)

2. The midi in and out on the v700 is really slow!!! I have an axe fx hooked up to the midi in and out and a midi librarian cant even seem to get midi messages to it efficiently. I've tried disabling other midi ports with no luck. Anyone have any suggestions? I would hate to have to by a separate midi io especially since the v700 is $4000 +

MIDI editor/librarians are notorious for being finicky as to interfaces. I have a number of expansion boards in my original Motif 7 that each have a standalone editor/librarian and the MOTU MIDI Timepiece AV USB will absolutely NOT facilitate communications between the expansion cards and the software. I have to reconfigure the connections to use the MIDI port on my Edirol UA1000 if I want to use the ed/lib s/w. The ed/lib wants to see as little confusion as possible for communications.

Some ed/lib s/w can change the communication rate between the s/w and the hardware - the ed/lib for my Moog Voyager rack mount hardware synth does that. In absence of buying another MIDI interface you may want to see if your s/w has something like this.

You may end up getting a simple 1 port MIDI interface and using that to interface with your axe fx box. Unlike with audio interfaces, you can have multiple MIDI interfaces with no problems.

Re:Bugs, problems, setup and fixes (smoochy)

Thu, 05 Nov 2009 15:29:28 GMT

i've been running the v on vista 64 bit since it came out... had the first one issued in Canada. i trust that you've updated the firmware... that's the first thing it should clear up the driver problem. made a big difference with the drivers. next... i hope you weren't planning on using the v synth.... unless you want to load the 32 bit software and run both. other wise it's a boat anchor. other than that the v has performed pretty good. also unless it's an audio track the meters on the console won't indicate. it's apparently a bug their working on so don't be surprised if you don't see any activity on the meters when it's a midi track.... to tell you the truth they could have fixed it already and i just haven't noticed... i don't really look at the meters that much anyways. the surround features of the the v studio where awesome i definitely recommend you set up for surround... the console and software excelled in that department. your going to dig it.

Bugs, problems, setup and fixes (jzl)

Thu, 05 Nov 2009 14:09:30 GMT

Hi,
I've just built a project studio based around a v700. I think generally we should get a thread going on things that aren't working as I have a vested interest in getting the v700 working as great as can be.

I've had a few issues so far: (im running vista64)

1. My computer will not recognize the drivers unless i turn the v700 io on after the computer has booted. It didn't always do this though. And occasionally I receive a message that windows does not recognize the driver. I switched usb connections and this seemed to help the "windows does not recognize" problem.

2. The midi in and out on the v700 is really slow!!! I have an axe fx hooked up to the midi in and out and a midi librarian cant even seem to get midi messages to it efficiently. I've tried disabling other midi ports with no luck. Anyone have any suggestions? I would hate to have to by a separate midi io especially since the v700 is $4000 +

3. The bit depth in sonar is disabled will using the v700. It seems I'm stuck at 16 bits. Is there a way to change this?

4. I tried to sync the vstudio to the ax fx (it runs 48000 and 24bit) unit via rca (its hooked up through digital io 1) can clock syncing only happen if its a AES/EBU connection? I know this isn't so much a v700 question but thought I'd throw it out there.

Thanks for any help!