Studio One recording midi out from VST??????

[Trancit]

Hi there,

I ran into trouble by trying to record the output of Riffer/Cream/ any Midi VST to a new track in S1 4...

Perhaps I am doing it wrong... so here is what I try:

Track 1: Midi VST i.e. Cream/Kirnu triggered by a long sustained note
Track 2: any synth playing the incoming midi (of course I set the track input to the Midi VST)...

If I play normally everything is fine, the synth plays the incoming midi without problems except when looping (on loop jump I get only a long sustained note...
More problems starting if I try to record the incoming midi to track 2...
The visual feedback is already weird...long notes are shown jumping up and down everything is flickering... and when I stop the record I end up either with nothing (no clip...nothing) or with a clip with 1 sustained note which isn´t necessarily the trigger note of the clip on track 1...

Would be very nice, if someone could try too...

[firepile]

Works fine here.

[EnGee]

There are several Midi problems. You can read in Presonus Forums about some of them. Personally, I'm not using S1v4 now. I'm waiting for update(s) as I still have annoying random Loop Midi overdub recording.

[kevvvvv]

Last week I had a similar problem in S1 capturing Avenger sequence output.

Getting the real notes plus some thick line long note type of garbage in my destination midi file, which wouldn't delete in the normal way.

I tried transposing the whole destination midi up an octave (select all - shift up arrow)

Bingo. Problem went.

No idea why, but it did work.

[Trancit]

I am glad to be not the only one... but not so glad, that there seems to be some serious problems...

[zzz00m]

There are several Midi problems. You can read in Presonus Forums about some of them. Personally, I'm not using S1v4 now. I'm waiting for update(s) as I still have annoying random Loop Midi overdub recording.

Based on that quoted thread, I would expect an upcoming MIDI patch from PreSonus.

[EnGee]

I really hope so

[kevvvvv]

Just upgraded to the latest S1 fix version. Dunno how I missed it for so long

But there's some good chord track fixes in there.

Sorry for poor formatting

Version 4.1.1 Release Notes (October 30, 2018):
New features and Improvements: • [ATOM] Keyboard mode for Melodic Editor • [ATOM] Bank button follows bank color • [ATOM] Added user command assignments to pads 1-8 in Setup mode • [ATOM] Play button will change from green to light blue when loop is active • [Impact XT] Multiselect for pads (Shift or CMD) • [Tempo Track] improvements for "Scale Time" manual tempo mapping • [Tempo Track] Update timeline in realtime when warping • Master volume values are shown when slider in transport bar is moved • Increase grab area for automation lines by one pixel on each side • "Follow Chords" settings are now remembered when reverting instrument transformation • Improved spacing in Editor Inspector's chord input display • Added automatic detection for CME Xkey devices • Optimized MIDI update rate for Control Surfaces

The following issues have been fixed: • [Windows 7] Application hanging on launch with nVidia drivers newer than v388.71 • [Windows] Video not displayed on specific hardware • [Windows] Pen support disabled • [macOS] System command focus not working in dialog edit field • [Project Page] Audible pops at song transitions • [Project Page] Loudness detection post fx broken • [Browser] Crash on "Merge to Stereo File" • [Chord Track] Potential crash when playing back song with universal follow mode • [Chord Track] Dragging chords over existing ones won't reflect changes • "Follow Chords" creates wrong results when notes are longer than parts
PreSonus Studio One 4 – Version History
2
• "Copy to new Scratch Pad" ignores Tempo Track • Arranger track edits ignore time signature changes • Incorrect initial send automation on reloading a song • Freeze on moving Bus Channel • Added tempo points not snapping to grid • Timeline jumps when timebase is set to Beat-Linear • Restore version creates duplicate song version • Moving first tempo point of Scratch Pad impossible • In Beat-Linear mode, "Zoom to Loop" scrolls to wrong position • In Beat-Linear mode, the Waveform disappears on audio event in Scratch Pad • When "Release Audio device in Background" option is checked, Studio One exits looped region on losing focus • When "Apply folder track color to content" option is checked, the tracks inside a folder become all grey • Unexpected bounce results on different dropout protection settings • [Macro toolbar] Potential crash on clicking "New Page" • Nebula 4 VST2 plugin not loading • Soloing a Solo Safe Bus without function • Control linked channel fader jumps to initial value when assigned to control linked VCA • [Impact XT] Real time amp decay changes are glitchy • Audition notes not working when cursor follows edit position • Reveal precount early note extends to bar 1 when qwerty keyboard is used as input • Potential crash on undoing track duplications • Note-on at left locator recorded after loop cycle is placed wrong • Wrong note length and start position when played at right locator with Offset enabled • Wrong text color / background color for edit boxes of Arranger Track Inspector items • Odd behavior when copy/pasting automation point • Crash when saving song w/ empty Presence • Certain songs w/ Melodyne 4.2 get stuck at playback • Some add-ons (Sound Sets, VU-Meter, etc.) missing in Studio One Demo • Song loses "pin" state after restoring versions • Split at Grid only splits first few bars with odd tempo • Unexpected duplication result on event following chord • Crash on closing song after deleting Scratch Pads

[EnGee]

Sorry, I thought it is a bug! But it is a feature! Really!

The drawn notes are from another track (Battery track). OK! Back to music then