Kroneborge
Max Output Level: -65 dBFS
- Total Posts : 1300
- Joined: 2011/01/18 22:14:58
- Location: Lompoc CA (near Santa Barbara)
- Status: offline
Changing pan and volumes (all on their own) - Fixed stupid offset button
Ok, something is seriously broken here. When I add audio tracks in, I normally lower then 6-9db to make sure I have plenty of headroom. I KNOW that I have done this on most/all of the tracks in this song. Moreover, I specficially remember assigning at least some of the pans left and right. But guess what. I go in today to adjust stuff. All the volumes are at zero, and the pans too. I had thought this happened to me before, but thought my mind was surely playing tricks on me. This time I'm sure. So unless there is some type of global put all settings to zero hotkey that I keep hitting like a dumb A** I'm going to do my best to finish this song (it's almost done) and then either go back to 8.53, or switch to another DAW. I've really tried to give X1 a fair shot since X1b came out, but I still get crashes (not as many though) and have crazy stuff like this happen (I've already mentioned the disapearing automation). I mean how do you work around a bug where all your settings disapear?
post edited by Kroneborge - 2011/04/02 18:19:47
|
Qwerty69
Max Output Level: -62 dBFS
- Total Posts : 1435
- Joined: 2004/02/19 17:44:10
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 18:09:30
(permalink)
Sure you haven't inadvertently hit "O" and put everything into OFFSET mode?
J.
|
codamedia
Max Output Level: -67 dBFS
- Total Posts : 1185
- Joined: 2005/01/24 09:58:10
- Location: Winnipeg Canada
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 18:17:09
(permalink)
Sounds like offset mode to me as well. Screws you up terribly if you don't know you are there. After panning and setting levels, if you hit "O" it all zeros out (but will retain your level/pan settings)! Just hit "O" again to get things back to looking normal, then go read about offset mode  If this isn't offset mode - YIKES! Let us know, as that would not be good.
post edited by codamedia - 2011/04/02 18:20:05
Don't fix it in the mix ... Fix it in the take!
Desktop: Win 7 Pro 64 Bit , ASUS MB w/Intel Chipset, INTEL Q9300 Quad Core, 2.5 GHz, 8 GB RAM, ATI 5450 Video Laptop: Windows 7 Pro, i5, 8 Gig Ram Hardware: Presonus FP10 (Firepod), FaderPort, M-Audio Axiom 49, Mackie 1202 VLZ, POD X3 Live, Variax 600, etc... etc...
|
Kroneborge
Max Output Level: -65 dBFS
- Total Posts : 1300
- Joined: 2011/01/18 22:14:58
- Location: Lompoc CA (near Santa Barbara)
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 18:19:22
(permalink)
Hosted on my own petard it seems.
Guess I'll have to change the name of the thread.
That's ok, I would rather be wrong in this case. (see I was hoping there was a button)
Thanks guys !
|
Kroneborge
Max Output Level: -65 dBFS
- Total Posts : 1300
- Joined: 2011/01/18 22:14:58
- Location: Lompoc CA (near Santa Barbara)
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 18:21:21
(permalink)
Wait as long as we are here, does anyone know how to make the rest of the inspector show again? I hit PC, and now half of it is covered by a bunch of stuff about track name and stuff instead of the info that normally shows (even when I switch it back to CI, or TI)
|
codamedia
Max Output Level: -67 dBFS
- Total Posts : 1185
- Joined: 2005/01/24 09:58:10
- Location: Winnipeg Canada
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 18:29:09
(permalink)
Is the inspector showing too "narrow" or too "short". I'm not quite following.
If it's too narrow, simply grab the handle and drag it over, just like a typical window. This happened to me a few times and threw me off.
If it isn't that simple, maybe a quick re-start of Sonar will correct it.
Don't fix it in the mix ... Fix it in the take!
Desktop: Win 7 Pro 64 Bit , ASUS MB w/Intel Chipset, INTEL Q9300 Quad Core, 2.5 GHz, 8 GB RAM, ATI 5450 Video Laptop: Windows 7 Pro, i5, 8 Gig Ram Hardware: Presonus FP10 (Firepod), FaderPort, M-Audio Axiom 49, Mackie 1202 VLZ, POD X3 Live, Variax 600, etc... etc...
|
Kroneborge
Max Output Level: -65 dBFS
- Total Posts : 1300
- Joined: 2011/01/18 22:14:58
- Location: Lompoc CA (near Santa Barbara)
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 18:34:23
(permalink)
No, it's not the width, it's the top half of the inspector is showing all this wierd (and for me) irrelevant data that it normally doesn't show. On stuff like clip properties or track names.
If I change it to PC on a midi track it looks like it's supposed too.
|
HumbleNoise
Max Output Level: -46 dBFS
- Total Posts : 2946
- Joined: 2004/01/04 12:53:50
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 18:44:02
(permalink)
Click the track or clip button again and that info will disappear up into the header and all your info will show. I'm finding that drop down info really valuable when editing but it's in the way when tracking and comes up by default. I wish it would not come up by default. I've been using it a lot to line up clips using the stop and start time in the info box. Some info there also cannot be accessed in any other way like, I think, custom track colors.
post edited by HumbleNoise - 2011/04/02 18:47:11
Humbly Yours Larry Sonar X2 x64 MAudio 2496 Yamaha MG 12/4 Roland XV-88 Intel MB with Q6600 and 4 GB Ram NVidia 9800 GTX Windows 7 x64 Home Premium
|
Kroneborge
Max Output Level: -65 dBFS
- Total Posts : 1300
- Joined: 2011/01/18 22:14:58
- Location: Lompoc CA (near Santa Barbara)
- Status: offline
Re:Changing pan and volumes (all on their own)
2011/04/02 20:33:02
(permalink)
HumbleNoise
Click the track or clip button again and that info will disappear up into the header and all your info will show. I'm finding that drop down info really valuable when editing but it's in the way when tracking and comes up by default. I wish it would not come up by default. I've been using it a lot to line up clips using the stop and start time in the info box.
Some info there also cannot be accessed in any other way like, I think, custom track colors.
That fixed it, ty
|