I have had long conversations here to ensure I understood Offset.  I DO NOT want to use it: I just don't want it screwing up my projects.
 
• I have disabled the shortcut cut for Offset.
• There is an actual button called Offset on the VS-700 console.
• If I load a project to mix, the first thing I do is turn Offset ON using the console switch to ensure all the faders are at zero.  I then turn it off and don't touch it again.
 
I was about ready to export a project I was mixing—the one I had to redo after a number of problems documented here recently—and suddenly the levels were all wrong.  I looked closely in track view and saw that some tracks had the + sign indicating Offset mode and some did not (they had the line graph symbol).  All of the tracks had screwed up levels, though.
 
How does that even happen?  I was assured on this forum that Offset is all or nothing and you can't just put some tracks in Offset.
 
What the heck?
 
 

got any macro's or key bindings ?
 
that's all that comes to mind here.

Yeah, I've never seen a case where only some tracks are in Offset mode and others are not.  I didn't think this was possible either!   Sounds like a good test case to send in to the bakers for review. 
 
 

OK, guys, no worries.
 
This used to happen all the time when the O key was activated and I accidentally went into Offset mode, but I was assured many times that Offset is all or nothing.
 
So, either my system is weird or there is a bug that requires a very specific scenario.
 
One factor: I do have a VS-700 Console and I/O and there is an Offset button on the console; so, perhaps there is some weird code lying in the ROM of the VS-700 that explains why I get this and other errors other people don't.
 
Anyway, I just exported this project from Hell (to audio), so we shall see if any of these weird things happen on new tracks.

There are some weirdnesses with the V-Studio. When I dragged some chords from the browser into a project, they would trigger lights on the console. I have no idea why.
 
Konrad, I'm beginning to think you don't need a new computer...you need an exorcist who specializes in poltergeists.

Anderton
There are some weirdnesses with the V-Studio. When I dragged some chords from the browser into a project, they would trigger lights on the console. I have no idea why.
 
Konrad, I'm beginning to think you don't need a new computer...you need an exorcist who specializes in poltergeists.

Or where is Mulder and Scully when you need them . This is clearly an X file :-))

Hello Mr. Konrad, sometimes life has a way of being difficult.  I must say that this forum has been very free in lending their time to help you wade across this muddy Rubicon.  Keep on fighting for your goal.  The day that you finish this project will be a day of rejoicing throughout the land. I can't wait to hear the finished project.  It pains me to say that your problems, through the advice of the many experienced responses, has helped me understand the art or recording.  Bless you Konrad, and bless all of the responders.
 
the blind horse

We're all in this together! Bringing computers into the music-making process is a blessing and a curse, regardless of which software you use. I cannot emphasize enough how crucial the computer is to having a satisfying venture into music software.

I started out with a scuzi, custom build and blew money on Plextors, etc...  Then when thru the Gateways and Dells...  Jim Rosenberry has totally convinced me again on a purpose build and the back up service was a HUGE extra.

Thanks for all the kind words.
 
Craig, I need to think to remember what MIDI setting in Preferences caused the behavior you describe.  I know when my Preferences were not set up right, notes on a controller keyboard did a Maschine-quality light show on the console because the console thought it was supposed to respond to MIDI.
 
I hope Tascam develops a solution.  I love the VS-700 but it is homeless now and I'd like a fully-supported and current solution.