[Bug]: Unable to Use On Intel Mac

[mtdvlpr]

Hi Brothers,

I really like the look and feel of the new interface. I do have some observations, and maybe a bug. Including screenshots to help:

1. On launch, there is an immediate error that nothing could be retrieved for the meeting dates:
   

These issues have been fixed already

3. When I imported the files I had gotten from another Mac, the results don’t stick to the numbering system which used to put them in the correct order. (See screenshots of how it looks before download and after download) 

4. This is how they download from DropBox folder (Notice not in correct order, even ignoring the numbering system):
   

After manual change to ordering of files:

5. Notice too that there isn’t a heading for the WT study on this view. But that might be because it didn’t automatically download anything.

6. Also, when I try to move the songs into the correct order, they can’t be dragged to the top of the screen, and then the screen automatically scroll to the place I want to inset it. It takes several moves to get the media to where it needs to land.

7. Is there a list of keyboard shortcuts that would allow moving to the next piece of media rather than manually selecting it?

8. Also, noticed that you can only have the small window or full screen rather than being able to set the screen to the size the user might need. Probably necessary when doing a hybrid ZOOM meeting.

I wasn’t able to make this version download any media for any future meeting, and that includes this Sunday and next Tuesday. Not seeing any interface that would allow manual selection of a date for media. If you use the calendar, it will return this:

We won’t have any need for VLC with this new version. Just need a little tweaking possibly? I appreciate all your great work on this wonderful tool!

Thanks,
Mark Cillis
@.***

On Oct 17, 2024, at 10:02 AM, Manoah Tervoort @.***> wrote:

Note that the congregation sync feature is not present in the upcoming big release (v24.10.x) and up.

—
Reply to this email directly, view it on GitHub #2709 (reply in thread), or unsubscribe https://github.com/notifications/unsubscribe-auth/A6S45XGLTO2VJ6QZMMFB7OLZ37NQNAVCNFSM6AAAAABP2NVXXCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJXGM3DMNY.
You are receiving this because you were mentioned.

Originally posted by @skimark1 in #2709 (comment)

[alanfermtz]

The first screenshot happens to me if I finished my setup, then go clear cache, and return to multimedia page

[mtdvlpr]

@skimark1, you can still download the previous version and in the settings disable automatic updates. Once the problem has been solved, we'll notify you and you can safely upgrade again.

[sircharlo]

Is this an Intel Mac?

[skimark1]

YesThanks,MarkSent from my iPhone 15 Pro MaxOn Oct 21, 2024, at 4:54 PM, Charles Olivier Savignac ***@***.***> wrote: Is this an Intel Mac? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[skimark1]

I've got a 2023 MacBook Air M2 series, and M3 works fine on it. Must be an Intel thing?

[sircharlo]

Ok, thank you. I'll see how to force a recompilation for Intel Macs of the module that's breaking.

[skimark1]

Really appreciate your hard work on this! Saves a lot of time for all the brothers. Thanks, Mark Cillis ***@***.***

…

On Oct 21, 2024, at 7:48 PM, Charles Olivier Savignac ***@***.***> wrote: Ok, thank you. I'll see how to force a recompilation for Intel Macs of the module that's breaking. — Reply to this email directly, view it on GitHub <#2773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6S45XFC6QT4CCNRZ3IAA2LZ4WVGDAVCNFSM6AAAAABQFNULYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYGA2DINRVG4>. You are receiving this because you were mentioned.

[sircharlo]

If only it can work on Intel Macs now :)

[Jiang-TJ]

Hope a solution to this intel mac problem can be found. Thanks friends for your hard work, it really means a lot!

[mtdvlpr]

I found a post that might be related:

WiseLibs/better-sqlite3#126 (comment)

[mtdvlpr]

Hi @skimark1, could you try the below version for me?

https://we.tl/t-sAEBOeDUiw

[mtdvlpr]

@skimark1, I also have another one that might give less security issues:

https://we.tl/t-hV16x8Wa8r

[skimark1]

That works!!! Thanks, Mark Cillis ***@***.***

…

On Nov 4, 2024, at 8:13 AM, Manoah Tervoort ***@***.***> wrote: @skimark1 <https://github.com/skimark1>, I also have another one that might give less security issues: https://we.tl/t-hV16x8Wa8r — Reply to this email directly, view it on GitHub <#2773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6S45XFJRRMLA6QRKD6OFNLZ66FJPAVCNFSM6AAAAABQFNULYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUHE3TMNBUGM>. You are receiving this because you were mentioned.

[sircharlo]

That works!!! Thanks, Mark Cillis

Just to be clear, you mean that the app fully works as expected on an Intel Mac?

[mtdvlpr]

@skimark1, I also have another one that might give less security issues:

https://we.tl/t-hV16x8Wa8r

This one is built from https://github.com/sircharlo/meeting-media-manager/tree/fix/macos-intel

[mtdvlpr]

@skimark1, does everything work as expected now? Or did it only solve the security warning?

[skimark1]

That one still has the security warning. Thanks, Mark Cillis ***@***.***

…

On Nov 4, 2024, at 8:30 AM, Manoah Tervoort ***@***.***> wrote: @skimark1 <https://github.com/skimark1>, does everything work as expected now? Or did it only solve the security warning? — Reply to this email directly, view it on GitHub <#2773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6S45XHKH6X3HGLUGTZLPSLZ66HLHAVCNFSM6AAAAABQFNULYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVGAZDANRWGU>. You are receiving this because you were mentioned.

