Anderton

ramscapri
 
Why is the "How to Download the ………. Update" section not included anymore in the ezine which used to follow the update features summary page ?

The embarrassing reason is...I forgot in one issue, and that got carried over to subsequent ones. Great point...thanks for the reminder!

Thanks for noting that Craig. The ezine is such an important and very much indispensable part of every update that almost anything missing in there will be noticed by someone or the other   great work by you and the team putting that together.
 
I think that this probably did come up in some post but just to reconfirm, downloading the core installer and Platinum Instrument Collection setups should cover everything for this update including the Melodyne tempo detection feature (that is, presuming one will not need to go to Celemony account to get something downloaded from there) ?
 
 

ramscapri
I think that this probably did come up in some post but just to reconfirm, downloading the core installer and Platinum Instrument Collection setups should cover everything for this update including the Melodyne tempo detection feature (that is, presuming one will not need to go to Celemony account to get something downloaded from there) ?

As with every release, there is an update to the local help file. The new tempo detection feature is all SONAR, nothing new from Celemony required.

WOW! The Melodyne tempo map feature is awesome BUT .. it's a real resource hog as well. In fact, I didn't realize it'd hoard so much RAM. I'm using an i7 core desktop with 16GB of RAM and Win7 Ultimate 64bit + SSD drives and so forth.

I opened up a studio recording with 22 mono tracks in it, only copied the tracks as they were (no plug-ins) and pasted them into a completely new project. I then ran Melodyne through the 22 tracks @ 48KHz/24-bit, the song altogether was a bit over 6 mins long and so were the tracks. It sure did clog up SONAR to a point where I was nearly convinced that there has been a memory leak or a similar bug somewhere and that I'd have to close down SONAR forcibly via the Task Manager.

Luckily, SONAR didn't freeze. The tempo calculation is excellent, in fact, it now does a much better job at times when compared to the old AudioSnap function, which has its good sides of course, but still. My problem is that even with just the 22 "raw" mono tracks, a 6-minute take and _nothing_ else running on the software or otherwise, it's really resource-intensive to operate. I noticed that upon activating Melodyne as clip FX for each of the tracks, SONAR now fills up around 10GB of RAM! That's just way too much for my setup. Either my workflow isn't correct or the Melodyne implementation just blows up the RAM memory usage.

The tempo insertion from a Melodyne-processed track worked just fine, but now I'm stuck with SONAR clogging up my RAM big time. if you have any ideas how I could easily adjust just a few parts of the song I'm working on tempo-wise, i.e. to first set the project tempo from a single Melodyne track, and then make other clips follow it, and not having to wait hours for the adjustment? All tips would be appreciated. I do have the latest Melodyne standalone purchased as well, so I could probably try doing the same task within the Melodyne 4 software. I also noticed that while the tempo mapping works just fine, it's yet another dead-end to select "follow project tempo" from the Melodyne Region FX menu.

As soon as the number of Melodyne-activated tracks/clips increase, the resource-grabbing gets real intense, up to the point that you can only try to wait it out. Saving the project as a plain .CWP file also becomes increasingly difficult as what was previously 1-2 megs has suddenly bloated into around 100 megs. And that's just the CWP project file. Also, when I got the project tempo from one of the Melodyned tracks, then selected all the tracks and from the to follow the project tempo (although it'd been already calculated and inserted from one of the Melodyned tracks), it'd completely throw the tracks in a nonsensical mess, so ... either I'm doing something wrong or all of the new Melodyne tempo map features don't yet work as they should.

In any case, the new Melodyne implementation is very promising, and if you only need to find the tempo from one track, it's an excellent tool for tempo mapping that way. Just beware if you have a multitrack project that needs tempo adjustment with individual tracks altogether, you'll clog up your system pretty quickly. :P


 
 

Choose one track to derive the tempo. Then use other Melodyne functions to conform the other tracks to that tempo.

Just updated to the .03 update.  
LOVE the help section!!!  Learned a few "quick" buttons (and I thought I had a pretty decent workflow).
 
Gonna spend some time with that one. 
 
Also, new synths are really good too!  Love them both!
 

AudioAnnihilator
WOW! The Melodyne tempo map feature is awesome BUT .. it's a real resource hog as well. In fact, I didn't realize it'd hoard so much RAM. I'm using an i7 core desktop with 16GB of RAM and Win7 Ultimate 64bit + SSD drives and so forth.

I opened up a studio recording with 22 mono tracks in it, only copied the tracks as they were (no plug-ins) and pasted them into a completely new project. I then ran Melodyne through the 22 tracks @ 48KHz/24-bit, the song altogether was a bit over 6 mins long and so were the tracks. It sure did clog up SONAR to a point where I was nearly convinced that there has been a memory leak or a similar bug somewhere and that I'd have to close down SONAR forcibly via the Task Manager.

 
If you are creating 22, 6 minute tracks its a lot of audio for melodyne to analyze and store so I'd expect it to consume a lot of memory. If all you want is the tempo map, you can get rid of the melodyne region once you have extracted the tempo map. That will release the memory use. Additionally once you have got the other tracks to follow the tempo map you can render the region fx to "print" it and release RAM again. 
Alternatively you can use audio snap to follow the tempo rather than Melodyne.
 

Anderton
Choose one track to derive the tempo. Then use other Melodyne functions to conform the other tracks to that tempo.

Thanks a lot for the tip, will try to find a workaround and that just might be one.
 
However, between my last post and this I found out a few things. First of all, it somehow helped out a bit to make a "Bounce to clip(s)"-round before activating the Melodyne. Still it was sluggish, but not as much, can't figure out what might be the reason.

I tried one more thing: since I have the Melodyne 4 complete version as a standalone license as well, I tried dumping the audio tracks into it and noticed that it's waaaaaaaaaay faster to process the very same 22 tracks of audio inside the standalone version. On top of that, the standalone Melodyne 4 even tries to learn something from its "neighbor" tracks (which is not the case in when running these same Melodyne functions within SONAR) - the track alignment seems to get a lot better, it's much faster to use etc., so, I guess it's once again a matter of having the right tool for the right job and not trying to do everything "under the same roof" (or DAW in this case).

Noel Borthwick [Cakewalk]
If you are creating 22, 6 minute tracks its a lot of audio for melodyne to analyze and store so I'd expect it to consume a lot of memory. If all you want is the tempo map, you can get rid of the melodyne region once you have extracted the tempo map. That will release the memory use. Additionally once you have got the other tracks to follow the tempo map you can render the region fx to "print" it and release RAM again. 
Alternatively you can use audio snap to follow the tempo rather than Melodyne.

Yep, was thinking something similar, thanks! Still, the Melodyne 4 standalone version is way faster, smarter in algorithmic sense and less memory-consuming than using Melodyne as a Region FX with the current version of SONAR. :P

AudioAnnihilator

Noel Borthwick [Cakewalk]
If you are creating 22, 6 minute tracks its a lot of audio for melodyne to analyze and store so I'd expect it to consume a lot of memory. If all you want is the tempo map, you can get rid of the melodyne region once you have extracted the tempo map. That will release the memory use. Additionally once you have got the other tracks to follow the tempo map you can render the region fx to "print" it and release RAM again. 
Alternatively you can use audio snap to follow the tempo rather than Melodyne.

Yep, was thinking something similar, thanks! Still, the Melodyne 4 standalone version is way faster, smarter in algorithmic sense and less memory-consuming than using Melodyne as a Region FX with the current version of SONAR. :P

but simple drag and drop to the timeline is brilliant. I don't want to go outside Sonar to get the tempo if I can get it as easily as I can get it now

AudioAnnihilator
I tried one more thing: since I have the Melodyne 4 complete version as a standalone license as well, I tried dumping the audio tracks into it and noticed that it's waaaaaaaaaay faster to process the very same 22 tracks of audio inside the standalone version. On top of that, the standalone Melodyne 4 even tries to learn something from its "neighbor" tracks (which is not the case in when running these same Melodyne functions within SONAR) - the track alignment seems to get a lot better, it's much faster to use etc., so, I guess it's once again a matter of having the right tool for the right job and not trying to do everything "under the same roof" (or DAW in this case).

From what I heard Celemony is considering an update to bring ARA access up to parity with the standalone version. When that happens you should have more multitrack editing functionality rolled in to the VST3 version.