Anyone ported X.FM~ yet?

[stringtapper]

I've been so busy I haven't done much Max-ing in a while, but if someone hasn't done it already I may make a late-summer project out of porting the X.FM~ synth to M4L.

[Machinate]

where's this patch? in the max subfolders?

[pid]

Max > Extras > ExamplesOverview > Latest > Synth > X.FM~

or

Max Application Folder / examples / synths / FMsynth

...it's been there for the last 2 years, since Max5 launched. It is a truely beautiful piece of Max patching by, yes you guessed it, Mr Manuel Poletti, again.

i study his patches weekly, and learn new things every time. simple and perfect and powerful, each and every one.

i think your man behind the bloc controller has ported a specific bloc version of it too, somewhere.

[Machinate]

Ayups. Create a new object; name it as mentioned above, then wait a moment for the program to load and presto. Double click to open.

haha, oh yeah. Brainfart there. Cheers to both of you.

[Machinate]

oh yeah, I remember this one.

I've got the basics up and running now in MaxForLive. The big challenge is redoing the interface in tabs or something to fit in the Live scheme of things.
- or would people prefer it had a pop out window?

(god I hate the device view limitations in Live right now!)

[stringtapper]

oh yeah, I remember this one.

I've got the basics up and running now in MaxForLive. The big challenge is redoing the interface in tabs or something to fit in the Live scheme of things.
- or would people prefer it had a pop out window?

(god I hate the device view limitations in Live right now!)

Yeah the interface is really the bulk of the work. Seems like a tabbed interface a la Sampler would be the most Ableton-y solution, but a pop-out window would be very cool (and probably less work).

[pid]

the thing is, there are SO SO many infuriating issues with using pop out windows. i prefer the tabs approach these days. i worked with pop outs a lot, and they are great whilst device building, but as soon as you start putting the thing through its paces you run in to huge issues with threads / defer / deferlow / oops wrong place / damn what gets stored. ever tried opening a pop out window in the middle of a cpu crunching set whilst playing? even though you thought you'd got the hang of deferlow? yes, it gets really yucky.

i think there is some mythical/secret formula for how to init m4l patches and how to queue priority things (defer etc) that cycling 74 are not telling us just to keep maxforlive interesting for all us suckers.

pop outs are only any use for standalone tasks like 'settings', 'prefs', 'help files' etc.

my two cents. must be having a boring afternoon here sorry.

[hoffman2k]

Do you mean that by just having the patch inside a patcher object and opening that patcher with the thispatcher commands somehow alters the signal flow? (my lord what a sentence...)
If so, sounds like a major bug that needs looking at.

I can't confirm such behavior. I'm also sure there isn't something mystical going on in the loading order.
Ask somebody from Cycling and they'll probably link you to a reference page on this or to paraphrase: First the devices and everything else in the set is loaded, then the pattr content and then the loadbangs. I left some stuff out there cause I can't recall the correct order. I'd look for the ref page (if there is one on this) but I'm getting 404's.

[broc]

Ask somebody from Cycling and they'll probably link you to a reference page on this or to paraphrase: First the devices and everything else in the set is loaded, then the pattr content and then the loadbangs.

Actually that's not true.
There was a lengthy discussion about loading order on the cycling forum where developer Jeremy Bernstein explained this:

When a device is opened in Live, the entire patch is loaded/created, just like in Max, loadbangs are serviced and so on. Automated parameters, however, do nothing until Live initializes their values. We tell Live what the initial value should be and Live, after the patch has loaded (incl. loadbang servicing), sends the value. So the order is loadbang, then parameters.

When a device is opened in Max, we have complete control over the process, and the loadbang sequence services parameters first, then loadbangs.

Quoted from this thread
http://cycling74.com/forums/topic.php?id=25322

[hoffman2k]

Ask somebody from Cycling and they'll probably link you to a reference page on this or to paraphrase: First the devices and everything else in the set is loaded, then the pattr content and then the loadbangs.

