Ok. My bad. Nouveau client snafu.
On Fri, Feb 21, 2020, 2:40 PM IOhannes m zmölnig wrote:
> Am 21. Februar 2020 18:52:00 MEZ schrieb Andrew Lyons >:
> >I did start a new thread. I suspect you are mistaken. Happy Friday!
>
>
> you most certainly did not.
>
> your original mail contains a
Am 21. Februar 2020 18:52:00 MEZ schrieb Andrew Lyons :
>I did start a new thread. I suspect you are mistaken. Happy Friday!
you most certainly did not.
your original mail contains a header:
> In-Reply-To: <2bb7a77d-3f7e-479a-8078-11707cbf3...@gmail.com>
...and accordingly shows up as a reply
I gave it a try but couldn't get it working right away - I need to get back
to it but haven't had much time in the last couple of weeks.
cheers
Miller
On Fri, Feb 21, 2020 at 05:15:46PM +0100, Jo??o Pais wrote:
> Any news about this? I would like to try it out, on both pc and mac.
>
> jmmmp
>
I did start a new thread. I suspect you are mistaken. Happy Friday!
> @ Andrew Lyons
> Pleas don't hijack threads. If you have a new question, compose a new
> email to pd-list@lists.iem.at and never just take a random old email and
> change the subject / content.
>
Thanks Dan. I'll run some more tests and try out Ingo's suggestion.
On Fri, Feb 21, 2020, 3:29 AM Dan Wilcox wrote:
> PD tries to handle MIDI as fast as it gets it, hence Miller's warning.
>
> First, does Pd lock up on the RPI *without* your patch running? If so,
> then Pd itself is clogged up
Thanks Ingo. I will try that out.
On Thu, Feb 20, 2020, 9:00 AM Ingo wrote:
> Use
>
>
>
> [unpack f f f]
>
>| \ \
>
>| \ \
>
>| | |
>
> [speedlim 25]| |
>
>
You can represent *any* string in Pd as a list of bytes and convert from
to Pd symbols with [list fromsymbol] / [list tosymbol]. What do you need
to do exactly?
Christof
On 18.02.2020 13:01, Markus Brandt wrote:
dear list!
Has anyone of you an idea, how i can get a string like the the one
Am 18. Februar 2020 13:44:25 MEZ schrieb IOhannes m zmoelnig :
>
>
>zexy's [msgfile] has a CSV-mode.
>
>but i can't remember whether i've released that version yet :-(
now i remembet, that i did include it in zexy-2.3.0.
however, only now i realized that while msgfile now supports CSV-files,
Looks like this issue
https://github.com/pure-data/pure-data/issues/895
I can recover the locked-up Pd by disconnecting the ALSA MIDI in the
QjackCtl Graph. (see animated gif in the github issue)
The MIDI device I'm experiencing this issue with is a Sensel Morph in
14bit MIDI mode.
@
Yeah, one of each. I'm following the file format specifications but I also need
real files to read & compare my own output with.
I've been so deep in this soundfile overhaul that I might as well see if we can
add this.
> On Feb 21, 2020, at 1:58 PM, Ingo wrote:
>
> Dan, do you mean a simple
Dan, do you mean a simple soundfile that has loop markers embedded? I have tons
of them.
Do you need .wav or .aiff or both? Mine are usually .wav but I can convert it
to .aiff as well.
I'll have to check on my old computer first to make sure whether the files
header contain the loops.
Can someone send me example files with encoding loop positions? I started with
demo soundfile meta data reading/writing but now I need some sample files to
work with. I saved a couple via Logic Pro X but the region info is saved as
simple markers, not using instrument or sampler chunks.
> On
PD tries to handle MIDI as fast as it gets it, hence Miller's warning.
First, does Pd lock up on the RPI *without* your patch running? If so, then Pd
itself is clogged up by all the messaging on the RPI. If it's your patch, then
your message handling can/should be optimized ala Ingo's
13 matches
Mail list logo
