Sonar 7: First Impressions / Bug Report

Page: < 1234 > Showing page 3 of 4
Post
Blades
Max Output Level: -43 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/29 22:59:38
Funny thing about the look of the buttons: I was just talking to a friend of mine who also just got S7 and we agreed that while neither of us thought that there "needed" to be a change, we both prefer the new look. for me, it makes it a LOT easier to see which options are engaged and which ones not.

It really would be a nice upgrade, since it apparently does matter to a lot of people to allow for some degree of skinning - even with fairly tight parameters around the designs. If not that, then at least a few options for different looks - majjong (sp?) lets you choose differnt looking tiles, solitare: differnt card decks - why not Sonar
chipstar
Max Output Level: -85 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 00:11:43
Absolutely awesome and hilarious Blades. I thought the same thing. I should try using the bitmap import to see if I can at least give it a different feel even if I can't overhaul the entire 'look and feel.'
JDA
Max Output Level: -85 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 01:22:38

ORIGINAL: krizrox


ORIGINAL: brian brock

The new buttons are dark when not applicable, I suppose to make the screen less "busy", since apparently people complain about Sonar in that respect. I never found it busy, but not being able to see the buttons is bothersome, and I don't believe this is accessible in the color options.

The new buttons are also larger than the old ones - less screen for tracks etc.





Since you brought it up - I didn't want to be the first one to complain about this because in the scheme of things, it's not that important - but I agree. There's something odd about those new buttons. They are hard to see because of the darkness or the change in appearance (even with a 20" monitor). They have more of a 3D effect now and I think that's what makes them kind of hard to see. In terms of the size, I don't see it as an issue per se but the appearance... not a big fan of the new buttons. Here's another case where they could have left that alone and devoted time to other things. I still say that area above the track pane looks funny and unfinished. It's been like that for years now. Throwing a clock in there helped but it still needs some attention if you ask me. Whatever. Not a show stopper.



I don't like the new buttons in S7 and much prefer the ones in S6. The darker color with the 3D cartoonish effect does make them much harder to read. I actually was looking for a setting to change them back to the way S6 looks, but as far as I know there is no way to do that. It would be cool if they would make that a customizable option in a point release.

There's also an issue with Track Template VSTi Mono Outputs that was also in S6 were it reverts back to stereo, but Noel is aware of that problem and said it would be addressed soon.

Regards, JD...
saporta
Max Output Level: -89 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 03:25:20

ORIGINAL: JDA

I don't like the new buttons in S7 and much prefer the ones in S6. The darker color with the 3D cartoonish effect does make them much harder to read.



On the one hand I do find S7 has a "cleaner" look but on the other I am looking around longer for the buttons. I've been getting used to where my most often used buttons are since receiving S7 earlier this week. Now that I know better where to find them I am back to liking the seemingly brighter look of the buttons when activated in S7.

Didn't notice a size difference myself.
Hansenhaus
Max Output Level: -56.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 04:33:55
Regarding th S7 buttons -

Did a lot of people request the buttons get a make over? I don't recall reading anything here about that.

The S7 buttons are signifigantly larger. So much so that the same exact configuration of buttons from S6 takes an additional 1" of width and .5" of length on my screen. On S6 I had room for maybe one more tool bar before starting a new row but with S7 my current tool bar setup has no room left in the same row. Not a big deal but I prfer having as much room for tool bars and my tracks as possible.

The colors of the buttons were basically reversed. The S6 buttons had white backgrounds with black symbols. S7 uses black backgrounds with white symbols. I also feel they are a bit harder to read but I'm giving it a little more time before I commit to an opinion. To me, the sysmbols just don't look as distinct. The only reason I can guess why this was changed is to make any button engaged stand out much more form ones that are not. Personally, I had no problem with the S6 buttons. Sometimes I wonder if these decisions are made to simply make something look new and different vs. what's practical. It would definetely be cool if there was an option to revert back to S6 style buttons or a few other choices. Finale has this feature which I like a lot and includes several choices.

One other thing I really wish they would change is the ability to add tool bars along side the default tool bar. If you try and add a tool next to the default tool bar it is forced above or below that row. Kind of a waste of space.






beethoven17
Max Output Level: -82 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 09:03:34
I really like the look of the S7 buttons...but they don't seem to like ME very much!

After spending some time scanning along the rows for particular buttons, I now feel my eyesight's going even faster than it was before. Perhaps SONAR 8 should come with free reading glasses?

I DO like the way the record button (for example) positively gleams red when pressed!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 09:40:51
Eric,

