It would be really nice to be able to export xml’s (or. It was the first time in several years of using OM that I could finally get the cool things I created in OM out into the real world. om file, and it worked perfectly, everything was where it was supposed to be, the formatting was nice and readable, and the microtones were all there. But, when I reformatted the page, it started to look better, until NAP got confused and started moving things around arbitrarily, and stems started twisting around onto themselves, there was not way to work with it at all.īut, I imported it as an. If I wrote it unmetered, it might not be so complicated, but omquantify made it look pretty intricate (although in that case, it was accurate - the only thing it really seems to have problems with are 8ths and 16ths).Īnyway, when I imported that as an XML to NAP, the page was a huge cluttered mess with a million overlapping noes, a completely unreadable disaster. I suspect it may have something to do with the fact that I’m using a relatively old version of OSX (6.11), and maybe NAP doesn’t like it.Īs for the XML export, I just finished a big symphonic piece with a lot of complicated micropolyphony in 16 voices.
I did check in my documents folder, I made sure to choose “save to desktop” just to be sure. The eighth tones have always been a huge headache, as Sibelius and the other big notation programs don’t see them on xml files exported from OM. I am very much hoping they don’t do away with the OM exchange format, as it’s the only reliable way I’ve found to get things into NAPro (it’s true they discontinued OMNAP as a library, because it wasn’t necessary anymore, “save to NAPro” is a native feature (at least on OM 6.14, which I’m using). So, I’m not sure where you’ve got these facts from, but they directly contradict my empirical experience. This is the only solution I’ve found for exporting 1/8 tones, with the partial exception that you can save them as separate channels and then implode them once in sibelius, but that’s really more trouble than it’s worth. However, the OM exchange format works just fine, you just need to open it up in a text file and copy-paste into NAPro. I’ve tried to export XML about 10 different ways and it didn’t work. There are big problems with importing XML, the accuracy is extremely low, and when I try to export XML, literally nothing happens. I’m running OSX 10.11.06, and NAPro that was downloaded about a month ago, version 2.656. Hi Antonio, I don’t deny the possibility that you live in a different universe, or something, but in my universe:
In any event, I had a lot more trouble with this a few years ago and it seems that the quantization algorithms have been improved upon, but I wonder if anyone else has this problem? There are just some polys that seem to be resistant to being concatted no matter what. I made sure to put fillers at the end of all the polys so they would have an equal number of measures, but that didn’t help. I recently finished a symphonic piece and sometimes I just ended up exporting the fragments with simple rhythms to logic.Īnother issue, which might be a bug (?) is that when I concat polys, occasionally things get moved around, and I haven’t figured out a way to avoid this. Surprisingly, the quantization seems to work better on multiseqs with a lot of complex rhythms, but it often seems to have a problem with straight eights and sixteenths, even if you set the maximum subdivision extremely low. Does anyone have any advice on quantizing and concatting polys? I am frequently running into problems with this, of a few varieties: If I’m trying to quantize a multiseq (I usually put omquantify in a subpatch and run it through mapcar) it’s still extremely unpredictable which ones will go just fine, and which ones will get messed up.
0 kommentar(er)