Actually that's not true.
There was a lengthy discussion about loading order on the cycling forum where developer Jeremy Bernstein explained this:

When a device is opened in Live, the entire patch is loaded/created, just like in Max, loadbangs are serviced and so on. Automated parameters, however, do nothing until Live initializes their values. We tell Live what the initial value should be and Live, after the patch has loaded (incl. loadbang servicing), sends the value. So the order is loadbang, then parameters.

When a device is opened in Max, we have complete control over the process, and the loadbang sequence services parameters first, then loadbangs.

Quoted from this thread
http://cycling74.com/forums/topic.php?id=25322

Well it wouldn't be the first time I got something backwards with Max. Luckily there's always somebody else who read the same or similar

[Machinate]

hm.. Okay, does anyone have any hints as to how to quickly set up a tabbed interface? I wonder if there's a tutorial for it. Would dig in, seems simple enough to split the interface up a bit to make it workable.

[pid]

hi machinate.

i tend to do something like this:

Code: Select all

<pre><code>
----------begin_max5_patcher----------
1767.3oc6Zs0iZiCE9YleEQo8woH6DBA180c01G51pUZeqpBYHFv6DrQIF5z
V0+6qicBXGhSLWWl1UZjYR7si+NW74R91C87mxdFm668KdezqWuu8PudxWU7
hdkO2yeE54Yonb4v7o3Oyl9O9Op5hielKecJCkrBmm6Ap5ZNixyIeEWzMLnO
n70zMqHzTLWtZPswRQqji0+s3zsXNYFx683MX+8yisgWehqQ7YKIzESxvy3p
iAbzXwl4E.JZiCj+OrOv6SkSgjH2Ewg3MvQUqtZo4eYMVsH99depnmu+vCEM
O5J3rY0Tb1MAABri.Cjal3GIDDAZEBhsBADJ2+QO+oH5hWxnQo7fanQzUDMZ
VwYsGa97bL+NQsYzHIJAaEkBaSsQeKDbeEfThHBRljh2hyxILpFA0yeOgHYP
xlgCj+LXDXOcHP4EorYOgkjCn5kI34tuBr0XZSitpwbjD55LbNlxQ7RhVeWQ
aR4SZlmY1+bzLr0I2NSrm+hLRBiVPMFKQwqq1WAGTx.KZ2e.jifhV2vj4LV5
TT1VRNYZJ1fYHDjQTxJDWPJJBK.radjUqyJTFzWKLEIVik4yxXooFKkpmsMz
SBdKYF9yjD9R4ZsG1LtSRS3wPEy38sopYptkiS8.dP89rv8ro04nlWCZegZ8
zfFnxzDDH+Y7AZfGnEBz2oCzDkFpdb+ukFs5UY3R8OOdhHbwU8nE3FgXPeAy
7T.3fyEfgNAvgQE+DN3.skZ.73Vw2aJd9F3f6SHczPMHMJnKHM9NARUW458Z
n2qCtikTGJuLNtSI0naHrJAAea.C37NwpqqChpZsZ6C15IVd8j9TmwVsBqty
x2+BBFpc12kaLLQCfKnQvfXGgCCg3tNr68NHkPscQqjnJ5uYTHmsIaVEbWZr
zyj9Rv4bBcmSSebmnZswsjjjX5ZhDlIIqYB9XI44nH7wR0wuHo5HGo5Bwh6H
xtPo0M5FbeQ2.Go6w2ejMzAxN9BR1kuTP+pn.yQawISD6hvz1DDmmQltgqr4
XDUXSAHYKpJQ7eSQokwWt6lW+KdPWtLFaQ.9vdb4HSSvzp.mqhiVK3S8v0Gq
bQHVc4v.kqWFQr2XJCN1zlDDO15FTOtX3goJnkLE7nd1BPYK1IVU9J7popf7
gmaFE59nTjUgYrTVV4DjCXWyQl9AW1tyMEDvePSAA3xkBBf0TP.tAof354Yn
xQ4Pv0v0v6M+fChGcbmV3s3zlR1h6mmRR1YkVNlsn82FMSHY+lDDGoO.KlxG
pNb.UXdAwprUW6P5HdF3DdFBBZaurYroFXOp8nNE12mmxP0hDaMJSfQbb1Dk
ZY80mkQrs0yyXeESmH3Q07jPraM.s56pxMjcypAOQL42ELyzMX1b8t06W+fH
7I6oBFecViwfVwRD+gqIyaLDBcNyvUl5Cfkknt9y1JrgRThAVWh70XbRJYUa
qRNGuNusAfeVXLuTwB1uUhg+kzVOyqDJVpqrh6aeLDpo445inRryNxR3DTpl
Hm0y9RVF2PK1qlVbsEtg6tZh028oDQorR42C7o8.INFcQqlZNX+2gf6GxNCg
5+6Ev5XkU2lx61ZRhWJ4Ibt2eillaKyaAA8gCGObTP21NCUNbDMt+XH..FHr
iFJMpEF5pAzSJ+cccuETZmMXX2zkiFaG3eFVBufb20HJNUmVltypjNka3NMn
+vG0ZZ65lI0bJFFZ2I5KmaFvAppsnxzZvvp1SgQYVVlL1FZhQXL0BvFdevVa
ohY7kjbyXRusUMqCWZTRFgkoJuyplE2oSKG54PYmu58Eca.Gd9+ZQyq9qhVL
MQ8lWB4auRh2M+pG1UAFtUdcW7IkHFsEutsLDaoPADtu7JgpBYEcUb6NTcc.
LFzxV4n8knqgW2uHbsF7+tV+iiq0Mqpd24bsCj4cj60u82e269f2ehJr+f33
Kf+0JegDlutGcuFFN3R4dcvOmtWCtcNWCCCOemqG+eou0Wk5lOx0ZhBOspzE
LJtejPuP8g5n+zUpriCc7.E+SUI0CCj.efRIHBLd2SsWF0Sn.hbzzN9VhENf
QVP0q+2AVY7Ew3LqPO9KFtGTNPCiOFktxV4AOrvhvHkD4.UL2AcU3xi9acNr
yZaV9UN2.E3PkMgc8khaVfSciU64D7hrfol0e7gO7aESIeIYuG19q1jxIUxw
lLAFsC1vIH6ne8SCBENdsyktl0SQydZgD.sWIaPKb6xssLX2SrR1UdHXvI0f
X4ZYdyfBwqaJpD2OvDTn9mqgMyOFVMOzzScyNCDmxnhOqtAxezdxh3wwPrft
H1niiXgiGoQr5OclDKbjKT6oQrQ5zZz4Spt.rgmDoBGGpQqxmNWh0EX8zH1Q
JU18OXPphG99C+KfrrgNV
-----------end_max5_patcher-----------
</code></pre>

... REMEMBER TO VIEW / OPEN IN PRESENTATION MODE. of course.

it is just a very simple thing - but remember silly details like what gui object is in front / back / locked / etc...

it works embedding sub-BPatchers to your hearts content, too.

this device has a good tabbed interface worth looking at, for example:
http://www.maxforlive.com/library/device.php?id=245

cheers,
pid .

[bulo]

Do you mean that by just having the patch inside a patcher object and opening that patcher with the thispatcher commands somehow alters the signal flow? (my lord what a sentence...)
If so, sounds like a major bug that needs looking at.

At least, there's a major bug with pop-up windows:
Try midi-mapping a knob inside a floating window and tweeking it with your controller...

[pid]

as always, bulo is right.

and THEN, whilst doing bulo's midi experiment, try opening / closing said window programatically using pcontrol, whilst the set / device is 'running'.

then try a defer, then a deferlow, before the pcontrol. anyway, you will soon be pulling your hair out if there is any degree of gui complexity whatsoever.

for the record, i adore my m4l (!)

[bulo]

as always, bulo is right.

Exactly!! That's the point dude!
(I owe you a beer!)
I love myself.