Re: [PD] [leapmotion] how to get focus?

2023-04-24 Thread William Brent
Hi all. I'm  just circling back on this with an update after connecting
with rolf off-list. There was an issue on rolf's Windows machine that I
hadn't encountered in my Windows tests where application focus changes
weren't working as expected. Our setups were basically identical, but it
worked fine for me and only intermittently for rolf. I decided to sidestep
the need for application focus altogether by activating the
POLICY_BACKGROUND_FRAMES policy in the external. The new version of
[leapmotion] (0.2.4) that contains this update is available via deken for
Linux, macOS, and Windows. Further testing would be appreciated if anyone
is in the position to try it out.

And for anyone interested in this, I'll just say again that the
multi-platform and multi-hardware situation with LEAP has a lot of
potential for confusion. I was on a bit of a mission to make sense of it
all a few months back and still have a grasp on things if anyone needs
advice. The quick upshot is:

   - macOS: no support for the latest LEAP software (5.7.2) or the latest
   Ultraleap controller hardware. You can still use LEAP software 2.3.1 and
   the original Leap Motion Controller, but depending on your macOS version
   and hardware, you may have to resort to this annoying trick
   .
   In Pd, use the [leapmotion] extern version 0.2.4 from deken.
   - Linux and Windows: LEAP software 5.7.2 is supported, which allows you
   to use both the original Leap Motion Controller and the new Ultraleap
   controller. In Pd, use the [ultraleap] extern from deken. If you want to
   use the [leapmotion] extern, you'll have to install the old 2.3.1 LEAP
   software. One reason to use the old software is that it features
   tool tracking and pre-defined gesture tracking. The newest API doesn't.




On Mon, Apr 17, 2023 at 2:12 PM William Brent 
wrote:

> Is the controller not working with any software, or only not with
> [leapmotion]? I had the same issue of the controller not lighting up when I
> ran the LEAP 2.3.1 installer, but I documented this extra step in the
> [leapmotion] INSTALL.txt that fixes things:
>
> When running the installer, a popup warning appears about missing graphics
> drivers. This can be ignored. When installation is finished, navigate to
> C:\Program Files (x86)\Leap Motion\Core Services\Drivers
> and run dpinst64.exe to install 64-bit drivers for the Leap Motion
> Controller.
>
> For me, this extra step installs the drivers correctly and the device
> lights up/is recognized afterward. I just went through this process again
> on my W10 machine with no issues, and [leapmotion] works fine after that
> fix. Could you report specifically on your results of trying that?
>
>
> On Mon, Apr 17, 2023 at 8:55 AM  wrote:
>
>> well, i tried to go back on the W11 machine to the [leapmotion] setup:
>>
>> however, the controler isn't working, it doesn't show the 3 red
>> sensor-lights.
>>
>> re-installing the Gemini/[ultraleap] -> no problem.
>>
>>
>> installed the [leapmotion] setup on the old W10 -> same result: controler
>> not working.
>>
>> changing to Gemini/[ultraleap] -> working.
>>
>> ??
>>
>>
>> that's it for now.
>>
>> rolf
>>
>>
>> ro...@dds.nl schreef op 17-04-2023 12:33:
>>
>> thanks William,
>>
>> installing Gemini & [ultraleap] made it work!
>>
>>
>> only just now i have time to follow up on your suggestions.
>>
>> i'll also test on my old Windows 10 machine.
>>
>>
>> report of that will follow asap.
>>
>>
>> rolf
>>
>>
>> William Brent schreef op 16-04-2023 1:58:
>>
>> I just set up my Windows machine to match your system as closely as
>> possible, and all still works as expected with [leapmotion] for me. The
>> only difference is that I'm on Windows 10 rather than 11.
>>
>> After reading your message again, I see that you're occasionally getting
>> some tracking data, so most of what I said in my previous post is
>> irrelevant. But before I dig any further: are you *sure* you're clicked on
>> Pd to make it the foreground application when testing [leapmotion]? If
>> you're clicked on the desktop or any other window/app to lose focus, then
>> tracking data will stop flowing. And if those focus gained/lost messages
>> aren't making sense with the actual clicking you're doing, that's what we
>> need to look into. Maybe I can just disable the need for focus entirely...
>>
>>
>>
>> On Sat, Apr 15, 2023 at 2:53 PM William Brent 
>> wrote:
>>
>>> Hi rolf, there are a few confusing things in the LEAP world across
>>> Linux/Mac/Windows, but when I was working on this a few months back I did
>>> successfully get both [leapmotion] and [ultraleap] working on multiple
>>> Windows 10 machines with an original Leap Motion Controller. That said,
>>> since you're on Windows 11 there could be some new wrinkles. But here are
>>> some starting points to check:
>>>
>>> First, since you're using [leapmotion] and the old 2.3.1 LEAP software,
>>> did you see the Windows notes at 

Re: [PD] midi file into [text sequence]?

2023-04-24 Thread Alexandre Torres Porres
Em dom., 23 de abr. de 2023 às 10:25, Linux ROUEN Normandie <
linux.ro...@free.fr> escreveu:

> It would be useful if both MIDI Sequencer objects can directly share the
> same Text format
>

there's no reason to use both, one should be enough for your needs, that
makes more sense. Also, I can't mess with [seq] and break it, so it's a big
NO for this.

cheers
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list


Re: [PD] hardcoded samplerate in audio example

2023-04-24 Thread Miller Puckette

Yep... these patches date back to before that outlet :)

For now it migth suffice to mention that the patches only work on 44k1 
soundfiles... and incidentally, thee best one (teh phase vocoder) works 
fine on 48K files, you just have to adjust the transposition by 147 cents.


cheers

Miller

On 4/23/23 03:47, Patco wrote:

Hello,

  I've found something awkward in all fft patches from 03.audio-examples that 
leads to mistakes.

Samplerate is hardcoded to 44100, so this wouldn't work correctly when opening 
soundfiles having another samplerate.

  This should be corrected by using [soundfiler] second outlet instead of 
hardcoding samplerate.


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!!Mih3wA!CrYdxPP1DIwgweOlVm1jAUnUVItz5JBMO7EMwJgmlAXY63111FtyJQ70TGNPREswXJC1Mfe2UL13YOoWnA4$




___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list