21 postsPage 1 of 2
1, 2
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
User avatar
by garyanderson5 on Sun Oct 02, 2022 9:15 am
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.

Windows Pro 11 23H2, 13900K, Z790 Aorus Master, 64GB 32x2 G.Skill Trident Z C30 RAM, 3X 2TB Samsung 980 PRO, RX6650XT GFX Card, Corsair RM1000X PSU, Studio One Latest Version & Older versions, Baby Face Pro FS. Nektar T6,
User avatar
by philippebardyn on Sun Oct 02, 2022 9:19 am
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

Studio One 6.5 MacBook AIR M1 16mb Focusrite Scarlett 6i8 mk3. Maschine MK3 , Faderport 2018, ATOM SQ, Komplete Kontrol S49 mk2, Arturia keylab essential, Arturia key step 37 , Behringer MS1, Tb3, ASM Hydrasynth Explorer, Korg Wavestate, Roland TR6S, Electron Model Sample
User avatar
by jazzundso on Sun Oct 02, 2022 9:49 am
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?

Thanks

Works here. The input device is correctly stored and recalled:

Image

I don't have Scaler so I can't test how several instrument track behaves when a software instrument is used as an input.

Attachments
track-preset-input-device.gif

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || 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
User avatar
by garyanderson5 on Sun Oct 02, 2022 9:59 am
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.

Attachments
Capture.PNG

Windows Pro 11 23H2, 13900K, Z790 Aorus Master, 64GB 32x2 G.Skill Trident Z C30 RAM, 3X 2TB Samsung 980 PRO, RX6650XT GFX Card, Corsair RM1000X PSU, Studio One Latest Version & Older versions, Baby Face Pro FS. Nektar T6,
User avatar
by jazzundso on Sun Oct 02, 2022 10:04 am
I don't have such an instrument with a MIDI output but I'll investigate.

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || 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
User avatar
by garyanderson5 on Sun Oct 02, 2022 10:05 am
jazzundso wroteI don't have such an instrument with a MIDI output but I'll investigate.


Thanks Lukas :)

Windows Pro 11 23H2, 13900K, Z790 Aorus Master, 64GB 32x2 G.Skill Trident Z C30 RAM, 3X 2TB Samsung 980 PRO, RX6650XT GFX Card, Corsair RM1000X PSU, Studio One Latest Version & Older versions, Baby Face Pro FS. Nektar T6,
User avatar
by kmr on Sun Oct 02, 2022 1:12 pm
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">
User avatar
by garyanderson5 on Mon Oct 03, 2022 7:10 am
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.

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">


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.

Windows Pro 11 23H2, 13900K, Z790 Aorus Master, 64GB 32x2 G.Skill Trident Z C30 RAM, 3X 2TB Samsung 980 PRO, RX6650XT GFX Card, Corsair RM1000X PSU, Studio One Latest Version & Older versions, Baby Face Pro FS. Nektar T6,
User avatar
by kmr on Mon Oct 03, 2022 9:26 pm
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.
User avatar
by philippebardyn on Tue Oct 04, 2022 11:36 am
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

Studio One 6.5 MacBook AIR M1 16mb Focusrite Scarlett 6i8 mk3. Maschine MK3 , Faderport 2018, ATOM SQ, Komplete Kontrol S49 mk2, Arturia keylab essential, Arturia key step 37 , Behringer MS1, Tb3, ASM Hydrasynth Explorer, Korg Wavestate, Roland TR6S, Electron Model Sample
User avatar
by jazzundso on Tue Oct 04, 2022 11:53 am
I've reported this issue to development.

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || 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
User avatar
by kmr on Tue Oct 04, 2022 5:39 pm
jazzundso wroteI've already passed it on to development. Let's see what happens.

Thanks, guys, I'm new to the Presonus forums so I appreciate you posting the issue where the development team can review.
User avatar
by philippebardyn on Wed Nov 09, 2022 12:59 pm
Maintenance update 6.0.1 released today… not in the release notes .. will try tonight ..who knows cross finger

Studio One 6.5 MacBook AIR M1 16mb Focusrite Scarlett 6i8 mk3. Maschine MK3 , Faderport 2018, ATOM SQ, Komplete Kontrol S49 mk2, Arturia keylab essential, Arturia key step 37 , Behringer MS1, Tb3, ASM Hydrasynth Explorer, Korg Wavestate, Roland TR6S, Electron Model Sample
User avatar
by reggie1979beatz on Wed Nov 09, 2022 1:55 pm
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.

Bye......:roll:
User avatar
by philippebardyn on Wed Nov 09, 2022 2:05 pm
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

Studio One 6.5 MacBook AIR M1 16mb Focusrite Scarlett 6i8 mk3. Maschine MK3 , Faderport 2018, ATOM SQ, Komplete Kontrol S49 mk2, Arturia keylab essential, Arturia key step 37 , Behringer MS1, Tb3, ASM Hydrasynth Explorer, Korg Wavestate, Roland TR6S, Electron Model Sample
User avatar
by reggie1979beatz on Wed Nov 09, 2022 2:19 pm
I think I know what you mean. I'll have to see in a couple.

Bye......:roll:
User avatar
by arranger on Wed Jan 25, 2023 12:59 pm
hi ;))

can anyone tell if it will be further developed or fixed if it is a bug?

    Studio One 5 Pro 64-Bit
      Windows 10 Home 64-Bit
      i7-10700K CPU @ 3.8 GHz
      32,0 GB RAM
      User avatar
      by jazzundso on Wed Jan 25, 2023 7:58 pm
      Nobody can comment on that, no.

      Lukas Ruschitzka
      Studio One Specialist
      Advanced Studio One Tutorials || Free Studio One Scripts || 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
      User avatar
      by robertpaczkowski on Thu May 04, 2023 4:34 am
      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

      21 postsPage 1 of 2
      1, 2

      Who is online

      Users browsing this forum: Anderton, leosutherland and 61 guests