Celemony Melodyne: всё о ней. Вопросы, решения и тонкости работы. (1 онлайн
- Автор темы vax
- Дата начала
Для того что-бы подогнать два трека по темпу спетых в унисон я один трек поднимаю или опускаю на пол тона (для того чтобы они в редакторе не перекрывали визуально один другого), выключаю снэп квантайз и двигаю вручную. После выравнивания ставлю измененный вначале трек на место.
Vladimir_vc,
Не понял, вы имеете ввиду Celemony Melodyne Studio Edition ?
Там все нормально, слышно что двигаешь.
А в плагине методом научного тыка не смог активировать эту функцию. Ведь логически она должна быть там, Plugin ведь кэширует редактируемый файл в отдельную папку.
Не понял, вы имеете ввиду Celemony Melodyne Studio Edition ?
Там все нормально, слышно что двигаешь.
А в плагине методом научного тыка не смог активировать эту функцию. Ведь логически она должна быть там, Plugin ведь кэширует редактируемый файл в отдельную папку.
Нет я имею ввиду редактор в котором Вы открываете Melodyne Plugin (кубейс и др.). Вы же спрашивали о плагине а не о Melodyne Studio Edition.
Мне нужно ухватиться за сегмент мышкой и чтобы этот сегмент звучал, чо то не получается. Как "проиграть" в редакторе ? НЕ догоню никак:dash3:
В плагине такого нет. Проиграть в редакторе - нажать на play и слушать.
Это я фкурил в первую же минуту :russian_ru:
Вот обидно, иногда важно слышать границу при случае разделения ноты. А то делишь иногда :girl_prepare_fish:
Не в курсе случайно, в более поздних версиях плагина есть такая возможность ?
Попробовал сегодня ревайр мелодин студио с 5 кубом. Вывод- бридж и плагин не нужны. Полная синхронизация с темпом хоста. Транспорт работает в обе стороны-работаем в мелодине, а слышим все, что в хосте. Преключение между окнами удобнее при "отображать панель задач поверх остальных окон". Сказка!!!
chapson.st, пользуюсь только бриждем!!!)))Полная синхронизация с темпом хоста. Транспорт работает в обе стороны-работаем в мелодине, а слышим все, что в хосте. Преключение между окнами удобнее при "отображать панель задач поверх остальных окон". Сказка!!!Вывод-ревайр не нужен!!!)))))):sarcastic_blum:
Может оно и так, да только у меня чего-то в бридже транспорт из мелодина в куб не фурычит. Может глюк?
chapson.st, ну хз,вроде всё фурычит,почитай здесь,может разберёшся что к чему)))
aint2:
aint2:
апдэйт 1.1
Release Notes
Melodyne editor 1.1
Here is an overview of the bug fixes done since the last version 1.0 as well as a list of known issues and their solutions.
Improvements and Bug Fixes
Sound quality: improvements on monophonic files, such as vocals
Edited monophonic files now have the same sound quality as the original, unedited file.
Sound quality: artifacts when modifying note transitions
Now the sound stays natural when creating larger pitch jumps from one note to the other while having fast note transitions.
Sound quality: clicks shortly after playback start
Clicks in the audio signal are now avoided when starting the playback at spots close to note transitions.
Loading old sessions I
When opening a session or song, that was done with the old Melodyne plugin, the sound quality is now the same in Melodyne editor as it was with the old plug-in.
Loading old sessions II
A bug was fixed that could lead to a crash when working with certain sessions, that were done with Melodyne plugin 1.0.4.2 and that contained tempo changes.
Auto Save in Pro Tools
Using the Auto Save function in Pro Tools no longer locks the User Interface. In version 1.0 this used to make the whole program feel sluggish while Auto Save operation was taking place.
Wrong playback of the original track instead of the Melodyned version
A bug was fixed that – after certain editing actions – caused Melodyne to play back the original version of your track instead of the edited version.
Resolution of Note Separations
The resolution for separating notes in monophonic files has been increased. This affects both creating new separations and moving existing separations.
Autoscroll in Note Assignment mode
Automatic scrolling now works in Note Assignment mode, too.
Scrolling during transfer
Scrolling now works properly while a transfer is running.
Displayed notes in vertical Zoom Slider
The display of notes in the vertical Zoom Slider now works properly. Therefore double-clicking on this slider gives you the desired result now.
Saving to a wrong location
In certain situations transferred files got written in the private/tmp directory under Mac OS X.
Select Scale
The scale menu is now shown properly after having done a new transfer.
Replace Ranges
Replace Ranges now get updated properly after having learned a new tempo variation.
Inspector fields
Typing in certain values now leads to the expected result (e. g. +129 cents results in 1 semitone plus 29 cents)
Undo after having changed the algorithm
Changes done in the Algorithm menu can now be undone properly.
Logic 9.1.1: space bar
A bug was fixed that could cause a faulty behavior of the space bar in Logic
9.1.1: When you hit the space bar in order to stop the local playback of
Melodyne (which you started before by double-clicking in the Melodyne time
line), Melodyne in some situations didn't stop. Instead this action started the playback of the whole song. (This problem didn‘t exist in Logic 9.0.2. and was introduced with Logic 9.1.)
Cubase: jumping in the timeline
Jumping in the Cubase timeline by clicking on it while playback is running now makes Melodyne editor jump to the desired position as well.
Bypass in Cubase
A bug was fixed that could make Cubase crash when trying to control the transport from within the Melodyne window while the plug-in was bypassed.
Saving a Cubase/Nuendo project (Mac G5 only)
A bug was fixed that would prevent a project from being saved properly on a PPC Mac (G5). Also, undoing after removing Melodyne from the insert now works properly on a G5.
Stand-alone version: Save MIDI
A bug was fixed that could lead to a crash when exporting a MIDI file.
Stand-alone version: resetting the volume to ±0 db
Like in the plug-in version the volume can now be reset in the stand-alone version as well by command-clicking (or control-clicking on PC, respectively) on the volume control.
Stand-alone version: double-click to open a MPD file
Double-clicking on an MPD no longer opens a second, empty window.
Known issues and solutions
Buffer size
This isn't a bug, but it probably still needs some explanation: Melodyne editor prefers to have a large buffer setting. We recommend to set the I/O buffer size to 1,024 samples. Smaller values lead to a significantly higher CPU load.
Should you need to set smaller values, e.g. when doing the headphone mix directly in you computer and not via an external channel strip or mixer, deactivate (bypass) all Melodyne instances while tracking. Switch Melodyne back on when starting to edit your new tracks.
Strategies for effective usage of RAM
The RAM consumption of Melodyne editor strongly depends on the files you are using. With melodic or percussive files you will notice that Melodyne editor needs even less RAM than Melodyne plugin. But with polyphonic files the RAM usage can be higher. We can‘t, however, give you any absolute numbers in terms of megabytes per minute, since this strongly depends on the musical content of the files. Here are a few strategies you can use to minimize the RAM consumption:
First off you need to know that during and shortly after every transfer the RAM consumption is higher than a while after the process. Therefore doing multiple transfers at the same time temporarily increases the RAM usage a lot. A workaround for this would be to transfer tracks one after the other.
Often there is no need to transfer every track from the very beginning to its very end. Instead it is much more efficient to transfer only the part you currently want to edit. Even when you end up with having transferred the whole track in the end, you will have lower peak values of RAM consumption when you do it part by part and track by track.
And one last tip on saving RAM: certain DAWs will have a growing RAM usage simply because you are using them over hours. Therefore it's a good idea to save, quit, and restart your DAW from time to time.
Cubase: sync offset by cycle length
Activating the cycle in Cubase, but starting the playback at any position behind the cycle will offset Melodyne editor by the amount of the cycle length.
Example: you set a cycle around bar 3 and 4 (the length being two bars), but started playback in bar 7. Melodyne will play from bar 5 (i.e. Cubase position minus cycle length).
Workaround: when you want to play back at some later point in the song, turn cycle off in Cubase.
For other issues related to specific DAWs and their individual settings, please see here.
Release Notes
Melodyne editor 1.1
Here is an overview of the bug fixes done since the last version 1.0 as well as a list of known issues and their solutions.
Improvements and Bug Fixes
Sound quality: improvements on monophonic files, such as vocals
Edited monophonic files now have the same sound quality as the original, unedited file.
Sound quality: artifacts when modifying note transitions
Now the sound stays natural when creating larger pitch jumps from one note to the other while having fast note transitions.
Sound quality: clicks shortly after playback start
Clicks in the audio signal are now avoided when starting the playback at spots close to note transitions.
Loading old sessions I
When opening a session or song, that was done with the old Melodyne plugin, the sound quality is now the same in Melodyne editor as it was with the old plug-in.
Loading old sessions II
A bug was fixed that could lead to a crash when working with certain sessions, that were done with Melodyne plugin 1.0.4.2 and that contained tempo changes.
Auto Save in Pro Tools
Using the Auto Save function in Pro Tools no longer locks the User Interface. In version 1.0 this used to make the whole program feel sluggish while Auto Save operation was taking place.
Wrong playback of the original track instead of the Melodyned version
A bug was fixed that – after certain editing actions – caused Melodyne to play back the original version of your track instead of the edited version.
Resolution of Note Separations
The resolution for separating notes in monophonic files has been increased. This affects both creating new separations and moving existing separations.
Autoscroll in Note Assignment mode
Automatic scrolling now works in Note Assignment mode, too.
Scrolling during transfer
Scrolling now works properly while a transfer is running.
Displayed notes in vertical Zoom Slider
The display of notes in the vertical Zoom Slider now works properly. Therefore double-clicking on this slider gives you the desired result now.
Saving to a wrong location
In certain situations transferred files got written in the private/tmp directory under Mac OS X.
Select Scale
The scale menu is now shown properly after having done a new transfer.
Replace Ranges
Replace Ranges now get updated properly after having learned a new tempo variation.
Inspector fields
Typing in certain values now leads to the expected result (e. g. +129 cents results in 1 semitone plus 29 cents)
Undo after having changed the algorithm
Changes done in the Algorithm menu can now be undone properly.
Logic 9.1.1: space bar
A bug was fixed that could cause a faulty behavior of the space bar in Logic
9.1.1: When you hit the space bar in order to stop the local playback of
Melodyne (which you started before by double-clicking in the Melodyne time
line), Melodyne in some situations didn't stop. Instead this action started the playback of the whole song. (This problem didn‘t exist in Logic 9.0.2. and was introduced with Logic 9.1.)
Cubase: jumping in the timeline
Jumping in the Cubase timeline by clicking on it while playback is running now makes Melodyne editor jump to the desired position as well.
Bypass in Cubase
A bug was fixed that could make Cubase crash when trying to control the transport from within the Melodyne window while the plug-in was bypassed.
Saving a Cubase/Nuendo project (Mac G5 only)
A bug was fixed that would prevent a project from being saved properly on a PPC Mac (G5). Also, undoing after removing Melodyne from the insert now works properly on a G5.
Stand-alone version: Save MIDI
A bug was fixed that could lead to a crash when exporting a MIDI file.
Stand-alone version: resetting the volume to ±0 db
Like in the plug-in version the volume can now be reset in the stand-alone version as well by command-clicking (or control-clicking on PC, respectively) on the volume control.
Stand-alone version: double-click to open a MPD file
Double-clicking on an MPD no longer opens a second, empty window.
Known issues and solutions
Buffer size
This isn't a bug, but it probably still needs some explanation: Melodyne editor prefers to have a large buffer setting. We recommend to set the I/O buffer size to 1,024 samples. Smaller values lead to a significantly higher CPU load.
Should you need to set smaller values, e.g. when doing the headphone mix directly in you computer and not via an external channel strip or mixer, deactivate (bypass) all Melodyne instances while tracking. Switch Melodyne back on when starting to edit your new tracks.
Strategies for effective usage of RAM
The RAM consumption of Melodyne editor strongly depends on the files you are using. With melodic or percussive files you will notice that Melodyne editor needs even less RAM than Melodyne plugin. But with polyphonic files the RAM usage can be higher. We can‘t, however, give you any absolute numbers in terms of megabytes per minute, since this strongly depends on the musical content of the files. Here are a few strategies you can use to minimize the RAM consumption:
First off you need to know that during and shortly after every transfer the RAM consumption is higher than a while after the process. Therefore doing multiple transfers at the same time temporarily increases the RAM usage a lot. A workaround for this would be to transfer tracks one after the other.
Often there is no need to transfer every track from the very beginning to its very end. Instead it is much more efficient to transfer only the part you currently want to edit. Even when you end up with having transferred the whole track in the end, you will have lower peak values of RAM consumption when you do it part by part and track by track.
And one last tip on saving RAM: certain DAWs will have a growing RAM usage simply because you are using them over hours. Therefore it's a good idea to save, quit, and restart your DAW from time to time.
Cubase: sync offset by cycle length
Activating the cycle in Cubase, but starting the playback at any position behind the cycle will offset Melodyne editor by the amount of the cycle length.
Example: you set a cycle around bar 3 and 4 (the length being two bars), but started playback in bar 7. Melodyne will play from bar 5 (i.e. Cubase position minus cycle length).
Workaround: when you want to play back at some later point in the song, turn cycle off in Cubase.
For other issues related to specific DAWs and their individual settings, please see here.
Друзья, у меня непонятная проблема с мелодином-плагином... Вот трансферю в него вавки, правлю, все вроде нормально по началу, а потом в определенный момент какие-то из вавок просто берут и съезжают на другой участок трека. Чо это за хрень ваще? Я уже боюсь что-то в нем делать, ибо все манипуляции могут оказаться коту под хвост. Уже несколько раз так так было... Хост - куб 5 народный, версия плага 1.0.2.0.
Степашка, если ты в Кубе сдвигаешь отредактированные в Мелодине аудиоклипы, то они не сдвинутся и будут звучать на старых местах. Надо рендерить.
Да нету никаких смен :unknw:
Это я уже понял, но я вообще ничего не двигаю, а у меня вдруг куплет оказывается на припеве ни с того, ни с сего... Еще одну фишку заметил - если, допустим, припев размножить, даже еще до того как на него мелодин повесить, то потом достаточно только один припев затрансферить, а остальные он автоматически заменит. Не знаю, должно так быть или нет, но у меня то заменяет, то нифига...
Ребят , а видео обучалки для него нет? желательно на русском. и то все не вкурю его никак, правлю ноты, выравниваю все идеально например, а он лажает оч сильно и высит адски
Вроде, есть, кажется видел в... эээ... местах не столь отдаленных... Но не на русском...