Yes, there was a thread not long ago where people wanted more of a 3D look to the buttons in Sonar. My thoughts about it were exactly what we're seeing here, some will like it and some won't. I have to admit that I like the new look but, like you, I think that Cakewalk should've given us the option to revert them to the S6 look for those who prefer that instead. One thing I don't like is when hitting the PLAY button and hovering the mouse on top of it, makes it change into a speaker. I think this makes it look amateur.

I totally agree with you about the space next to the default tool bar. They should let us use this space, so I'm not sure why it is like that. If it wasn't for this empty area I would be able to have every tool I need in just two rows. Maybe we should summit it as a feature request .


Take care!
saporta
Max Output Level: -89 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 12:08:46

ORIGINAL: Hansenhaus

Sometimes I wonder if these decisions are made to simply make something look new and different vs. what's practical.
<.....>
One other thing I really wish they would change is the ability to add tool bars along side the default tool bar. If you try and add a tool next to the default tool bar it is forced above or below that row. Kind of a waste of space.



Coming from a software industry background I can tell you that customers need to SEE something different in order to feel like they are getting something new. Visual cues are important and add a perceived value. I do agree with everyone that having an option to revert to S6 button visuals or at least putting button attributes in the "color chooser" dialog is a very good idea.

I also agree with allowing default tool bar flexibility. There must be a reason they don't allow it.


bitflipper
01100010 01101001 01110100 01100110 01101100 01101
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 14:16:18
He's right. I routinely change some noncritical aspect of my software's visual characteristics with each major revision. It has nothing to do with functionality, it's purely for the psychological effect. Especially as the product matures, the needs shift from the UI to under-the-hood stuff, but users will be upset if the new version looks exactly like the old one - even if the new rev contains substantial improvements.

Even though I understand the GUI changes, I, too, would prefer the smaller buttons. Even with dual monitors, screen real estate is just too precious to waste on eye candy. I just want to maximize the number of tracks I can show at one time.

timfarman
Max Output Level: -87 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 14:40:03
Can I ask, is registration of Sonar 7 the same as 6? You emailed your serial number and got a second authorisation code from cakewalk If I remember right. I like to reinstall Windows XP if I have bad errors, which happens from time to time, and I find the Sonar registration great, where you get a Code you can keep and use again and again without having to re-register your software (I'm not internet-connected at home, nor do I want to connect using my DAW.
Hansenhaus
Max Output Level: -56.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 15:04:37

ORIGINAL: Jose7822

Eric,

Yes, there was a thread not long ago where people wanted more of a 3D look to the buttons in Sonar. My thoughts about it were exactly what we're seeing here, some will like it and some won't. I have to admit that I like the new look but, like you, I think that Cakewalk should've given us the option to revert them to the S6 look for those who prefer that instead. One thing I don't like is when hitting the PLAY button and hovering the mouse on top of it, makes it change into a speaker. I think this makes it look amateur.

I totally agree with you about the space next to the default tool bar. They should let us use this space, so I'm not sure why it is like that. If it wasn't for this empty area I would be able to have every tool I need in just two rows. Maybe we should summit it as a feature request .


Take care!


Well it looks like I missed the button conversation. :)

Another thing I noticed about the buttons today is while they take up more space, in some instances they appear smaller than the previous ones. The snap to grid button is a clear example of this. I opened up S6 and S7, made sure I had the same exact configurations on screen and then flipped back and forth. I was surprised to see how some of the new buttons appeared slightly smaller. They just have more space around them. Not a big deal though.

zip
Max Output Level: -90 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 15:09:07
Hi All,

I tried unfreezing a "GrooveSynth" I had done with S6 using several midi tracks.
When I unfroze in S7 all parts quantized to half. "Snap to Grid" was off.

Has anyone had this problem?

I'm I missing something obvious?

Thanks for any help,
Zip
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 15:27:59
Eric,

Here's the thread in case you want to read it:

http://forum.cakewalk.com/tm.asp?m=1120734&mpage=1&key=


Zip,

Could you provide some concrete steps to reproduce this. That would help a lot, thanks!

Take care!
zip
Max Output Level: -90 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 15:40:56
Hi Eric,

I recorded one kick drum track using Groovesynth which had 1/16 & 1/4 notes in it.
Then froze the synth and saved project in S6.

I opened in S7, unfroze and the notes were Quantized to 1/2.

Thanks,
Zip
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 15:52:32
Hey Zip!

I know you got confused but my name is Jose . I wanna ask you something though, does unfreezing the same track in Sonar 6 give you the same results you're seeing in Sonar 7?
krizrox
Max Output Level: -35 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 17:22:49
ORIGINAL: Hansenhaus


Well it looks like I missed the button conversation. :)

Another thing I noticed about the buttons today is while they take up more space, in some instances they appear smaller than the previous ones. The snap to grid button is a clear example of this. I opened up S6 and S7, made sure I had the same exact configurations on screen and then flipped back and forth. I was surprised to see how some of the new buttons appeared slightly smaller. They just have more space around them. Not a big deal though.





I must have missed it too but bitflipper's comments make sense. No one would be happy opening up a new version and seeing the exact same interface no matter how good it was before.

Hey before I forget - it there any sort of tool available that allows you to capture a particular color from another part of the screen and use it say... within Sonar? I'm looking for a color picker. I want to take colors from my Scope platform devices and try to incorporate them into Sonar somehow. I've been trying but it's a lot of work to try to match the colors. if anyone know sof a utility like that I'd be grateful.
post edited by krizrox - 2007/09/30 17:36:29
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 19:12:30
ORIGINAL: krizrox

ORIGINAL: Hansenhaus


Well it looks like I missed the button conversation. :)

Another thing I noticed about the buttons today is while they take up more space, in some instances they appear smaller than the previous ones. The snap to grid button is a clear example of this. I opened up S6 and S7, made sure I had the same exact configurations on screen and then flipped back and forth. I was surprised to see how some of the new buttons appeared slightly smaller. They just have more space around them. Not a big deal though.





I must have missed it too but bitflipper's comments make sense. No one would be happy opening up a new version and seeing the exact same interface no matter how good it was before.

Hey before I forget - it there any sort of tool available that allows you to capture a particular color from another part of the screen and use it say... within Sonar? I'm looking for a color picker. I want to take colors from my Scope platform devices and try to incorporate them into Sonar somehow. I've been trying but it's a lot of work to try to match the colors. if anyone know sof a utility like that I'd be grateful.



Oh damn!

I remember someone linking one of these apps a long time ago when Sonar 6 came out. Lemme see if I can find it...BRB.


EDIT: I found it! Go here: http://forum.cakewalk.com/fb.asp?m=969023


HTH
post edited by Jose7822 - 2007/09/30 20:29:01
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 22:24:28
Hey guys!


Just wanted to let you know about some new bugs that have been reported:

1) Clip FX Bug.

2) GUI Bug with Big projects.

3) Audio Cut (Split) Bug.


Give them a try if you'd like but don't forget to report them .


Take care all!
MArwood
Max Output Level: -57 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/09/30 23:49:14
I had a weird thing happen today! I clicked on autotune and clone ensemble popped up! I had to do it again to be sure I was not going click happy!!! I had just made a plugin layout. Don't remember all the details. I just clicked on a plugin layout again and it got corrected.

Locked up 3 times. All were S6 projects with Kontakt 2, EZDrummer and B4. Redid one of the projects in S7 from scratch. It seemed to be fine. Oh yea I forgot this one - Is it my imagination, or are the buses quieter? I put some reverbs on buses and they do not seen to have as much gain as in S6. I used Waves Renverb also FXReverb.

Max Arwood

post edited by MArwood - 2007/10/01 00:09:53
JDA
Max Output Level: -85 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/01 17:29:05

ORIGINAL: Hansenhaus

Regarding th S7 buttons -

Did a lot of people request the buttons get a make over? I don't recall reading anything here about that.

The S7 buttons are signifigantly larger. So much so that the same exact configuration of buttons from S6 takes an additional 1" of width and .5" of length on my screen. On S6 I had room for maybe one more tool bar before starting a new row but with S7 my current tool bar setup has no room left in the same row. Not a big deal but I prfer having as much room for tool bars and my tracks as possible.

The colors of the buttons were basically reversed. The S6 buttons had white backgrounds with black symbols. S7 uses black backgrounds with white symbols. I also feel they are a bit harder to read but I'm giving it a little more time before I commit to an opinion. To me, the sysmbols just don't look as distinct. The only reason I can guess why this was changed is to make any button engaged stand out much more form ones that are not. Personally, I had no problem with the S6 buttons. Sometimes I wonder if these decisions are made to simply make something look new and different vs. what's practical. It would definetely be cool if there was an option to revert back to S6 style buttons or a few other choices. Finale has this feature which I like a lot and includes several choices.

One other thing I really wish they would change is the ability to add tool bars along side the default tool bar. If you try and add a tool next to the default tool bar it is forced above or below that row. Kind of a waste of space.





I also missed the request for the button makeover.

You described perfectly why the buttons in S7 are much harder for me to see than the ones in S6. As a Sonar user with less than perfect vision changes like this can be an important issue. Anyway I'm hoping they will rethink it and at least make the Toolbar customizable to look like S6.

I actually sent in a feature request to make the Toolbar user customizable and I'd hope others would do the same. I don't want to take anything away from the users who prefer the new buttons in S7, but I think having the option to change things in the Toolbar would be a good thing.

Regards, JD...
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
RE: Sonar 7: First Impressions / Bug Report 2007/10/01 18:43:53
Give them a try if you'd like but don't forget to report them


I would caution against everybody reporting the same bugs, unless you have some new information, preferably an easily-repeatable test case. Somebody has to sort through all those bug reports and condense multiple reports into a single problem ticket. Having a hundred people report the same bug is only going to slow down the process.
altima_boy_2001
Max Output Level: -55 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/01 19:15:34
ORIGINAL: JDA
I also missed the request for the button makeover.

You described perfectly why the buttons in S7 are much harder for me to see than the ones in S6. As a Sonar user with less than perfect vision changes like this can be an important issue. Anyway I'm hoping they will rethink it and at least make the Toolbar customizable to look like S6.

I actually sent in a feature request to make the Toolbar user customizable and I'd hope others would do the same. I don't want to take anything away from the users who prefer the new buttons in S7, but I think having the option to change things in the Toolbar would be a good thing.

Those dark buttons are annoying...don't understand why you don't have the option to go back to previous version colors. Color presets have Sonar 6 and Sonar 5 colors as options so why not the same for buttons? Even if they clash with the new colors and look out of place I'd go back to the old ones...

For me, the best interface look was with Sonar 4 and the GUI color and style changes just goes downhill with every new addition...I'm not a kid anymore so I'd prefer it if my software didn't look cartoonish...
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/01 19:58:48

ORIGINAL: bitflipper

Give them a try if you'd like but don't forget to report them


I would caution against everybody reporting the same bugs, unless you have some new information, preferably an easily-repeatable test case. Somebody has to sort through all those bug reports and condense multiple reports into a single problem ticket. Having a hundred people report the same bug is only going to slow down the process.



Yes, very good point there Bit. Thanks!
Blades
Max Output Level: -43 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/02 08:03:50
Hey guys...can you reproduce this issue?

I've so far only tried this on one project - it's a revived S5 project.

It doesn't seem to matter where I put perfect space - I tried on an aux bus and a group bus - once it's there and enabled, Play does nothing at all. If I just disable PSpace, don't even have to delete it, everything rolls right along, enable = no play.

That's all the detail I have on it, as I just noticed it yesterday before walking away from the PC, so it may not even be reproducable, but I saw a similar complain in the forum this morning, so I thought I would throw it out there for some kicking around.
kp
Max Output Level: -61 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/02 08:37:32
Blades - check the MIDI Prepare buffer size (one of the global options pages). I can't remember whether you need to increase it or decrease it, but I can remember having something like this with Perfect Space in the past.

Alternatively, try changing the buffer size in Perfect Space itself (or both to come to some compromise).
Blades
Max Output Level: -43 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/02 17:24:14
Ok...I changed some settings around and it seems that it was just some combination of things that didn't make sense to PSpace.

When I have my latency in PSpace at 4096, anything less than 5.8ms set in Sonar does not play.
If I change perfect space to 1024, then I can play all the way down to 1.5ms Sonar latency.

So...lesson is: play with your settings.

Move along, nothing to see here...
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/02 17:46:16

ORIGINAL: Blades

Ok...I changed some settings around and it seems that it was just some combination of things that didn't make sense to PSpace.

When I have my latency in PSpace at 4096, anything less than 5.8ms set in Sonar does not play.
If I change perfect space to 1024, then I can play all the way down to 1.5ms Sonar latency.

So...lesson is: play with your settings.

Move along, nothing to see here...



Well I'm glad you got that working again.

Take care!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 16:43:14
Hey Eratu!

I would like for you to try playing a project in Sonar 7 and then, while the project is still playing, switch to another computer using your KVM switch. Everytime I try this the Audio Engine stops in Sonar 7 and I didn't have this problem before. I just want you to confirm this for me, please. Thanks!
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 17:10:40

ORIGINAL: Jose7822

Hey Eratu!

I would like for you to try playing a project in Sonar 7 and then, while the project is still playing, switch to another computer using your KVM switch. Everytime I try this the Audio Engine stops in Sonar 7 and I didn't have this problem before. I just want you to confirm this for me, please. Thanks!



Hey Jose,

