This is a multi-timbre channel related bug

Cubase
,
22

Hi,

…and I will disagree with @Johnny_Moneto again (sorry). :slight_smile:

My expectation is, I can see the Multi-instrumentul Return Channel, which is assigned to this given Instrument Track, when I select it. Same as it works with the MIDI Tracks routed to an Instrument.

  • Add an Instrument Track (HALion Sonic SE)
  • Enable 4 Multi-Instruments Returns.
  • Route the Instrument Tracks Return to HS Out 2.
  • Add 1 more MIDI Track, route it to the existing HALion Sonic Instrument Tracks.
  • Set its Returns to HS Out 3.
  • Expand the Multi-Instrument Returns of the Instrument Track and select HS Out 4 Return.
  • Select the MIDI Track.
    → The HS Out 3 appears in the Channel (which is the one, which is assigned to this MIDI Track).
  • Select the Instrument Track.
    → HS Out 4 appears in the Channel. I would expect to see HS Out 2, which is assigned to this MIDI source data in the given Instrument Track.
23

OK,.
I understand.

You are talking about a similar but different type of bug than what I am talking about.
My English translation tool may have misrepresented it.

Or perhaps you simply don’t understand.

It is a different type of bug, but there is no point in discussing it further.

OK? Let me explain one last time.

I am only talking about the “Miditrack” when output in multitimbral, not the pull-down track that expands when you click the down arrow on the instrument track.

You are fundamentally wrong. The image you are sending is a pull-down track, correct?

Please review my image again.
It is a “midi track”. I’ll say it again? Midi track.

Do you understand?
It’s a “midi track” connected to the 2nd channel of the underlying instrument track and beyond.

I’ll show you a picture. This is what you are talking about.

pull down
pull down1910×1038 335 KB

Of course I know this is a bug, and I have raised this issue on the forum.
I think the bug started around 13.

What I am saying is this. Look at the area circled in blue. It’s “Miditrack,” right? Do you see it?

bug1
bug11914×998 265 KB

bug2
bug21918×990 265 KB

In summary
I am saying

“The top left of the left-most inspector when connected to Miditrack from 2 ch. onwards.”

What you are saying is this

“the output of the second left inspector on the pull-down menu when you click the down arrow on the instrument track.”

And of course I know this is also a bug.
So the inspector output is buggy.

My native language is not English, so my English translation may not be perfect.
I am not writing this offensively.
I apologize if it is, and I am not trying to be offensive, but it may look that way because of the English translation tool.

If so, I apologize.

Is this understood? What I am saying is fundamentally different.

24

I wouldn’t. As per my previous post - select the return channel you want to see either on the Instrument track or by selecting one of the child tracks (audio return tracks). For me they should be the same, so currently it works as I would expect it.

Selecting this…

grafik
grafik352×376 5.35 KB

…is the same as selecting this:

grafik
grafik537×423 32.5 KB

…is the same as selecting this:

grafik
grafik685×293 20.9 KB

25

Are you mixing up midi channels with audio return channels?
You are aware that I can have a midi track set to midi channel 2 and the instruments return channel to 7? The Channel View would then show me channel 7 when I select the track with midi channel 2.

grafik
grafik694×432 40.9 KB

26

Just to throw a little more oil in the fire… The issues shown in this thread (and I already had rather heated exchanges about them in the past, here) are summing almost exactly the reasons why I still never use an instrument track with a VSTi set as a multiouts sound source : instrument rack all the way → problems solved…

27

Anyway, either you’re the one who can’t talk,
or my English translation tool is wrong.

I found out that we are not on the same page at all.
I know about that.

Please understand
that you are talking about something completely misguided to the issue I am talking about. (Aren’t you the one confusing the return channel with the midi channel?)

If you don’t understand after all that explanation, which of the following is the
cause?

1 Your inability to understand.

2 You don’t want to admit you are wrong, so you are shifting the point

3 Is it my way of telling the story or is it the English translation tool?

4I’m not smart enough to understand your story.

