Unable to use otioviewer in 0.17.0

[BertPlasschaert]

Required:

---

[x] I believe this isn't a duplicate topic
[x] This report is not related to an adapter

Select One:

[x] Incorrect Functionality or bug

Description

Only in OpenTimelineIO 0.17.0

I wanted to try out the otio viewer.
I followed the instructions from the quickstart guide
When I ran the otioview eld_file.edl command, the terimal hang for a solid second and returned to normal state without any error / feedback.
I tried to run otioview -h but this had the exact same error behavior as running the previous command.
I tried the same with otiostat by running the following command otiostat -h. This did return usage info, as did this command with the other available executables. This issue seems to be isolated to the otioview executable.
I had a look on the Slack channel and found a thread in which @JeanChristopheMorinPerso detailed that the exe is just a wrapper for the following command python -c 'import opentimelineview.console; opentimelineview.console.main()'. I opened a python session and tried to run the two commands but the interpeter crashed and exited after running the import command.

I tried the same steps on a seperate machine with the same python version and had the same issue, and on a third machine who had python 3.10.11 installed, also resulting in the same issues.

I tried this with both OpenTimelineIO and OpenTimelineIO-Plugins packages, Both have the same behaviour.
I downgraded to 0.16 and this resolved the issues I had.

Optional

---

Environment

Operating System: Windows 11
Python version if appropriate: 3.9.7 and 3.10.11

[apetrynet]

Hi @BertPlasschaert

Do you have pyside installed for your python version? I believe you can do: pip install pyside

[BertPlasschaert]

Hi @apetrynet,
Thank you for the quick followup.
I have installed PySide2 as described in the quickstart guide. This is my pip freeze:

OpenTimelineIO==0.17.0
PySide2==5.15.2.1
shiboken2==5.15.2.1

I've just now installed pyside as you suggested but this did not fix the behaviour I am experiencing.

[apetrynet]

Just to exclude some potential bugs related to removal of contrib adapters in 0.17.0, did you install opentimelineio-plugins or opentimelineio? If the later, could you please try uninstalling opentimelineio and installing opentimelineio-plugins and see if you get the same behavior?

Also, please paste the traceback from the terminal in a comment so, we can look for clues :)

[BertPlasschaert]

I tried both and both (using version 0.17.0) behaved exactly the same.
The thing is that there is no traceback the terminal just acts like the command is executed succesfully.

[apetrynet]

I'm not sure how it is on windows, but on Linux you should find the executable under .venv/bin/otioview
Could you please check if calling that path directly produces any output?
Or is there a way to check where the otioview executable is running from?

Sort of grasping at straws here, but find it strange that there's no output whatsoever.
I don't have a windows machine available and I'm away from my computer, so can't do too much digging.

[apetrynet]

@BertPlasschaert
Are you new to the project via dev days?
If you struggle with getting otioview to work, there is a new project called Raven that is meant to "replace" otioview in the future. Perhaps you have better luck with that.

[BertPlasschaert]

@apetrynet I tried calling them directly as you proposed. This did not alter the behaviour. On windows these are located in .venv/Scripts/

The only linux access I have is WSL2 but I dont know if this is supported by otio as this does not seem to work with 0.16.0 either.
When I try to run this in WSL Ubuntu I get the following error:

But I think this is just because WSL is not supported?

Thank you for the information about Raven. This looks very promising, I'll continue to look into that.

[apetrynet]

Looks like your Linux attempt is missing an OpenGL library, thus failing to import pyside6 and falling back on pyside2 which is not installed.

Whenever you have time, could you please check one more thing just to scratch an itch?

Again grasping at straws here.
Does windows run the executable that's in the current directory even if there's another one with the same name available in the $PATH environment variable?

On Linux we need to be specific like: ./otioview indicating that we want to run the one in this folder.
In this SO post I found that windows has a where command to list where an executable is located. If it lists several, the top one should be the default.
Does: where otioview give you the path to your current virtual environment?
And does calling otioview.exe -h make a difference?

[BertPlasschaert]

Thanks for the clarification regarding the WSL situation.

On my windows machinge, I ran the where command as proposed. This only had one entry, which is the correct one inside the virtual environment.

Calling this did not change the behaviour.
As mentioned This is not a blocking issue at all for me, but If you want me to test anything else please let me know where I can be of assitance.

[apetrynet]

Thanks for checking!
I'm out of ideas unfortunately.
Glad to hear this isn't a blocker for you.
Hopefully someone with more windows experience can chime in.

[brumenn]

I'm having the exact same issue on Windows 10, and I managed to launch otioview by installing pyside6 instead of pyside2, which at first throw an IndexError at line 222 of console.py:

Then, correcting the line 222 in console.py file from:

navigation_menu.triggered[[QAction]].connect(__callback)

to:

navigation_menu.triggered[(QAction)].connect(__callback)

seems to work as expected, which corresponds to the issue #1806.

This is my uv tree:

otio
├── opentimelineio v0.17.0
└── pyside6 v6.9.1
    ├── pyside6-addons v6.9.1
    │   ├── pyside6-essentials v6.9.1
    │   │   └── shiboken6 v6.9.1
    │   └── shiboken6 v6.9.1
    ├── pyside6-essentials v6.9.1 (*)
    └── shiboken6 v6.9.1

OS: Windows 10
Python version: 3.10.11

Hope this helps!