shawnbulen

Thanks for the response, brundlefly. F5 still works in most places, but not in the clip-start attribute of clip properties. (The main place I used it...) I hope that gets fixed soon. I'll bind F8 like you said, that will help a lot. I assumed the function was a problem, not the bind. Sounds like an easy fix 'till the next patch. Shawn

Shawn,

Keep in mind that using any of the 'already bound' keys that are the new defaults in X1 will, of course, affect those.

It's kind of a catch 22.   But at least it is do-able.

You're right.  I'll try binding it to ctl-G, where it's supposed to be in X1-ese.

At the moment, CTRL G is bound to "Go Thru" -- so if you don't need/use that often, that might be a good choice.

@John: I will look futher.. but it's very frustrating to have seemingly mastered a program - only to find that I need to learn all over again...

This is the main problem and believe me when I say I really understand this. Fortunately I believe it is worth the reeducation. I just wish I didn't have to start in grade school. I am willing to learn though.

This is not a competition. It is a discussion. If you have a counter point, please post it. Eventually we may all find none of us had the answer. Just saying...

So true and whats happening now is what we can do together. Help each learn this new thing.

If one has a feature in 8 that is apparently gone in X1 come in here post it and lets see if we can't collectively sort it out together.

ba_midi

shawnbulen

Thanks for the response, brundlefly. F5 still works in most places, but not in the clip-start attribute of clip properties. (The main place I used it...) I hope that gets fixed soon. I'll bind F8 like you said, that will help a lot. I assumed the function was a problem, not the bind. Sounds like an easy fix 'till the next patch. Shawn

Shawn,

Keep in mind that using any of the 'already bound' keys that are the new defaults in X1 will, of course, affect those.

It's kind of a catch 22.   But at least it is do-able.

You're right.  I'll try binding it to ctl-G, where it's supposed to be in X1-ese.

At the moment, CTRL G is bound to "Go Thru" -- so if you don't need/use that often, that might be a good choice.

Actually, the documentation says it's bound to 'go thru' (like the old F8) but in fact it's bound to 'search next'.   That's the problem - a simple error in the default key bindings.   Easily fixed by binding Ctl-G to 'go thru'. 

John

@John: I will look futher.. but it's very frustrating to have seemingly mastered a program - only to find that I need to learn all over again...

This is the main problem and believe me when I say I really understand this. Fortunately I believe it is worth the reeducation. I just wish I didn't have to start in grade school. I am willing to learn though.

Back in the 1980's, a co-worker of mine was reading a book.  I asked him what it was.  Coding in "C" or "C plus plus".  I had never heard of it.  This was a guy who decided to continue to self-educate on his own time, even though the company wasn't paying him to do it.
 
He was one of the first to leave that company and double his salary.
 
I never forgot that.  That's why the Reference Guide PDF is always open on my desktop whenever I have X1 up and running. 
 
And that is why I will not only have Scott Garrigus' book in my home and in my library, but on my desk, on my Nook reader, and (if available), on my Droid.  The hardcopy will usually be opened to some weird and wacky idea, and that book will go with me to my job in an unrelated field, the DMV, lunch, and the doctor's office until it is dog-eared and ragged.

shawnbulen

ba_midi

shawnbulen

Thanks for the response, brundlefly. F5 still works in most places, but not in the clip-start attribute of clip properties. (The main place I used it...) I hope that gets fixed soon. I'll bind F8 like you said, that will help a lot. I assumed the function was a problem, not the bind. Sounds like an easy fix 'till the next patch. Shawn

Shawn,

Keep in mind that using any of the 'already bound' keys that are the new defaults in X1 will, of course, affect those.

It's kind of a catch 22.   But at least it is do-able.

You're right.  I'll try binding it to ctl-G, where it's supposed to be in X1-ese.

At the moment, CTRL G is bound to "Go Thru" -- so if you don't need/use that often, that might be a good choice.

