Norrie
Max Output Level: -58.5 dBFS
- Total Posts : 1665
- Joined: 2010/04/20 15:48:15
- Location: Scotland
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 13:03:52
(permalink)
Playing a session and hiting the synth rack button on the Vs700 causes a crash
Anyone else found this ?
SONAR X3c Producer Pro Tools 11 Allen & Heath GS-R24 M Adam A77x i7 4930K @ 4.4Ghz
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 13:13:08
(permalink)
I just posted another I found:
Opening PRV when midi track empty or synth frozen causes Sonar Crash
Anyone else?
Keni
|
pinguinotuerto
Max Output Level: -71 dBFS
- Total Posts : 976
- Joined: 2009/12/01 18:46:41
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 15:55:31
(permalink)
I don't understand why people write that something is a bug without confirming if it happens to others. I've seen several posts (including from long-time experienced forum members) where people say they found a bug, and then asked if others are experiencing the same thing! It's not a bug unless it happens to more than one person. Sorry, but it's a little annoying. Seems like some people just LOVE to find bugs and post them on the forum. Bug addiction. I believe there's a 12 step program for that. 
HP DV7-3085 Laptop (Intel Core i7 720 1.6 GHZ, 6 GB RAM, 1333 MHZ FSB, 2 500GB 7200 RPM Internal HDs, 17" screen), HP 2009m Monitor, 2TB Ext Drive
Line 6 UX8 with PodFarm 2 Platinum 2 Joe Meek VC6Q British Channels
Sonar Platinum & X3e Producer (64 Bit) AD2 w Roland V-Drums (TD4KX2)
Windows 7 Home Premium (64 bit)KRK VXT 8 Monitors
Frontier Alphatrack, Razer Naga Mouse, nanoKontrol2
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 16:31:09
(permalink)
pinguinotuerto
I don't understand why people write that something is a bug without confirming if it happens to others. I've seen several posts (including from long-time experienced forum members) where people say they found a bug, and then asked if others are experiencing the same thing!
It's not a bug unless it happens to more than one person. Sorry, but it's a little annoying. Seems like some people just LOVE to find bugs and post them on the forum. Bug addiction. I believe there's a 12 step program for that.
I understand what you mean, but if no one had exploded a nuclear bomb, wouldn't it still be a bomb? It may occur that a particular way a user works or gear that is used may turn up problems that no one else has found.... If all is "legit" on the user's system.... there's a bug! Numbers don't determine the substance of a claim, they merely support it and demonstrate how wide-spread it is... Keni
|
jimknopf
Max Output Level: -86 dBFS
- Total Posts : 207
- Joined: 2009/02/12 09:12:16
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 17:01:54
(permalink)
Keni
I just posted another I found:
Opening PRV when midi track empty or synth frozen causes Sonar Crash
Anyone else?
Keni
Both working without any problem here. Just checked it again to be sure.
|
trimph1
Max Output Level: -12 dBFS
- Total Posts : 6348
- Joined: 2010/09/07 19:20:06
- Location: London ON
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 17:37:26
(permalink)
I tried opening PRV when I had an empty Midi track...see no issue with that but..I did see a crash to desktop with a frozen synth...I suspect that might have been my own fumble fingers though...
The space you have will always be exceeded in direct proportion to the amount of stuff you have...Thornton's Postulate. Bushpianos
|
pinguinotuerto
Max Output Level: -71 dBFS
- Total Posts : 976
- Joined: 2009/12/01 18:46:41
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 17:53:38
(permalink)
Keni
pinguinotuerto
I don't understand why people write that something is a bug without confirming if it happens to others. I've seen several posts (including from long-time experienced forum members) where people say they found a bug, and then asked if others are experiencing the same thing!
It's not a bug unless it happens to more than one person. Sorry, but it's a little annoying. Seems like some people just LOVE to find bugs and post them on the forum. Bug addiction. I believe there's a 12 step program for that.
I understand what you mean, but if no one had exploded a nuclear bomb, wouldn't it still be a bomb?
It may occur that a particular way a user works or gear that is used may turn up problems that no one else has found.... If all is "legit" on the user's system.... there's a bug!
Numbers don't determine the substance of a claim, they merely support it and demonstrate how wide-spread it is...
Keni
Hey Keni, I agree with you 100%, but perhaps my point got lost in the rest of the message. It's not people posting their problems on the forum that "bugs" me (no pun intended  ),I think that's the most useful part of the forum--finding help from others and asking them to try to replicate things we're encountering. What I was refering to was the loose usage of the term bug. It seems like the minute some folks encounter a problem, they have to call it a bug before verifying if it is indeed a bug. That's all!
HP DV7-3085 Laptop (Intel Core i7 720 1.6 GHZ, 6 GB RAM, 1333 MHZ FSB, 2 500GB 7200 RPM Internal HDs, 17" screen), HP 2009m Monitor, 2TB Ext Drive
Line 6 UX8 with PodFarm 2 Platinum 2 Joe Meek VC6Q British Channels
Sonar Platinum & X3e Producer (64 Bit) AD2 w Roland V-Drums (TD4KX2)
Windows 7 Home Premium (64 bit)KRK VXT 8 Monitors
Frontier Alphatrack, Razer Naga Mouse, nanoKontrol2
|
Keni
Max Output Level: -17.5 dBFS
- Total Posts : 5769
- Joined: 2003/11/04 10:42:15
- Location: Willits, CA USA
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 22:27:07
(permalink)
Yes... Frequently people jump to the conclusion that some issue is a bug when in fact it's not... I know I've done this a few times myself... Everyone does at some point...
But I must also update my info about the bug I posted here. It turns out to be related to Sonar Plus as it stops happening if I close Sonar Plus (1.0.0.7), so I've notified benstat.... I'm sure that'll get fixed very soon...
Keni
|
dlion16
Max Output Level: -83 dBFS
- Total Posts : 391
- Joined: 2007/03/08 15:21:55
- Location: East Quogue, NY
- Status: offline
Re:Bug Hunt - X1b
2011/03/22 23:15:55
(permalink)
X1b. two issues.
1 - Screenset doesn't remember the size of the CV. I have a 20" and 24" monitor setup, CV on the 24. I open a project, Screenset 1 has TV on the 20, CV on the 24. The CV has two inches of space above the top of the title bar. I drag it up to fill the screen, save the project. I go to Screenset 5, then back to 1, CV is back to the original height, not the full full height I just set.
2 - TV. I do housekeeping on a project before saving it. Collapse the TV vertically so each track is minimized; 4 archived tracks are visible. I hide them all, either by selecting track numbers and rt-clicking hide or through Track Manager. Save the project. Close, reopen. The tracks are spread out as they were before I minimized all. The four archived tracks I just hid are now visible again.
Anybody seeing these?
|
Bub 
Max Output Level: -3.5 dBFS
- Total Posts : 7196
- Joined: 2010/10/25 10:22:13
- Location: Sneaking up behind you!
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 00:09:29
(permalink)
Track interleave still changes back to mono on it's own after setting it to stereo.
"I pulled the head off Elvis, filled Fred up to his pelvis, yaba daba do, the King is gone, and so are you."
|
rickpaul
Max Output Level: -89 dBFS
- Total Posts : 99
- Joined: 2003/11/04 13:17:20
- Location: Laguna Hills, California, USA
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 02:08:19
(permalink)
One of my two biggest pet peeve bugs from X1 and X1a is still there in X1B: The Mute tool doesn't work for audio clips (Problem Report ID: CWBRN - 4289). (Basic gist: Select the Mute tool from the control bar, move the cursor over an audio clip's bottom portion, and click on it. This should toggle the mute status of the clip, but it doesn't. It does change the Now Time -- it seem sto be acting like the arrow tool.) I should note that I use the x64 version of SONAR in case it is specific to that version (I don't have the 32-bit version installed, so can't say if it also occurs there). Mute tool does work fine for MIDI notes.
Not so much a bug as an annoyance: When you start SONAR X1b, the splash screen stays up all the time until SONAR comes up, and has an always-on-top behavior. This is new in X1b. With X1a and X1 (and earlier versions of SONAR), the splash screen went away pretty quickly and only the plug-in scanning dialog was visible, but it didn't have an always-on-top behavior, so it was possible to do other work while waiting for SONAR to come up. The reason this is such an annoyance is that SONAR takes a VERY long time to come up the first time I launch it after a system boot. We're talking on the order of 5 minutes. Thus, I have generally launched it while doing e-mail and other similar work so it would be ready when I'm ready to use it, not 5 (or so) minutes later. With the new behavior, the SONAR flash screen obscures the main part of my screen, so I can't see the other applications I'd be working on (or would have to make them unuseful sizes to get them enough off to the edges of the splash screen to be able to see them all, or at least as much as would fit in that space). (If you're wondering why SONAR takes so long to come up for me the first time after a boot, I think it is because I have a boatload of software instruments and audio plug-ins, and it must try to load all of them, including dealing with iLok authorizations for every plug-in that uses that, on the first load after a reboot. I can actually see the delay each time it mentions an iLok-protected plug-in. Most others stream by more quickly. Of course, I can't see the dialog with X1b, so that observation was from X1a and earlier.)
I also had a SONAR crash in a session this morning. I was dragging a plug-in (I think Lexicon Pantheon) from one project's bus to a similar bus in another project, and boom! I didn't have time to troubleshoot with the client sitting over my shoulder, so I just had to bring SONAR back up and manually load the plug-in and recreate settings in the destination project, not daring to tempt fate by trying again in case it was just a fluke. This is probably the first general SONAR crash I've seen in quite awhile (I do have one recurring hang situation related to rendering clips with AutoTune Evo in the clip FX bin -- haven't yet had a chance to try that to see if it might be cured in X1b, but I'd be surprised since it was there in earlier versions of X1 and also at least 8.5.3, possibly also earlier -- might be a 64-bit version-specific issue, such as with BitBridge).
I am at least glad the Smart tool bug in selecting clips in layers is fixed in X1b. Working around that one was pain in the butt in earlier versions of X1.
Rick
==================================== Rick Paul Web: http://www.rickpaulmusic.com/ ==================================== System: ASUS X99-Deluxe, i7-5820K, 16 GB RAM, Win10Pro x64, MOTU 828x, SONAR Platinum
|
pinguinotuerto
Max Output Level: -71 dBFS
- Total Posts : 976
- Joined: 2009/12/01 18:46:41
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 02:16:05
(permalink)
rickpaul
One of my two biggest pet peeve bugs from X1 and X1a is still there in X1B: The Mute tool doesn't work for audio clips (Problem Report ID: CWBRN - 4289). (Basic gist: Select the Mute tool from the control bar, move the cursor over an audio clip's bottom portion, and click on it. This should toggle the mute status of the clip, but it doesn't. It does change the Now Time -- it seem sto be acting like the arrow tool.) I should note that I use the x64 version of SONAR in case it is specific to that version (I don't have the 32-bit version installed, so can't say if it also occurs there). Mute tool does work fine for MIDI notes.
Rick
It works fine for me. Using 64 bit also. I can mute/unmute by clicking the top half or bottom half. You do know that if you click and drag on the bottom half you mute that section of the clip and to unmute you click and drag the top, right?
HP DV7-3085 Laptop (Intel Core i7 720 1.6 GHZ, 6 GB RAM, 1333 MHZ FSB, 2 500GB 7200 RPM Internal HDs, 17" screen), HP 2009m Monitor, 2TB Ext Drive
Line 6 UX8 with PodFarm 2 Platinum 2 Joe Meek VC6Q British Channels
Sonar Platinum & X3e Producer (64 Bit) AD2 w Roland V-Drums (TD4KX2)
Windows 7 Home Premium (64 bit)KRK VXT 8 Monitors
Frontier Alphatrack, Razer Naga Mouse, nanoKontrol2
|
ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 02:19:43
(permalink)
Rick,
I noticed similar behavior tonight - but it seemed to be related to the bottom-most track in the project.
If I clicked 'near' a clip in the bottom track - not on it - the now time would move there.
This does not happen anywhere else in the clip pane area, only that bottom most track (below).
I don't have my setup to do that, so I know it's something weird and I wonder if that's what you're seeing as well.
|
ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 02:22:41
(permalink)
pinguinotuerto
I don't understand why people write that something is a bug without confirming if it happens to others. I've seen several posts (including from long-time experienced forum members) where people say they found a bug, and then asked if others are experiencing the same thing!
It's not a bug unless it happens to more than one person. Sorry, but it's a little annoying. Seems like some people just LOVE to find bugs and post them on the forum. Bug addiction. I believe there's a 12 step program for that.
I STRONGLY disagree with the statement that it's not a bug unless it happens to more than one person. It may take time for people to do things that expose the bug. It may be an esoteric bug that requires a specific set of circumstances or gestures. I think it more appropriate to say it's not a "confirmed" bug until some other user experiences it or can duplicate it. But many bugs have been found over the years - here on this forum - that no one else was able to repro UNTIL one of the bakers did.
|
pinguinotuerto
Max Output Level: -71 dBFS
- Total Posts : 976
- Joined: 2009/12/01 18:46:41
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 02:46:53
(permalink)
ba_midi
pinguinotuerto
I don't understand why people write that something is a bug without confirming if it happens to others. I've seen several posts (including from long-time experienced forum members) where people say they found a bug, and then asked if others are experiencing the same thing!
It's not a bug unless it happens to more than one person. Sorry, but it's a little annoying. Seems like some people just LOVE to find bugs and post them on the forum. Bug addiction. I believe there's a 12 step program for that.
I STRONGLY disagree with the statement that it's not a bug unless it happens to more than one person.
It may take time for people to do things that expose the bug.
It may be an esoteric bug that requires a specific set of circumstances or gestures.
I think it more appropriate to say it's not a "confirmed" bug until some other user experiences it or can duplicate it.
But many bugs have been found over the years - here on this forum - that no one else was able to repro UNTIL one of the bakers did.
Billy, My point is that one can not be certain about a problem being a bug unless it can be replicated by someone else. In the case of your example, one of the bakers. Otherwise, chances are it's something system specific. The point is this: People say, "I found a bug", and then they ask, "can you guys see if this happens to you too?" How can you say you found a bug if you don't know if it can be replicated by another user with the same or a similar setup? In my humble opinion, people should say, "i'm having a problem, can you see if this happens to you too?" How many threads have we not seen where people say," Found Bug", only to change it later to, "Not a bug, my bad"? That's all I was trying to say. People are "trigger happy" about calling problems they encounter "bugs" or should I say, people are "bug happy".
HP DV7-3085 Laptop (Intel Core i7 720 1.6 GHZ, 6 GB RAM, 1333 MHZ FSB, 2 500GB 7200 RPM Internal HDs, 17" screen), HP 2009m Monitor, 2TB Ext Drive
Line 6 UX8 with PodFarm 2 Platinum 2 Joe Meek VC6Q British Channels
Sonar Platinum & X3e Producer (64 Bit) AD2 w Roland V-Drums (TD4KX2)
Windows 7 Home Premium (64 bit)KRK VXT 8 Monitors
Frontier Alphatrack, Razer Naga Mouse, nanoKontrol2
|
jimknopf
Max Output Level: -86 dBFS
- Total Posts : 207
- Joined: 2009/02/12 09:12:16
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 05:43:28
(permalink)
+1
It's not about supressing bug reporting (bug reporting is ALWAYS helpful), it's just about narrowing down possible reasons for problems before veryfying a bug.
|
trimph1
Max Output Level: -12 dBFS
- Total Posts : 6348
- Joined: 2010/09/07 19:20:06
- Location: London ON
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 09:36:00
(permalink)
Bub
Track interleave still changes back to mono on it's own after setting it to stereo.
I've had that twice so far..is this an intermittent thing though?
The space you have will always be exceeded in direct proportion to the amount of stuff you have...Thornton's Postulate. Bushpianos
|
ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
Re:Bug Hunt - X1b
2011/03/23 15:27:17
(permalink)
pinguinotuerto
ba_midi
pinguinotuerto
I don't understand why people write that something is a bug without confirming if it happens to others. I've seen several posts (including from long-time experienced forum members) where people say they found a bug, and then asked if others are experiencing the same thing!
It's not a bug unless it happens to more than one person. Sorry, but it's a little annoying. Seems like some people just LOVE to find bugs and post them on the forum. Bug addiction. I believe there's a 12 step program for that.
I STRONGLY disagree with the statement that it's not a bug unless it happens to more than one person.
It may take time for people to do things that expose the bug.
It may be an esoteric bug that requires a specific set of circumstances or gestures.
I think it more appropriate to say it's not a "confirmed" bug until some other user experiences it or can duplicate it.
But many bugs have been found over the years - here on this forum - that no one else was able to repro UNTIL one of the bakers did.
Billy,
My point is that one can not be certain about a problem being a bug unless it can be replicated by someone else. In the case of your example, one of the bakers. Otherwise, chances are it's something system specific.
The point is this:
People say, "I found a bug", and then they ask, "can you guys see if this happens to you too?"
How can you say you found a bug if you don't know if it can be replicated by another user with the same or a similar setup?
In my humble opinion, people should say, "i'm having a problem, can you see if this happens to you too?"
How many threads have we not seen where people say," Found Bug", only to change it later to, "Not a bug, my bad"?
That's all I was trying to say. People are "trigger happy" about calling problems they encounter "bugs" or should I say, people are "bug happy".
I think we're ending up saying pretty much the same thing, then. However, I would add one thing to the end of you're comment above: "People are buggy" ;)
|
rickpaul
Max Output Level: -89 dBFS
- Total Posts : 99
- Joined: 2003/11/04 13:17:20
- Location: Laguna Hills, California, USA
- Status: offline
Re:Bug Hunt - X1b
2011/03/24 03:32:08
(permalink)
pinguinotuerto
It works fine for me. Using 64 bit also. I can mute/unmute by clicking the top half or bottom half. You do know that if you click and drag on the bottom half you mute that section of the clip and to unmute you click and drag the top, right?
I just looked back at the Help for the Mute tool to double check the new behavior, and I see what I was describing was not quite right, but the larger point remains in terms of the behavior I'm seeing (or not seeing, depending on your perspective). I am specifically trying to do clip-level (not time range-level) mutes, where you should be able to mute or unmute the entire clip by clicking in the proper area of the clip, and Now Time should not change when you do that. However, clipping in either area of the clip has no effect on the mute status of the clip, and the Now Time does change. The time range mute feature also does not work on my system, and Now Time gets set at the start of the click-drag motion. Also, the despite seeing the Mute tool (looks like an "M") selected in the Tools module of the Control Bar, the actual cursor looks like the Select tool (arrow cursor), whether you are hovered over a clip or not. This has been the case 100% of the time, both in projects originally created in X1 and in projects created in older versions of SONAR. I also just tried using the pop-up Tool selector to see if that might give different results than the Tool section of the Control bar, but it behaves the same. It's very interesting to hear that this works for some others, including on the x64 version of SONAR X1/X1a/X1b. I'm really wondering what the specifics are for making it consistently not work on my system now. Rick
==================================== Rick Paul Web: http://www.rickpaulmusic.com/ ==================================== System: ASUS X99-Deluxe, i7-5820K, 16 GB RAM, Win10Pro x64, MOTU 828x, SONAR Platinum
|
rickpaul
Max Output Level: -89 dBFS
- Total Posts : 99
- Joined: 2003/11/04 13:17:20
- Location: Laguna Hills, California, USA
- Status: offline
Re:Bug Hunt - X1b
2011/03/24 03:53:22
(permalink)
ba_midi
I noticed similar behavior tonight - but it seemed to be related to the bottom-most track in the project.
If I clicked 'near' a clip in the bottom track - not on it - the now time would move there.
This does not happen anywhere else in the clip pane area, only that bottom most track (below).
I don't have my setup to do that, so I know it's something weird and I wonder if that's what you're seeing as well.
Thanks for your notes, Billy. I just double checked since I am most frequently using this in conjunction with comping and the track I'm comping is often (but not always) the bottom-most track. However, on my system the behavior I mentioned occurs no matter what track it is, and also whether or not there are layers active and displayed in the track (one thing I was specifically wondering about after reading the other response saying it was working for someone -- I mostly used the Mute tool with layered tracks while comping, but I also thought I'd checked it out in non-layered tracks previously). In my case the Now Time moves if I click on a clip, too. Rick
==================================== Rick Paul Web: http://www.rickpaulmusic.com/ ==================================== System: ASUS X99-Deluxe, i7-5820K, 16 GB RAM, Win10Pro x64, MOTU 828x, SONAR Platinum
|
rickpaul
Max Output Level: -89 dBFS
- Total Posts : 99
- Joined: 2003/11/04 13:17:20
- Location: Laguna Hills, California, USA
- Status: offline
Re:Bug Hunt - X1b
2011/03/24 04:54:48
(permalink)
Some new/additional observations on the Mute tool behavior I am seeing:
I was experimenting with the supposed lasso behavior mentioned in the Help file, which also was not working (at least on my system) according to the documentation. In the process of doing that, however, I accidentally discovered that the cursor actually did change to a Mute tool cursor when I was holding down Alt while moving the cursor over clips. Additional experimentation showed it also would turn the cursor to a Mute tool performance if I was already hovered over a clip and then held down Alt. In fact, not only did the cursor appearance change, but the Mute tool then worked as a Mute tool -- not quite according to the documentation (e.g. clicking on the clip toggled the mute status independent of whether you were in the top or bottom half of the clip, though the time range muting by click dragging did work according to the top/bottom half positioning -- in both cases when used with Alt). Actually, in some cases, it seems you have to hit Alt twice to get the cursor to change from the arrow, which appears by default in all cases (and also reappears if you release Alt then move off any current clip to a blank space or another clip, as well as if you release Alt then move between the top and bottom portions of the current clip), to the mute or unmute variants of the Mute tool.
Combining the Ctrl key with the Alt key does make the exclusive clip soloing in layers work, and the time range muting by Alt-click-dragging works, as well. However, lassoing behavior as described in the documentation doesn't work, independent of the Alt-key status (non-Alt key lassoing is supposed to mute clips while Alt key lassoing is supposed to unmute them -- by lassoing here, I specifically mean starting the click-drag motion outside of clip areas in area "C" as showing in the documentation).
So I guess the good news is that there is a workaround for basic clip muting, which is my main need. The bad news is that it is still messed up, at least on my system. I might add that the documentation also talks about being able to set Mute tool options by "clicking the small down arrow to the right of the button". Assuming they mean the little arrow-type thing in the lower right of the Mute tool in the control bar, that doesn't seem to do anything, at least on my system. I wonder if somehow getting at these options would show some preference setting that reverses something in the behavior of the tool. I also looked for options for the Mute tool elsewhere in SONAR, but did not find anything. I also looked in my INI files to see if there was anything of that sort. Perhaps the documentation is just incorrect about there being options for it (e.g. a holdover comment from earlier versions of SONAR where I seem to recall there was a option whether your default Mute tool behavior worked with clips or time ranges). If there were some setting here, though, it's at least conceivable this could explain why my system is behaving differently than others' systems in this area.
Rick
==================================== Rick Paul Web: http://www.rickpaulmusic.com/ ==================================== System: ASUS X99-Deluxe, i7-5820K, 16 GB RAM, Win10Pro x64, MOTU 828x, SONAR Platinum
|
rickpaul
Max Output Level: -89 dBFS
- Total Posts : 99
- Joined: 2003/11/04 13:17:20
- Location: Laguna Hills, California, USA
- Status: offline
Re:Bug Hunt - X1b (fix for my Mute Tool bug)
2011/04/13 11:31:13
(permalink)
rickpaul
Some new/additional observations on the Mute tool behavior I am seeing:
(rest snipped for brevity)
Some good news on this problem. Cakewalk replied to my problem report asking for a project to recreate the problem, and last night I supplied a simple one -- really any project could recreate it on my system from the simplest to the most complex. Alongside that, though, I also provided my notes from this thread and my best guess that it might be related to the former Mute Tool preference that allowed selecting time range muting (the SONAR default) or clip muting (my preference) for the default behavior of the Mute Tool.
This morning they replied that they think it was due to a registry setting that got erroneously copied over by the migration wizard (I was upgrading from SONAR 8.5) and asked me to try deleting the following registry entry:
[HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\X1\ToolView] "TimeDragMode"=dword:00000000
then to start SONAR again to see if the Mute Tool worked properly. It did. (Yay!)
I know I'm replying to my own reply on this thread and from awhile back, but I thought the information might be useful in case anyone else is seeing this problem. It looks like it would only have occurred if you upgraded from a previous version of SONAR and allowed the migration wizard to copy your settings from that previous version. It may also rely on your having changed the default behavior of the Mute Tool in that previous version. This could explain why others here were not seeing the issue.
Rick
==================================== Rick Paul Web: http://www.rickpaulmusic.com/ ==================================== System: ASUS X99-Deluxe, i7-5820K, 16 GB RAM, Win10Pro x64, MOTU 828x, SONAR Platinum
|