Room for new packages
- Edited
What about Ctrlr, a programmable (lua scripting) midi editor for hardware sequencers, written in Juce?
I don't know an alternative for this software in Linux.
The stable downloadable binaries (at ctrlr.org) are working without issues in Kaos, but maybe, when compilated from source code in Kaos, this software will be still more integrated in Kaos.
Another proposition: luatex.
Luatex offers pdftex enriched with the lua scripting language.
- Edited
thomaslemmens programmable (lua scripting) midi editor for hardware sequencers, written in Juce
Not a single person has ever mentioned using this for KaOS in it's seven years existence. Any added should have the potential to be actually used by more then one.
It is also fully GTK centered, seems LMMS (in repo and Qt based) has quite a few of it's features (MIDI VST editor for example).
This has been asked for twice now, still not something that looks desirable to many.
See post 76
- Edited
demm
Qtractor and lmms (via wine?) can load (some?) vst's (important feature to use only one midi port), but can not construct them.
Using Ctrlr, you can construct midi editors for nearly any midi hardware (sequencer, mixer, sampler., drummachine..) both as a standalone editor or as a vst-plugin. And this in different ways for every single machine (library, patch editor, mixer, sysex dump organiser ...). Ctrlr can output this drivers also as a xml file.
So Ctrlr can be a very useful auxiliary program for such software as qtractor , lmms or Rosegarden.
It features also the lua scripting language that still enhances its use in a steep way.
Nevertheless you are right to favour software used by many users.
And it is really a pity it isn't Qt centered. But I'm not aware of an alternative in linux
thomaslemmens Qtractor and lmms (via wine?)
Why wine? Both are in the repo.
https://kaosx.us/packages/view.php?repo=apps&name=lmms-1.2.1-3
https://kaosx.us/packages/view.php?repo=apps&name=qtractor-0.9.12-1
- Edited
mendez
Further checking showed fwupd is useful for many, added (though a bit limited for now, not all extra depends added, since it takes about 6-7 more to enable full UEFI & Dell support).
Fwupd & libxmlb are added (build repo).
https://github.com/KaOSx/main/commit/be814e378bc33747ada110e772429d62690f0d0c
thomaslemmens Linux LMMS installations require Wine
Please let me know it works if you add Wine to your install, then I will add that as a depend to lmms.
I failed to load a vst plugin (windows 32, win 64 or linux) neither in Lmms nor in Qtractor.
I've no idea why, I can only guess.
Maybe a compile option is missing.
The Qtractor manual list as one of the optional packages VST-SDK - Steinberg’s Virtual Studio Technology plugin format. The manual asks us to 'note that Qtractor can still use most VST plugins when using the included VeSTige reverse-engineered VST headers instead http://www.steinberg.net/'
Maybe in Lmms there is an issue because wine is called in Kaos by 'wine64' and not 'wine'
Maybe I did something wrong without knowing it.
demm ok to start a poll, but maybe add megasync and nextclod/owncloud together is the best way. I saw the price for these service for a year:
Megasync 400Gb or 2Tb 50€/100€
Nextcloud 100Gb or 200Gb 54€/108€
Pcloud 500Gb or 2Tb 50€/100€
Gdrive 100Gb or 200Gb or 2Tb 20€/30€/100€
but, Gdrive is built in plasma, Pcloud is an electron app. Just download and it works. Nextcloud have a very full service (calendar, mail, ecc) and megasync makes packages for a lot of distro. (great support for GNU/Linux).
My 2cents.
[deleted]
How about active window control widget for plasma?
[deleted]
jomada Thanks a lot, that was a dumb question as always ...
Thanks a lot!
KBlocks? I was inspired by the entry on Planet.
mendez KBlocks? I was inspired by the entry on Planet.
Sure, can come back now, it used to be in, but wasn't ported when the full switch to Plasma 5 occurred, see libkdegames for the entry:
https://github.com/KaOSx/apps/blob/master/libkdegames/PKGBUILD#L22
Intel media driver is the new replacement of libva intel driver, they should be in conflict, older cards should keep using old driver.
https://github.com/intel/media-driver/
- Edited
@demm more investigation is needed
toni ~ export LIBVA_DRIVER_NAME=iHD
toni ~ vainfo
libva info: VA-API version 1.6.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/lib/dri/iHD_drv_video.so
libva error: /usr/lib/dri/iHD_drv_video.so has no function __vaDriverInit_1_0
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
toni ~ 1 nm --demangle -D /usr/lib/dri/iHD_drv_video.so | grep __vaDriverInit
0000000000483120 T __vaDriverInit_1_7
Libva searches for __vaDriverInit_1_0 but new driver provides __vaDriverInit_1_7
// Edit: That was a partial update, only new packages was installed, i update libva as well, it works
toni ~ export LIBVA_DRIVER_NAME=iHD
toni ~ vainfo
libva info: VA-API version 1.7.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.7.1)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 (b78a8d7f)
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
Should new driver set new environment variable export LIBVA_DRIVER_NAME=iHD
by default when installed and to remove when deinstalled?
- Edited
hi Demm,
I just discovered BashTop, a really cool system monitoring thing written entirely in Bash, see here:
https://www.linuxuprising.com/2020/04/bashtop-is-cool-linux-resource-monitor.html
It depends on core packages we already have in KaOS (this is the PKGBUILD for Arch):
# Maintainer: Sébastien Luttringer
pkgname=bashtop
pkgver=0.8.15
pkgrel=1
pkgdesc='Linux resource monitor'
arch=('any')
url="https://github.com/aristocratos/bashtop"
license=('Apache')
depends=('bash' 'coreutils' 'grep' 'sed' 'gawk' 'procps-ng')
makedepends=('git')
optdepends=(
'curl: themes download'
'lm_sensors: cpu temperatures'
)
source=("git+https://github.com/aristocratos/bashtop.git#tag=v$pkgver")
sha256sums=('SKIP')
package() {
cd $pkgname
install -Dm755 bashtop -t "$pkgdir/usr/bin"
}
I would love to see this one added, since it would take very little extra package space to get part of default KaOS. What do you think?
If it's a bad idea, let me know, I'll add it on KCP...
Cheers,
Gunther