Hi, > there limitations compared to the main editor, but it works quite > well. (well, will by final v1.0 release, which is happening very soon) There are a few oddities that arise out of its architectural reliance on midiquest. Midiquest is a very complex program and offers numerous ways to achieve the same result. This is undoubtedly a good thing in a program that is a general purpose midi editor/librarian, but where it is used for a specific end (like the evolver vyzor) it can seem a little fustian at times. This is definitely an app where you will have to read the manual to get the most from it. >I'm not looking to shell out for yet another editor, but if vyzor can >deliver total recall within a host Total recall is not quite there yet. You have to save your settings to a file before quitting and then reload that file after you have loaded your project file. Saving in the host does not save the current settings. There is also a relation between the page currently displayed and the underlying automation data - each page has different parameters - and so you need to remember to always have the same page open when you automate via your host. A few small niggles aside, I like the vyzor. With a bit of planning and understanding of how the program works, it basically replicates the functionality of the virus ti's total control for the evolver. Without the crashing and satan's saw <wink/> And the dynamic sequencer display is very, very cool.
Message
Re: Vyzor Editor Question
2006-07-03 by Pierre Zeeman
Attachments
- No local attachments were found for this message.