ArrayArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2009-07-15T12:06:01+02:00 https://brainmodular.com/forums/app.php/feed/topic/1656 2009-07-15T12:06:01+02:00 2009-07-15T12:06:01+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9722#p9722 <![CDATA[max vs usine]]>
Up to me, the main and first advantage for USINE VS MAX is that: after programming your patch is represented in a user friendly environment !

for synthesis (FM, additvie...) MAX is more extended.

we can use this maxim:

"...whith max you learn programming, whith usine you play music..."

Statistics: Posted by cybercharles — 15 Jul 2009, 12:06

]]> 2009-07-15T11:37:14+02:00 2009-07-15T11:37:14+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9718#p9718 <![CDATA[max vs usine]]> - conductor (snapshots for master, patches and subpatches!)
- easy midi learn everywhere for everything
- nice interface objects for quick parameter automation
- integrated GUI design
- sequencer
.. some of the points are surely possible with max too. still, it may also show advantages over other music programming softs like bidule, PD, audiomulch, synthedit, synthmaker..
2) Max has an object approach: you put object on a patch and you exchange informations by 'messages'. (typically in the 80's style of programming ?). At the contrary Usine has a flux approach like a guitar player and his 'pedals' connected by cables. It's a newer approach.
as said i am not a max user, but i wouldnt agree 'message-based' is not as a good as 'flux-based'.
as i understand it 'flux-based' relates to the behavior of a constantly running analog oscillator, while 'message-based' is something like a digitial midi keyboard. in Usine mostly everything (besides midi) behaves like oscillators - control data communication too.
this surely reminds of how real hardware works, as senso says.

and in Usine a lot of stuff is faster to do. on the other hand u got to use a lot of event control modules (hasChanged etc.) when u want a, say, 'message-based' behavior. i'd conclude 'flux-based' is just another attenuation?however, i like it this way - its more 'organic' :)

Statistics: Posted by amiga909 — 15 Jul 2009, 11:37

]]> 2009-07-15T09:29:55+02:00 2009-07-15T09:29:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9711#p9711 <![CDATA[max vs usine]]> 1) Usine has more macroscopic modules, and you can patch faster
2) Max has an object approach: you put object on a patch and you exchange informations by 'messages'. (typically in the 80's style of programming ?). At the contrary Usine has a flux approach like a guitar player and his 'pedals' connected by cables. It's a newer approach.

Statistics: Posted by senso — 15 Jul 2009, 09:29

]]> 2009-07-14T16:28:57+02:00 2009-07-14T16:28:57+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9702#p9702 <![CDATA[max vs usine]]> Thanks for your input though

blugaruda

Statistics: Posted by blugaruda — 14 Jul 2009, 16:28

]]> 2009-07-14T10:46:55+02:00 2009-07-14T10:46:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9694#p9694 <![CDATA[max vs usine]]> max msp is a general multimedia programming application, with much more low level programming facilities. usine on the other hand is a music application that has its focus on the creation of live setups. there is no non-programmer approach to max, whereas usine serves both programmers and musicians.

i guess u could do everything in max what u can do in usine. but it would take much more time.

never done something with max msp thu.

Statistics: Posted by amiga909 — 14 Jul 2009, 10:46

]]> 2009-07-14T08:57:22+02:00 2009-07-14T08:57:22+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9693#p9693 <![CDATA[max vs usine]]> What do you feel the main differences between max msp and usine are?

Statistics: Posted by blugaruda — 14 Jul 2009, 08:57

]]> BrainModular BrainModular Users Forum 2009-07-15T12:06:01+02:00 https://brainmodular.com/forums/app.php/feed/topic/1656 2009-07-15T12:06:01+02:00 2009-07-15T12:06:01+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9722#p9722 <![CDATA[max vs usine]]>
Up to me, the main and first advantage for USINE VS MAX is that: after programming your patch is represented in a user friendly environment !

for synthesis (FM, additvie...) MAX is more extended.

we can use this maxim:

"...whith max you learn programming, whith usine you play music..."

Statistics: Posted by cybercharles — 15 Jul 2009, 12:06

]]> 2009-07-15T11:37:14+02:00 2009-07-15T11:37:14+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9718#p9718 <![CDATA[max vs usine]]> - conductor (snapshots for master, patches and subpatches!)
- easy midi learn everywhere for everything
- nice interface objects for quick parameter automation
- integrated GUI design
- sequencer
.. some of the points are surely possible with max too. still, it may also show advantages over other music programming softs like bidule, PD, audiomulch, synthedit, synthmaker..
2) Max has an object approach: you put object on a patch and you exchange informations by 'messages'. (typically in the 80's style of programming ?). At the contrary Usine has a flux approach like a guitar player and his 'pedals' connected by cables. It's a newer approach.
as said i am not a max user, but i wouldnt agree 'message-based' is not as a good as 'flux-based'.
as i understand it 'flux-based' relates to the behavior of a constantly running analog oscillator, while 'message-based' is something like a digitial midi keyboard. in Usine mostly everything (besides midi) behaves like oscillators - control data communication too.
this surely reminds of how real hardware works, as senso says.

and in Usine a lot of stuff is faster to do. on the other hand u got to use a lot of event control modules (hasChanged etc.) when u want a, say, 'message-based' behavior. i'd conclude 'flux-based' is just another attenuation?however, i like it this way - its more 'organic' :)

Statistics: Posted by amiga909 — 15 Jul 2009, 11:37

]]> 2009-07-15T09:29:55+02:00 2009-07-15T09:29:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9711#p9711 <![CDATA[max vs usine]]> 1) Usine has more macroscopic modules, and you can patch faster
2) Max has an object approach: you put object on a patch and you exchange informations by 'messages'. (typically in the 80's style of programming ?). At the contrary Usine has a flux approach like a guitar player and his 'pedals' connected by cables. It's a newer approach.

Statistics: Posted by senso — 15 Jul 2009, 09:29

]]> 2009-07-14T16:28:57+02:00 2009-07-14T16:28:57+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9702#p9702 <![CDATA[max vs usine]]> Thanks for your input though

blugaruda

Statistics: Posted by blugaruda — 14 Jul 2009, 16:28

]]> 2009-07-14T10:46:55+02:00 2009-07-14T10:46:55+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9694#p9694 <![CDATA[max vs usine]]> max msp is a general multimedia programming application, with much more low level programming facilities. usine on the other hand is a music application that has its focus on the creation of live setups. there is no non-programmer approach to max, whereas usine serves both programmers and musicians.

i guess u could do everything in max what u can do in usine. but it would take much more time.

never done something with max msp thu.

Statistics: Posted by amiga909 — 14 Jul 2009, 10:46

]]> 2009-07-14T08:57:22+02:00 2009-07-14T08:57:22+02:00 https://brainmodular.com/forums/viewtopic.php?t=1656&p=9693#p9693 <![CDATA[max vs usine]]> What do you feel the main differences between max msp and usine are?

Statistics: Posted by blugaruda — 14 Jul 2009, 08:57

]]>