![]() There are other names that have significance, and as I recall "Bass" might be one of them, but who knows without doing experiments. "Synthesizer" probably works, but "Piano" is golden. Regarding sending notes and data from Studio One Professional to NOTION, and vice-versa, the names of Instrument Tracks, Audio Tracks, and Staves are used, where for example if you want notes on a grand staff to be sent and received correctly, the name should be "Piano", since this is what tells the software internally how to treat the notes and data. īy design and intent, ReWire does not support it. Using "repeats" and similar nonsense changes the way people think, and it transforms a song into a caricature. ![]() Ĭut, copy, and paste are fair game, and I use these techniques frequently but I keep the timeline sequential with no jumping from one place to the next. I do not use "repeats", first and second endings, and all that nonsense, which is what I consider it to be. ![]() Įven when songs are constructed by splicing sections of magnetic tape, nothing is an exact repeat in every respect. "Repeats" are relics of a time when music was notated on parchment by scribes, hence the goal was to save paper (or sheep). Is Rewire looking at track names, or is there some sort of a hidden 'ID' involved for each track? Here's a related question: When sending to S1 and using Rewire, how is the back and forth between Notion and Studio One actually 'managed'. In the short term, I'll just 'long hand' the repeats ie, replace the repeats by manually duplicating the repeated sections. Perhaps there's something about my workflow that's relevant to the issue I'm experiencing. (I did this for the Lead Vocal and Chorus, as well as the Piano - melody.) Though I gave unique names to each resulting 'chunk', I didn't change the distance between the chunks (which would surely be asking for Rewire trouble). With the new tracks, (from my second 'send to Studio One'), I did some splits, to eliminate sequential rests that occur when a particular instrument is silent. Essentially, my second 'Send to Studio One' created duplicates of the differently named original tracks, then I disabled the original tracks in Studio One. With my most recent send, I did a fresh send of the Notion tracks, into my existing Studio One song. The S1 piece I'm working on was originally created via a send from Notion, and I've done some modifications along the way. It might even be related to starting my S1 song before I introduced Rewire. Repeats consistently fail when Rewire / S1 are involved, but they work correctly when S1 isn't open.īefore reporting this as a bug, I thought I should check to see if others have noted / reported this particular issue. I've tested the same Notion piece, when Notion was synced to S1 via Rewire, vs. As a result, synchronization between Notion and S1 fails. ![]() Seems to be working okay, except the repeats in Notion are ignored. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |