Sorry, It was late...or early, depending on your perspective.  I meant the 'beats in clip' button vs the orig. bpm button.  for vocals, I use the 'tempo' button option. 

If you have a few MIDI tracks and then solo one the MIDI meters no longer work after you unsolo. Confirmed - though I only get it if the transport is stopped - if project is playing it behaves normally. Midi meters return once project closed & reopened.

edit to add - all tracks other than the soloed one lose their midi activity soloed track keeps going.

Okay. I'm finally seeing this. You have to stop the transport while the one track is playing back soloed; then the MIDI activity indicators in the other tracks will have stopped showing activity when you restart playback, and will stay that way when you unsolo the one track.

I also found, however, that you can easily get the activity back by muting and unmuting the tracks with inactive meters, either with the transport running or stopped.

Also, I would say that it makes sense for MIDI meters to cease showing activity when another track is soled, just as audio meters do. The bug is that they don't come back.

I am finding the samples from Ezdrummer are taking much longer to load under the 8.5.1 version.   It works but it takes a long time.  Has anyone else noticed this?

John

I'm still not getting Sonar to crash.

LOL that is so funny. Now we are trying to crash it. Well I crashed it by trying a PSP plugin in a project. It seems PSP is not Sonar friendly any more.

Johnny5078


I am finding the samples from Ezdrummer are taking much longer to load under the 8.5.1 version.   It works but it takes a long time.  Has anyone else noticed this?

John

It's always been slow for me John. I've been told the reason for that is due to me running 24/48 and the EZD samples are not the same so it converts or something as it's loading up. Since day 1 it's always been a long load time for me though....and I have a pretty quick system.

LOL that is so funny. Now we are trying to crash it. Well I crashed it by trying a PSP plugin in a project. It seems PSP is not Sonar friendly any more.

 You guys think this is funny – huh   
 
I’m not trying to crash Sonar 8.5, but it crashes every single time I try to deselect my PadKontrol.
I opened “Midi Device Setup”, deselect my PadKontrol or Edirol PCR50, click OK and Sonar 8.5 hangs. 
I was surprised the first time it happened and ruled it off as an isolated incident, but after I restarted Sonar (then later rebooted) I realized that I cannot deselect a midi device in Sonar.
 
This has never happened in any of my prior versions of Sonar.   Of course I can just power down the units or unplug its USB cable, but I sometimes switch between Reason/Sonar and like turning on/off devices to avoid duplicate triggers.

Anyone here knows another way to deselect a midi-device in Sonar?

krazylain

LOL that is so funny. Now we are trying to crash it. Well I crashed it by trying a PSP plugin in a project. It seems PSP is not Sonar friendly any more.

 
 
 
You guys think this is funny – huh   
 
I’m not trying to crash Sonar 8.5, but it crashes every single time I try to deselect my PadKontrol.
I opened “Midi Device Setup”, deselect my PadKontrol or Edirol PCR50, click OK and Sonar 8.5 hangs. 
I was surprised the first time it happened and ruled it off as an isolated incident, but after I restarted Sonar (then later rebooted) I realized that I cannot deselect a midi device in Sonar.
 
This has never happened in any of my prior versions of Sonar.   Of course I can just power down the units or unplug its USB cable, but I sometimes switch between Reason/Sonar and like turning on/off devices to avoid duplicate triggers.
 
Anyone here knows another way to deselect a midi-device in Sonar?
 

Actually krazy, we think issues like that suck and wanna see ya get it fixed. :) I had this issue in Sonar 5. Try doing this to humor me....I know this sounds strange. But, when I had this issue in Sonar 5, it would crash on me every time. What stopped it was the order in which I enabled/disabled the midi stuff. Instead of working with your midi in first, try enabling the midi out of the unit first, then the in. See if it makes a difference at all just for the heck of it. I soo had this same thing happen with my JL Cooper controller. Sometimes it would be disabled in the midi options and to enable it, the first thing I'd do is go for input. As soon as I did that and enabled the output, bang...crash or a hang every time. So, one time I went in and did it in reverse...output first then input and it never did it again. Thought I was seeing things, went back and tried in first then out, crash and hang.
 
I'm not sure this will help fix your problem, but it's the only thing I can suggest as I have had something similar to this happen to me. Good luck.

This has never happened in any of my prior versions of Sonar.   Of course I can just power down the units or unplug its USB cable, but I sometimes switch between Reason/Sonar and like turning on/off devices to avoid duplicate triggers.

8.5 added support for dynamically adding and removing USB MIDI ports. This may be both the cause of and the answer to your problem. What happens if you power down the device(s) while SONAR is running? You should get a dialogue pop-up within a few seconds that says:

<MIDI Device Name>


The above Audio/MIDI device was disconnected from your system. Would you like SONAR to reroute these outputs to an available device?
Clicking 'No' allows SONAR to remember output settings to this device.
Note: If playback is in progress, clicking 'Yes' will stop the transport.

brundlefly

Have you tried appending the correct file extension yourself?  For example, naming it "Test Project 8.5.cwp" instead.

Yes. The file format is fine. It's just that the extension is written incorrectly. Incidentally, I do not have Windows set to "Hide extensions for known file types". I like to know exactly what I'm looking at all the time.

What you're running into is not a Sonar problem per se but a Windows problem. Windoze will allow you to have any extension you want, even if it's illegitimate. And multiple periods are not allowed.

What you're running into is not a Sonar problem per se but a Windows problem. Windoze will allow you to have any extension you want, even if it's illegitimate. And multiple periods are not allowed.

Darn. I thought we were done beating this dead horse. Please go back and read my post #66.

No issues on my end John. Then again, I'm sure the version of the plugs I'm using may be the case. Version 1.6. All worked perfectly here without a crash.

Thanks Danny. I took another look at it and my version is 1.8. I also have the 1.9 version and the 1.6 version. I upgraded to the 1.9 and it didn't work on my system. I then wrote PSP and they basically said "tough". I uninstalled the 1.8 version and installed the 1.6 version just now. I got a huge loud distorted sound with the meters at clipping and beyond but it didn't crash Sonar so I went to audio options and unchecked the double precision 64 bit audio engine. It worked fine. But now I don't know if its worth it not to have the the 64 bit engine on. I will try the 1.9 version and see what happens.

Update the 1.9 version crashed Sonar.

A little more investigating. All the other hosts I have run the PSP stuff just fine. Samplitude Studio and Reaper. Sonar is the only one that is having problems. The version 1.9 wont even load in Sonar without a crash.

So to summarize PSP Stereo Pack 1.6 works as long as the 64 bit audio engine is off. The other versions will not work with Sonar 8.5.1. Version 1.8 did work with Sonar 8.3.1. All seem to work with any other host. I have found this pack to be very useful. I will try 1.8 again.


UPDATE TWO! Its working the 1.8 version with the 64 bit audio engine on. YEH! And thanks Danny for getting me to try different stuff. If you hadn't shown any interest in this I might have just not pursued it.

OK - this forum software is ****ed - I'm replying to John ::
 
You really might wanna try mix pack2 - the bass module is waaay better....

donald


The Arpegiator doesn't work as adversited. I've tried out a number of different patterns, which I've double checked with similar patterns in P5 and in S8.51PE I more often than not get the root note playing 1/32s all the way through the pattern. It gets better, i.e. less noise from the 1/32s root notes if I increase mix. It depends a bit on what instrument I'm using, but I've compared it to http://www.youtube.com/watch?v=oLUNeZZf9WM with the same setup in Sonar, but it doesn't sound anything like it.
This has to be a bug somewhere, or I'm just really stupid and don't understand how to use it.

Confirmed - this arp does not work well at all - it seems full of bugs which I will attempt to describe below. Before I do that, let me respectfully say that I am fairly ticked off by yet another half finished feature being deployed (track layer and instrument track bugs are still there) without any thorough testing! I use arps all the time, and I can honestly say I think this one was either conceived, built, and tested by someone who had never used one before, or is simply so full of bugs that it just appears that way. This feature was one of the reasons I opted for this upgrade (which is a bit slim on features otherwise) and it doesn't work. Please Cakewalk, take more time to design and test your features. Now to specific problems with the arp:

1.) The mix control does not work properly. 50% should indicate the arped pattern and source notes can be heard equally, and thus 0 and 100 percent would be the arp only and source only respectively, yet sometimes no setting I choose gets rid of the unintended mix of the source note, and no setting gets me only the arped pattern or the trigger source. 100 percent sometimes produces silence.

2.) The dropdown menus and selection arrows do not seem to work correctly. I have to select the same selection repeatedly to change from dotted, triplet, etc. since the menus do not work right. I am also not convinced that the selections for tempo even match what they say they are - eg. eight notes sound super slow (more like quarters).

3.) The displays of arp controls, such as "Octave 1" do not update properly. Half the time I select octave of 1 the display stays at 2, etc.

3.) There appears to be random 32nd and 64th notes interspersed behind what I should be hearing. Others have also pointed this out. Happens most with patterns as opposed to "shapes".

5.) All of the included patterns (all from Project 5) seem to sound ridiculous when played with this arp. This is NOT how they should sound, as pointed out by others who did direct comparisons with P5. They are as good as useless if this arp interprets tempo, pitch, and other settings differently.

6.) Who ever heard of a swing setting of off or on?! Seriously this can't be real?! The whole point of swing is to slide the notes in time to change the feel of how they interact with other tracks. What are we supposed to do with on or off and no way to control the amount? Make this a percentage like every other arp on the planet.

7.) Changing from pattern "Rhythm Only" (chord) To "Forward" (Up) should sound identical if only one key is depressed. Instead "Forward" sounds like it has less velocity.

8.) Adjusting the 'duration' control causes more droning or echoed notes behind the intended notes instead of simply changing the length. Settings over 100% sound like the Mix control was changed, and actually start to add back in the source note. It really doesn't make sense to have more than 100% duration notes in my opinion.

9.) The names of the standard patterns are ridiculous. "Forward/reverse" and "circular forward", etc. instead of the typical and functionally descriptive "up", "down", "up and down" etc. used by every other arp in the world. Same thing for "Rhythms Only" which really should be called "Gate" or "Chord" like other arps to accurately describe the function. Viewing the arpeggiated patterns on a piano roll might help Cakewalk find better names.

I can see the promise of this tool, but it just doesn't seem to have been designed by someone who actually uses arps. It was definitely not tested by someone who uses and understands them. I found all of these problems within about ten minutes - why couldn't the beta testing team or the software engineers? I think Cakewalk might do better to focus on longer design and testing of features which would also offer the advantage of less time spent programming. Whats strangest is that the Project 5 arp was used and loved by many, but they didn't just convert it for use in Sonar, instead making a new one that doesn't work...

D.

Could you do a screen print of the buttons with those options, please.

I think mine is corrupt because there is no such wording attached  to any of the buttons and I've been all over it.

Or show me how it looks so it triggers from the beginning, from the current position or continue because I've tried every option under the sun and it's just doing what it likes. Believe me, I wouldn't post without testing.

I've discovered why the columns move (disappear) when it's in its default small size. It's affected by the scroll wheel. If you left click to the right of the last column. You can scroll (down) the columns out of sight. So if you have three columns and left click to the right of the third column, you can then use your scroll wheel to make the first two disappear. Then it allows you to make more columns without enlarging and a scroll bar then appears on the bottom. If you then left click to the left of the column then it 'locks' it out of sight until you left click on the right of the column again. That's one odd feature.

It happens on the large view too. This mean if you accidentally do it, you can 'lock' columns out of view - like I did. Sorted that bit, at least!

Also what options do you get in the from the 'options' button - mine just gives one about empty cells?

Thanks.