![]() ![]() I haven't done extensive testing, but it looks like you can delete the track contents while retaining the track envelopes. This works fine for checking things out early on. Then delete the current track contents (not the tracks!) and cut/paste the newly imported track contents into their correct position. When the MuseScore composition changes, save it as a MIDI file and re-import into the project using Insert / Media file. Set up the project tracks as you want and save the project. When done, export a MIDI file back to MuseScore and incorporate the edits into the original score.Īs for track templates, they appear to be unnecessary. Regarding the optimal workflow with MuseScore, I don't know, but my current thinking is to compose as completely as possible in MuseScore, transfer the project to REAPER using a MIDI file and then do all edits in REAPER. If there are major edits, errors are bound to creep in and the two pieces of music will not be in synch.Īny other thoughts on the MuseScore/REAPER workflow would be welcome. It still seems you want to have the composition as final as possible. This might be the solution for small editing changes. To be honest, I don't even know how to copy/paste from one set of tracks to another. I assume modifications to the MIDI note events made in REAPER would pretty much disappear.Īny advice on using track templates (or any other tools) to facilitate re-importing a modified MIDI file and retaining as much setup and edits as possible would be welcome. It would be even better if I could re-import a MIDI file and just import the notes, leaving any controller settings as is (volume tweaks, for example). I don't know if (or how) I can apply a track template to an imported MIDI file so that I can at least have the track names and the right instruments set up. I tried creating a track template and using it, but perhaps I don't understand exactly what this is for or how best to use it. If I go back to MuseScore, make some edits, export a new MIDI file and read it back into REAPER, I may have to do all the setup work again. There is a lot of track setup work needed just to get REAPER to play the imported MIDI tracks. Currently, I am assuming that REAPER and MuseScore work best when the composition is fully created in MuseScore and only then passed on to REAPER by exporting a MIDI file from MuseScore. The score contains all the notes and performance instructions and is the master from which the audio rendition is created. When composing, my ideal end product is a score, but a nice (albeit synthetic) rendition of that score is also a goal. But before Musescore I used Capella and that wasn't better, not just in reliability but also in unwanted changes when introducing new versions.The problem of using both MuseScore and REAPER is mentioned here and there in the forums and in other postings on the net. It's just a pity that every new version requires a lot of re-learning by the end-users. ![]() I'm not complaining, especially about free software. With Windows people were even joking that as Windows 10 had a 0 in the "major" release number it was double trouble with 10.0 came out. The point about not using a version with a 0 in it is very well known in the computer science scene even though it shouldn't be. I was hoping that testing before the release were more thorough, especially to make sure that everything that used to work in the previous release version would still work in the next release version. I am now retired as a computer scientist and am just a musician using the software for making arrangements. I also taught them that a release version is not intended for further testing but should really be finished. I did teach my students very explicitly about the importance of thorough (beta) testing. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |