PreSonus Forums

klypeman wroteMy bad then Still what you wrote first didn’t describe that..

I wrote "after update" Didn't I?

pawelhebda wrote

klypeman wroteMy bad then Still what you wrote first didn’t describe that..

I wrote "after update" Didn't I?

Of what ? SO5.2 or UAD plugins ?
I guess it was the DAW but that was not clear so had to guess. Just trying to help if needed but you sound like you’re good so, cheers !

Baphometrix wroteI'm seeing that if you mute an Instrument track from its channel OR from it's Inspector, the Mute button for that track header does not light up. And vice-versa. Meaning if you click the Mute button in the instrument track's header, the corresponding Mute button won't light up in the Inspector or the Mixer channel.

Is anyone else seeing this? The muting actually happens in all cases, but it makes it really hard to understand what you're seeing in the Arranger, because you might have some channels muted but the Arranger won't show those same muted tracks as actually appearing muted.

Yes, I'm seeing this. It's the correct behavior and it's been that way for 10 years

The reason is that instrument tracks and channels are not the same thing. An instrument track doesn't contain audio. It contains notes and other events which are sent to an instrument. This instrument creates audio and that's what goes into your mixer channel. If you mute the instrument track, no notes will be sent to the instrument. But the instrument's audio output is not muted! Imagine an organ VSTi with a leslie simulation that produces a constant rotary noise. Although your instrument track is muted, you still hear the rotary speaker noise. If you want to does not want to hear anything you have to mute the channel, not the instrument track.

That's why track mute and channel mute are not synchronized. That's correct and it's indeed very important and not "an issue". You could have a multitimbral instrument like KONTAKT with 16 MIDI channels and 16 different instruments. (This means you can have 16 instrument tracks routed to the same instrument and play 16 different instruments on different MIDI channels). If you want to mute just one instrument track, you don't want to mute the whole KONTAKT in the mixer (which would mute all the other 15 instruments too).

This doesn't happen with Audio tracks. Only with Instrument tracks.

Correct. Because audio tracks actually contain audio data so there is a 1:1 relationship between track and channel.

Glad to see: bugs being squashed
Sad to see: the issue with the controller at the beginning of a track being "not zero" even though the controller was actually at zero when recording started. Hard to explain this one, but I know I'm not the only one, it's not limited to the Roland Handsonic, and other have seen this as well.

It's hardly the end of the world, but it would be nice to see this fixed. Basically a controller that should be at zero ends up recording something like a value of 5 at the beginning of a track. In my case, this is cc21 event, which is the "mute" on a Handsonic. So, if I'm playing a Conga, it will be a muted Conga until I actually mute it and release that mute - then it will be open like it should have been. In most cases, this is probably pretty subtle as to go un-noticed, but in a case like this one, it wrecks that starting percussion.

Baphometrix wrote

bruceqld wrote

Baphometrix wroteI'm seeing that if you mute an Instrument track from its channel OR from it's Inspector, the Mute button for that track header does not light up. And vice-versa. Meaning if you click the Mute button in the instrument track's header, the corresponding Mute button won't light up in the Inspector or the Mixer channel.

Is anyone else seeing this? The muting actually happens in all cases, but it makes it really hard to understand what you're seeing in the Arranger, because you might have some channels muted but the Arranger won't show those same muted tracks as actually appearing muted.

This doesn't happen with Audio tracks. Only with Instrument tracks.

I reported this after a previous update but It is an intended behavior. The inspector mirrors the console, not the track, as you can have more than one instrument track assigned to a single channel in the console.

Funny how we notice these things after an update. i did the same.

May I ask how, exactly, this is done? I've never noticed such an option. I've just looked carefully and cannot figure out how to do this in any obvious way. And it's completely counter-intuitive to me. I've never run across this ability in any other DAW, either.

Even if you create a multi-instrument, it still appears as only a single track in the arranger. Even if you create a multi-output instrument, every output channel gets its own track in the console.

You can easily create another instrument track (or duplicate the one you have) and set its output to an existing instrument. You do not have to create multiple outputs to use a multi channelled vst. You can have just a stereo output with multiple tracks on various midi chanels routed to the instrument. It can be done in any DAW. I agree, however, that the mute behaviour seems counter intuitive, hence attempting to report it previously. Sonar had a far better method for dealing with this by changing the colour of the mute button in the console if multiple tracks were routed to it but only some were muted. The inspector mute button then stayed in sync with the track and the console.

Those saying this was not in 5.2 are wrong. It has always been like this. Roll back as far as you like and check:)

I having a big problem with score view in the new update. No matter what part I click, I get only the the first 31 bars of that track. Even if there isn't any parts for that track in those 31 bars. Cannot scroll the score past bar 31. At the end of bar 31 is the double bar indicating the end of the piece.

The 5.2.1. update appears to have solved a problem I was having with my Zoom keyboard shortcuts in the Edit window for Midi tracks - I have the Zoom Verticle and Horizontal mapped to my four arrow keys on my keyboard but under 5.2.0 for some reason, when editing in the Midi Edit window, these arrow keys suddenly became track and channel changers rather than zoom. Resetting the keyboard shortcuts made no difference - used to zooming with the arrow keys this was very annoying.

5.2.1 appears to have solved this issue. So that's good - some strange bug fixed but not noted anywhere.

So, the update appears to have fixed the problem of S1 restarting on it's own after shutting it down. It did not fix my other issue of getting the new screen that says it has a problem and cannot start. I still get it every time I open S1 and have to tell it to open normally. Annoying!

rodshort wroteSo, the update appears to have fixed the problem of S1 restarting on it's own after shutting it down. It did not fix my other issue of getting the new screen that says it has a problem and cannot start. I still get it every time I open S1 and have to tell it to open normally. Annoying!

You've already posted on another thread so I've answered here:
viewtopic.php?f=151&t=44438&start=40

Anybody else having similar issues I suggest moving to this thread or starting your own.

Anybody getting high CPU usage when an instrument track is record armed? I don't know if this happened in previous versions. Arturia Juno, Toontrack, Omnisphere... they all climb up to 80 to 90 percent when I record arm the track.

ericma2 wroteAnybody getting high CPU usage when an instrument track is record armed? I don't know if this happened in previous versions. Arturia Juno, Toontrack, Omnisphere... they all climb up to 80 to 90 percent when I record arm the track.

When you arm that's generally when the audio interface drivers kick in.
I think your audio interface firmware is now 3.6.1?
Also try removing your audio interface drivers and then installing the latest.
Also if there are any unused audio interface drivers that can be removed, do that.
When you are done don't forget to reboot.

Check your audio device settings, specifically the Processing tab. Try different settings for „ Enable low latency monitoring for instruments“. Some instruments work better with, others without this option.

Baphometrix wroteI'm seeing that if you mute an Instrument track from its channel OR from it's Inspector, the Mute button for that track header does not light up. And vice-versa. Meaning if you click the Mute button in the instrument track's header, the corresponding Mute button won't light up in the Inspector or the Mixer channel.

Is anyone else seeing this? The muting actually happens in all cases, but it makes it really hard to understand what you're seeing in the Arranger, because you might have some channels muted but the Arranger won't show those same muted tracks as actually appearing muted.

This doesn't happen with Audio tracks. Only with Instrument tracks.

Yea same thing here. For vst instruments it's not such a big deal for me really, as wehn you mute the "MIDI track" in the arranger the plugin won't produce sound, but when you use external instruments via and aux channel it get annoying, as I always have to go into the mixer or inspector to actually mute the audio of the track.

[Edit] So I get that this is intentional then. Maybe an option to choose between both modes would be cool though.

leonordmann wrote[Edit] So I get that this is intentional then. Maybe an option to choose between both modes would be cool though.

In my personal opinion, I think that what would be better than that option would be if their Channel link feature (the “Channel” drop down in the inspector for Instruments) also applied to this situation. It’d be nice if you could control the track’s associated Channel or Aux by clicking with a mouse modifier or something like that. It would also take a different color to show that a Track’s assigned channel is muted (even if the track is not).

I think there’s plenty of benefit to keeping them partially separated, so I’d love to see them linked more selectively without having to just turn on and off some behavior manually.

