ENTERPRISE // Buttons get De-Coupled When Sharing via Private Marketplace
System Information
SoundFlow 4.1.10
OS: darwin 19.6.0
ProductName: Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H512
Steps to Reproduce
- Create a Surface
- Distribute via Private Marketplace
- Download and evaluate on other workstations
Expected Result
Surface should function exactly the same on each workstation
Actual Result
Buttons randomly become decoupled, are different for each workstation
Workaround
N/A
Other Notes
This is complete killer for the app, makes Enterprise plan completely worthless and unusable. We've brought this up many times, have tested many times, we need this fixed immediately..
Links
User UID: qocpwEcEL4UVPS7SLjFvSZGr0MN2
Feedback Key: sffeedback:qocpwEcEL4UVPS7SLjFvSZGr0MN2:-MV300dvJFAEOEWMk4bl
- JJoe Trapanese @Joe_Trapanese
To clarify - All buttons work on the workstation the Surface was built on, but different buttons fail on each workstation that downloads the Package. Failures appear random.
Kitch Membery @Kitch2021-03-05 20:42:26.182ZHi @Joe_Trapanese ,
I'm sorry to see you are experiencing this issue.
From what you describe you are seeing it seems as though the issue may be that there are other external package commands that are being used in the package that is being shared.
Any external packages whos commands have been used in the shared package need to be installed on each workstation for the commands to be triggered.
Let me know if this makes sense, or if you do infact have all the required packages installed on each workstation.
- JJoseph Trapanese @Joseph_Trapanese
Hey Kitch,
Derek here. Previous to this package I published for the team a few days ago, I believe what you described had been part of the problem. In this most recent version, however, I made sure that the package containing the surface also contained all the commands that were referenced within it (aside from a few commands that are part of the system commands that Soundflow comes with, but these were not causing problems anyway, luckily). We've experienced buttons not working and not throwing any error logs on one workstation after being installed, but the same buttons worked on a different workstation after being installed, so it still remains puzzling as to what how this is happening.
- Kitch Membery @Kitch2021-03-06 03:11:23.953Z
Hi Derek
That does seem strange. I will have @chrscheuer take a look at the log to see if he can pinpoint what is happening.
I assume all the devices are on the latest version of the SoundFlow app, and that the computers are all on the latest version of SoundFlow (4.2.2)?
Also if you can provide more information listing the commands that have been decoupled and the ones that are not throwing errors, that would be very helpful.
Christian Scheuer @chrscheuer2021-03-06 14:46:17.462ZHi Derek,
Please let us know:
- which account the package in question was shared from
- what is the name of the package
- what is the name of the surface
- which account did you install the surface on
- which button could we test with to see the issue
I know you mentioned having general problems, but it helps a lot in testing if we can start with a single instance/example of something not working, so we know where to look.
- Christian Scheuer @chrscheuer2021-03-06 15:04:24.080Z2021-03-06 18:42:55.511Z
From what I can see, the account studio@joec....com (Derek's) has produced a package called "BB SOUNDFLOW MAIN PACKAGE" with a surface called "BB MASTER v4.2".
This has been installed into the account "joe@joec....com" (Joe's, I suppose).
When I test a number of buttons on that surface in Joe's account, that installed surface works completely fine.However, I can also see that you appear to still be using the "bug" where you can accidentally duplicate a surface in-place, and that you've then moved that duplicate to a local package in Joe's account called "JT EDITS".
As we've mentioned, this currently isn't supported, and any surface being moved with that currently unsupported mechanism, will not work or may only randomly work.We've already lined out in several emails and in Kitch's phone call with you the solution to this:
- We need to add a new feature called "Make Editable Copy" for surfaces, which will support the moving of a surface from a package to another package.
- The bug where Cmd+D is currently accepted should be fixed.
Until we've implemented these new features and the bug fix, you shouldn't utilize the Cmd+D bug to move surfaces around to other package, as it will cause random errors as the ones you may be seeing.
- Christian Scheuer @chrscheuer2021-03-07 18:49:26.910Z
We will be beta testing a preview release that implements the two fixes I mentioned above in the coming week.
If they pass our beta testing, they'll be part of the upcoming 4.2.3 release.
We'll let you know once we know more.- JJoseph Trapanese @Joseph_Trapanese
Christian, thank you for your quick reply! Feel free to close this bug, as we spent some time this weekend working on it and it appears to have all been a problem with Keyboard Maestro and not Soundflow! Apologies for the wasted time and energy. Thank you so much for your help, and we look forward to chatting soon about the new v4.2! best, Joe
- Christian Scheuer @chrscheuer2021-03-09 14:55:36.821Z
All good :)
Since the report still addresses the issue of moving surfaces out of their packages in an unsupported way, I just wanted to follow up on my comments above:
I can confirm that our beta test of the upcoming 4.2.3 release is going well, so you can expect these two fixes to be part of it when it comes out later this week:- We need to add a new feature called "Make Editable Copy" for surfaces, which will support the moving of a surface from a package to another package.
- The bug where Cmd+D is currently accepted should be fixed.
- Christian Scheuer @chrscheuer2021-03-09 19:40:58.740Z
4.2.3 is now going through our last testing phase with the following release notes.
We expect this to be out by the end of the week.
- Christian Scheuer @chrscheuer2021-03-10 16:28:01.647Z
4.2.3 with the above mentioned fixes is now out for manual download:
https://soundflow.org/cp/downloadsPlease be aware that when you upgrade to 4.2.x from 4.1.x, you'll need to make sure your iOS and Android devices are also running 4.2.
IMPORTANT: We will be turning on the auto-update from 4.1 to 4.2 sometime in the coming week or so, so now is a good time to make the switch.