Jump to content

Melodyne Update?


Johnbee58

Recommended Posts

Sorry if I'm late on this.  I have my Melodyne Essentials configured to not alert me of new updates and I checked it manually this morning and found that there was an update back in June.  Has anybody experienced any issues with it?  I'm wondering if it's safe to go ahead and run the update or wait for some bug fixes.

Thanks

🙂John B

Link to comment
Share on other sites

55 minutes ago, noynekker said:

The update notes also reference a few specific Cakewalk fixes . . . which is great to see that Melodyne is paying serious attention to Cakewalk by Bandlab.

Hey @noynekker. Where did you read those release notes? The changelog on Celemony's website is actually for version 4.2, which did include fixes for both Cakewalk and Studio one. I just want to check it is worthwhile before messing with Melodyne:)

Link to comment
Share on other sites

here's the notes from the email:

Improvements in the current Version 4.2.4

Melodyne 4.2.4 brings the following improvements and numerous minor optimizations all of which make your use of Melodyne more enjoyable, reliable and swift. (Starting from Version 4.1, which according to our database is the latest version you have.)

New functions and improvements

Compatibility: From Version 4.2.4 on, Melodyne is compatible with Apple’s macOS 10.15 Catalina.

Better window management in Studio One 4: Melodyne’s zoom and other window settings now remain constant when you select a new audio region, instead of being displayed with individual settings as previously.

Faster loading with ARA: In DAWs with ARA support, extensive projects now load considerably faster.

ARA in Logic: Melodyne 4.2 supports ARA integration into Apple’s new Logic Pro X 10.4.3. With ARA, transfers are no longer necessary in Logic, and Melodyne follows all changes made to the audio track.

The transfer path in Cakewalk/Sonar: When using the Melodyne VST3 plug-in in Cakewalk/Sonar, the transfer path is now created automatically within the current project (Cakewalk Projects / / Melodyne / Transfers).

Improved interaction: Melodyne 4.2 interacts even better with Studio One and now requires Studio One Version 3.5.6 or later.

Additional keyboard shortcut: You can now assign a keyboard shortcut from the Preferences dialog for the command “Reseparate Notes at Starting-Point Lines” that appears in the context menu in Note Assignment Mode; the shortcut is then also available in edit mode.

Bug fixes

Fixed: In Version 4.2.2, Melodyne in certain configurations displayed the message “expired” at start-up and refused to launch.

Fixed: In Cakewalk, under certain circumstances, instead of new files being analysed automatically, you had to select an algorithm manually in order to trigger the detection process.

Fixed: In the stand-alone implementation of Melodyne, closing a project without saving sometimes led to a crash if other projects were open at the time.

Fixed: In Logic, validating the Melodyne plug-in sometimes slowed down the launch of the DAW.

Fixed: In the stand-alone implementation of Melodyne, opening or importing projects under certain circumstances led to a crash.

Fixed: In ARA mode, it could happen under certain circumstances that the monitoring during blob editing no longer functioned after starting and stopping playback.

Fixed: In Cakewalk, selecting a new clip sometimes led to a misalignment of the Melodyne position display.

Fixed: During ARA operation with Mixcraft and Cakewalk, blob monitoring and scrubbing were no longer available in Melodyne if you started playback in the DAW.

Fixed: With Melodyne in Player Mode (i.e. without activating the program on the computer being used), the ARA plug-in sometimes crashed when you switched from Track Edit Mode to Clip Edit Mode.

Fixed: If the detection was aborted after a transfer with the Melodyne plug-in and you subsequently tried to move audio material whilst holding down the ALT key, a crash was sometimes the result.

Fixed: If an audio file was selected in the track pane of the stand-alone implementation of Melodyne studio, adjusting the fine tuning in the inspector sometimes led to a crash.

Fixed: In Studio One, in projects with many Melodyne clips, the generation of additional Melodyne instances (using the command “Open in Melodyne”) sometimes slowed down the program.

Fixed: In Studio One under Windows, the color of the note background used to change when you altered the zoom level.

Fixed: In Studio One, the function “Unison Spread” sometimes shifted the notes in Melodyne several octaves.

Fixed: In Studio One, use of the Note Separation Tool under certain circumstances led to a crash.

Fixed: In Studio One, the note display (the lines superimposed on the waveform) was previously not updated when notes were deleted in Melodyne.

Fixed: In Studio One, in the case of copied events, “Follow Clip Selection in the DAW” resulted in the wrong bars being shown.

Fixed: In Cakewalk/Sonar, the export of a 16-bit audio file edited with Melodyne sometimes led to a crash.

Fixed: In Cakewalk/Sonar, use of the Freeze function sometimes led to a crash.

Fixed: In all DAWs with ARA, changes to the key or scale were previously not saved.

Fixed: In all DAWs with ARA, use of the Compare switch stopped local playback in Melodyne.

Fixed: In Logic 10.3, the opening of some projects with Melodyne could lead to a crash.

Fixed: In Digital Performer, the opening of projects previously edited with Melodyne sometimes led to a crash.

Fixed: In the plug-in, the command “Restore File to Original State” could under certain circumstances result in the wrong notes being deleted.

Fixed: Canceling a transfer could lead to a display error or even (if you proceeded with editing ) to the DAW crashing.

Fixed: In the plug-in, the assignable keyboard shortcut “Repeat Last Menu Action” did not work.

Fixed: If the Scale Window was open when you switched from edit mode to Note Assignment Mode, the wrong area of the timeline used to be displayed.

Fixed: In the Sound Editor, no peak values were displayed for the spectrum when Note Assignment Mode was active.

Fixed: In Melodyne studio’s track list, the “Edit” and “Reference” buttons could both be activated by Alt-clicking.

Fixed: In Melodyne studio, when multiple tracks were copied simultaneously, their contents were sometimes swapped.

Fixed: In Melodyne essential, the assignable keyboard shortcut for “Separate Notes as Trills” was missing.

Fixed: In Melodyne essential, opening a document saved by Melodyne studio sometimes resulted in the wrong track being displayed.

Fixed: In the stand-alone application, it was impossible to copy and paste notes in Tempo Assignment Mode.

Fixed: In the stand-alone application, a new detection sometimes led to the audio being offset in the timeline.

Fixed: In the stand-alone application under macOS Version 10.12, crashes sometimes occurred when the import audio function was used.

Link to comment
Share on other sites

6 hours ago, pwalpwal said:

 

The transfer path in Cakewalk/Sonar: When using the Melodyne VST3 plug-in in Cakewalk/Sonar, the transfer path is now created automatically within the current project (Cakewalk Projects / / Melodyne / Transfers).

 

6 hours ago, pwalpwal said:

 

Fixed: In Cakewalk, under certain circumstances, instead of new files being analysed automatically, you had to select an algorithm manually in order to trigger the detection process.

 

6 hours ago, pwalpwal said:

 

Fixed: In Cakewalk, selecting a new clip sometimes led to a misalignment of the Melodyne position display.

Fixed: During ARA operation with Mixcraft and Cakewalk, blob monitoring and scrubbing were no longer available in Melodyne if you started playback in the DAW.

 

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...