Once this distinction hit me full in the face, I've stopped using the Arrangement Track headers to mute or solo anything at all. (I almost never need multiple Instrument tracks driving different channel inputs to the same Software Instrument.)

Instead, I now just pop the Console open when I need to solo/mute stuff. And I'm much happier. Everything "makes sense" in the Console.

Example of another weakness/weirdness when trying to use the Track header mutes/solos. We have "exclusive solo" or (dim solo) in Studio One, right? You hold Alt (Option) while clicking a solo button and it automagically UN-solos everything else that was previously soloed, right?

So, this works great in the Console. Alt-click a channel's Solo button, and suddenly only it (and any downstream busses it passes through) are soloed. You get what you expect. Alt-click the Solo button on a BUS and suddenly only that BUS, its upstream channels/busses, and its downstream busses are soloed. Again, everything makes sense.

But now try this up in the Arranger. Make three tracks and then pack them into a parent Folder track A. Make another three tracks and pack them into a parent Folder track B.

Now, click the Solo button on Folder Track A. It lights up, all three of its children tracks light up, and Folder B and its three children are muted. This is an expected outcome. Repeat this process by un-soloing Folder A and instead soloing Folder B. Again, you get what you expect.

But now try do to an Exclusive Solo switch from Folder Track A to Folder Track B. Go on, try it! You will absolutely NOT get what you expect.

Baphometrix wrote... Make three tracks and then pack them into a parent Folder track A. Make another three tracks and pack them into a parent Folder track B.

Now, click the Solo button on Folder Track A. It lights up, all three of its children tracks light up, and Folder B and its three children are muted. This is an expected outcome. Repeat this process by un-soloing Folder A and instead soloing Folder B. Again, you get what you expect.

But now try do to an Exclusive Solo switch from Folder Track A to Folder Track B. Go on, try it! You will absolutely NOT get what you expect.

What I didn't expect is that you made such a long post, but you didn't write down what would actually happen.

Mirek Mach wrote

Baphometrix wrote... Make three tracks and then pack them into a parent Folder track A. Make another three tracks and pack them into a parent Folder track B.

Now, click the Solo button on Folder Track A. It lights up, all three of its children tracks light up, and Folder B and its three children are muted. This is an expected outcome. Repeat this process by un-soloing Folder A and instead soloing Folder B. Again, you get what you expect.

But now try do to an Exclusive Solo switch from Folder Track A to Folder Track B. Go on, try it! You will absolutely NOT get what you expect.

What I didn't expect is that you made such a long post, but you didn't write down what would actually happen.

Only the bottom track in each folder will be soloed.

Hey community,
I found a problem. It is not possible anymore to remove a layer from several selected tracks. (grouped or not grouped doesn't make a difference). Only the layer in the current selected track will be removed. Add Layer and Duplicate works as expected.
As an example: I've got a drum recording with 20 tracks, everything has been recorded to takes, about 10-15 takes. Now I unpack those takes to layers and want to sort out some takes where the performance is not perfect. With this problem I have to select the right layer in every track and have to remove it individually. And if you don't know about that and you expect that the layer will be removed in every track you have a complete messed up session.
Perhaps someone would be so kind to cross check if this is only on my system or if this is really the actual beahviour.
Thanks everybody and cheers,

So someone just posted Studio One is selecting inputs when you change a track from stereo to mono. I am not even sure if this is normal as i always bus tracks and mono from the bus but i thought i would ask.

Steps to test.
1.Create a stereo track,
2. Select no input.
3.Then select mono or stereo on the track.

Studio One V4 and 5.2 selects the input on of your interface on it's own. It does this without changing the input to none also. Steinberg UR44 i tested with. Guy was using a roland that asked the question. If you send the track to a buss and mono the buss it is unaffected and keeps the input as it should be.

Is this normal behaviour or something not working as it should?

garyanderson5 wroteSo someone just posted Studio One is selecting inputs when you change a track from stereo to mono.

I thought it always did that, and I find it helpful in most cases. I guess it depends how you set up your I/O settings and whether or not one has audio tracks with no input assigned frequently.