No problems here... just tried it out now. Perhaps you have a conflicting key-binding issue? The key I use to switch is the CTL key... I just double-click it on the keyboard and it works just fine, and doesn't do anything to Sonar. Perhaps your KVM switch uses a different key combination that conflicts with Sonar? I have a rather old but trusty little KVM from years ago... I think it's a Linksys. Try manually switching your KVM if it has a manual button and see if that triggers the problem.
sparkyness
Max Output Level: -89 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 17:21:28
Have spent the last two evenings trying to sort out latency issues with External Inserts. My rather lengthy moan, trials and tribulations are on this thread: http://forum.cakewalk.com/tm.asp?m=1175856

Have got it reduce from a slap back echo to phasey nastiness, but little luck otherwise. As a recent convert from Cubase, I might add that their implementation of hardware support is a lot less hassle by a long way in my experience. Reported to tech support via email yesterday as well. No response as yet.
post edited by sparkyness - 2007/10/04 17:31:27
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 17:29:00
Hey Eratu!

Thanks for trying it out. To be honest I didn't know I could assign a keybind to this thing as I always use the physical button to switch between computers. Mine is a discontinued Belkin KVM switch with USB and media (speaker + mic) conncetions, but I don't use the latter. It doesn't use drivers but there's a software that comes with it which enables me to switch by clicking the virtual button that it installs, but it is not necesary so I don't use that either. So basically, I have nothing from it installed (no software or drivers) and only my Keyboard Video and Mouse connected to it. For some reason this didn't used to happen before but now, since installing Sonar 7, it is. I already reported this to Cakewalk but I have no idea if there's a fix for this. Anyways, I appreciate your time.

Thanks!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 17:45:17
Hey Sparkyness,

Sorry to hear this. I would've helped you but when I tried the EI plugin I used a Multi-FX unit and it worked fine. I didn't have to mess with the offset button either but that could've been attributed to the nature of the FX themselves. On the other hand, I didn't notice any phasing when the unit was bypassed either. Since I don't own another piece of hardware to try it out I probably can't really help you much but I'll try to run some more tests later tonight. Hopefully someone else can help you out before then.

Take care!
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 17:47:05
Not sure if I was clear... when I mentioned key-binding, I was implying that maybe some existing and NEW key-binding inside Sonar conflicted with your KVM's trigger key. Most KVMs I've tried have a button combination on the QWERTY keyboard itself that triggers an action on the KVM, and it usually doesn't require drivers of any kind. (Mine uses a double CTRL click, others I've seen use a double shift, or double delete, or some other combo that the KVM intercepts and performs some action on.) So what happens in some apps is that the app AND the KVM will respond to the key combination sometimes.... it's weird. I recall some other program I used in the past that did something strange when I used my KVM key command. I had to be careful. I haven't installed any drivers at all for my KVM... it works with *almost* anything, including Linux machines. But that QWERTY key combination is in addition to the manual button most KVMs have. So I was thinking that perhaps whatever your Belkin uses on your QWERTY keyboard, you were triggering both -- both the KVM action, and a new action inside Sonar 7 that you didn't have previously. I hope that makes sense.

Also, I have two monitors, so maybe something is happening there that's different? Don't recall if you're setup has two. Not sure that would make any difference at all.

Anyway, I guess the thing to try is another KVM. They're so cheap now... problem is that so many of them are still picky. I bet something quirky outside of Sonar is happening. :(
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 17:57:18
Ahhhh! (light bulb turns ON).

Ok, I see where you're going with this. I thought about it but didn't go the extra mile. I should've deducted it since using a keybinding would be like using the physical button to trigger the switch between systems. I will investigate that for sure. I'll report back if I have discovered anything new...thanks!

Take care!
sparkyness
Max Output Level: -89 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/04 18:37:43

ORIGINAL: Jose7822

Hey Sparkyness,

Sorry to hear this. I would've helped you but when I tried the EI plugin I used a Multi-FX unit and it worked fine. I didn't have to mess with the offset button either but that could've been attributed to the nature of the FX themselves. On the other hand, I didn't notice any phasing when the unit was bypassed either. Since I don't own another piece of hardware to try it out I probably can't really help you much but I'll try to run some more tests later tonight. Hopefully someone else can help you out before then.

Take care!



Cheers.....now appear to have it working as an insert on a track but still getting phase issues when using External Insert on a bus. Can't figure that one out!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/05 01:06:02
Hey Sparkyness,

I've just finished messing around with the External Insert plugin and made a couple of observations. The first one is that each time you press the "Delay" button without running the project afterwards will not give you accurate calculations hence you'll get various accending latencies. But if you run a couple of seconds of the project after making the calculations the first time and then hit "Delay" once more, the latency number will go down to it's actual value and will stay there no matter how many times you click it. I tried this with two different projects and I got consistent measurements both times (38ms). I think this is why people are having issues with it, since all the calculations before running the project are wrong.

The other thing I noticed was the phasiness you were refering to but I couldn't find a way to completely eliminate it (even though my first observation helped reduce it). Also, the offset buttons didn't seem to be doing anything but I might be wrong. I did try some high settings but heard no difference. Anywho, give it a try and let me know if this helps a little.

Take care!
sparkyness
Max Output Level: -89 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/05 03:06:38
I had noticed similarthings already, in regards to the differing delay calculations depending on whether you play the project or not. In fact, I can't even get a delay measurement without running the project first.....but I do have consistent results now. The problem was that I was testing it on a bus as most of my outboard gear is used on busses for the likes of parallel compression (as opposed to insert compression) or reverb used across various instruments.

It works fine when used as an EI on a track....just not on a bus where the phase issues remain and the offset values aren't helping matters when I use them. Bizarre.

Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/06 13:40:25
BUG FIX UPDATE:


Hey all!

I just wanted to give you an update on the bugs that have been confirmed and fixed by Cakewalk for those of you who didn't know. I'll link the posts where the bugs were confirmed by either Cakewalk themselves or by people who have been in contact with them next to the name of the bug. Hopefully, the fixes will be released in the first patch. Here they are:

- Clip FX Bug: http://forum.cakewalk.com/fb.asp?m=1174234

- Large Project Redraw Bug: http://forum.cakewalk.com/fb.asp?m=1177331

- Split Tool (Cut Tool) Bug: http://forum.cakewalk.com/fb.asp?m=1176732

- LP-64 EQ and Compressor Bug: http://forum.cakewalk.com/fb.asp?m=1171264

- VC-64 "Manual" Button (Reg Edit Fix): http://forum.cakewalk.com/fb.asp?m=1167499

- Bus Soloing (Dim Solo) Bug: http://forum.cakewalk.com/fb.asp?m=1170072 / http://forum.cakewalk.com/fb.asp?m=1171728

- Controller Drawing Bug: http://forum.cakewalk.com/fb.asp?m=1171410

- Sonar 7 x64 Plugin Manager Bug: http://forum.cakewalk.com/tm.asp?m=1176820&mpage=1&key=�


Well, that's all I have for now. Still no word about the Step Sequencer CPU munching bug or the phasing problems with the EI, but hopefully they have corrected those as well.

Take care all!
post edited by Jose7822 - 2007/10/08 14:52:22
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/06 14:04:20
Thanks, Jose, you are awesome! I think I saw in a recent thread that Keith from Cakewalk had confirmed that they had fixed (or were going to fix) the SS CPU bug. I can't recall the thread... but it was within the last 24-48 hours I believe.
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/06 17:22:35

ORIGINAL: eratu

Thanks, Jose, you are awesome! I think I saw in a recent thread that Keith from Cakewalk had confirmed that they had fixed (or were going to fix) the SS CPU bug. I can't recall the thread... but it was within the last 24-48 hours I believe.



Cool! That's good news. Take care!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/09 21:52:18
Hey Eratu and everyone!

I think I just figured out my problem with the KVM switch. I guess at some point in time I was experimenting with how certain Hotfixes improved my system's performance by uninstalling and reinstalling them but I had forgoten to re-install one of them. This past weekend I decided to do my tri-annual system clean-up event by reformating my HDDs so that I could have a fresh install of Windows but more importantly of Sonar 7. I proceeded to install everything from a drivers and hotfixes CD I have created except one Hotfix. But I still had the KVM problem until today when I decided to install it and....abracadabra.....the thing just works. I'm again able to switch systems without the audio engine stoping, YESSSS! Anyways, the Hotfix I'm talking about is this one:

http://support.microsoft.com/kb/888111

And this is the list of improvements for the user according to the knowledge base:


• Easier installation of audio peripherals
• Easier installation of audio drivers
• Better system stability
• Better performance
• Glitch-free audio
• Improved security of the content that you want to help protect
• Fewer vendor-supplied drivers
• Less need to upgrade drivers
• Guaranteed basic audio support for UAA-compliant devices


You have to call M$ to get it but it's free. I guess I could post it here if you tell me that you would like to have it. Anyways, I just wanted to share that and let you know that I'm back in business.

Take care!

P.S. By the way, this has also cured the white SOD I used to get everytime I started Sonar for the first time after booting up Windows.

