-=-incremental update suggestion-=-

Sep 11, 2006 at 7:09pm

-=-incremental update suggestion-=-

Hi, in regards to the incremental update I think it would be beneficial to remove externals which have found their way into the latest release. For example, there is seq~ which was built on 03-01-06, but that also coincides with the date of the build for Max/MSP 4.5.7 externals which makes it difficult to determine which one is best. And, earlier things like the multislider may or may not be applicable anymore. We just don’t know. Maybe it’s not the greatest idea to have an incremental update. I would rather not even fret about such a thing, personally.

#27573
Sep 13, 2006 at 8:20am

Dear James,

it’s your problem ! Pretty selfish here, not considering people (like
me) who don’t update on time because they don’t want to change the main
software they’re working on while their actual projects aren’t done.
Incremental update is awsome. Thanks again to C74.

f.e

f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|

James Aldridge wrote:
> Hi, in regards to the incremental update I think it would be beneficial to remove externals which have found their way into the latest release. For example, there is seq~ which was built on 03-01-06, but that also coincides with the date of the build for Max/MSP 4.5.7 externals which makes it difficult to determine which one is best. And, earlier things like the multislider may or may not be applicable anymore. We just don’t know. Maybe it’s not the greatest idea to have an incremental update. I would rather not even fret about such a thing, personally.
>
>
>
>

#83497
Sep 13, 2006 at 8:46am

It may be interesting to note somewhere in the incremental update page
from which Max’ version an object is included in the standard
distribution and shouldn’t be used anymore. But indeed, I’d be happy if
I could for instance update an Max 4.3 version as much as possible
(even the v3 I’m still using for some projects).

On 13 sept. 06, at 10:20, f.e wrote:

> it’s your problem ! Pretty selfish here, not considering people (like
> me) who don’t update on time because they don’t want to change the
> main software they’re working on while their actual projects aren’t
> done. Incremental update is awsome. Thanks again to C74.

> James Aldridge wrote:
>> Hi, in regards to the incremental update I think it would be
>> beneficial to remove externals which have found their way into the
>> latest release. For example, there is seq~ which was built on
>> 03-01-06, but that also coincides with the date of the build for
>> Max/MSP 4.5.7 externals which makes it difficult to determine which
>> one is best. And, earlier things like the multislider may or may not
>> be applicable anymore. We just don’t know. Maybe it’s not the
>> greatest idea to have an incremental update. I would rather not even
>> fret about such a thing, personally.

#83498
Oct 2, 2006 at 12:00pm

Don’t ever say we don’t listen to our beloved customers! The incremenal updates site has been remodelled, and a few new updates have appeared, as well. Please feel free to comment on usability issues with the new layout.

http://cycling74.com/twiki/bin/view/IncrementalDownloads/WebHome

jb

#83499
Oct 2, 2006 at 1:27pm

Woah ;)

#83500
Oct 2, 2006 at 6:35pm

#83501
Oct 2, 2006 at 8:17pm

My build-in stereo output has become mono – everything is being sent out
both speakers. It is not only maxmsp, where I get no panning between dac
output 1 and 2. Also audacity doesn’t pan a mono file, and apple’s sound
configuration app. gives me identical output from both speakers when
hitting either the left or right speaker button.

So, the problem must be burried somewhere in the system setup – but
where? Did trash com.apple.audio.DeviceSettings.plist but no cigar.

Pbook G4, OSX10.4.7

*L

#83502
Oct 2, 2006 at 8:34pm

Lars, you should start a new post to make sure your problem is seen by the whole list.

#83503
Oct 2, 2006 at 10:03pm

On Oct 2, 2006, at 1:17 PM, Lars Graugaard wrote:

> My build-in stereo output has become mono – everything is being
> sent out both speakers. It is not only maxmsp, where I get no
> panning between dac output 1 and 2. Also audacity doesn’t pan a
> mono file, and apple’s sound configuration app. gives me identical
> output from both speakers when hitting either the left or right
> speaker button.
>
> So, the problem must be burried somewhere in the system setup – but
> where? Did trash com.apple.audio.DeviceSettings.plist but no cigar.
>
> Pbook G4, OSX10.4.7
>

I had the same exact problem on my PB G4//OS X 10.4.8 — but I was
able to solve the mono output by going into the ‘audio MIDI setup’
and switching the output from 1ch-16bit -> 2ch-16bit under the Audio
Output settings

not sure how this got switched while installing Max/MSP but once I
changed this setting and rebooted Max the audiotester patch in extras
seemed to indicate all was well again

#83504
Oct 3, 2006 at 12:50am

Well, my ‘audio MIDI setup’ only has 2ch-16bit and 2ch-24bit settings to
choose from. I already tried to mess around with them and other settings
in there to see if I could trick the machine into giving me my 2
channels back, but so far no luck.

I am actually suspecting some audio driver hick-up and will try to
remove all except those in the present ad folder.

Anybody else having experienced this weird behaviour?

Kim Cascone wrote:
>
> On Oct 2, 2006, at 1:17 PM, Lars Graugaard wrote:
>
>> My build-in stereo output has become mono – everything is being sent
>> out both speakers. It is not only maxmsp, where I get no panning
>> between dac output 1 and 2. Also audacity doesn’t pan a mono file, and
>> apple’s sound configuration app. gives me identical output from both
>> speakers when hitting either the left or right speaker button.
>>
>> So, the problem must be burried somewhere in the system setup – but
>> where? Did trash com.apple.audio.DeviceSettings.plist but no cigar.
>>
>> Pbook G4, OSX10.4.7
>>
>
> I had the same exact problem on my PB G4//OS X 10.4.8 — but I was able
> to solve the mono output by going into the ‘audio MIDI setup’ and
> switching the output from 1ch-16bit -> 2ch-16bit under the Audio Output
> settings
>
> not sure how this got switched while installing Max/MSP but once I
> changed this setting and rebooted Max the audiotester patch in extras
> seemed to indicate all was well again
>
>
>
>

