kevinwal

outland144k
Hi Guys:
 
The March update is not showing up in Command Center (I'm guessing that it's out from the positive comments here). Ideas?
 
Thanks for all your work!
 
Dan
 
BTW- What's it called?

In CCC, right click on Sonar, select "Rollback" and you'll see the early release entry in there. Intuitive, huh? :)

 
Really. I'm not sure why I didn't think of it. 
 
Thanks to all who answered. Right now, the only thing that shows up is "Early Access". I'll be doing that (I figure "anything I can do to help", you know?). 
 
Can I make a suggestion to the bakers? If you're going to implement "Early Access", it might help to get a relatively detailed profile of the musicians opting to help you piece together the data. It may help to evaluate if the way an individual uses Sonar and the way they perceive and/or ideally desire to use Sonar match up. Maybe you've done this already (I haven't had a chance to check as EA is still DLing) or maybe this is just beyond you concerns. This is offered in the spirit of FWIW.
 
Anyhow, thanks again.
 
BTW- assuming that the Early Access DL is not the new update, is there a name for the update available? It does help to identify the updates beyond all the numbers (yes, I do agree, however, that 2016.03 is pretty straight-forward if we're going over to that).
 
Dan

This is indeed a solid release!

So, early release works with ARA tempo extraction (best news and tool I have seen in a decade). I read the release notes and it appears that the bakes also implemented it quite cleverly with a ton of useable options.
 
Now, can't wait for the official release.
 
Thanks guys for keeping us all posted on the progress.
 
Jim

outland144k

kevinwal

outland144k
Hi Guys:
 
The March update is not showing up in Command Center (I'm guessing that it's out from the positive comments here). Ideas?
 
Thanks for all your work!
 
Dan
 
BTW- What's it called?

In CCC, right click on Sonar, select "Rollback" and you'll see the early release entry in there. Intuitive, huh? :)

 
Really. I'm not sure why I didn't think of it. 
 
Thanks to all who answered. Right now, the only thing that shows up is "Early Access". I'll be doing that (I figure "anything I can do to help", you know?). 
 
Can I make a suggestion to the bakers? If you're going to implement "Early Access", it might help to get a relatively detailed profile of the musicians opting to help you piece together the data. It may help to evaluate if the way an individual uses Sonar and the way they perceive and/or ideally desire to use Sonar match up. Maybe you've done this already (I haven't had a chance to check as EA is still DLing) or maybe this is just beyond you concerns. This is offered in the spirit of FWIW.
 
Anyhow, thanks again.
 
BTW- assuming that the Early Access DL is not the new update, is there a name for the update available? It does help to identify the updates beyond all the numbers (yes, I do agree, however, that 2016.03 is pretty straight-forward if we're going over to that).
 
Dan

Yep, they're going forward with the year and month release number scheme now. 

tenfoot

Jim Kalinowski

tenfoot
 
Found 2 bug fixes so far - render bit rate change now works as advertised, and a docked piano roll note/controller alignment bug gone as well.

One bug that is not yet fixed (or at least I saw it happen again last night) is the timeline in docked PRV does not always line up with the events in the PRV until you scroll the PRV.  I was hoping that would get fixed as part of the controller/note alignment problem.

I haven't seen that problem in the new version yet Jim. Have you found a consistent way to reproduce it?

This works every time:
 
1. Create a MIDI track and on a measure other than the first (let's use the 2nd measure) add some MIDI notes.
2. In one screenset, dock the PRV and have the PRV display the MIDI track from step 1.
3. Go to another screenset that has the track view in it and set the now time in the time ruler to be the measure where you added the MIDI notes in step 1.
4. Go back to the screenset you used in step 2.
 
What I see every time is the vertical line for the start/now/current time in the PRV is all the way to the left.  The ruler at the top of the PRV shows that measure 2 is the measure all the way to the left.  That part is fine.  However, my MIDI notes are on measure 3...they are not lined up with the current time.  Once I start clicking on the right scroll arrow at the bottom of the PRV, the now time and ruler start moving to the right and eventually line up with and stay synched with the MIDI notes.  
 
This bug has been there for a while.  It was talked about once or twice on the forums.  I'll submit a bug report (hey, aren't we supposed to be getting a new feedback portal? :) )

ampfixer
Thanks Craig, it looks like I need to do some homework and explore Melodyne upgrades. 90% of the stuff I record is with people that can't, or won't use a click.

This is *exactly* one of the powerful use cases of tempo extraction. You can record live and then sync other tracks in the project, including loops and virtual instruments to the tempo map of the live recording. It makes it a lot easier when the measures line up with the recording...

bitman
Now if it will just stop crashing creating a Fx Region for melodyne.
I plan to update everything tonight, Sonar, Melodyne essential and see how it goes. :-)

Is this in the early access release or in Newburyport? There are a bunch of ARA fixes in the new build as well.
Let me know ASAP if the crash occurs in the latest update. You can download it via the rollback menu in command center.

ok

kevinwal

outland144k

kevinwal

outland144k
Hi Guys:
 
The March update is not showing up in Command Center (I'm guessing that it's out from the positive comments here). Ideas?
 
Thanks for all your work!
 
Dan
 
BTW- What's it called?

In CCC, right click on Sonar, select "Rollback" and you'll see the early release entry in there. Intuitive, huh? :)

 
Really. I'm not sure why I didn't think of it. 
 
Thanks to all who answered. Right now, the only thing that shows up is "Early Access". I'll be doing that (I figure "anything I can do to help", you know?). 
 
Can I make a suggestion to the bakers? If you're going to implement "Early Access", it might help to get a relatively detailed profile of the musicians opting to help you piece together the data. It may help to evaluate if the way an individual uses Sonar and the way they perceive and/or ideally desire to use Sonar match up. Maybe you've done this already (I haven't had a chance to check as EA is still DLing) or maybe this is just beyond you concerns. This is offered in the spirit of FWIW.
 
Anyhow, thanks again.
 
BTW- assuming that the Early Access DL is not the new update, is there a name for the update available? It does help to identify the updates beyond all the numbers (yes, I do agree, however, that 2016.03 is pretty straight-forward if we're going over to that).
 
Dan

Yep, they're going forward with the year and month release number scheme now. 

 
That's kind of a bummer. I liked the idea of naming them after streets in Boston. Now we'll never know which streets in Boston have names that starts with the letters "Q", "X", or "Z".
 
Maybe the bakers could start naming them after craft beers like "Dirt Wolf", "Limbo", or "Hobgoblin". Heaven knows that there are enough of them nowadays. There are really good ones, too.
 
Dan

bitman
Me too.
 
Can't wait to try this.
I can't AND won't cut to a click.
 
To be able to quantize the midi drums to a free form performance tempo map is what I've needed for as long as I have used a DAW. I could never get my head around Audio Snap. The thought of teaching it the song (transients) just never sat well with me. While I am stuck at work and can't try it yet, leave it to the wizards at Celemony.
 

+1 This is so going to become my number one feature. Can't wait to try. Thanks Bakers. This release alone will be worth my years payment.