EDIT: OK, maybe not the white SOD .
post edited by Jose7822 - 2007/10/10 01:52:22
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/10 09:09:51
Yahoooo! Glad it's up and running. Thanks for the tip. I've never heard of that fix before. I'll make a note of it if I might need it in the future.
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/16 14:40:42
Happy Update!

Just wanted to give you the heads up on the known bugs we have discussed in this thread (refer to post #158 of this page). As of Sonar 7.0.1 and my limited time testing it, it seems that all of these bugs have been squashed out of existence and now Sonar 7 is performing awesomely. The Step Sequencer, which was the one I had major grips with, is now ROCK SOLID! No more CPU hoging, slow drawing or child windows sneaking up on you. I can't believe how stable this thing is for me right now. Major kuddos for Cakewalk and the beta team. Nice job!

Take care all!


P.S. Eratu, now you can automate the new plugs.
post edited by Jose7822 - 2007/10/16 14:57:27
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/16 14:55:13
Holy crap! Is 7.01 already out?! How did I miss that!
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/16 15:04:09
They must have been working around the clock on this update. In the notes, just about all of the known issues I've heard about appear to be fixed. Downloading and installing now. Just in time for this big project I'm working on! Great job, Bakers!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 00:30:57
Dang it!

I knew I spoke too soon. Even though the Step Sequencer is performing better than before I'm still experiencing CPU munching when the interface is opened. Also, the freaking child window (when double-clicking on the sound names) still creeps behind the interface effectively locking it and the only way to make it show up on top is by clicking the Windows "Start" button.

Please Cakewalk fix this on the next patch, please....I really appreaciate the improvements though.


On the same note, I think I found a bug with the RXP Player. For some reason I'm not able to audition or load any grooves into it. I admit I haven't used it in a while but I remember being able to click on the grooves to audition them and then double-clicking would load 'em into the player. Well, none of that happens anymore. Can anyone confirm this?

Thanks!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 01:02:24
Found another one (actually you might call it a variation of a previous one). Give this a try:

1- Open one of you current projects containing several Audio Tracks.

2- Use the Split/Cut Tool and start splitting audio clips (the more the better).

3- Go to Tempo View and make some radical tempo changes (I drew various "V" shapes).

4- Now go back to Track View....Surprise!

5- And for the final touch, play the project.


Interesting, huh? Just in case you're wondering, in step (4) you should notice that parts of the split audio clips suddenly disapeared. In step (5), everything plays out of sync with repect to each other. It's like tempo changes are not applied globally but more like individually and each track has it's own tempo. Anyways, try this out as well as the one at the bottom of my previous post.


Thanks a lot guys!
post edited by Jose7822 - 2007/10/17 11:39:39
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 09:41:19

ORIGINAL: Jose7822

Dang it!

I knew I spoke too soon. Even though the Step Sequencer is performing better than before I'm still experiencing CPU munching when the interface is opened. Also, the freaking child window (when double-clicking on the sound names) still creeps behind the interface effectively locking it and the only way to make it show up on top is by clicking the Windows "Start" button.

Please Cakewalk fix this on the next patch, please....I really appreaciate the improvements though.



Yeah, in testing 7.01 briefly last night I also experienced some strange behavior. I don't know for sure if it is the step sequencer's fault yet and I don't have enough time right now to troubleshoot it as I normally would. But while the improvements are appreciated, like Jose says, I suspect there's a lot more work to do!
jeffn1
Max Output Level: -72 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 10:16:37
I might be the only one with this problem, but here is my bug report:

I can't seem to open a project in Sonar 7 that uses Kontakt 2 and Guitar Rig 2. I am using it in Windows XP. I have 3 gb's of Ram.

I have this problem when I install Guitar Rig 2 as an effect with Kontatk (using the Prominy LPC sample library with the superperformance multi loaded).

I can load up Guitar Rig 2 in the project and it works fine. But, when I open up the project after, it freezes.

If I load it while holding the shift button, I can load the project without Guitar Rig 2. So, it is not the large multi causing it.

Similarly, if I load the project in safe mode and do not load Kontakt 2, but do load Guitar Rig 2, it will load Guitar Rig 2 fine.

So, it appears there is some interaction between Guitar Rig 2 and (in my case) Kontakt 2. (If course this is a little ironic, considering they are both NI products).

Interestingly, I do not have this problem with Guitar Rig 1.

Also, I was doing the exact same thing in Sonar 3.1.1 (I just bought Sonar 7) and I did not have a problem.

jeffn1
Legion
Max Output Level: -55.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 11:02:03
Universal UVI Player DXi, unable to acces GUI and Universal UVI Player VST crashes sonar:

"A fatal error has ocurred in plugin 'UniversalUVIPlayerVST'

Module: c\program files\steinberg\vstplugins\romplers\UltimateSoundBank\UniversalUVIPlayer\UniversalUVIPlayer.dll
Exception code: c0000005
Adress: 132752EE:00000002:0012F1A8

As a result of this error SONAR is about to exit abnormally.
Should SONAR attempt to save a recovery copy of your work?"
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 16:30:22
jeffn,

Sadly I won't be able to help you with this as I don't use Guitar Rig. Hopefully someone else has these two plugs so they can test it out. Anyone?


Legion,

The best way to report this is by sending a mini dump to Cakewalk. In order to do this follow the steps provided here:

http://www.cakewalk.com/support/problemreporter/minidump.asp


HTH
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 16:33:06
So, anyone willing to confirm these bugs I've described in posts #166 and 167?
jeffn1
Max Output Level: -72 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/17 21:20:59

ORIGINAL: Jose7822

jeffn,

Sadly I won't be able to help you with this as I don't use Guitar Rig. Hopefully someone else has these two plugs so they can test it out. Anyone?


Legion,

The best way to report this is by sending a mini dump to Cakewalk. In order to do this follow the steps provided here:

http://www.cakewalk.com/support/problemreporter/minidump.asp


HTH


Thanks, I will do that.

jeffn1
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/18 16:01:05

ORIGINAL: dbmusic


ORIGINAL: Noel Borthwick [Cakewalk]


ORIGINAL: krizrox


ORIGINAL: Duojet


ORIGINAL: dbmusic


ORIGINAL: krizrox

I have enough time now with V7 to state that the popping and clicking associated with multi-processor support has been corrected. I've done a recording session and 6 hours of mixing work. Not a single pop or click. If you're a veteran of this problem and waiting to buy V7, I say go for it.

I did, however, notice a couple of other nagging problems that weren't resolved:

1) that annoying motorboating noise (it's an extremely annoying noise that sounds like Jim Carey in Dumb and Dumber making the most annoying noise in the world). Still random. Still there.
2) the black screen of death that appears every time you open V-Vocal.

