Replies: 3 comments 3 replies
-
|
If you open the log (⌘⇧L while the Bunch menu is open), is there any
error shown when opening the Bunch as it tries to set the volume? Some
audio devices do not provide a volume property. I would be curious if
mute/unmute worked in the same place.
…-Brett
On 4 Nov 2022, at 10:58, xstrex wrote:
Just getting started with a bunch for work, launching all my apps,
using moom to arrange them. I've got audio muting and screensaver
activation working when exiting the bunch, but for whatever reason
setting audio output when launching the bunch does nothing.
Here's the bunch
```yaml
---
title: Work Default
sequence: sequential
---
@@
# System
# Start
(audio output volume 60)
# End
!!(audio output mute)
!!(sleep screensaver)
# Desktop 1
# ***@***.***}
Microsoft Outlook
%KeePassXC
Microsoft Teams ~5
Slack ~5
(pause 10)
* tell application "Moom" to arrange windows according to snapshot
"Work1" ~20
# Desktop 2
# ***@***.***}
%Obsidian
Sublime Text
iTerm
%Firefox
* tell application "Moom" to arrange windows according to snapshot
"Work2" ~10
```
--
Reply to this email directly or view it on GitHub:
#268
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Just made a new bunch (below) and opened/closed it. The audio output volume never changes, yet the audio output does mute (when closing). The log shows nothing relevant, or related to audio or the system. ---
title: testing
sequence: sequential
---
(audio output volume 60)
!!(audio output mute) |
Beta Was this translation helpful? Give feedback.
-
|
Do you get a more relevant message if you set log level to debug (under help menu)?
- Brett
…On Nov 4, 2022 at 3:25 PM -0500, xstrex ***@***.***>, wrote:
Just made a new bunch (below) and opened/closed it. The audio output volume never changes, yet the audio output does mute (when closing). The log shows nothing relevant, or related to audio or the system.
---
title: testing
sequence: sequential
---
(audio output volume 60)
!!(audio output mute)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
In debug I see the following lots (personal info redacted) With debug enabled, when I ran the bunch audio level did not change to 60, but audio was muted when exiting. |
Beta Was this translation helpful? Give feedback.
-
|
Well, that indicates it at least _thinks_ it can set the volume on your
device. I have at least one audio device that can handle the mute/unmute
but doesn't respond to volume changes, but it lets me know that that
property isn't accessible in the log. I'm not certain what could be
going on with yours.
Bunch uses some deprecated private APIs to do its audio device
interactions, so those are likely to break with time and I'll need to
find an updated method. In the meantime, if you can figure out how to do
what you want with AppleScript, you should be able to just send
AppleScript commands using `*` lines to affect things like output device
and volume, especially if you're not switching audio devices, e.g.
* set volume output volume 60
https://coolaj86.com/articles/how-to-control-os-x-system-volume-with-applescript/
…-Brett
On 4 Nov 2022, at 17:05, xstrex wrote:
In debug I see the following lots (personal info redacted)
```
2022-11-04 15:59:25: ⚪Launched
==========================================
2022-11-04 15:59:25: 🔘Observing
file:///Users/xxxxxxxxx/Documents/Bunches/ for changes
2022-11-04 15:59:25: 🔘Generating status menu
2022-11-04 15:59:36: ⚪[test] Open >>>>>>>>>>>>>>>>>>>>>
2022-11-04 15:59:36: ⚪[test] Processing command "audio output volume
60"
2022-11-04 15:59:36: ⚪[test] Set volume for output device to
0.600000
2022-11-04 15:59:36: 🔘Generating status menu
2022-11-04 16:00:19: ⚪[test] Closing <<<<<<<<<<<<<<<<<<
2022-11-04 16:00:19: ⚪[test] Processing command "audio output mute"
2022-11-04 16:00:19: ⚪[test] muting output
2022-11-04 16:00:19: 🔘Generating status menu
2022-11-04 16:00:28: ⚪[test] Open >>>>>>>>>>>>>>>>>>>>>
2022-11-04 16:00:28: ⚪[test] Processing command "audio output volume
60"
2022-11-04 16:00:28: ⚪[test] Set volume for output device to
0.600000
2022-11-04 16:00:28: 🔘Generating status menu
2022-11-04 16:00:42: ⚪[test] Closing <<<<<<<<<<<<<<<<<<
2022-11-04 16:00:42: ⚪[test] Processing command "audio output mute"
2022-11-04 16:00:42: ⚪[test] muting output
2022-11-04 16:00:42: 🔘Generating status menu
2022-11-04 16:01:01: 🟡Debug Level set to 2. Restart required to
enable.
```
With debug enabled, when I ran the bunch audio level did not change to
60, but audio was muted when exiting.
--
Reply to this email directly or view it on GitHub:
#268 (reply in thread)
You are receiving this because you commented.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Hey, thanks, just tested the applescript method, and it did in fact work as you'd expect! Thank you! |
Beta Was this translation helpful? Give feedback.
Answer selected by
xstrex
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Just getting started with a bunch for work, launching all my apps, using moom to arrange them. I've got audio muting and screensaver activation working when exiting the bunch, but for whatever reason setting audio output when launching the bunch does nothing. I believe I'm calling it right, just not sure why it's not firing; any ideas?
Here's the bunch
Beta Was this translation helpful? Give feedback.
All reactions