Hi, with Studio One 6, is there a way to store MIDI input device and input MIDI channel as part of a track preset? When I drag the folder of tracks to 'Track Presets' to make a track preset, no options are given during the copy and when I drag and drop the presets, the input midi instrument and channels and not preserved. For my application, it would be better to be preserved. Anyone know a way to have MIDI routing preserved with track presets? If not, is there a place to submit feature requests to Presonus?
Thanks |
Ahh right i see what you mean now i just tried scaler into serum and your right it can't remember the midi out into serum when you drag the track preset back in. Kinda sucks.
Last edited by garyanderson5 on Sun Oct 02, 2022 9:30 am, edited 2 times in total.
|
I share the same concern. From what I understand It should be able to store at least the midi routing. And it's not. My example : I have one track with Scaler for midi chords generation and one track with a synth that has the Scaler as midi input. Everything works fine. I'm selecting both tracks , save it as track preset but when reusing, the midi routing is not preserved indeed. I also tried with a folder track. Same. Is this a normal behaviour ? The documentation is quiet generic in the reference manual about what we are expecting to see saved or not
|
kmr wroteHi, with Studio One 6, is there a way to store MIDI input device and input MIDI channel as part of a track preset? When I drag the folder of tracks to 'Track Presets' to make a track preset, no options are given during the copy and when I drag and drop the presets, the input midi instrument and channels and not preserved. For my application, it would be better to be preserved. Anyone know a way to have MIDI routing preserved with track presets? If not, is there a place to submit feature requests to Presonus? Works here. The input device is correctly stored and recalled: I don't have Scaler so I can't test how several instrument track behaves when a software instrument is used as an input.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
Thats not the same thing your saving one track. Save two tracks a synth into an arp via midi in on the arp so the synth triggers the arp. The connections lost when you drag the preset back in when it has more than one channel in the preset. Pic below after a track save the connection has reset on serum.
|
I don't have such an instrument with a MIDI output but I'll investigate.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
jazzundso wroteI don't have such an instrument with a MIDI output but I'll investigate. Thanks Lukas |
Thank you Gary and Philippe for verifying the behavior and to Lukas for testing. I agree, the documentation is scant but it does mention "routing" as being stored.
I looked inside the .trackpreset zip file that SOv6 stores and did verify the the midi device and the midi channel are being stored in Devices/musictrackdevice.xml file within the zip archive. Below is an excerpt from that file with MultiArp VST output being routed into software synth VST tracks. So, it appears the input MIDI device and channel are stored in the .trackpreset file, but not being applied when bringing in that preset. Looking through the manual and the program, I couldn't find anything that would control whether particular saved routings are applied when the preset is bought into the project. <MusicTrackChannel transpose="0" velocity="0" iconid="" name="Channel03" label="Arp 1" mute="0" solo="0" soloSafe="0" color="FFD89D00"> ... <Connection x:id="recordPort" objectID="{...}/MusicOutput00" friendlyName="1 - MultiArp/MIDI Output 1"> ... <MusicTrackChannel transpose="0" velocity="0" iconid="" name="Channel04" label="Arp 2" mute="0" solo="0" soloSafe="0" color="FFD89D00"> ... <Connection x:id="recordPort" objectID="{...}/MusicOutput01" friendlyName="1 - MultiArp/MIDI Output 2"> |
kmr wroteThank you Gary and Philippe for verifying the behavior and to Lukas for testing. I agree, the documentation is scant but it does mention "routing" as being stored. Thats great info thanks for that. Hopefully it all helps pin this one down. It's looking more like it is supposed to remember those settings wich i would of thought it was able to do it's just not reading or detecting them as you bring it back in. Thanks KMR. |
garyanderson5 wroteThats great info thanks for that. Hopefully it all helps pin this one down. It's looking more like it is supposed to remember those settings wich i would of thought it was able to do it's just not reading or detecting them as you bring it back in. Thanks KMR. Gary, that's my take on it as well, no reason to store the MIDI routing if not meant to be used. I'm expecting this is a version x.0.0 type problem and we'll see a MIDI routing in track presets being properly set when loading tracking presets. |
I will enter a ticket to see if it's a bug to squash or a "missing features"... honestly when I saw trackS presetS , I was exited about being able to store midi routing between tracks... So cross fingers
|
I've reported this issue to development.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
Maintenance update 6.0.1 released today… not in the release notes .. will try tonight ..who knows cross finger
|
If you are talking about "atom/sq/(insert keyboard here), then it looks like it.
I don't have many instrument track presets currently, but one I use said "atom" and I saved a version set to sq and another one set to the nektar T4, and they are as expected. EDIT: I didn't try the midi input channel, hold please........ ..........Yep, it did. |
Ok made some additional checks : When the midi routing is based on hardware device then it work
But when the midi routing implies cross plugin connections ( here I used the Scaler VST midi output as midi input of Hive ) it does not work. Perhaps because these are non persistent midi in/out devices like the hardware keyboards are |
Nobody can comment on that, no.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
philippebardyn wroteBut when the midi routing implies cross plugin connections ( here I used the Scaler VST midi output as midi input of Hive ) it does not work. The input midi instrument and channels are also not preserved when you transform Instrument Track to Audio Track and then transform it back to Instrument Track. This is a real workflow killer if you use Scaler or any other 3rd party MIDI fx plugin - you have to set the routing manually after each transformation! Things are getting even worst if you use multitimbral setup with multiple MIDI channels and need to transform audio back to instrument track to edit some notes. P.S. I tested the "instrument freeze" function in Cubase, Cakewalk and Ableton - in all cases, routing was properly restored. I'd suggest creating a "bug report" support ticket.
Studio One 6 Pro; OS: Win.10 Pro
Computer: Dell Precision M4700 Mobile Workstation, i7-3740QM 16 GB RAM, 256GB System SSD; 2TB Library SSD; 1TB Projects SSD, 4TB Backup HDD Audio Interface: M-Audio ProFire 2626; M-Audio Air 192-6 MIDI Controllers: Roland A49, Korg MicroKontrol, Korg PadKontrol, Peavey Studiomix, NI Kore 2 |
Users browsing this forum: No registered users and 101 guests