I think it is one of these.
Honestly, if you don’t understand after all that explanation.

Just understand this.

You are totally misguided.
At least it appears that way with the tools I translate.

I’m talking about the problem where if you open the Instrument Track pulldown, select 2ch as the return channel, and then close it, the top left-most Inspector output of the Instrument Track’s 1ch becomes 2ch.

I consider this just an act of trolling as it is completely misguided.
Please do not post in this thread any further.

If you have something completely different to say, it is not a discussion at all.

28

Can someone please help me,
Is this the solution that Jhonny is talking about?

I don’t understand it at all, maybe because I’m not very smart.
Or is my problem badly written?

If anyone has a workaround for this bug, I would really appreciate it if someone could write to me.

29

Apparently you understand …
Really good.

I understand the workaround.

But here’s why I don’t dare do it.

VST
VST1913×1077 195 KB

I often layer presets on top of each other, and if I do that, I can avoid this situation by using multitimbral.

There are various disadvantages to multitimbral output, though.

At the very least, is there any advantage to seeing the same inspector on the 1ch and 2ch of an instrument?

Who would argue that this is an improvement? Who would argue that this is more convenient?

It looks like a bug to me at least.
(Is there any advantage?)

30

Hi @Johnny_Moneto,

Maybe I’m missing something but…

If I add a MIDI Track and route it to the Instrument and set its own Return (HS Out 2), then anytime I select the MIDI Track, I can see its Return in the Channel, so I can manipulate it.

But the source Instrument Track is the problem. If I select the source Instrument Track (the parent), I don’t see the assigned Return in the Channel; I see the last selected one. So, how do you know to which Return goes the signal from these MIDI Parts/data if it’s not shown in the Channel?

I mean… Of course, I know, this is not the real routing. The real routing is done in the Instrument itself. This is just a helper to make the mixing easier for me, so if I select the MIDI Track (MIDI Source), I can see/get the Return immediately. But this is the thing, this use case doesn’t work for the Instrument (parent) Track.

31

Hello Martin,

I have been told I am a troll and that I don’t contribute to this topic. I was also asked not to post here anymore.

32

Hi @Johnny_Moneto,

As you know, sometimes we disagree with each other, but I always respect you :man_bowing: and I find your opinion very valuable. Therefore I will be happy if you could reply in a Private Message. Thank you!

33

I am sorry, but this is outrageous! @Johnny_Moneto is one of the most valued members in this forum and his contributions are based on a deep understanding of this software.

Even if one takes into account that things might have gone lost in translation, you don’t get what he’s pointing at, or you simply disagree: This not the way to thank someone for contributing valuable perspectives to solve YOUR problem.

1 Like
34

I’m sorry!

I am sorry that I went a little too far in saying that you are a troll.

I think that I wrote something completely different from what you meant, and I am sorry for that.

And you said it was an improvement.

Do you see any advantage to it? I asked.

And I would like to say that you did not answer frankly to that.

First of all, I said that Martin is reporting it.

Yet you said this.

You said it was an improvement.

If it’s not a bug, but an improvement, then you could have just said, “Here’s the benefit,” and then
would have said, “Here’s how to work around it.”

If you could write it that way.

I apologize for my overstatement.

I wish you had taken my sentiments into consideration when you wrote.

Oh, am I communicating this well?

35

If possible, could you translate it here:
?
Perhaps it might be better translated here.

36

Did you see the above exchange?

I really apologize for the bad writing, though,

I’m really sorry for the way I wrote it, but it didn’t seem to me like I was offering an opinion on how to solve the problem.

And the fact that you wrote about the reported
being an improvement and not a bug seemed to me like you were trying to pick a fight.

I asked him if there was a benefit to being frank about it.

He didn’t answer frankly and seemed to be writing about something else
, so I got a little heated.

Maybe the English translation tool I use just doesn’t work well.

Would it be possible for you to give me an advantage or workaround to this instead?

I have apologized to the person in question for the excessive writing.

1 Like