One is export to midi, the other is export tempo map. In Melodyne studio (the standalone version) there are 2 different export to midi commands. I can't see what I'm doing wrong, Can anyone advise? I just dusted off my old Sonar and it works fine there, but not in Mixcraft. the midi file, viewed on the timeline, is around twice as long as the underlying audio. Like around half of what it should be, i.e. Lingyai wrote:Unfortunately, when I use Melodyne Studio's Export as Midi command within Mixcraft (saving the midi file to a folder) and then drag that midi file into Mixcraft, the tempo is way, way wrong. My copy of their software is probably 5 years old. Melodyne keep sending me upgrade info and I suppose it's time I upgrade with them. It's been awhile since I have needed or wanted to do that and I admit to not really know what I was doing when I did it It clears up any timing issues if you want some kind of a ghost effect or synth since it's basically a copy of the main track in midi form. Worked really well for that.If the bass is off a few cents in tuning, the software puts it to the closest range.Īlso works well to copy say a vocal track, convert it to midi and use a synth to accentuate the main vocal track. I have used ARA to convert this to midi and replace that bass with a sampled one. My main use for it has been to replace a bad bass track in mono which it seemed to work well for. I confess to not knowing the inner working of this technology called ARA I think? Even though I own an older copy of Melodyne Studio and have done similar in another daw. I think it is early days for this kind of software, in 10 years it should be commonplace and work a lot more completely and cheaply. The full version of Melodyne (which I acquired through through 2 half price upgrades - check places like for cut price deals on software) enables audio to be polyphonically pulled apart and the results can be converted to midi tracks, however those midi tracks work best as a way of analysing included notes that can be then used to understand what note structures are in the tracks before recording (or pencilling-in notes more precisely on the piano roll) into new tracks, as the midi it creates includes interpretations of every piece of hum or background noise as a note, so it gets very complicated (unless you spend years adapting to it's workflow methods) to use it directly for that purpose if deconstructing multi-note layerings (it also takes a long time to process layered material, whereas single note, monophinc material can be analysed quickly). "As Greg suggests the results are variable, but interesting. Can be done but as I say: loads of patience and a LOT of time required. Works alright for drums too but again: simple if it's just an (audio) drum track but not so simple if you're trying to pull apart a mix. But when you start working with audio that has multiple instruments and you have to coax Melodyne into finding the notes well it can become a new career (it's not as automatic as some videos on YouTube would have you believe)!!! LOL!!! If you have a bass (audio) track and that's the only instrument well then no problem. Except there was only ONE single (and simple) instrument (keyboard) in the audio track. There's one in particular where the chap extracts MIDI from an audio jingle. I've seen some of those YouTube videos on this. Greg has summed up the Mixcraft side of things.Īs somebody who has Melodyne Studio (and upgraded to Studio for this very purpose): it's not as easy as simply dragging an audio track onto a MIDI track (wish it were) not by any stretch of the imagination.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |