Sorry to _low_show - this was meant for the list.
On Mon, Oct 11, 2021 at 03:19:45PM +0200, _low_show wrote:
> Looks great, will make some time to try it out! Thanks for making this!
I somehow deleted the original post, but refer to
> https://youtu.be/51eHCA4oCEI
> https://lv2plug.in/book
I never got to grips with turtle. In particular not with
things like:
@prefix doap: <http://usefulinc.com/ns/doap#> .
@prefix lv2: <http://lv2plug.in/ns/lv2core#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix units: <http://lv2plug.in/ns/extensions/units#> .
All docs and tutorials I found mention that the URLs do NOT
mean that an application reading a file that contains them
would actually need to read them from the web (which would
be a unacceptable security risk anyway).
But that means that whatever is defined by those URLs
must actually be hard-coded in any LV2 host that reads
the 'manifest.ttl' or 'my-plugin.ttl' files.
Which raises the question why those @prefix lines are
required at all. They could be used in theory to check
that what is hard-coded corresponds to what is defined
in those URLs. But to do that the application would
need to access them.
So all that these lines seem to provide is some illusion
of conformity which isn't enforced or checked at all.
So the conclusion is that this isn't any better than any
ad-hoc way of encoding the plugin metadata.
Or am I missing something essential ?
TIA for any reply that would enlighten me...
--
FA
Hi all!
I have recently released first preview of SoundTracker v1.0.3. Here are
new features of this pre-release:
* General:
- Indication of the current playing instrument / sample number in scopes
(optional via Settings)
- On new instrument or sample loading ins / sample name(s) can be
overwritten or kept (configurable via Settings -> GUI settings)
- Extended pattern sequence editor with DND (activaled by right-click on
the playlist area)
* Instrument editor:
- Envelopes cutting / copying / pasting / scaling
- Indication of the keys playing with the current instrument also in the
pattern / song playing mode
* Track editor:
- Track line insertion / removal
- Masking for cut / copy / paste operaions
I invite everyone to test this pre-release and look forward your
feedback (bugreports and feature requests).
Download: https://sourceforge.net/projects/soundtracker/files/
Regards,
Yury.
Looks great, will make some time to try it out! Thanks for making this!
On Mon, 11 Oct 2021, at 12:00, linux-audio-dev-request(a)lists.linuxaudio.org wrote:
> Send Linux-audio-dev mailing list submissions to
> linux-audio-dev(a)lists.linuxaudio.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.linuxaudio.org/listinfo/linux-audio-dev
> or, via email, send a message with subject or body 'help' to
> linux-audio-dev-request(a)lists.linuxaudio.org
>
> You can reach the person managing the list at
> linux-audio-dev-owner(a)lists.linuxaudio.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linux-audio-dev digest..."
>
>
> Today's Topics:
>
> 1. Programming LV2 plugin from scratch tutorial video series
> (Sven Jaehnichen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 10 Oct 2021 13:58:57 +0200
> From: Sven Jaehnichen <sjaehn(a)jahnichen.de>
> To: linux-audio-announce(a)lists.linuxaudio.org,
> linux-audio-dev(a)lists.linuxaudio.org, devel(a)lists.lv2plug.in
> Subject: [LAD] Programming LV2 plugin from scratch tutorial video
> series
> Message-ID: <bd239f3c-c8d5-f4fa-d1b2-bb5525ff8a2a(a)jahnichen.de>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi,
>
> I started with a programming tutorial series about making LV2 plugins.
> Really from scratch. Dedicated for beginners.
>
> I read in chats from so many hobbyist and bedroom producers that that
> they want to make LV2 plugins but they don't have any idea how to start.
> The most of them have got some basic programming experience. With Java,
> Python, Javascript, or maybe some basic C/C++. I want to take them by my
> hand and want to guide them to make some LV2 plugins. Step by step. I'm
> also going to explain technical aspects. The turtle language, how LV2
> plugins work, what is realtime, and so on.
>
> The first videos are online:
>
> https://youtu.be/51eHCA4oCEI
>
> Two more are already pre-produced, and will follow within the next weeks.
>
> In addition, there's a great resource by David called LV2 book
> https://lv2plug.in/book/ which helped me to start just a few years ago.
>
> Please give me some feedback. And I'm open for any suggestion.
>
> Regards,
> Sven
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev(a)lists.linuxaudio.org
> https://lists.linuxaudio.org/listinfo/linux-audio-dev
>
>
> ------------------------------
>
> End of Linux-audio-dev Digest, Vol 176, Issue 2
> ***********************************************
>
Hi,
I started with a programming tutorial series about making LV2 plugins.
Really from scratch. Dedicated for beginners.
I read in chats from so many hobbyist and bedroom producers that that
they want to make LV2 plugins but they don't have any idea how to start.
The most of them have got some basic programming experience. With Java,
Python, Javascript, or maybe some basic C/C++. I want to take them by my
hand and want to guide them to make some LV2 plugins. Step by step. I'm
also going to explain technical aspects. The turtle language, how LV2
plugins work, what is realtime, and so on.
The first videos are online:
https://youtu.be/51eHCA4oCEI
Two more are already pre-produced, and will follow within the next weeks.
In addition, there's a great resource by David called LV2 book
https://lv2plug.in/book/ which helped me to start just a few years ago.
Please give me some feedback. And I'm open for any suggestion.
Regards,
Sven
Good to know there's a new hdspm driver being worked on.
> The settings of the card can nevertheless be graphically
> set, using alsamixer in the terminal.
I've only had limited success using alsamixer to change settings
on HDSPe MADI cards. I've found amixer and alsactl (both CLI)
more useful here. I made a web page describing their use with the
HDSPe MADI:
http://www.jrigg.co.uk/linuxaudio/hdspe-madi.html
Much of it should also be applicable to the HDSPe AES32 (allowing
for different parameter names and channel numbers).
John
Hi,
I've been searching all day through the linus audio mailing list archives,
and I couldn't find any confirmation that this card is working on Linux.
When I look at the source code of the hdspm driver, I see lot's of references
to the AES32, so I suppose it is at least partly supported.
Is there anyone here that knows more about this card?
Thanks!
lieven
Hi,
I am using custom build real-time kernel 5.12.2-rt3-fw. JACK with ALSA
backend on Mackie Onyx 1640i.
Lenovo Thinkpad T420 with FireWire. Debian Bullseye (11.0 - stable)
JACKD version 1.9.17.
I am using 512 samples 3 periods @48kHz.
The problem is that long run playback only around 1h (but the time
differs), result in
XRUN detected by JACK logs and the whole audio stops. So I have to
restart JACK in order to make it work.
DMESG is silent about that issue. But sometimes I get:
snd_oxfw fw1.0: Detect discontinuity of CIP: E8 00
And different hex values there.
Here is interesting part from the log:
Sun Sep 12 22:10:12 2021: Jack: JackRequest::Notification
Sun Sep 12 22:10:12 2021: Jack: **** alsa_pcm: xrun of at least 0.027 msecs
Sun Sep 12 22:10:12 2021: Jack: Repreparing capture
Sun Sep 12 22:10:12 2021: Jack: Repreparing playback
Sun Sep 12 22:10:12 2021: Jack: ALSA XRun wait_status = 0
Sun Sep 12 22:10:12 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 22:10:12 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 22:10:12 2021: Jack: JackClient::ClientNotify ref = 2 name =
dbusapi notify = 3
Sun Sep 12 22:10:12 2021: Jack: JackClient::kXRunCallback
Sun Sep 12 22:10:12 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 22:10:12 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 22:10:12 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 22:10:12 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 22:10:28 2021: ERROR: ALSA: poll time out, polled for
15998655 usecs, Retrying with a recovery, retry cnt = 1
Sun Sep 12 22:10:44 2021: ERROR: ALSA: poll time out, polled for
15998654 usecs, Retrying with a recovery, retry cnt = 2
Sun Sep 12 22:11:00 2021: ERROR: ALSA: poll time out, polled for
15998659 usecs, Retrying with a recovery, retry cnt = 3
Sun Sep 12 22:11:16 2021: ERROR: ALSA: poll time out, polled for
15998649 usecs, Retrying with a recovery, retry cnt = 4
Anyone have idea what might be the cause of this XRUN? Or how to debug that?
Its reproducible on my setup. Another log catched the same issue:
Sun Sep 12 16:50:44 2021: Jack: **** alsa_pcm: xrun of at least 0.030 msecs
Sun Sep 12 16:50:44 2021: Jack: Repreparing capture
Sun Sep 12 16:50:44 2021: Jack: Repreparing playback
Sun Sep 12 16:50:44 2021: Jack: ALSA XRun wait_status = 0
Sun Sep 12 16:50:44 2021: Jack: JackRequest::Notification
Sun Sep 12 16:50:44 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 16:50:44 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 16:50:44 2021: Jack: JackClient::ClientNotify ref = 2 name =
dbusapi notify = 3
Sun Sep 12 16:50:44 2021: Jack: JackClient::kXRunCallback
Sun Sep 12 16:50:44 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 16:50:44 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 16:50:44 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 16:50:44 2021: Jack: JackEngine::ClientNotify: no callback
for notification = 3
Sun Sep 12 16:51:00 2021: ERROR: ALSA: poll time out, polled for
15998366 usecs, Retrying with a recovery, retry cnt = 1
Sun Sep 12 16:51:16 2021: ERROR: ALSA: poll time out, polled for
15998353 usecs, Retrying with a recovery, retry cnt = 2
Sun Sep 12 16:51:32 2021: ERROR: ALSA: poll time out, polled for
15998352 usecs, Retrying with a recovery, retry cnt = 3
Sun Sep 12 16:51:48 2021: ERROR: ALSA: poll time out, polled for
15998367 usecs, Retrying with a recovery, retry cnt = 4
Sun Sep 12 16:52:04 2021: ERROR: ALSA: poll time out, polled for
15998353 usecs, Retrying with a recovery, retry cnt = 5
Sun Sep 12 16:52:20 2021: ERROR: ALSA: poll time out, polled for
15998371 usecs, Reached max retry cnt = 5, Exiting
Sun Sep 12 16:52:20 2021: ERROR: JackAudioDriver::ProcessAsync: read
error, stopping...
Sun Sep 12 16:52:20 2021: Jack: JackPosixThread::ThreadHandler : exit
I am willing to provide additional info.
Thank you in advance,
AreYouLoco?