Quick Access Utility (QAU) 1.0.2

[efromdc]

Hi there.

A quick question- is this on a completely vanilla install (I.e.- no other plugins?). If not, what plugins are installed? If so, can you remove QAU and run it to get me a log file, so that I can see your system config?

Appreciate the help.
"Vanilla" = 100% fresh out the box / stock install / zero plugins.

Here is the vanilla log file:

16:41:33.248: CPU Name: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz16:41:33.249: C - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

Again, thanks!
Erik / eFromDC

 

[FiniteSingularity]

Appreciate the help.
"Vanilla" = 100% fresh out the box / stock install / zero plugins.

Here is the vanilla log file:

16:41:33.248: CPU Name: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz16:41:33.249: C - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

Again, thanks!
Erik / eFromDC

Thanks for the log.

Its strange, as I am unable to replicate the issue (just did a vanilla 30.1.2 install with only the QAU plugin, and all booted/ran fine). Does the issue persist with older versions of OBS (say 30.1.1?)

 

[efromdc]

Thanks for the log.

Its strange, as I am unable to replicate the issue (just did a vanilla 30.1.2 install with only the QAU plugin, and all booted/ran fine). Does the issue persist with older versions of OBS (say 30.1.1?)

Haven't tried it with any other version.

For the record this is with 30.1.2 portable if that makes a difference....? I avoid installs that write to my registry...

 

[FiniteSingularity]

Haven't tried it with any other version.

For the record this is with 30.1.2 portable if that makes a difference....? I avoid installs that write to my registry...

All of my installs are portable as well, and it seems to be working without issue in a vanilla portable 30.1.3 and 30.1.2 for me. Looking through the crashlog you posted earlier, its not crashing in a spot that I've seen before. I'll look through the code and see if I can figure out what might be causing the crash (though its hard to fix if I can't replicate it).

 

[ShaneS]

I love the idea of this. I am running a Mac mini Intell i7 with OS 10.14 . When I try to install, it says."

DISTRIBUTION_TITLE can’t be installed on this computer."

Any idea? OS too old or something?

 

[FiniteSingularity]

I love the idea of this. I am running a Mac mini Intell i7 with OS 10.14 . When I try to install, it says."

DISTRIBUTION_TITLE can’t be installed on this computer."

Any idea? OS too old or something?

Hi Shane-

It should work fine on 10.14.

Is there anything else in your console logs when you try to install? One issue with the MacOS version of the plugin- I do not yet have a MacOS signing certificate (raising funds right now to purchase an Apple developer subscription so I can do so). You may have to go into your settings and allow the app to be installed (I believe it is in `System Settings --> Privacy and Security --> Security`). Please let me know if that doesn't help, and we can dig into it a bit more.

 

[l1i1l]

Hi, @FiniteSingularity .

I noticed one problem: if the transition between scenes is launched via the "Advanced Scene Switcher" plugin macro, the Manual window of your plugin does not display the result of switching to a new scene (the previous scene remains highlighted).

 

[FiniteSingularity]

Hi, @FiniteSingularity .

I noticed one problem: if the transition between scenes is launched via the "Advanced Scene Switcher" plugin macro, the Manual window of your plugin does not display the result of switching to a new scene (the previous scene remains highlighted).

I'll definitely look into this. It is a little tricky, to keep the UI consistent, as changing the active/highlighted scene in a manual dock, only makes sense if the "click through to scene" option is enabled.

 

[l1i1l]

I'll definitely look into this. It is a little tricky, to keep the UI consistent, as changing the active/highlighted scene in a manual dock, only makes sense if the "click through to scene" option is enabled.

I don't know how the OBS is structured, but it's obvious that information about which scene is active should be obtained from the OBS own data (based on which scene is actually displayed in the Program window). This will solve all potential problems, because the logic of the OBS using plugins implies that switching between scenes can be done without using the OBS own tools — by means of any other plugins (not only Advanced Scene Switcher plugin).

 

[FiniteSingularity]

I don't know how the OBS is structured, but it's obvious that information about which scene is active should be obtained from the OBS own data (based on which scene is actually displayed in the Program window). This will solve all potential problems, because the logic of the OBS using plugins implies that switching between scenes can be done without using the OBS own tools — by means of any other plugins (not only Advanced Scene Switcher plugin).

Correct- programmatically, its quite easy to do/keep updated. The issue is making a consistent/non confusing interface. UIs tend to become less usable overall, when things are not consistent. In this case, there are two different scenarios:

1. A manual dock that is not being used to switch scenes. Clicking on the items in the dock is only done to pull up the context menu options, or use the buttons on the right side. In this case it would not make sense to switch the active item to the active scene.
2. A manual dock with the "clicking switches scenes," option enabled. Now when we click on a scene we are switching the active output, and it might make sense to switch the active item.

But to further complicate things, the manual dock can (and often does) contain non-scene items. So what if I am currently working on changing parameters on my face cam source which I have in my dock, seeing how those changes affect its rendering in various scenes. If we have the manual dock switch its active item, every time I change a scene, it is going to de-select the source I want to be editing (the face cam in the manual dock). This can make things quite confusing/frustrating.

That is not to say changing the focus is a bad idea. I just need to think a bit about how it would work, while keeping things consistent.

 

[l1i1l]

Correct- programmatically, its quite easy to do/keep updated. The issue is making a consistent/non confusing interface. UIs tend to become less usable overall, when things are not consistent. In this case, there are two different scenarios:

1. A manual dock that is not being used to switch scenes. Clicking on the items in the dock is only done to pull up the context menu options, or use the buttons on the right side. In this case it would not make sense to switch the active item to the active scene.
2. A manual dock with the "clicking switches scenes," option enabled. Now when we click on a scene we are switching the active output, and it might make sense to switch the active item.

But to further complicate things, the manual dock can (and often does) contain non-scene items. So what if I am currently working on changing parameters on my face cam source which I have in my dock, seeing how those changes affect its rendering in various scenes. If we have the manual dock switch its active item, every time I change a scene, it is going to de-select the source I want to be editing (the face cam in the manual dock). This can make things quite confusing/frustrating.

That is not to say changing the focus is a bad idea. I just need to think a bit about how it would work, while keeping things consistent.

Of course, you are a specialist creating a wonderful product, and I will not even try to give technical advice due to my complete lack of competence in this matter regarding the OBS. I am simply reasoning from the point of view of an end user (who has been developing advanced use cases for various software products for a quarter of a century). And you must admit, from the end user's point of view, the situation when the focus (highlighting) in the dock sometimes switches, and sometimes does not, is no less confusing and frustrating.

Complex, advanced scenarios for using the OBS inevitably involve creating dozens of scenes, most of which are never independently output for broadcast or recording, but are only auxiliary for constructing the final ("on-air") scenes. And for me personally, your plugin has made it possible to use the Manual dock to collect together only the final scenes used for output, which allows you to separate them from all the other scenes. This avoids possible confusion and clutter in the "on-air" dock.

Perhaps the solution would be to create two versions of the Manual dock — one for the purposes you described, and the second — for use as a full-fledged "on-air" (as I described).

In any case, I am sure that you will be able to find the most optimal solution to the problem (to the delight of all users). I wish you inspiration!

 

[l1i1l]

Sorry, but I allowed myself again to think a little more as an end-user ))

The presence of a simple checkbox in the Manual dock settings seems to be the simplest option — like "Switch only through click" (it can be left enabled by default for compatibility with the current logic of using the dock). This will eliminate any confusion and the appearance of unnecessary versions of the dock, and will allow you to use manual docks in the desired mode at any time.

Perhaps, in technical terms, this is also not difficult to implement.
I'm simply expressing an idea.

 

[TMBGeeks]

Feature Suggestions

#1: On Source Search, have the ability to add "quick search" terms that you often search for. Like buttons above or below the search bar to keep you from having to type them each time.

#2: On Dynamic docks, have the option to reverse the sort order and also sort alphabetically. A-Z and Z-A but also Hierarchy Bottom-Top (the current order) and Hierarchy Top-Bottom, I can see uses for all 4.

#3: Filter out what shows in search results (i.e. - Effect Filters, Sources, and even by Source Type). Having the ability to make separate docks dedicated to searching one or some could be useful.


And just wanted to let others know about and compliment a cool feature already implemented. Not only is the ability to search effects filters great, but I added a "Move" filter to a source and then renamed the filter to "Test" and when I searched for "Move", that source still showed up. So cool.

 

[FiniteSingularity]

Feature Suggestions

#1: On Source Search, have the ability to add "quick search" terms that you often search for. Like buttons above or below the search bar to keep you from having to type them each time.

#2: On Dynamic docks, have the option to reverse the sort order and also sort alphabetically. A-Z and Z-A but also Hierarchy Bottom-Top (the current order) and Hierarchy Top-Bottom, I can see uses for all 4.

#3: Filter out what shows in search results (i.e. - Effect Filters, Sources, and even by Source Type). Having the ability to make separate docks dedicated to searching one or some could be useful.


And just wanted to let others know about and compliment a cool feature already implemented. Not only is the ability to search effects filters great, but I added a "Move" filter to a source and then renamed the filter to "Test" and when I searched for "Move", that source still showed up. So cool.

Thank you! Those are great ideas! Would you be able to add them as a feature request on the project’s GitHub? If you go to the GitHub page (link in the plugin description) click “issues” then open a new issue for each feature and select the Feature Request for the issue type. I’d really appreciate it as it lets me track the requested features and their progress in the code.