Friture does not open on MacOS Big Sur #154
Comments
|
i have the same issue |
|
Running the latest and greatest from sources give me this error: |
|
|
please let me know what else i can share to fix this. i like the app, but it's completely broken now on Big Sur |
|
Friture would actually work if built from source on Big Sur, but that was before the 11.1 upgrade. Now I get the same error when launching Friture from within the virtualenv |
|
Can you please share the steps to build from source ?
… On Dec 31, 2020, at 07:01, enryfox ***@***.***> wrote:
Friture would actually work if built from source on Big Sur, but that was before the 11.1 upgrade. Now I get the same error when launching Friture from within the virtualenv
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
You need to install homebrew https://brew.sh/index; following procedure is then the friture linux installation guide modified for macos (not fully tested, I just edited the procedure by memory) 1 Install git brew install git 2 Install python 3.9 brew install python@3.9 3 Clone the repository git clone https://github.com/tlecomte/friture.git 4 Update pip, setuptools and virtualenv python3 -m pip install --upgrade pip 5 Create a virtualenv and activate it virtualenv -p /usr/local/bin/python3 buildenv 6 Install Friture requirements (PyQt5, etc.) pip3 install -r requirements.txt 7 Build Cython extensions python3 setup.py build_ext --inplace 8 Run Friture python3 main.py |
|
i will try that, i was using python3.8 ... i should 3.9
thank you
…On Thu, Dec 31, 2020 at 10:51 AM enryfox ***@***.***> wrote:
You need to install homebrew https://brew.sh/index; following procedure
is then the friture linux installation guide modified for macos (not fully
tested, I just edited the procedure by memory)
1 Install git
brew install git
2 Install python 3.9
brew install ***@***.***
3 Clone the repository
git clone https://github.com/tlecomte/friture.git
cd friture
4 Update pip, setuptools and virtualenv
python3 -m pip install --upgrade pip
pip3 install --upgrade setuptools
pip3 install --upgrade virtualenv
5 Create a virtualenv and activate it
virtualenv -p /usr/local/bin/python3 buildenv
source ./buildenv/bin/activate
6 Install Friture requirements (PyQt5, etc.)
pip3 install -r requirements.txt
7 Build Cython extensions
python3 setup.py build_ext --inplace
8 Run Friture
python3 main.py
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAIKGM4VNZPBRSLN474HVDSXTB3PANCNFSM4U4YTKNQ>
.
--
Best Regards,
H
|
|
Python 3.8 has the same pyOpenGL problem as the official friture build. It is fixed in python 3.9, but anyway friture crashes with an error after the boot screen. |
|
Dear all, Sorry for this issue. I don't have access to any Mac myself, and that does not make it to fix such errors. I've just released Friture 0.42 (https://github.com/tlecomte/friture/releases/tag/v0.42), could you confirm that this version has the same problem ? (I guess it has the same problem since you tried building from source already) It looks like some of you have succeeded building with Python 3.9 and that solved the problem ? |
|
just tried, same error with the `Friture 0.42`
Can you share some instructions of how to package the mac version? i can
try to work on that a bit to help you
…On Fri, Jan 8, 2021 at 2:07 PM Timothée Lecomte ***@***.***> wrote:
Dear all,
Sorry for this issue. I don't have access to any Mac myself, and that does
not make it to fix such errors.
I've just released Friture 0.42 (
https://github.com/tlecomte/friture/releases/tag/v0.42), could you
confirm that this version has the same problem ? (I guess it has the same
problem since you tried building from source already)
It looks like some of you have succeeded building with Python 3.9 and that
solved the problem ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAIKGKLOYHQWQC4ITAFKDLSY5637ANCNFSM4U4YTKNQ>
.
--
Best Regards,
H
|
|
trying `brew install python@3.9` now
…On Fri, Jan 8, 2021 at 2:21 PM HGrosman ***@***.***> wrote:
just tried, same error with the `Friture 0.42`
Can you share some instructions of how to package the mac version? i can
try to work on that a bit to help you
On Fri, Jan 8, 2021 at 2:07 PM Timothée Lecomte ***@***.***>
wrote:
> Dear all,
>
> Sorry for this issue. I don't have access to any Mac myself, and that
> does not make it to fix such errors.
>
> I've just released Friture 0.42 (
> https://github.com/tlecomte/friture/releases/tag/v0.42), could you
> confirm that this version has the same problem ? (I guess it has the same
> problem since you tried building from source already)
>
> It looks like some of you have succeeded building with Python 3.9 and
> that solved the problem ?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#154 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABAIKGKLOYHQWQC4ITAFKDLSY5637ANCNFSM4U4YTKNQ>
> .
>
--
Best Regards,
H
--
Best Regards,
H
|
|
Regarding building from source, the script used by the build pipeline can give you the steps: https://github.com/tlecomte/friture/blob/master/.github/workflows/install-macos.sh |
|
no luck with python 3.9 on macos:
looks like a different issue though:
```
sounddevice.PortAudioError: Error opening Recorder: Internal PortAudio
error [PaErrorCode -9986]
2021-01-08 15:03:45,843 CRITICAL friture.exceptionhandler: Unhandled
exception: Traceback (most recent call last):
File "/Users/haim_grosman/v/friture/main.py", line 6, in <module>
main()
File "/Users/haim_grosman/v/friture/friture/analyzer.py", line 365, in
main
window = Friture()
File "/Users/haim_grosman/v/friture/friture/analyzer.py", line 87, in
__init__
self.settings_dialog = Settings_Dialog(self)
File "/Users/haim_grosman/v/friture/friture/settings.py", line 60, in
__init__
channels = AudioBackend().get_readable_current_channels()
File "/Users/haim_grosman/v/friture/friture/audiobackend.py", line 379,
in get_readable_current_channels
nchannels = self.device['max_input_channels']
TypeError: 'NoneType' object is not subscriptable
```
[image: image.png]
…On Fri, Jan 8, 2021 at 2:43 PM Timothée Lecomte ***@***.***> wrote:
Regarding building from source, the script used by the build pipeline can
give you the steps:
https://github.com/tlecomte/friture/blob/master/.github/workflows/install-macos.sh
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAIKGOV7LGMTALQZM5KY73SY6DCFANCNFSM4U4YTKNQ>
.
--
Best Regards,
H
|
|
Just to summarise: python 3.8 has a problem with OpenGL libraries on Macos Big Sur; it can be fixed by manually editing a python file in the environment used to build friture (i can give details if needed). The OpenGL problem is fixed in python 3.9. Either with Python 3.9 or a fixed python 3.8 you then get the error File "/Users/haim_grosman/v/friture/friture/audiobackend.py", line 379, That is new to Macos 11.1, because I was able to have friture run in Macos 11.0.1. I have no idea how to fix that error. |
|
Here it is: 21-01-09 16:45:26,825 INFO friture.analyzer: Friture 0.42 starting on Darwin (darwin) |
|
Thanks! So the initial error occurred when trying to read from the microphone: |
|
I wonder if it might be because Friture is not asking for permission to read from the microphone. Are you getting the macos popup saying that Friture would like to access the microphone ? |
|
Actually I had already granted mic permission to the terminal app where I launch friture; i remember that in macos 11.0.1 it would not ask for permission, but friture would start and not capture anything from the mic. After allowing mic access to the terminal, friture was working fine. |
|
Ok, thanks. So there must be something else. For my reference anyway, I think I'll review what might be added for proper mic permissions: |
|
Another possibility is that the mic input does not support the format that Friture requests (48 kHz with 16 bit samples). Just to confirm: does your mic input work from other apps ? If you could test with Audacity, that would be great. Thanks! |
|
Audacity works fine, it can monitor and record from the microphone. |
|
as a side note it looks like also pyinstaller is having problem in big sur, it cannot find system libraries... |
Sorry, may bad ... pyinstaller 4.1 works fine, it was 4.0 having problems |
|
@enryfox I've pushed a change to log the supported input formats, to rule that scenario out. That being said, I believe the issue is the one currently being discussed in PortAudio repository:
There is also an identical issue in the python-sounddevice repository (it's the portaudio wrapper that Friture uses): In that thread, a workaround is suggested, by installing portaudio from the tip of the repo, with: Would you be in position to test that workaround, and/or the latest Friture code from Git (for the supported formats log), please ? |
|
Updated my local repo and installed portaudio using the command brew install portaudio --HEAD good news is, now friture starts-up correctly and works fine (audio is captured from the internal mic). I'm still unable to generate a self-contained re-distributable application which works correctly: pyinstaller works fine (apparently) but the resulting app hangs on start-up with no error. |
|
I just wanted to report (may not be helpful, but...) as we are validating software for macOS 11 here: We have the "PyOpenGL" error with Friture .41 on mac OS 11.1 (both Intel and M1), so I downloaded (today) .42 and installed that -- but when I launch it, it just throws up the Spinning Wheel of Death. From reading above it seems like some people got .42 working -- so is there something we might need to do on our end to get .42 to function? (.41 still works on our macOS 10.15 and earlier systems, fwiw...) |
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
For Macos Big Sur, the stable portaudio (19.6.0) makes Friture freeze on startup. So we install from latest master instead, and we tell pyinstaller to bundle that version instead of the version provided by python-sounddevice. See #154 Also remove the vcruntime140.dll workaround that is not needed with latest pyinstaller, and was getting confusing to apply next to the Macos setting.
|
Portaudio has now closed their GitHub issue about Macos Big Sur compatility. I have uploaded Friture 0.44 which contains the latest Portaudio code with all the Macos fixes. Would you be able to test friture.dmg 0.44 please ? @stevemaser @enryfox @korovkin @kitified |
|
Your latest 0.44 hangs on start-up with no error message thrown. |
|
Thank you very much for trying @enryfox The macos dmg is built with the portaudio brew package installed from HEAD: install-macos.sh#L16, and then we have a pyinstaller hook to use that version of the library: hook-sounddevice.py So it seems that is not enough. Any idea ? |
|
The problem is not the portaudio library, but in the pyinstaller. Running friture from source code works fine, but the app bundle generated by pyinstaller does not work, it hangs on start-up with no indication of what is wrong. The app bundle I created on January 30th still works, but if I try to create a new one from source, I get the same result as with your latest 0.44 pkg. |
Attempt to fix #154: Friture pyinstaller package does not work on Macos Big Sur. There are multiple reports online about PyQt5 apps not starting correctly on Macos Big Sur. The fix involves setting the `QT_MAC_WANTS_LAYER` env variable, which is now done by default on PyQt5 5.15.2 and later. Here we update to PyQt5 5.15.3. References: https://tickets.metabrainz.org/projects/PICARD/issues/PICARD-1858 https://stackoverflow.com/questions/64833558/apps-not-popping-up-on-macos-big-sur-11-0-1?noredirect=1&lq=1 https://stackoverflow.com/questions/64818879/is-there-any-solution-regarding-to-pyqt-library-doesnt-work-in-mac-os-big-sur https://riverbankcomputing.com/news/PyQt_v5.15.2_Released > The QT_MAC_WANTS_LAYER environment variable is automatically set on macOS.
|
Thanks - working now |
|
Sorry — I just got back to this today.
I downloaded .44 on my newly reloaded 11.2.3 system and it does nothing other than SPOD when I launch it.
I don’t have any additional developer tools installed — this is a base OS (with a few other apps installed…)
- Steve
… On Mar 7, 2021, at 11:46 AM, Timothée Lecomte ***@***.***> wrote:
Portaudio has now closed their GitHub issue about Macos Big Sur compatility. I have uploaded Friture 0.44 which contains the latest Portaudio code with all the Macos fixes.
Would you be able to test friture.dmg 0.44 please ? @stevemaser @enryfox @korovkin @kitified
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@enryfox I assume your comment is about the PyQt5 update ? That's great news ! Thanks !! @stevemaser Feel free to test again with Friture 0.45, freshly released a couple minutes ago: https://github.com/tlecomte/friture/releases/tag/v0.45 |
|
For 0.45, I get “PyOpenGL must be installed to run this example”
(I can’t remember if this is expected on an OS-only system or if I need something else to make this work…)
- Steve
… On Mar 8, 2021, at 4:17 PM, Timothée Lecomte ***@***.***> wrote:
@enryfox I assume your comment is about the PyQt5 update ? That's great news ! Thanks !!
@stevemaser Feel free to test again with Friture 0.45, freshly released a couple minutes ago: https://github.com/tlecomte/friture/releases/tag/v0.45
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I cloned the git branch from scratch and built the app bundle with the new QT and it now works. Unfortunately, the 0.45 release has the same issue as post #1: Have you reverted back to an older version of python ? |
|
Hi, are there any news on this subject? I tried to install friture 0.45 on the Mac OS Big Sur 11.2.3, but I get the same error “PyOpenGL must be installed to run this example” as shown. If I want to compile it myself, which version should I use then? |
|
@tlecomte Looks like Portaudio has upgraded to version 19.7.0, which supposedly fixes it on BigSur, in case you want to not build directly from the latest master |
Basically getting this issue. Installing
pyopenglin my env doesn't help (I assume because friture has its own python installation).(Another user posted in the google group here: http://friture.org/forum.html?place=msg%2Ffriture%2Fm-eNLpOqQDc%2Fsh4IlNNgCAAJ)
Happy to do any troubleshooting I can to help!
The text was updated successfully, but these errors were encountered: