Re: [PD] [PD-announce] Pd 0.52-2 released

2022-03-29 Thread Alexandre Torres Porres
Em ter., 29 de mar. de 2022 às 11:12, Christof Ressi 
escreveu:

> From my understanding, yes. For that reason, I guess it's not a good idea
> to provide universal binaries at this point and we should rather ship
> seperate binaries. Once most externals are available as universal binaries,
> we might ship Pd as a universal binary as well.
>
Of course, you can always force apps to run under Rosetta, but I don't
> think that's a good user experience.
>

I agree, separate binaries makes more sense these days.
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list


Re: [PD] [PD-announce] Pd 0.52-2 released

2022-03-29 Thread Dan Wilcox
Ah right, as Edwin wrote, you can also right-click on the application, choose 
Get Info, the check Open in Rosetta to force running as x86_64 on M1 macs. 
However, as Phil notes, this means Pd is running under arch emulation and will 
be slower, so this is more of a temporary workaround until you can update your 
externals to universal/native builds.

> On Mar 29, 2022, at 9:08 PM, Dan Wilcox  wrote:
> 
> it works the same as *any* existing application that is compiled for multiple 
> architectures: it uses the current system architecture but default. If you 
> want, you can force an architecture via using "arch" on the command line:
> 
> https://medium.com/swlh/run-x86-terminal-apps-like-homebrew-on-your-new-m1-mac-73bdc9b0f343
>  
> 
> 
> For Pd, you can't do this by double-clicking to launch the application but by 
> invoking the core internally:
> 
> arch -x86_64 /Applications/Pd-0.52-2.app/Contents/Resources/bin/pd
> 
> This should force running the core as x86_64 with Rosetta 2.
> 
> No, nothing has changed about which externals can be loaded. If the external 
> is compiled for the architecture you are running Pd under, then it should 
> load.
> 


Dan Wilcox
@danomatika 
danomatika.com 
robotcowboy.com 



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


Re: [PD] [PD-announce] Pd 0.52-2 released

2022-03-29 Thread Dan Wilcox
it works the same as *any* existing application that is compiled for multiple 
architectures: it uses the current system architecture but default. If you 
want, you can force an architecture via using "arch" on the command line:

https://medium.com/swlh/run-x86-terminal-apps-like-homebrew-on-your-new-m1-mac-73bdc9b0f343
 


For Pd, you can't do this by double-clicking to launch the application but by 
invoking the core internally:

arch -x86_64 /Applications/Pd-0.52-2.app/Contents/Resources/bin/pd

This should force running the core as x86_64 with Rosetta 2.

No, nothing has changed about which externals can be loaded. If the external is 
compiled for the architecture you are running Pd under, then it should load.

> On Mar 29, 2022, at 4:02 PM, Alexandre Torres Porres  wrote:
> 
> Em seg., 28 de mar. de 2022 às 07:17, Dan Wilcox  > escreveu:
> Howdy Miller,
> 
> the macOS 10.10+ build is working fine and supports both x86_64 & arm64. I 
> think you can remove the link to my previous 0.52-1 arm64-only build on the 
> download page.
> 
> Great to know that, so let me see if I get it straight. If you have an apple 
> silicon, it'll run under the hood the arm code and then it will only find and 
> load 'arm64' externals? Or can you load both externals types? How does it 
> work?
> 
> Oh, and Miller's site should say it is a universal binary ready for the new 
> macs!
> 
> cheers


Dan Wilcox
@danomatika 
danomatika.com 
robotcowboy.com 



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


Re: [PD] [PD-announce] Pd 0.52-2 released

2022-03-29 Thread Philip Stone via Pd-list
On an M1 Mac, Deken will only show Darwin-arm64 externals (that is, if you have 
the  ‘Hide foreign architectures’ option checked, which I believe is the 
default). If that box is unchecked, you’ll see all architectures.

If you have old Darwin-amd64-32 externals lying around (like I did) Pd will 
attempt to load them, but will throw an error complaining about the mismatched 
architecture.


Phil Stone
Davis, CA  USA

--

Message: 2
Date: Tue, 29 Mar 2022 11:02:11 -0300
From: Alexandre Torres Porres 


Em seg., 28 de mar. de 2022 ?s 07:17, Dan Wilcox 
escreveu:

> Howdy Miller,
>
> the macOS 10.10+ build is working fine and supports both x86_64 & arm64. I
> think you can remove the link to my previous 0.52-1 arm64-only build on the
> download page.
>

Great to know that, so let me see if I get it straight. If you have an
apple silicon, it'll run under the hood the arm code and then it will only
find and load 'arm64' externals? Or can you load both externals types? How
does it work?

Oh, and Miller's site should say it is a universal binary ready for the new
macs!

cheers
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.puredata.info/pipermail/pd-list/attachments/20220329/31ea5abf/attachment-0001.htm>

--

Message: 3
Date: Tue, 29 Mar 2022 16:10:31 +0200
From: Christof Ressi 
To: pd-list@lists.iem.at
Subject: Re: [PD] [PD-announce] Pd 0.52-2 released
Message-ID: <5009ad6d-2207-bdfc-9c9b-afd8baa09...@christofressi.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

> If you have an apple silicon, it'll run under the hood the?arm code
> and then it will only find and load 'arm64' externals?
 From my understanding, yes. For that reason, I guess it's not a good
idea to provide universal binaries at this point and we should rather
ship seperate binaries. Once most externals are available as universal
binaries, we might ship Pd as a universal binary as well.

Of course, you can always force apps to run under Rosetta, but I don't
think that's a good user experience.

Christof

On 29.03.2022 16:02, Alexandre Torres Porres wrote:
> Em seg., 28 de mar. de 2022 ?s 07:17, Dan Wilcox
>  escreveu:
>
> Howdy Miller,
>
> the macOS 10.10+ build is working fine and supports both x86_64 &
> arm64. I think you can remove the link to my previous 0.52-1
> arm64-only build on the download page.
>
>
> Great to know that, so let me see if I get it straight. If you have an
> apple silicon, it'll run under the hood the?arm code and then it will
> only find and load 'arm64' externals? Or can you load both externals
> types? How does it work?
>
> Oh, and Miller's site should say it is a universal binary ready for
> the new macs!
>
> cheers
>
>
>
> ___
> Pd-list@lists.iem.at  mailing list
> UNSUBSCRIBE and account-management 
> ->https://lists.puredata.info/listinfo/pd-list
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.puredata.info/pipermail/pd-list/attachments/20220329/926b2bde/attachment-0001.htm>

--

Message: 4
Date: Tue, 29 Mar 2022 13:33:06 -0300
From: Alexandre Torres Porres 
To: Pd-List 
Subject: Re: [PD] more features for [file] (Get directory of current
patch)
Message-ID:

Content-Type: text/plain; charset="utf-8"

Em s?b., 26 de mar. de 2022 ?s 03:46, IOhannes m zm?lnig 
escreveu:

> > yeah, that's great. I have a n external that does that [slice]
>
> yeah. and zexy has [niagara] that does this.
> my git history only reaches back to 2002, and it was there back then.
>
> but i was really talking about [list split] here.
>

For the record, my reasoning was: "*I know there are externals but this is
such an important feature that we shouldn't rely on externals for that and
have a native solution instead (I have made an external for that myself and
would gladly remove it from my library)*." I wasn't bragging about
externals I have or promoting them, sorry if I gave that idea...



>
> >>
> > yup, this is the issue, when splitting a file with a space, like
> > *Users/porres/Desktop/rename\
> > copy.pd*
> >
> > I get:
> >
> >   list / Users porres Desktop *list\ rename\ copy.pd*
> >
> > so for the file name I actually get *symbol list\ rename\ copy.pd*
>
> not for me.
> could you please provide a patch that shows this problem (without also
> requiring a copy of your harddisk; that is: the filename-with-space
> should be stored in the patch), and attach it to your bug-report.
>
&

Re: [PD] more features for [file] (Get directory of current patch)

2022-03-29 Thread Alexandre Torres Porres
Em sáb., 26 de mar. de 2022 às 03:46, IOhannes m zmölnig 
escreveu:

> > yeah, that's great. I have a n external that does that [slice]
>
> yeah. and zexy has [niagara] that does this.
> my git history only reaches back to 2002, and it was there back then.
>
> but i was really talking about [list split] here.
>

For the record, my reasoning was: "*I know there are externals but this is
such an important feature that we shouldn't rely on externals for that and
have a native solution instead (I have made an external for that myself and
would gladly remove it from my library)*." I wasn't bragging about
externals I have or promoting them, sorry if I gave that idea...



>
> >>
> > yup, this is the issue, when splitting a file with a space, like
> > *Users/porres/Desktop/rename\
> > copy.pd*
> >
> > I get:
> >
> >   list / Users porres Desktop *list\ rename\ copy.pd*
> >
> > so for the file name I actually get *symbol list\ rename\ copy.pd*
>
> not for me.
> could you please provide a patch that shows this problem (without also
> requiring a copy of your harddisk; that is: the filename-with-space
> should be stored in the patch), and attach it to your bug-report.
>
> gfmds
> IOhannes
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list