Actually, the documentation says it's bound to 'go thru' (like the old F8) but in fact it's bound to 'search next'.   That's the problem - a simple error in the default key bindings.   Easily fixed by binding Ctl-G to 'go thru'. 

Nice catch, Shawn.  There are some other wrong entries in the documentation as well.

(Note to John:  be careful what you read ;) )

Sonar 8.5 worked with Zoomtext. If I don't move any knobs or faders in X1, it works fine as well. Move a knob or a fader and the screen jumps around and the focus (where the pointer is) jumps all over the place.

(Note to John: be careful what you read ;) )

I'm beginning to see that.  The question is where is the real thing? Is it what was printed in the manual or is it somewhere else? Where do we go for the definitive answer?

I don't know if this view has been stated but if you guys/gals look at this new interface as no longer button driven but menu driven it may help. The thing to keep in mind is that each view has its own menu that is peculiar to it. We long time Sonar users are used to a structure that was both local and global. Here everything is local. The CV has a menu that is totally different from the TV. No buttons yet it has everything the old CV had but with some extra stuff.

The new smart tools are if you think about it not new at all but an extension and refinement of the MIDI tools introduced in 7.

With this idea in mind that the menu is where things get done we can better work in this new environment. Even the filter is a menu.

I make no comment on whether this is a good thing or not. I am simply pointing out what I think will help us grasp this new interface. I think we will need all the help we can muster.

John

(Note to John: be careful what you read ;) )

I'm beginning to see that.  The question is where is the real thing? Is it what was printed in the manual or is it somewhere else? Where do we go for the definitive answer?

I don't know if this view has been stated but if you guys/gals look at this new interface as no longer button driven but menu driven it may help. The thing to keep in mind is that each view has its own menu that is peculiar to it. We long time Sonar users are used to a structure that was both local and global. Here everything is local. The CV has a menu that is totally different from the TV. No buttons yet it has everything the old CV had but with some extra stuff.

The new smart tools are if you think about it not new at all but an extension and refinement of the MIDI tools introduced in 7.

With this idea in mind that the menu is where things get done we can better work in this new environment. Even the filter is a menu.

I make no comment on whether this is a good thing or not. I am simply pointing out what I think will help us grasp this new interface. I think we will need all the help we can muster.

Gee, John - you say all that almost as if you actually got/bought the program and are using it LOL.

Tell ya what, for me personally -- instead of saying something like:

"if you guys/gals look at this new interface as no longer button driven but menu driven it may help"

 - I would ask that you give thought to those of us who actually are using (or trying to use) the program and maybe have the ability to come to some conclusions, awareness, discoveries of our own.   We might say to you:  "If you guy actually used the program, it might help" ;)

I'm not trying to be disrespectful -- but I've spent a couple of days mixing in X1 and tonight TRYING to do a new tune, and finding many problems (some of which are known to many USING it already).  So to some extent when I see you suggest how others should "look at X1" without actually getting in the cockpit to drive the ship, it just bothers me a bit.

Sure my reaction at the moment might be driven by deep frustrations from the bugs I'm running into, but still I would ask that you, my friend, just step back a little and ask yourself how it might seem to some of us who really are getting in the dirt, so to speak.

I won't list the actual bugs I've run into just tonight (the list would not be pretty).  But I keep trying anyway.  I can report these things and help CW based on *first hand* experience.

But trust me, my friend, you too may find that your entire thinking and feeling may change (for better or worse, but change it might) when you actually have, use, and dig in to the program.

I hope I didn't seem like I'm venting on you too much - but I do feel I needed to say this.

Sorry you feel that way. I didn't see any mandate on this forum that specified anyone posting here had to have the program.

I can see if what I say is wrong or is giving people incorrect information that one might question how well a person is familiar with the program but you aren't saying that. You aren't correcting anything all you are doing is questioning me for not being in the X1 club as yet.

Please correct my postings. Find where I am wrong but don't attack me for not having the program.