AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Copying MIDI From One Project To Another (A Bug?)
Hello Everyone, This goes back to some recent MIDI problems I was having. I sometimes copy MIDI from one project to another, and I realize that when you copy a clip from one project to another, it ALSO copies the MIDI input selection for some reason! So for instance, if I have a MIDI track that is set to OMNI in my source project, and a MIDI track with the MPK225 as the input in my destination, if I copy and paste MIDI data from my source project, to the destination project, the MIDI input of the destination project, ALSO changes to OMNI!
(note: if there is already MIDI data on the track, it seems like it doesn't switch, only if you are copying the MIDI to an EMPTY track in your destination project). Seems like a small little bug or mis-programming there, unless there is a use-case which I am missing.
Either way, I wanted to share this, maybe the bakers will change this behavior or someone can shed some light. If not, maybe it will at least help someone else realize why sometimes their MIDI track is accepting input you wouldn't expect! -Adam
|
Jeff Evans
Max Output Level: -24 dBFS
- Total Posts : 5139
- Joined: 2009/04/13 18:20:16
- Location: Ballarat, Australia
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/05 21:53:18
(permalink)
I would not necessarily see this as a bug. It is quite normal really. Bit like opening another Sonar session say that was done using a completely different audio interface and routing than yours. Often the session will try and remember this and attempt a similar routing except that the interface is not there and some simple re routing on your part will get your interface working instead. Happens in Pro Tools quite bit too. It is just a simple matter of checking where midi track input signals were coming from and where they are going and re-route as necessary.
Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/05 22:19:09
(permalink)
Jeff Evans I would not necessarily see this as a bug. It is quite normal really. Bit like opening another Sonar session say that was done using a completely different audio interface and routing than yours. Often the session will try and remember this and attempt a similar routing except that the interface is not there and some simple re routing on your part will get your interface working instead. Happens in Pro Tools quite bit too. It is just a simple matter of checking where midi track input signals were coming from and where they are going and re-route as necessary.
but remember, I am simply copying MIDI clips! I am not importing a track template or anything. Why would pasting a few notes change the already existing input? You can copy notes from a different track INSIDE your project and nothing changes, so why from OUTSIDE your project?
|
mhazdra
Max Output Level: -90 dBFS
- Total Posts : 16
- Joined: 2010/09/18 02:01:12
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/09 03:14:27
(permalink)
I am having similar issues. I want to just copy MIDI notes. However the patch information somehow gets copied. I look in the event list and do not see any Patch Change events. Also, a few months ago I copied MIDI from one project to another and Cakewalk crashed.
" Much of the Beauty that arises in art comes from the struggle an artist wages with his limited medium." - Henri Matisse Cakewalk User Since 1988 (Cakewalk V2.0)
|
Slugbaby
Max Output Level: -33.5 dBFS
- Total Posts : 4172
- Joined: 2004/10/01 13:57:37
- Location: Toronto, Canada
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/09 08:41:05
(permalink)
Perhaps it's something in your process? I open the project I want to copy from, and the project I want to copy to (with the destination Midi clip already created). CTRL- Drag/drop the midi clip to the new project and it's done. This doesn't copy the output settings.
|
SquireBum
Max Output Level: -84 dBFS
- Total Posts : 347
- Joined: 2013/06/26 13:23:55
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/09 11:30:25
(permalink)
SilverBlueMedallion I sometimes copy MIDI from one project to another, and I realize that when you copy a clip from one project to another, it ALSO copies the MIDI input selection for some reason! So for instance, if I have a MIDI track that is set to OMNI in my source project, and a MIDI track with the MPK225 as the input in my destination, if I copy and paste MIDI data from my source project, to the destination project, the MIDI input of the destination project, ALSO changes to OMNI!
-Adam
I cannot reproduce this behavior on my system using Copy/Paste or using Ctrl+Drag to copy a MIDI clip from one project to another. There must be something set up differently on your system or as @Slugbaby states "something in your process". -- Ron
Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5 Windows 10 x64 AMD Phenom II X4 955 3.20 GHz 8 GB Ram Nvidia GeForce 9500 GT Echo Gina 3G
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/10 14:09:58
(permalink)
SquireBum
SilverBlueMedallion I sometimes copy MIDI from one project to another, and I realize that when you copy a clip from one project to another, it ALSO copies the MIDI input selection for some reason! So for instance, if I have a MIDI track that is set to OMNI in my source project, and a MIDI track with the MPK225 as the input in my destination, if I copy and paste MIDI data from my source project, to the destination project, the MIDI input of the destination project, ALSO changes to OMNI!
-Adam
I cannot reproduce this behavior on my system using Copy/Paste or using Ctrl+Drag to copy a MIDI clip from one project to another. There must be something set up differently on your system or as @Slugbaby states "something in your process".
 -- Ron
thanks for the video. Well for one, i am not dragging and dropping. I am copy/pasting with CTRL+C and CTRL+V
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/10 14:23:29
(permalink)
 copy paste working fine using right click context menus. So you have some choices. Drag and drop or right context menus. I wouldn't call it a bug as much as I would say its probably a focus condition with key commands.
post edited by chuckebaby - 2017/02/10 15:11:37
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
SquireBum
Max Output Level: -84 dBFS
- Total Posts : 347
- Joined: 2013/06/26 13:23:55
- Status: offline
Re: Copying MIDI From One Project To Another (A Bug?)
2017/02/10 17:04:49
(permalink)
SilverBlueMedallion thanks for the video. Well for one, i am not dragging and dropping. I am copy/pasting with CTRL+C and CTRL+V
I also tested with Copy/Paste (Ctrl+C/Ctrl+V) and it worked the same as drag and drop on my system. Just to make sure that it functioned correctly with only 1 MIDI port enabled, I disabled my Echo Gina interface input and all of the 3rd party loopback ports. -- Ron
Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5 Windows 10 x64 AMD Phenom II X4 955 3.20 GHz 8 GB Ram Nvidia GeForce 9500 GT Echo Gina 3G
|