Mike the behaviour you are seeing when double clicking the MIDI track to open the PRV and the snap to resolution changes is consistently repeatable. I can't make out whether it's a bug or should be a feature request to allow different resolutions in different views but either way it's not logical behaviour.

The 1/16 triplets I think you mentioned is just co-incedental - if you change the resolution in your PRV to 1/2 for example and then close it - go back to the Track View the snap to resolution is now 1/2 as is expected if the snap to is now global. But, change the snap to resolution in the TV to something else 1/16 for example and now double click a MIDI track to open the PRV the snap to resolution changes to 1/2 in the PRV.

You'd expect that if snap to isn't global but it has now also changed in the TV. I can't make out whether snap to is global and the bug is re-setting it to the last setting in the PRV, or if we should be able to set different snap to resolutions in different views and the bug is stopping that.

Either way there is no logic to the behaviour. It may already have been reported but I've done it anyway. The more bug reports the merrier......... CWBRN-3853

dontletmedrown


I just watched the video.  I've always had unexpected results using groove-clipping since maybe Sonar 6.  Because of it, I changed my workflow and now I always compose to a metronome. If I need to loop something, I'll do it manually.  That always works out faster than trying to arm-wrestle Sonar.

Hi Dave,

I don't know if you noticed but my project was set at 96bpm and I free played without a metronome at 95.72bpm.

There was a metronome... it was in my head.   :-)  I'm a guy that insists that I am not a good musician, I'm just a sound tech with a solid work ethic who practices a lot in my free time.


Like I said above I start projects in a wide variety of ways. What ever suits the project or mood.

If Set Measure/Beat is simply not going to work I'll go back to the fit to improvisation as I have that worked out real well... but it's a joy kill type of drudgery to prepare a MIDI clip for fit to improv once you've played a nice groove.

Set Measure/Beat at Now was designed and sold to use precisely to streamline the fit to improv process and provide a sensible way to quickly average a tempo across a series of measures of freely played music.

Set Measure/Beat at Now is also a great first step to preparing free played music for staff transcription.

best regards,
mike

stratman70

mike_mccue

John T


Imagine having to start "from scratch" on a four bar loop when you knew exactly how to fix it even beforehand. Oh, the agony.

More attacking the messenger.

Slime Ball.

Mike while you have toned down your constant, constant attacks in almost every positive thread here-does not mean the past all goes away. Read over "your" posts since X1 came out. Sorry, but they are "ATTACKS" on the software, the company and anyone who dared post a positive thread.
Now you are trying to tone it down. OK-That's good. That's a start. I have watched your video 5X and I have read and re-read the post from the Geek and 2 others about the process you filmed. Without really ever using the process in my work it's fairly easy to see how to avoid what happened-Yes, I know you followed the manual word for word. But, Mike, your sonar knowledge and skillset are far beyond mine and the manual-so why.............................
Reporting John T. and I guess myself is OK. Have at it. But please report yourself. I NEVER attacked CW, never went out of my way to sabatoge every positive thread because I was unhappy. I only responded "in kind" to you when you engaged in this offensive of yours against CW, X1 and anyone who posted positive experiences. It amazes me how you do your best to undermind the launch of X1 and then turnaround and accuse others of attacking you.
You use "nice words, inuendo and intellectual wit" to sugar coat your attacks.
 

It's gone to a S**T fight between John T and Mike. Should have never gone there. We all all have our own agenda, our own personal stress due to our own immediate future coming up. If you want to be constructive in this "forum", add answers and questions, not deragitive remarks about the poster. Clarify the problem whether it is a brain fart on the part of the poster or a bug in "our" system. Otherwise, you aren't adding to the knowledge and learning yourself.

UnderTow

rbowser


Setting beat at now?--Why?

So that the Project Tempo gets adjusted top what is being played. That is quite obvious.

I guess the manual says that, and this whole section that you were referring to should be rewritten.

No of course not. The bugs should be fixed.

Making a groove clip is a much more straight forward proposition and works when the length of the clip is correct before applying the groove.

This is true. I tend to automatically hit Bounce-To-Clips before turning anything into a groove clip but that doesn't mean that Sonar shouldn't work the other way round too. Or, if there are technical limitations to fully implementing this, Sonar should do the "apply trimming" or "bounce to clips" itself with a warning that any data outside the clip will be lost. As it stands, the implementation is either buggy or sloppy depending on how you look at it.

You seem to be arguing something truly bizarre: That it is OK that the software is implemented the way it is, that users should figure out their own workarounds and that there is something wrong with Mike for pointing out the flaws. That is pretty damned freaky if you ask me.

Mike, I basically was simply asking if your post was to be taken literally when you said you were putting together a hypothetical situation.  If you feel like you shouldn't have done that now, and you're pissed off at yourself, don't take it out on me because I can push back when I want.  Ok?

No, you are being silly. Mike demonstrates some clear bugs in Sonar. End of story. It is absolutely legitimate for Mike to get pissed off at people questioning his intentions and, as so often on this forum, completely missing the point! Mike is trying to get the software that we all use improved. He is doing us all a service. You and John T are just sabotaging a perfectly good thread. (For reasons that I, as a sane person, can not comprehend). You are doing us all a disservice.

UnderTow

Now you're pissed off. And noone's right. The clarifications have been ignored as to the new settings in X1 that cause this. The extra steps Mike took have been ignored. John T has inflamed the situation 'cause he don't know either. A lock down is eminnent and we will have to start over to figure out the right way. Meanwhile, lets all blame it on Cakewalk while we figure out if we've misunderstood where we are in the process of editing. 
 

Mike my man you are truly gifted at finding bugs.
Forget those who mention "work arounds". First time I heard that phrase was when I bought my first Porsche 911 and it vibrated at 85 mph. The dealer told me not to drive over the speed limit.
My response was, in a car that can do 140 mph?

My only question is what theme are you using and can you post it somewhere?
Looks great!

I'm irritated. Do some people think Mike should have made a video of himself happily workaround those bugs (or implementation flaws, I will not involve in that discussion) instead of showing what triggered them and how they manifest?

Seems to me that would have defeated the purpose.

frankandfree


I'm irritated. Do some people think Mike should have made a video of himself happily workaround those bugs (or implementation flaws, I will not involve in that discussion) instead of showing what triggered them and how they manifest?

Seems to me that would have defeated the purpose.

no. it should work the way mike wants it to work. but it don't, now right now, maybe never. what are gonna do? keep scratching and itch that already irritated. sometimes in life your path is blocked for whatever reason. getting around the problem or through in some fashion it is the way.

guitarmikeh


http://forum.cakewalk.com/fb.ashx?m=2191697

http://forum.cakewalk.com/fb.ashx?m=2191728

please try these

Hey GuitarMikeh....thanks!
How is the weather today in someplace else?

haha!

I think were in agreement then sir.
did you try what mike did?
do you have another way of doing this?
how do you accomplish this task?
thanks
these things I would like to know.

in reply to guitarmikeh:

Sorry, no X1 here. But from seeing the video I assume most of the problems are with Set Measure/Beat at now. I guess I'd calculate the tempo myself and avoid that command, or if possible, use it, note the tempo it calculates, undo and set the tempo manually. Maybe it's all easily solved by first trimming/bouncing the clip and then use SM/BaN (as Brundlefly named it in his relentless efforts to point at issues with it in 8.5)? I don't know.

Thing is, it's ok to present workarounds in a thread that has the purpose to point at issues, but it can easily blur the actual message if stressed too much. People start to think "Ah, it's quite easy to get along, so there is no problem". Makes it hard to stay focused on the issue.
The better strategy with regards to a fix by Cakewalk would be to get in and try to shed light on the issues by using the problem commands in different contexts.
Eg, are the problems with SM/BaN Undertow found in 8.5 still existing in X1? Is there a possible connection between the issues? Is that miracle note a result of note length not being handled nicely when trimming as Mike assumes in one of his posts? Of course drum notes do have a length, even if it's not shown in the Piano Roll, so here could be a possible clue to that part. Why does nobody try to do the same procedure once with an overlapping note and another time after trimming the note to the desired item boundary first?

In other words, people should rather help Mike documenting the problem in all thinkable facets instead of discussing whether his video is optimal or concentrating on ways around. That would be the constructive way to help Cakewalk sort it out. IMO.


(edited... had a misnomer there)

right. the problem and "hoops" method both should be addressed. any alternative is a good alternative.

sandman5000


I agree.   What if they just published the workaround as the actual steps and process to accomplish a  task?  then its not a workaround but the way it works.  So same difference to me.  I dont get lost in unproductive nonsense.  HOWEVER,  if there is no workaround and its a genuine bug, then by all means cakewalk should be called on it and the should address it it ASAP.

I agree that genuine bugs need to be reported, and I also agree with the bolded statement above, or what I would call "Getting wrapped around the axle" as in "No use getting wrapped around the axle about it" as one of the best managers I've ever had used to say to me when I would get lost in the minutia and lose focus of the larger picture. 

Some bugs are show stoppers, others are annoyances, some have smaller or larger impacts on different users - they are still bugs if "as designed" or "as implemented" they do not function, but as long as they are reported and I have a workaround I can keep working and in the end - that's the larger picture for me and I'd rather not get "wrapped around the axle" about it to the point that I'm not productive because of my emotions on the subject.

As always individual mileage may vary.

Yes UnderTow - but for the time being it is nice to know that there is a work around. Nobody will disagree bugs must be solved, but in my opinion this forum is also useful for helping other people to get work done...

There is something wrong - agreed, but I do think that point is made by now - won't you agree?

JClosed


Yes UnderTow - but for the time being it is nice to know that there is a work around. Nobody will disagree bugs must be solved, but in my opinion this forum is also useful for helping other people to get work done...

There is something wrong - agreed, but I do think that point is made by now - won't you agree?

Evidently the time being has been approximately 5 years. :-(

best regards,
mike