Load gig File as it was saved: Setlist View et al

And that change you believe is just a couple lines of code?
Do you know the code?
As a developer you know for sure that jus adding some lines of code without deep thinking about the consequences can end in disaster,

Oops! Sorry, you’re right! It’ll be a well known feature by v6! :joy:

Yes, every line of code needs deep thought about the consequences! I didn’t mention the design meetings, documentation and test time for those lines of code! Are you involved in the development of GP? Of course, I don’t work for Deskew so I haven’t seen the code. It seems well enough designed to be able to take enhancements without breaking unrelated stuff, but of course I can’t know that for sure.

No doubt. Something like the Setlist MIDI config (ability to use e.g. CC msgs to control other parts of GP) and putting that into other MIDI config areas…now that really is a major change that would effect many components, and would have a lot of bw compat issues to contend with… the Setlist MIDI config is really good…would be fantastic to see it wherever MIDI config is involved. :+1:

…thinking…we could modify this…

…with a drop down box like this…
…and then we could select this…

Shouldn’t take more than a couple of lines of code…

Oh wait … we did this already!

1 Like

In that case, an inexpensive UPS might be worth the investment!

Does it see it at the same port?

How do you know GP doesn’t see it?

Did you have the Global MIDI Monitor open?

What does that mean?

What same mechanism?

Hi, Yes pianopaul pointed me to that. So that’s good.
It’s a little different than what I was mentioning - i.e. A gig file is saved. it looks and feels exactly as it should be for the gig. But wait, when I load it isn’t.
The Initial View is one way to get the view functionality, just a bit less intuitive and I guess is global to GP (doesn’t follow the loaded gig file), but that’s ok, there’s plenty of things to like about GP!

I’m referring to the way Setlist configures/handles MIDI for ctonrolling the Setlist view/parts etc. It can take CCs, Note, pretty much any MIDI message and use it to change things like song part variations and send custom msgs out to external gear…fantastic! (might not have the nomenclature right, but hopefully you know the bit I’m taking about).
This is a truly brilliant part of the product. It’s so good, it’s way more useful than just for Setlists (although yes, great for that too!).
So I use ‘Setlist View’ to control ‘Rackspace Variations’ - not really anything to do with setlists, as my show is live. So would be cool to use the same idea in other places (for example the MIDI section in the Rackspace editor - more than one line of code for this one! :slight_smile:
Hopefully that clarifies what mean?

Sorry - still no idea — what exactly do you want to be able to do? Perhaps an explicit example? There’s nothing special about setlist view and CC messages - you can assign any message you want to select a particular song part.

Hi, yes I’ve used the Global Monitor, which is pretty useful for checking/testing MIDI.
The DAW-like thing of saving current MIDI config would be really cool, but isn’t a trivial feature to add.
Windows does create all kinds of USB headaches, but for example, I (virtually) never have MIDI connectivity errors with my DAW (unless of course something is actually disconnected :joy: !)
But for whatever reason, I almost always get at least one not connecting at GP startup, and some devices connect, some do sometimes, the combination can tend to change with every load. Sometimes, they all work and no problem. On gig night, it’s the not knowing that is the problem. I’ve got 5 MIDI devices that I connect on stage, so not that many.

If this kind of issue is a ‘new’ thing for GP - i.e. others aren’t seeing this, it could be that one of my MIDI devices isn’t playing ball and causing an issue (some MIDI vendors don’t have USB experts :grimacing:), so I will try a stress test with different combinations.

Thank you for taking an interest! :+1:

I thought choosing “last viewed” would have the gigfile open exactly as it was closed. Mine always do, but I’ve got so much stuff in mine I’m not exactly sure if there’s something else causing that.

If you want to set up a gigfile so it always opens in Setlist View or Rackspace view depending on what you last saved you should be able to do that by saving a button widget in the Global Rackspace and assigning it to “System Actions → TogglePanelSetlistView”. It will then toggle on or off according to whether you’re in Setlist mode, and should return you to whatever mode you were in when last saved. (I haven’t tested this, but I think it should work.)

Regarding your MIDI issues, I think you might be suffering from the problem that every time you plug any USB device into a different USB port Windows considers it to be a different device.

In GP you can click “Options → MIDI Ports” and see the list of available ports. GP does remember what you choose there.

If the MIDI from something that is connected isn’t getting to GP then it may be because that device doesn’t have a multi-client MIDI driver and some other program grabbed it first. When that happens there’s not much GP can do about it until whatever other program grabbed it releases it.

There’s nothing special about setlist view and CC messages - you can assign any message you want to select a particular song part.

Yes, that’s it! I think there is a lot that is special about Setlist View - because you can assign any message you want to do all manner of things (DAWs really struggle with this, so GP having it, especially for live is fantastic).

The salient point here is you can’t do that in other parts of GP - it’s limited mostly to PC msgs only.
I think this is good example, but still relatively new to GP…
I believe to control Rackspace Variations from the Rackspace View (i.e. not from Setlist View) you have to use PC msgs. PC msgs these days are problematic as many controllers are setup for note and CC. Also you can get PC changes in places you don’t actually want them! (and an be a pain to disable and will that hurt something else etc etc)

This is why I mentioned it as an RFE - it is far from trivial to port the Setlist View’s ‘any-MIDI-message-to-any-command’ thing to other parts of GP without serious thought, design consideration and testing.

Thanks for your response.
It does look like there’s a few ways to get Setlist View to come up at start and your suggestions sound good. ‘last viewed’ is really good, as it would then presumably follow the gig file that was loaded (rather than a global setting). So I’ll try that, thanks.
Yes USB devices and MIDI on Windows is, umm, let’s just say, very ‘Microsofty’ :joy: !
I do have a MIDI controller who definitely doesn’t have a multi-client driver! (the others do) I make sure its config utility is not running as given the chance, it will connect to it and, as you rightly say, takes control of it and won’t share it with anyone.
Those things aside, I just don’t get MIDI issues when starting Studio One. Having written device drivers for Windows over the years, I know all too well the minefield, particularly with Windows USB.

The only thing that is currently limited to PC messages is selection of variations.

But you can just create a GigScript that would convert incoming CC messages with a certain number (say) to PC messages to which variations would respond.

Some examples are in this article: [blog] The most flexible MIDI processing

1 Like

Thanks for the tip…I’ll search up an article on the scripting for MIDI msg xlate.
I do like the scripting feature, great for customization.
Thanks! :slight_smile:

Great! Thank you for sharing this - very useful!
Great GP community - you ask a question, and lots of useful answers are forthcoming…! :+1:

Here’s a trivial example where incoming notes are being converted into CC messages where the CC number is the Note Number and the CC value is the Note Velocity