Re: [PD] [PD-announce] Pd 0.52-2 released

2022-03-29 Thread Christof Ressi
If you have an apple silicon, it'll run under the hood the arm code 
and then it will only find and load 'arm64' externals?
From my understanding, yes. For that reason, I guess it's not a good 
idea to provide universal binaries at this point and we should rather 
ship seperate binaries. Once most externals are available as universal 
binaries, we might ship Pd as a universal binary as well.


Of course, you can always force apps to run under Rosetta, but I don't 
think that's a good user experience.


Christof

On 29.03.2022 16:02, Alexandre Torres Porres wrote:
Em seg., 28 de mar. de 2022 às 07:17, Dan Wilcox 
 escreveu:


Howdy Miller,

the macOS 10.10+ build is working fine and supports both x86_64 &
arm64. I think you can remove the link to my previous 0.52-1
arm64-only build on the download page.


Great to know that, so let me see if I get it straight. If you have an 
apple silicon, it'll run under the hood the arm code and then it will 
only find and load 'arm64' externals? Or can you load both externals 
types? How does it work?


Oh, and Miller's site should say it is a universal binary ready for 
the new macs!


cheers



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


Re: [PD] [PD-announce] Pd 0.52-2 released

2022-03-29 Thread Alexandre Torres Porres
Em seg., 28 de mar. de 2022 às 07:17, Dan Wilcox 
escreveu:

> Howdy Miller,
>
> the macOS 10.10+ build is working fine and supports both x86_64 & arm64. I
> think you can remove the link to my previous 0.52-1 arm64-only build on the
> download page.
>

Great to know that, so let me see if I get it straight. If you have an
apple silicon, it'll run under the hood the arm code and then it will only
find and load 'arm64' externals? Or can you load both externals types? How
does it work?

Oh, and Miller's site should say it is a universal binary ready for the new
macs!

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


Re: [PD] how to write different types to [text]

2022-03-29 Thread Roman Haefeli
On Tue, 2022-03-29 at 10:55 +0200, Christof Ressi wrote:
> 
> How am I supposed to know that
> 
> 1 2 3, a b c, foo bar baz;
> actually counts as 3 "lines"?
> 
> I think a more proper term would be "message". I think the
> documentation has to be improved. @porres to the rescue!! :-)

+1

Roman


signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list


Re: [PD] how to write different types to [text]

2022-03-29 Thread Christof Ressi



Another side note: it would be nice if a negative field count for
[text get] would output all fields up to the next seperator (comma or semi).

I agree and it does so already.


I don't think so:

1 2 3 a b c d e f;

[0 3 -1( -> [text get]

gives me: "text get: bad field count (-1)"
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list


Re: [PD] how to write different types to [text]

2022-03-29 Thread Christof Ressi

You cannot _create_ lists ending with a comma, however. I propose a
'type' inlet in [text set] and [text insert], just for completeness and
consistency.

[11 12 13(  [2( [1( <- type
  |   /  /
[text insert ]

with above text buffer example would create:

1 2 3, foo bar baz, 11 12 13, 5 6 7;

Roman


This sounds reasonable! Also, we could add a "type" outlet to [text 
size], so I can know the type of a "line" without actually outputting 
its content. Maybe also for [text sequence].


Sorry again for the confusion. At least I could help you resolve your 
original issue :-)




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


Re: [PD] how to write different types to [text]

2022-03-29 Thread Christof Ressi

On 28.03.2022 22:43, Roman Haefeli wrote:


```
eins;
zwei;
drei, vier;
fuenf;
```

[text size] returns 5. [2(-[text get] returns 'symbol drei'. The
message after that is accessed with [3(-[text get].


Wow, you're right of course! *big facepalm* In all these years I never 
realized that comma seperate messages count as seperate "lines"!


The documentation of [text] only always speaks of "lines" and one would 
think that "line" would mean, well, "line of text".


From [text get]:

"text get" reads the nth line from the named text and outputs it.

From [text size]:

"text size" reports the number of lines in the text or the length of a 
specified line.

How am I supposed to know that

1 2 3, a b c, foo bar baz;

actually counts as 3 "lines"?

I think a more proper term would be "message". I think the documentation 
has to be improved. @porres to the rescue!! :-)


Christof

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