lorneyb2

In PRV view for you Harp track highlight your Velocity controller lane.  Click in the purple box and select Display all continuous controllers.  Then hit the Plus sign in the velocity track until you are no longer getting anything but velocity lanes.  You may now be displaying an extra CC64 lane showing channel 1(or another incorrect channel).   Check the area where you had the problem to see if  there are any events showing up in an additional lane.  I have had this occur especially after having multiple tracks up in the PRV. 

Also when inserting the CC New value  type ensure that both the Controller Type and Channel are selected as it always defaults to Channel 1 which may be part of the cause. 

Hi, Lorne - Good stuff, but it isn't what's happening here.  The problem I'm describing will happen with a brand new, freshly inserted MIDI track.  There'll be no CC64, no nothing - but soon after recording in the track it will respond to the CC64 on another track.  I've looked in the Event List to double check also that no stray events were being recorded, and they aren't - What is definitely happening is the MIDI data from another track will intermittently effect another track - Weird stuff, but happens fairly often.

Thanks for your help.

Randy B.

Danny,
 
I don't know what the Clockworks thing is, but from all I've read so far about your situation, it seems like the approach to debugging it needs a little tweaking.   I think you're trying too many things randomly rather than developing a "bottom up" review, so to speak.
 
A few things stick out as I read your last post....  and that is the following:
 
- More and more it seems to me you have a MIDI loopback somewhere.  Either via cabling (ie, maybe you have a "thru" cable as opposed to a standard MIDI cable somewhere in the chain) - or you have a bad cable somewhere.
 
- Your devices may not be hooked up right (as in ordering)
 
- Your MIDI Prepare Buffer is suggesting a problem.   In ALL the years I've been working with Sonar I have never had to have my MPB higher than 250, even though 500 is Sonar's default.   Anyone needing more than 500 would suggest a concern.  So you're having to go to 2000 previously and thinking it may work now makes me wonder what is causing all that clogging.
 
- Drivers are always suspect, of course.
 
But I still would lean toward cables/cabling at the moment.  
 
Regardless, it seems you need to go about this by starting with a *very* minimal setup and slowly add things in one at a time to see when/where the problem happens.   It's really the better way to debug this, I think.
 
 
 

Have you tried to insert an all notes off midi CC (123) at the beginning of the song so that it starts fresh before the notes start to play?

Billy: Thanks for the reply. All cables are in/out. No midi thru's at all on anything. As for the order, I've never had a problem with the order before. I've used this exact configuration with 2 other pc's without a problem. I will look into it as it could be something just not jiving with the new system somewhere so I'm going to disconnect everything and try stuff one at a time.

Midi buffer question/answer: I used WDM before in my last rig, not asio. When several VSTi's and certain plugs were used while using the VSTi's with mid tracks I had created, I was getting random note drops like crazy on drums and keys. Like, in one section, a kick would disappear...yet if I stopped playback and restarted near that spot, the kick would trigger and a snare would drop out somewhere later. Or, a string patch wouldn't play a chord in a section, and then the next pass it would and it would drop out somewhere else. This happened when at least 2 softsynths were running with a few UAD plugs or plugs that took up a little bit of cpu.

A guy from this forum told me to change that buffer that had a 500 default to 1000 or 2000. This instantly fixed my problem and it never dropped any notes again. Keep in mind, it only dropped the notes while playing back in real time...they weren't missing if I froze a track or bounced down. So I assumed I would most likely have this problem again with this rig. But I do not get any of that. I believe ASIO is what fixed me up there as I have found loads of performance gains that I never had before. I've since brought this setting back to 500 as it didn't fix the issue I am currently experiencing.