#83505
Oct 3, 2006 at 3:10pm

On Oct 2, 2006, at 5:51 PM, Lars Graugaard wrote:

> Well, my ‘audio MIDI setup’ only has 2ch-16bit and 2ch-24bit
> settings to choose from.
are you using a Firewire audio I/O? I am assuming you are if you are
able to choose 2ch-24bit from the output choices

> I already tried to mess around with them and other settings in
> there to see if I could trick the machine into giving me my 2
> channels back, but so far no luck.
>
> I am actually suspecting some audio driver hick-up and will try to
> remove all except those in the present ad folder.
that would be my guess…

>
> Anybody else having experienced this weird behaviour?
sorry my solution wasn’t able to help you…
send me an email off list and let me know what the problem was when
you get it sorted out?

#83506
Oct 9, 2006 at 11:39am

Hi,

I tried already al lot off times to make a kind of automatic sound
peak limiter/corrector. Before the output of the MAXMSP patch i wanna
have a smooth automatic limiter/corrector so that if the sound goes
to high in volume the volume is corrected smooth and automatic.

Is there an example or external that does that nice?

regards, bart

#83507
Oct 9, 2006 at 12:21pm

u mean something like a limiter msp object…

http://www.cycling74.com/twiki/pub/Share/Jhno/limi031204.sit

#83508
Oct 9, 2006 at 12:58pm

#83509
Oct 9, 2006 at 2:14pm

This is a compressor made with native max objects:

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#N vpatcher 635 335 1069 715;
#P window setfont “Sans Serif” 9.;
#P newex 56 104 34 196617 /~ 2.;
#P newex 56 85 27 196617 +~;
#P newex 37 248 53 196617 gate~ 2 1;
#P newex 79 268 35 196617 *~ 1.;
#P newex 37 298 35 196617 *~ 1.;
#N comlet (signal) Out L;
#P outlet 37 320 15 0;
#N comlet (signal) In L;
#P inlet 39 41 15 0;
#P newex 353 201 29 196617 * 0.;
#P newex 353 182 29 196617 t b f;
#P newex 353 144 31 196617 !/ 1.;
#P newex 353 163 30 196617 !- 1.;
#N comlet (float) release;
#P inlet 201 41 15 0;
#P newex 201 60 94 196617 prepend rampdown;
#P newex 114 60 81 196617 prepend rampup;
#P newex 114 228 34 196617 +~ 1.;
#P newex 114 248 53 196617 gate~ 2 1;
#P newex 114 208 39 196617 >~ 0.2;
#P newex 283 221 40 196617 +~ 0.2;
#P newex 256 241 37 196617 !/~ 1.;
#P newex 283 201 34 196617 /~ 3.;
#P newex 114 147 125 196617 rampsmooth~ 1000 1000;
#P newex 156 268 35 196617 *~ 1.;
#P newex 56 123 31 196617 abs~;
#P newex 114 298 35 196617 *~ 1.;
#N comlet (float) treshold;
#P inlet 314 41 15 0;
#N comlet (float) makeup gain;
#P inlet 378 41 15 0;
#N comlet (signal) In R;
#P inlet 73 41 15 0;
#N comlet (float , ms) attack;
#P inlet 114 41 15 0;
#N comlet (float) ratio;
#P inlet 353 41 15 0;
#N comlet (signal) Out R;
#P outlet 114 320 15 0;
#P connect 15 0 27 0;
#P connect 27 0 25 0;
#P connect 26 0 25 0;
#P connect 25 0 24 0;
#P connect 23 0 28 0;
#P connect 28 0 29 0;
#P connect 29 0 7 0;
#P fasten 4 0 25 1 383 296 67 296;
#P connect 3 0 28 1;
#P connect 27 1 26 0;
#P connect 23 0 27 1;
#P connect 11 0 26 1;
#P connect 2 0 16 0;
#P connect 7 0 9 0;
#P connect 16 0 9 0;
#P connect 17 0 9 0;
#P connect 9 0 13 0;
#P connect 13 0 15 0;
#P connect 15 0 14 0;
#P connect 8 0 6 0;
#P connect 14 0 6 0;
#P connect 6 0 0 0;
#P fasten 4 0 6 1 383 296 144 296;
#P connect 5 0 13 1;
#P connect 14 1 8 0;
#P connect 3 0 14 1;
#P connect 11 0 8 1;
#P connect 18 0 17 0;
#P connect 9 0 11 0;
#P connect 9 0 10 0;
#P connect 10 0 12 0;
#P connect 12 0 11 1;
#P connect 1 0 10 1;
#P connect 22 0 12 1;
#P connect 1 0 20 0;
#P connect 20 0 19 0;
#P connect 19 0 21 0;
#P connect 5 0 22 0;
#P connect 21 0 22 0;
#P connect 21 1 22 1;
#P pop;
#P newobj 24 186 92 196617 p compressor;
#P window clipboard copytext “p compressor” #E;
#P window clipboard copycount 1;

Cheers,
Mattijs

#83510
Oct 9, 2006 at 2:21pm
#83511
Oct 9, 2006 at 2:34pm

#83512
Oct 11, 2006 at 11:47am

#83513

You must be logged in to reply to this topic.