33 postsPage 2 of 2
1, 2
It means that during the first test, the instrument output (on the MIDI track in the track arrange view) is empty. And afterward, a drum instrument / plugin is selected from its drop down menu. So, yes, something is then put between the input and the signal going to the MIDI file which allows the C4 to be recorded after 1 take.

The instrument input—the V-Drums ("keyboard instrument") remains the same, throughout.

And, all output is within the DAW. There's nothing outboard going on.

As an aside, half of the struggle in communicating is getting the language right, including with these DAWs. Over the years I've had to learn how various DAWs name their constituent parts. Digital Performer even has something called "chunks." At least S1 uses names within the range of sanity. :) But I sometimes have to go back and articulate stuff more clearly cause I tend to use a lot of Swahili slang when posting here. :)

Nip wrote
roland1 wroteBut if I then instantiate a VSTi (SSD5 for instance) or that placeholder V-Drum instrument I created, in the instrument output, then suddenly the CC4 records reliably with every pass and prints to every take.



I don't follow what you say here, compared to first post?
Are you having something in between inputs and the VSTi?

That could mean that, whatever, is having problem when time suddenly jumps back in the loop.

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.
User avatar
by Nip on Tue May 14, 2019 10:16 am
Before I abandoned StudioOne 2.x there were issues with recording any midi CC - unless you had monitor on(arm for record was not enough). So normal use of VSTi was no problem - but with external gear in some cases where I recorded both audio directly, and another midi track as well not monitored.

So never running StudioOne v3.x I don't know when they fixed that. I started with 4.1 last fall.

Now there are other things that are strange - using a lot of external gear as I do - I have to make one keyboard setup entry and only use input, never output of midi. Then create an instrument and only use midi output to that one. Or I don't get these ports available in settings for ins/outs.

So to me it seems StudioOne is in the middle of some transformation - needing double setup of midi source part like keyboard and another setup for output to instrument. And you always have to avoid using one side available in setup dialog. I scratched my head plenty over that when I started last fall.

So input port I use now for DTX is a midi input only - which works fine, looping or not as recorded - but midi track assigned to something.

But could be I did not use what you do - which I still don't get why there is nothing assigned to output.
When you do - it works - you said.

If you rely on monitor thru the keyboard setup you created?
Use a separate setup instrument for that. Dialog encourage you to think you can assign both ins and outs in one definition.

Hope you get some new ideas what to look for....still something using monitor or not?
It's something you do that a couple of us did not do, it seems.

*** Windows 7 Pro * i7-860 2.8 Ghz 16 GB ram * RME HDSP 9632+AI4S+Audient ASP 800 * GT730 ***
User avatar
by roland1 on Tue May 14, 2019 10:50 am
Well, my good dude, in regards to your earlier post, the "thing" that's having the problem is the empty instrument output slot—when there's nothing's in there.

Once I fill that output with an instrument plugin (SSD5) or an instrument controller, then it sends CC4 reliably.

The pic below shows SSD5 in the instr. output. Before, as I was testing, I left it empty, which resulted in the problem of CC4 not showing up after 1 take.

Next to that image is an open options window for configuring external instruments, etc. Here you can see that I've created a keyboard instrument, which is what gets the V-Drums into Studio One from the outside—and yay, it mostly works. I've also now created an "instrument instrument" (or whatever convoluted name is used to describe it) which acts like a surrogate/proxy VSTi device that allows me to fill the instr. output slot without engaging an actual plugin that makes noise and wastes RAM.

Hey, I didn't write this program, so it's somebody else's fault that I'm struggling to explain something that also makes no sense to me. :D Hope that helps to explain it.

CC4_MIDI_issue_nodes_instr_outputs.gif


Nip wrote
roland1 wroteBut if I then instantiate a VSTi (SSD5 for instance) or that placeholder V-Drum instrument I created, in the instrument output, then suddenly the CC4 records reliably with every pass and prints to every take.



I don't follow what you say here, compared to first post?
Are you having something in between inputs and the VSTi?

That could mean that, whatever, is having problem when time suddenly jumps back in the loop.

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.
User avatar
by Nip on Wed May 15, 2019 2:02 am
Your explanation how you are doing it was rather late - so excuse us testing maybe the most common ways to do it.

Since I had that issue with monitor off in StudioOne v2.x - just arm a track for record and record and just notes were recorded, not midi CC. If monitor on also midi CC were recorded.

So it seems somewhat related and I would not be surprised knowing how it is setup we can reproduce this as you do it with empty outs. And I think it's all midi CC that is not recorded - being similar to my old problem.

I find to have HH pedal really provide the right cooosh I have to use a VSTi like SuperiorDrummer, so I could not do it like you. So to get same result I need to use monitor through daw - to get exactly the same feel.

I record my Hammond XK3C the way you do - and record audio beside midi - since Hammond has some silly implementation of midi needing to change setup in organ switching from record and playback. So I really want this to work, doing volume pedal or drawbars while playing. But I seldom do loop recording as such so never was a problem so far - I just remove a take or add a layer and record again.

I will try and reproduce next time at StudioOne so you can report it as a bug.
Devs separate midi CC in a special way regarding recording it seems if this can be reproduced.

Your workaround is probably assign to any VSTi and move fader down on that while recording drums.

So to quote you "Stay strong Roland...."

*** Windows 7 Pro * i7-860 2.8 Ghz 16 GB ram * RME HDSP 9632+AI4S+Audient ASP 800 * GT730 ***
User avatar
by roland1 on Wed May 15, 2019 5:48 am
Yesterday, I thought I could sit down and drum a little with CC4 using the output instrument I created in (external controllers options). Well, all of a sudden it stopped recording even the snare drum and kicks. Only one tom and a cymbal was recorded (and I'd played the song through 3 times at that point. F***).

So I erased that proxy V-Drum instrument thingy completely.

Anyway, I decided to go back and put the SSD5 in and just use my slider on the fader port to turn its volume up and down. It does work as a workaround, but I shouldn't need it.

Presonus???

Nip wrote...
Your workaround is probably assign to any VSTi and move fader down on that while recording drums.

So to quote you "Stay strong Roland...."

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.
User avatar
by roland1 on Sun Mar 22, 2020 8:37 pm
I ran into the same problem again today and it seems what NIP had written earlier holds true:

If you turn the monitoring button off, CC#4 data is not properly recorded in loop mode after the first pass. However, when you turn it on, the CC#4 information seems to work in loop mode.

Huh? Really?

True Story.

So engaging "monitor" seems to have some affect on incoming MIDI data as well. Fascinating.

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.
User avatar
by roland1 on Sun Mar 22, 2020 9:21 pm
NOPE! Engaging the monitor button doesn't work either. I guess S1 is still crap for recording CC#4 in loop mode. At least on my setup. How about yours?

As I indicated in an earlier post, this setup works flawlessly in Reaper, so I don't have to:

1) Try buying a new V-Drum kit
2) Try buying a new computer,
3) Try reinstalling my OS,
4) Try upgrading all my plugins,
5) Try converting to a monotheistic religion.

Nope. It just doesn't friggin' work as it's supposed to.

But it does a lovely job on the first pass. :p

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.
User avatar
by robertgray3 on Sun Mar 22, 2020 10:41 pm
This only happens when there is no instrument on the instrument track

Assign that track to some instrument, any instrument, and mute the audio output of it.

You can always remove the instrument later.

Yes it's weird that they haven't fixed it yet but idk if it's worth complaining about this for a year when the workaround is so simple.

My feature requests (every vote helps!)

Mac OS X Mojave 10.14.6
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by roland1 on Mon Mar 23, 2020 6:11 am
Have you tried it? Just FYI, I was actually the person who first made that comment/discovery about instantiating an instrument. But it's not true. At least not in 4.61, which I've just recently switched to in my main machine. (I'm also using Slate 5.5 as the instrument.)

None of the above works. The CC#4 stops recording beginning on the second pass. I've gone through all of this and what I thought was working before, clearly isn't.

I avoided V-Drum loop recording for a while by just doing full song length passes, but yesterday I was working on 8 bar Chorus sections and it failed again. Or more accurately, it reminded me of its failure to work.

Always works on the first pass though, so the hh pedal is working. Studio One, not so much...





robertgray3 wroteThis only happens when there is no instrument on the instrument track

Assign that track to some instrument, any instrument, and mute the audio output of it.

You can always remove the instrument later.

Yes it's weird that they haven't fixed it yet but idk if it's worth complaining about this for a year when the workaround is so simple.

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.
User avatar
by robertgray3 on Tue Mar 24, 2020 6:13 pm
It is true. Just tested it on Mac. Works as long as it’s pointing to an instrument. Loop Recording Takes mode. CC4 or any other controller data.

Either it works differently on Mac then PC or you’re doing something different than I am.

If you want a video of it working just let me know.

Hopefully that will help you work around it. Good luck!

My feature requests (every vote helps!)

Mac OS X Mojave 10.14.6
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by roland1 on Tue Mar 24, 2020 8:46 pm
I'm doing this CC#4 recording on a PC. So maybe there's something else going on.

It seems to get jammed somehow. You can see it in the original GIF I created on the first page(?) That's what's happening. Tracks fine on first pass, then stops recording CC to the body of the file. It only records the end points it seems, which leaves a straight line where open hat dips are supposed to be.

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.
User avatar
by robertgray3 on Tue Mar 24, 2020 10:09 pm
roland1 wroteI'm doing this CC#4 recording on a PC. So maybe there's something else going on.

It seems to get jammed somehow. You can see it in the original GIF I created on the first page(?) That's what's happening. Tracks fine on first pass, then stops recording CC to the body of the file. It only records the end points it seems, which leaves a straight line where open hat dips are supposed to be.


Yes and like I said in multiple posts that only happens for me if the Instrument track is not routed to a VST/AU instrument. I have not tested with my External Instruments but if you add a placeholder VST that makes no noise (like Impact or SampleOne) this will not happen anymore. It is a bug. This is a workaround. For some reason it hasn’t gotten fixed- my guess is whoever has contacted Support about it has not been able to communicate it properly. Luckily it is easy to work around it.

My feature requests (every vote helps!)

Mac OS X Mojave 10.14.6
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by roland1 on Wed Mar 25, 2020 8:17 am
FYI, that VSTi / drum instrument is always in the track as a matter of habit. Not sure if I mentioned that in multiple posts, but that has been my practice from the time I realized it might have an affect. But it's still screwing up...

So, having the VST in the channel is neither the cause of the problem, nor the cure. Better programming, I suspect, might be.

I'm gonna do my V-Drum fixes in Reaper. It has less MIDI drift, too, apparently.


robertgray3 wroteYes and like I said in multiple posts that only happens for me if the Instrument track is not routed to a VST/AU instrument. I have not tested with my External Instruments but if you add a placeholder VST that makes no noise (like Impact or SampleOne) this will not happen anymore. It is a bug. This is a workaround. For some reason it hasn’t gotten fixed- my guess is whoever has contacted Support about it has not been able to communicate it properly. Luckily it is easy to work around it.

I use: Studio One Pro v4.53 on i7 7700 win10 PC w16GB RAM and Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors pretending to like the product. It's easy to forget that fact with the music blaring and their happy smiles flashing.

33 postsPage 2 of 2
1, 2

Who is online

Users browsing this forum: fernandogaspar and 15 guests