Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please help us test releases for different plattforms #182

Open
5 tasks
pajowu opened this issue Jan 3, 2022 · 5 comments
Open
5 tasks

Please help us test releases for different plattforms #182

pajowu opened this issue Jan 3, 2022 · 5 comments
Labels
ci help wanted Extra attention is needed packaging

Comments

@pajowu
Copy link
Member

pajowu commented Jan 3, 2022

Currently we are building releases for different architectures, operating systems and distributions. We do not use all these platforms and mainly rely on our build system to produce correct outputs (😬)

Please help us test, especially on

  • Windows
  • Debian
  • Ubuntu
  • Fedora
  • Arch Linux

The most important parts are:

  • Importing (aka transcribing) a audio/video file
  • Exporting as Audio
  • Exporting as Video
  • Exporting using the OTIO exporter
@pajowu pajowu added help wanted Extra attention is needed ci packaging labels Jan 3, 2022
@pajowu pajowu pinned this issue Jan 3, 2022
@jgarplind
Copy link

Hi there. First time user since today, running on Windows 10.

Importing/transcribing worked fine, so major kudos for that!

I did find this minuscule issue which I'm not sure if it's within your reach to fix or not, the link to "Open Acknowledgements" does not take tab focus, nor is it click- or interactable.

image

I'd assume this is a platform issue, which seemed to be the scope of this issue.

Let me know if you'd prefer similar "reports" as own issues in the future, or if this comment serves it's purpose perfectly fine!

@pc-coholic
Copy link

pc-coholic commented Feb 17, 2022

0.2 release on Ubuntu 20.04.3:

  • .deb works as intended
  • .AppImage: Transcription silently fails (command line only provides a generic child process exited with code null).

Edit: Taking it back - apparently the deb encounters the same issue from time to time... Is there a way to have the server log more verbosely to debug this more?

@lucaswerkmeister
Copy link
Contributor

I’ve tried audapolis-linux-x64-0.2.1-1.pacman on Arch Linux, and it seems to work fairly well (though the launcher entry seems to generate without an icon, see below), though I’ll point out that .pacman is not the usual file name extension for Arch Linux packages (since this package is XZ-compressed, that would be .pkg.tar.xz, I believe).
Screenshot from 2022-02-22 22-56-20

Also, the package is seemingly installed under a package name that includes the version:

$ pacman -Qi audapolis
error: local database is inconsistent: name mismatch on package audapolis-0.2.1
error: local database is inconsistent: version mismatch on package audapolis-0.2.1
error: package 'audapolis' was not found
$ pacman -Qi audapolis-0.2.1 
error: local database is inconsistent: name mismatch on package audapolis-0.2.1
error: local database is inconsistent: version mismatch on package audapolis-0.2.1
Name            : audapolis-0.2.1
Version         : 1-1
Description     : None
Architecture    : x86_64
URL             : https://github.com/audapolis/audapolis#readme
Licenses        : AGPL-3.0

@majewsky
Copy link

majewsky commented Aug 2, 2022

Also regarding the Pacman package, your packaging is quite unfortunate because the metadata files are placed near the tail end of the tar archive. I have the package here with the uncommon .pacman ending renamed to .tar.xz, and I can see this:

$ tar tf audapolis-linux-x64-0.2.1-1.tar.xz | cat -n | awk '$2~/^\./'
 18471	.INSTALL
 18472	.PKGINFO
 18473	.MTREE

Compare a distro-supplied package, where the metadata is in front:

$ tar tf /var/cache/pacman/pkg/firefox-103.0.1-1-x86_64.pkg.tar.zst | cat -n | awk '$2~/^\./'
     1	.BUILDINFO
     2	.MTREE
     3	.PKGINFO

This would not be a big deal since most packages are rather small, but your package is particularly large, so it really hurts interactive performance that Pacman needs to read through the entire thing to even as much as display a name and version. On first trying to install, I actually thought the package was broken because Pacman was just stuck for 15 seconds before showing the confirmation prompt.

@mildred
Copy link

mildred commented Jul 23, 2024

Running AppImage version 0.3.0_4 on Linux x86_64 (Fedora 40), Everything seems to work fine except the keyboard shortcuts (especially the clipboard). I opened a webm video file, made a few changes, exported as video with separate subtitle track. No issue.

Apart from the shortcut issue, this seems to be really a great software. I'll certainly be using it soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci help wanted Extra attention is needed packaging
Projects
None yet
Development

No branches or pull requests

6 participants