Whatever - not show stoppers. Happy just to be able to take advantage of the MP thingy now.



I wish someone to would have a clue about this "motorboating noise" and how to resolve it. I have it too Larry and it drives me freaking nuts. I can reproduce it by simply opening a project and playing an audio track for the first time. After that it seems to occur randomly.



do you have read/write caching (or buffering) turned on? if so try turning it off. i forget exactly where the setting is, somewhere in audio preferences. if the number is too low i used to get that sound. I don't even have them checked anymore.


I checked to be sure - read/write caching is disabled. I've never enabled read/write caching ever. One time I think I tried it but it made things worse so I left it off. Thanks for the suggestion though.



What hardware? From your description it seems like it would be driver related. A noise like that can happen when the driver is continuously repeating a buffer of audio rather than streaming the audio we send to it.




Using an RME Fireface 800 here with XP SP2. Different driver updates have had no effect toward resolving this "motorboating".


I've just started to get this random, periodic motorboating noise after some updates to drivers, BIOS, CPU, plugins and Sonar 7.01. Obviously, several key changes to the system have been made, and that makes it almost impossible to determine what specifically is causing the problem. Anyone resolve this motorboating problem?
Mike Fisher
Max Output Level: -63 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/18 16:03:46

ORIGINAL: eratu

Is 7.01 already out?! How did I miss that!


7.0.1
eratu
Max Output Level: -46.5 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/18 16:07:26

ORIGINAL: Mike Fisher


ORIGINAL: eratu

Is 7.01 already out?! How did I miss that!


7.0.1


Thanks, usually I'm a stickler for details like that.
Mike Fisher
Max Output Level: -63 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/18 16:10:44

ORIGINAL: eratu
Thanks, usually I'm a stickler for details like that.


What's amazing is how many things were addressed in just a '.0.1' update!
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/18 16:24:04
Sooooooo, do I have any volunteers?
Jose7822
Max Output Level: 0 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/18 20:58:40
Anyone????
Blades
Max Output Level: -43 dBFS
RE: Sonar 7: First Impressions / Bug Report 2007/10/18 22:16:05
Jose, I'll take a look at them next opportunity...my mother just moved back into town and it is unfortunately going to rule some of my time in a less-tan-pleasant way.

If this update doesn't make it obvious that they are paying attention to threads in the forum, I don't know what will...and you know what - it's the logical threads with decent presentation of the cases and no arguing that they seem to have paid attention to - like this one.
Page: < 1234 > Showing page 3 of 4