[sircharlo]

That one still has the security warning. Thanks, Mark Cillis

But does the app run as it should?

[skimark1]

Everything works as expected, just get the security challenge to be able to open it the first time. Thanks, Mark Cillis ***@***.***

…

On Nov 4, 2024, at 8:51 AM, Charles Olivier Savignac ***@***.***> wrote: That one still has the security warning. Thanks, Mark Cillis But does the app run as it should? — Reply to this email directly, view it on GitHub <#2773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6S45XFMIETPMQXRZLNXTWDZ66CXDAVCNFSM6AAAAABQFNULYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVGA3TEMJVGA>. You are receiving this because you were mentioned.

[mtdvlpr]

@skimark1, thank you for helping us pinpoint the problem and resolve it!

[sircharlo]

Everything works as expected, just get the security challenge to be able to open it the first time.

This is great news!!

[sircharlo]

Thanks for your hard work @mtdvlpr !!

[mtdvlpr]

Important

You might have to install the new version manually instead of automatically, due to a bug that's been fixed for upcoming releases.

[skimark1]

One thing I noticed is that if you click the red ball button, it doesn’t quit M3. Instead it is left running and I don’t see a way to bring the window back without actually quitting the app and relaunching. Might be confusing for some? Love the progress made! Thanks, Mark Cillis ***@***.***

…

On Nov 6, 2024, at 8:16 AM, Manoah Tervoort ***@***.***> wrote: Important You might have to install the new version manually instead of automatically, due to a bug that's been fixed for upcoming releases. — Reply to this email directly, view it on GitHub <#2773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6S45XDMN7WDE5LCAPGVBLTZ7IXFDAVCNFSM6AAAAABQFNULYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQGAZTMNRQHE>. You are receiving this because you were mentioned.

[mtdvlpr]

@skimark1, correct me if I'm wrong, but the default behaviour for macos is to keep the app running even if all windows are closed. You can activate thr app again by simply clicking the M3 icon once more. This should create another window again.

[sircharlo]

One thing I noticed is that if you click the red ball button, it doesn’t quit M3. Instead it is left running and I don’t see a way to bring the window back without actually quitting the app and relaunching. Might be confusing for some? Love the progress made! Thanks, Mark Cillis @.***

@mtdvlpr This is why i had removed the macOS check here:

meeting-media-manager/src-electron/electron-main.ts

Line 32 in dbef70a

if (PLATFORM !== 'darwin') app.quit();

Do you think we should either revert to quit when windows are closed, or to recreate the main window on activate?

[skimark1]

That is the expected behavior, but when you click the open app icon, nothing happens. Have to manually quit the app, either with right click on icon in dock or by selecting quit from the menu bar. Then when you relaunch M3 things go back to normal? I wondered too, if it is possible to customize the Yeartext window with a custom background? Thanks, Mark Cillis ***@***.***

…

On Nov 6, 2024, at 10:24 AM, Manoah Tervoort ***@***.***> wrote: @skimark1 <https://github.com/skimark1>, correct me if I'm wrong, but the default behaviour for macos is to keep the app running even if all windows are closed. You can activate thr app again by simply clicking the M3 icon once more. This should create another window again. — Reply to this email directly, view it on GitHub <#2773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6S45XCDQDJB5RE2NHG5UKLZ7JGGFAVCNFSM6AAAAABQFNULYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQGM3DONZQGI>. You are receiving this because you were mentioned.

[mtdvlpr]

@skimark1, I gound the bug and fixed it.

@sircharlo, I think it's better to stick with the system default behaviour. That's (I assume) what macos users are accustomed to. But if our macos users prefer actually closing m3 when the windows are closed, then let's do that.

[sircharlo]

If you found the bug I'm happy to leave the behavior as is.

[skimark1]

I think the behavior is fine, just the fact that closing the window doesn't let you reopen it by clicking on M3. That needs fixing, and if understand correctly you might have found the bug?Thanks,MarkSent from my iPhone 15 Pro MaxOn Nov 6, 2024, at 10:50 AM, Charles Olivier Savignac ***@***.***> wrote: If you found the bug I'm happy to leave the behavior as is. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[mtdvlpr]

@skimark1, yes. The bug has been fixed and will be in the next release.

[skimark1]

Excellent! Is the Yeartext screen customizable for background color? We have used a custom background that matches our decor for as long as we’ve displaying media and, although not an absolute necessity, some may ask about if if we can no longer display it. Thanks, Mark Cillis ***@***.***

…

On Nov 6, 2024, at 10:57 AM, Manoah Tervoort ***@***.***> wrote: @skimark1 <https://github.com/skimark1>, yes. The bug has been fixed and will be in the next release. — Reply to this email directly, view it on GitHub <#2773 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6S45XC625PIDZXIDA4MRB3Z7JKBBAVCNFSM6AAAAABQFNULYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQGQZTEMRQGQ>. You are receiving this because you were mentioned.

[mtdvlpr]

@skimark1, the yeartext screen can have a custom background image, but it is not persistent anymore, so every time you restart M3, the background is reset to the yeartext. This is intended behavior, because the guidelines specify the yeartext should be shown during regular meetings (unless it's a special occasion like the memorial). Days like the memorial is why the custom background feature exists.

[sircharlo]

@skimark1 To add to @mtdvlpr's excellent answer, we simply try to replicate known behaviors as much as possible and not deviate from what one would normally expect to see. There's much to be said for a consistent look, no matter which meeting one attends, anywhere in the world!