Drivers: when I installed the motu, I just installed the 64 bit driver pack for it. There is another that has a wizard detection that analyzes your system and decides which is your best option. I un-installed the 64 drivers that I originally put in last night, and went with the latest MOTU midi drivers using the wizard. It installed the 64 bit drivers....I rebooted, and then turned on the motu....no issues there so we're right where we need to be as far as that goes. There is no "revert back to 32 bit" as the lastest drivers for Win 7 have the wizard...or I can just do what I did before and just install the 64's using that driver pacage...which was older than the ones I just installed last night. So I think I'm ok there...unless those drivers are the issue. I could try something older just to see if and how it works and I may do that. It's on my list to try after I sort out some of this other stuff.

Cables: they are all relatively new and never move or get stepped on. I tested each one using some of my other rack gear to make sure there were no issues with them. I shook them while doing patch changes and never got any errors or inconsistencies...so I think we're ok there too. All in to out...out to in...no midi thru's are being used. Turning global to off usually kills the midi loop issue. But setting the ClockWorks module to anything other than "internal" also kills the midi loop/doubling sound...so that too is now solved and ok. I'll proceed with one piece at a time and do a process of elimination to get to the bottom of this per your instructions and report back. Thanks Billy!

Memphis Jo: Thanks for the advice. Just to clarify a few things..as well as some new developments. When I said "everything is working perfectly" what I mean was, I'm sending and receiving midi as I should. Things are triggering and patches are changing just the way they should be. The stuck note issue is now just in my hardware. No internal Softsynths are sticking on me, so whatever I did in that ClockWorks thing must have made a difference. So this is a step in the right direction. The midi is printing fine and can be run through my SS's with no issues, no stuck notes, no errors. The Roland V Drums brain is perfect for drums and only seems to stick if I put it in instrument mode to where it plays piano, strings etc. Anything with a chord and something held...it just sticks. Sometimes it frees itself up, other times it doesn't.

The same with my M-1, Roland R-8, and Kawai. They all work perfectly for drums....they stick with other instruments...which I really don't use anyway, so I'm not going to lose much sleep over it. I have near zero latency with this rig (1.3ms at 128 samples) so I can trigger VSTi's in real time. However, if I DID want to use my hardware gear, it should work properly and not get stuck. So I'm definitely going to get to the bottom of this and take the advice of Billy and you and scale things down to pinpoint the issue.

I still think this has something to do with 64 bit drivers...but I should find all this out tonight with a stripped down rig. As far as the camera, no Sir...not on this new box. All it has hooked up to it is an RME FF 800 and UAD 2 quad. As for USB, I have the MOTU and a Tranzport controller and that's all this pc has going on.

Robo: Thanks for that suggestion. Can you tell me how I would go about doing that? I'm not very midi savvy unfortunately. I use midi to trigger my hardware, change patches in my guitar processors and midi devices, create midi tracks to send through samplers or VSTi's and that's about all I know about it. If you wouldn't mind telling me how to go about that, I'll definitely try it. If by chance you tell me and I try it and it works...would I need to do this all the time and if so, why? How come I never had to do this before? What would cause this to be new in the mix?

Chappel: Thanks again. I will try it with one instance at a time and see how it works.

I thank you all for your kind replies and advice. I will try everything and get back to you as soon as I can. If you come up with anything else, I'm all ears. :)

Thanks Chappel, yep....fully aware of that. All my stuff has midi in/out/thru jacks and none of the internal porting is set to "thru" for anything. :)

Yeah I know it's probably sticking there on the drums too, Frank. It's as you said, the one off's and lack of sustained notes hide it. I'm still testing over here. Hopefully I'll have some news about something by tomorrow. Thanks! :)

[quotecliffbatson]I've checked/unchecked everything reasonable to try.

You should probably start a different thread for this. I don't think the two issues are related, especially if you experience this only with GPO.

But here are some things to check: Do you maybe have disk caching enabled (it shouldn't be)? IIRC, GPO is a disk-streaming synth, so this could be a factor. Also, I saw a comment (not sure of its accuracy) that GPO only works with ASIO drivers. Did you maybe change to WDM with SONAR 8.5? Could it be effect tails that you're hearing, or is it really distinct notes from after you stopped playback? I would make sure the setting for Play Effect Tails After Stopping is the same in 8.5 as it was in 6.