Re: [PD] Test audio and MIDI window doesnt appear
Strange, I'll take a long on my Ubuntu. Does this work ok with different versions of Pd? How about the version that comes with Ubuntu Studio? .hc On Jul 27, 2007, at 2:49 PM, Javier García wrote: Hi to all, when i open Media menu i find default-MIDI activated. Then i go to Test audio and MIDI and i open the window normally, but if i activate then OSS, ALSA, jack or ALSA MIDI Nothing appears when i press Test audio and MIDI any idea? Pd version 0.39.2-extended-rc5 Intel Core Duo/Ubuntu Studio 7.04 br. Javi _ ¿Estás pensando en cambiar de coche? Todas los modelos de serie y extras en MSN Motor. http://motor.msn.es/researchcentre/ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list http://at.or.at/hans/ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [Gem] pix-native?
Most VJs use something very lightly compressed, and use a spatial only compressor, non temporal codec (some call these editing vs delivery codecs or intra vs interframe encoding). This makes it easier to seek to a frame (scratching and jumping around, etc) More than likely you will be fine with photojpeg (for progressive) and motion jpeg-b (for interlaced footage) at around 75% quality. Compressions is a tradeoff with bandwidth and cpu time spent decoding. For example Uncompressed 1080i is around 170/sec. Uncompressed Standard Def NTSC around 27MB/s (not including audio streams) Compare to HDV and DV which is 3.6MB/sec more here : http:// www.apple.com/xsan/videoworkflow.html Jpeg codecs live in the middle of that realm, depending on your quality setting, framesize and frames per second. If you can sustain the datarates for the number of streams you want the uncompressed will always win with ease of CPU decoding, at the expense of being NASTILY hard on your drives. In other words, Chris was saying, there is no universal answer and you will have to do some testing. On Jul 29, 2007, at 11:36 PM, yonsei wrote: Hi, I see. I am running powerbook G4 1.67 with OS 10.4.10 thank you Baruch On Jul 30, 2007, at 2:03 AM, chris clepper wrote: The answer depends a lot on your OS and hardware. On 7/29/07, yonsei [EMAIL PROTECTED] wrote: Hi, Is there a 'native' container or codec for [pix_film], in terms of minimizing cpu load in rendering to gemwin? I guess qt mov would be the preferred container, but is there anything better? What about codecs? I have gotten about 33% less load (than photojpeg) by using uncompressed qt, but is there anything better? thanks! Baruch ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list v a d e // www.vade.info abstrakt.vade.info ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [Gem] pix-native? [RAM disk]
vade wrote:
If you can sustain the datarates for the number of streams you want the
uncompressed will always win with ease of CPU decoding, at the expense
of being NASTILY hard on your drives.
Chris also suggested using a RAM disk, which would save a lot of wear
and tear on the HD in the case of uncompressed video.
I did some research on RAM disks for OS X. Seems like you can skip
buying a license for Rambunctious and just use the command line. I
promised Baruch that I would post on this, so some recipes follow,
copied from various internet sources...
best,
d.
*
#!/bin/sh
NUMSECTORS=524288
# 64mb = 131072
# 128mb = 262144
# 256mb = 524288
# 512mb = 1048576
# 1gb = 2097152
mydev=`hdid -nomount ram://$NUMSECTORS`
newfs_hfs $mydev
mkdir /tmp/ramdrive
mount -t hfs $mydev /tmp/ramdrive
Save the file with a name like 'mkramdisk.sh', and give it executable
permissions:
chmod 755 mkramdisk.sh
Run it. Voila. This script is right out of the man page for hdid. You
can also read about doing this at
http://www.kernelthread.com/mac/osx/arch_fs.html
Creating a RAM disk was easy in 9, and, until now, undocumented in X.
There is a utility called ramBunctious (available at VersionTracker)
that brings this functionality back to X (well, at least it puts a GUI
on it).
For those of you interested in how this works from the command line, its
pretty simple. First, create a read/write disk image (you can do this in
Disk Copy). Next, create the /dev entry for RAM using the hdid tool.
Finally, copy the contents of the disk image to the RAM /dev entry and
mount it. Because the disk image is mounted from the /dev entry, any
changes occur in RAM. Here are the Terminal commands:
[First, calculate the number of 512K blocks you need: numblocks = (image
size in MB) * 2048; for example: 5MB = 10240 blocks]
% hdid -nomount ram://numblocks
[result: /dev/disk1]
% dd if=/path/to/image/file.dmg of=/dev/disk1 bs=512
[result:2866+0 records in
2866+0 records out
1467392 bytes transferred in 1 secs (1467392 bytes/sec)]
% hdiutil mount /dev/rdisk1
You need to change the 1 in disk1 and rdisk1 to whatever number is
returned by the first command.
Please be sure to check out ramBunctious; it has excellent documentation
on the state of RAM disks in X and when you should/should not use them.
The reason I mention it here is because it could have a huge positive
impact on the functionality of a bootable X cd.
**
How to create a RAM disk on OS X
32768 = size in sectors (16MB in this case, a sector is 512 bytes)
$ hdid -nomount ram://32768
/dev/disk1
$ newfs_hfs /dev/disk1
$ mkdir /tmp/ramdisk1
$ mount -t hfs /dev/disk1 /tmp/ramdisk1
To unmount:
hdiutil detach /dev/disk1
to osx files tiger ramdisk ram disk by peter on Thu Mar 30 16:25:22 EST 2006
**
I have thrown together a quick script for anybody that wants to create a
ramdisk regularly. It's flexible enough for me, but can be edited to
offer more options (if u know a little .sh scripting). The disk is
dynamicly named and will show up on the desktop when the script is
finished. Unmounting can be done as any drive in the finder. The major
differences between my and the above approach is that I use diskutil to
mount the created drive, so Finder likes it better, and i give the
volume a label, so it can be better recognized by the user ...
Here it is:
Leila:~ samynew[14:30:55]$ cat ramdisk
#!/bin/bash
if [ -n $2 ]; then ARG_ERR=ERR; fi
if [ -z $1 ]; then ARG_ERR=ERR; fi
if [ -n $ARG_ERR ];
then
echo 1 argument: size in MB
exit
fi
MB_SIZE=$1
let MB_SIZE *= 2048
echo Creating ${MB_SIZE} 512-blocks ramdisk
CREATED_RAMDISK=`hdid -nomount ram://${MB_SIZE}`
echo New block device: ${CREATED_RAMDISK}
DISK_NAME=`basename ${CREATED_RAMDISK}`
echo Creating volume with label: ${DISK_NAME}
newfs_hfs -v ${DISK_NAME} /dev/r$CREATED_RAMDISK
echo Mounting in /Volumes/${DISK_NAME}
mkdir /Volumes/${DISK_NAME}
diskutil mount ${CREATED_RAMDISK}
Make sure it's chmodded to be executable: chmod u+x ramdisk
Run as: ./ramdisk size-in-MB
For those of you interested in how this works from the command line,
it's pretty simple. First, create a read/write disk image (you can do
this in Disk Copy). Next, create the /dev entry for RAM using the hdid
tool. Finally, copy the contents of the disk image to the RAM /dev entry
and mount it. Because the disk image is mounted from the /dev entry, any
changes occur in RAM. Here are the Terminal commands:
First, calculate the number of 512K blocks you need: numblocks = (image
size in MB) * 2048; for example: 5MB = 10240 blocks. Open a terminal and
type:
% hdid -nomount ram://numblocks
[result: /dev/disk1]
Replace numblocks with the number you calculated in the first step. Next
type:
% dd if=/path/to/image/file.dmg of=/dev/disk1 bs=512
[result:2866+0 records in
2866+0 records out
1467392 bytes transferred in 1 secs (1467392 bytes/sec)]
% hdiutil mount
Re: [PD] [Gem] pix-native? [RAM disk]
hi,
some sources suggest that there is no or little advantage to use a
ramdisk in os x because the system caches data which has frequent
access anyway.
so a ramdisk can be counterproductive in a cenario where you have
little ram:
lets say you have one gig memory. 300 mb are used by some
applications which are open, and another 300 by the system. now you
have a video in your ramdisk of also 300. the system tries to cache
it because it wants to accellerate but can't allocate enough anymore
and data will be swaped on the harddisk..
so you end up with less performance and more harddrive access because
of the ramdisk..
i'm curious about your findings.
greetings, m.
http://lowendmac.com/x-basics/02/0201.html
http://www.kernelthread.com/forums/viewtopic.php?t=138
Am 30.07.2007 um 10:08 schrieb Derek Holzer:
vade wrote:
If you can sustain the datarates for the number of streams you
want the
uncompressed will always win with ease of CPU decoding, at the
expense
of being NASTILY hard on your drives.
Chris also suggested using a RAM disk, which would save a lot of wear
and tear on the HD in the case of uncompressed video.
I did some research on RAM disks for OS X. Seems like you can skip
buying a license for Rambunctious and just use the command line. I
promised Baruch that I would post on this, so some recipes follow,
copied from various internet sources...
best,
d.
*
#!/bin/sh
NUMSECTORS=524288
# 64mb = 131072
# 128mb = 262144
# 256mb = 524288
# 512mb = 1048576
# 1gb = 2097152
mydev=`hdid -nomount ram://$NUMSECTORS`
newfs_hfs $mydev
mkdir /tmp/ramdrive
mount -t hfs $mydev /tmp/ramdrive
Save the file with a name like 'mkramdisk.sh', and give it executable
permissions:
chmod 755 mkramdisk.sh
Run it. Voila. This script is right out of the man page for hdid. You
can also read about doing this at
http://www.kernelthread.com/mac/osx/arch_fs.html
Creating a RAM disk was easy in 9, and, until now, undocumented
in X.
There is a utility called ramBunctious (available at VersionTracker)
that brings this functionality back to X (well, at least it puts a GUI
on it).
For those of you interested in how this works from the command
line, its
pretty simple. First, create a read/write disk image (you can do
this in
Disk Copy). Next, create the /dev entry for RAM using the hdid tool.
Finally, copy the contents of the disk image to the RAM /dev entry and
mount it. Because the disk image is mounted from the /dev entry, any
changes occur in RAM. Here are the Terminal commands:
[First, calculate the number of 512K blocks you need: numblocks =
(image
size in MB) * 2048; for example: 5MB = 10240 blocks]
% hdid -nomount ram://numblocks
[result: /dev/disk1]
% dd if=/path/to/image/file.dmg of=/dev/disk1 bs=512
[result:2866+0 records in
2866+0 records out
1467392 bytes transferred in 1 secs (1467392 bytes/sec)]
% hdiutil mount /dev/rdisk1
You need to change the 1 in disk1 and rdisk1 to whatever number is
returned by the first command.
Please be sure to check out ramBunctious; it has excellent
documentation
on the state of RAM disks in X and when you should/should not use
them.
The reason I mention it here is because it could have a huge positive
impact on the functionality of a bootable X cd.
**
How to create a RAM disk on OS X
32768 = size in sectors (16MB in this case, a sector is 512 bytes)
$ hdid -nomount ram://32768
/dev/disk1
$ newfs_hfs /dev/disk1
$ mkdir /tmp/ramdisk1
$ mount -t hfs /dev/disk1 /tmp/ramdisk1
To unmount:
hdiutil detach /dev/disk1
to osx files tiger ramdisk ram disk by peter on Thu Mar 30 16:25:22
EST 2006
**
I have thrown together a quick script for anybody that wants to
create a
ramdisk regularly. It's flexible enough for me, but can be edited to
offer more options (if u know a little .sh scripting). The disk is
dynamicly named and will show up on the desktop when the script is
finished. Unmounting can be done as any drive in the finder. The major
differences between my and the above approach is that I use
diskutil to
mount the created drive, so Finder likes it better, and i give the
volume a label, so it can be better recognized by the user ...
Here it is:
Leila:~ samynew[14:30:55]$ cat ramdisk
#!/bin/bash
if [ -n $2 ]; then ARG_ERR=ERR; fi
if [ -z $1 ]; then ARG_ERR=ERR; fi
if [ -n $ARG_ERR ];
then
echo 1 argument: size in MB
exit
fi
MB_SIZE=$1
let MB_SIZE *= 2048
echo Creating ${MB_SIZE} 512-blocks ramdisk
CREATED_RAMDISK=`hdid -nomount ram://${MB_SIZE}`
echo New block device: ${CREATED_RAMDISK}
DISK_NAME=`basename ${CREATED_RAMDISK}`
echo Creating volume with label: ${DISK_NAME}
newfs_hfs -v ${DISK_NAME} /dev/r$CREATED_RAMDISK
echo Mounting in /Volumes/${DISK_NAME}
mkdir /Volumes/${DISK_NAME}
diskutil mount ${CREATED_RAMDISK}
Make sure it's chmodded to be executable: chmod u+x
Re: [PD] [Gem] pix-native? [RAM disk]
On Mon, 30 Jul 2007, Derek Holzer wrote: Chris also suggested using a RAM disk, which would save a lot of wear and tear on the HD in the case of uncompressed video. What's the difference between a file on the HD that can be cached to RAM, and a file on the ramdisk that can be swapped to the HD ? Both can be in either place depending on OS decisions, so... _ _ __ ___ _ _ _ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [Gem] pix-native? [RAM disk]
There is always the possibility of paging RAM to disk at any point for any bit of memory and this goes for something like pix_buffer or Pd's table/array too. Obviously, the machine needs to have not only the free memory for the RAM disk but a comfortable amount of headroom. The OSX memory manager won't always do the right thing, but one can try to minimize its stupidity. A lot of the kernel code is still based on assumptions about ancient hardware and non-existent server scenarios, and it certainly pays the price for it. On 7/30/07, Max Neupert [EMAIL PROTECTED] wrote: hi, some sources suggest that there is no or little advantage to use a ramdisk in os x because the system caches data which has frequent access anyway. so a ramdisk can be counterproductive in a cenario where you have little ram: lets say you have one gig memory. 300 mb are used by some applications which are open, and another 300 by the system. now you have a video in your ramdisk of also 300. the system tries to cache it because it wants to accellerate but can't allocate enough anymore and data will be swaped on the harddisk.. so you end up with less performance and more harddrive access because of the ramdisk.. i'm curious about your findings. greetings, m. http://lowendmac.com/x-basics/02/0201.html http://www.kernelthread.com/forums/viewtopic.php?t=138 ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Scanned Synthesis in PD using webcams
Hi Frank I seen in a previous mail you explained a little about whats going on the Scanned Synthesis Example patch .. I am trying to undestand fully what is going on in this example for a project I am doing .. I was wondering if you could briefly explain what is happening in the [pd sound] [pd 1sur2] subpatches as I'm confused to what exactly their purposes are ... Thanks .. Dave. On 7/18/07, Frank Barknecht [EMAIL PROTECTED] wrote: Hallo, Frank Barknecht hat gesagt: // Frank Barknecht wrote: Basically you write the positions of the masses into a table, then play back the table with [tabread4~] or [tabosc~]. Attached is a real-Pd version of my ascii stuff, slightly improved. Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Scanned Synthesis in PD using webcams
oups, i forgot to send to the list basically, the shape of the string is recorded in 2 table (one for X deformation, and 1 for Y deformation). this tables are read at audio rate. in fact, in order to avoid audio click when changing the value inside the table, 2 table are used (for X deformation). data is writen alternativelly in both table. so, [pd 1sur2] is like [alternate]. when the shape of the string is written in 1 table, this table is read for the audio synthesis, and the other table is used next time. [pd audio] is where the shape of the string it recorded in the table. here is a more simple version of the same patch. it's easier to understand, but you can hear some click. cyrille David Divilly a écrit : Hi Frank I seen in a previous mail you explained a little about whats going on the Scanned Synthesis Example patch .. I am trying to undestand fully what is going on in this example for a project I am doing .. I was wondering if you could briefly explain what is happening in the [pd sound] [pd 1sur2] subpatches as I'm confused to what exactly their purposes are ... Thanks .. Dave. On 7/18/07, Frank Barknecht [EMAIL PROTECTED] wrote: Hallo, Frank Barknecht hat gesagt: // Frank Barknecht wrote: Basically you write the positions of the masses into a table, then play back the table with [tabread4~] or [tabosc~]. Attached is a real-Pd version of my ascii stuff, slightly improved. Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list #N canvas 581 245 589 507 12; #N canvas 106 24 1257 767 corde 0; #N canvas 306 123 345 326 mass 0; #X obj 65 20 inlet; #X obj 65 80 outlet; #X obj 124 135 gemhead; #X obj 125 82 unpack s f f; #X obj 124 166 translateXYZ 0 0 0; #X obj 170 108 / 100; #X obj 216 109 / 100; #X obj 124 194 sphere 0.1; #X obj 131 17 r \$1-on; #X obj 65 52 mass2D \$0-mass 10 -260; #X connect 0 0 9 0; #X connect 2 0 4 0; #X connect 3 1 5 0; #X connect 3 2 6 0; #X connect 4 0 7 0; #X connect 5 0 4 1; #X connect 6 0 4 2; #X connect 8 0 2 0; #X connect 9 0 1 0; #X connect 9 0 3 0; #X restore 153 387 pd mass; #X msg 721 211 setK \$1; #X obj 721 243 s link; #X obj 721 159 + 1; #X msg 805 211 setD \$1; #X msg 890 211 setD2 \$1; #N canvas 306 123 419 313 mass 0; #X obj 24 99 outlet; #X obj 145 98 gemhead; #X obj 137 134 unpack s f f; #X obj 143 190 translateXYZ 0 0 0; #X obj 185 160 / 100; #X obj 228 161 / 100; #X obj 144 224 sphere 0.1; #X msg 25 42 reset; #X obj 152 26 r \$1-on; #X obj 28 71 mass2D foo 10 -300 0; #X connect 1 0 3 0; #X connect 2 1 4 0; #X connect 2 2 5 0; #X connect 3 0 6 0; #X connect 4 0 3 1; #X connect 5 0 3 2; #X connect 7 0 9 0; #X connect 8 0 1 0; #X connect 9 0 0 0; #X connect 9 0 2 0; #X restore 17 360 pd mass; #N canvas 306 123 309 290 mass 0; #X obj 24 23 inlet; #X obj 24 83 outlet; #X obj 83 138 gemhead; #X obj 84 85 unpack s f f; #X obj 83 169 translateXYZ 0 0 0; #X obj 129 111 / 100; #X obj 175 112 / 100; #X obj 83 197 sphere 0.1; #X obj 131 17 r \$1-on; #X obj 25 55 mass2D \$0-mass 10 -220; #X connect 0 0 9 0; #X connect 2 0 4 0; #X connect 3 1 5 0; #X connect 3 2 6 0; #X connect 4 0 7 0; #X connect 5 0 4 1; #X connect 6 0 4 2; #X connect 8 0 2 0; #X connect 9 0 1 0; #X connect 9 0 3 0; #X restore 298 393 pd mass; #X obj 17 386 link2D link 30 1 1; #X obj 168 349 link2D link 30 1 1; #N canvas 306 123 311 292 mass 0; #X obj 24 23 inlet; #X obj 24 83 outlet; #X obj 83 138 gemhead; #X obj 84 85 unpack s f f; #X obj 83 169 translateXYZ 0 0 0; #X obj 129 111 / 100; #X obj 175 112 / 100; #X obj 83 197 sphere 0.1; #X obj 131 17 r \$1-on; #X obj 24 55 mass2D \$0-mass 10 -180; #X connect 0 0 9 0; #X connect 2 0 4 0; #X connect 3 1 5 0; #X connect 3 2 6 0; #X connect 4 0 7 0; #X connect 5 0 4 1; #X connect 6 0 4 2; #X connect 8 0 2 0; #X connect 9 0 1 0; #X connect 9 0 3 0; #X restore 442 387 pd mass; #N canvas 306 123 299 280 mass 0; #X obj 24 23 inlet; #X obj 24 83 outlet; #X obj 83 138 gemhead; #X obj 84 85 unpack s f f; #X obj 83 169 translateXYZ 0 0 0; #X obj 129 111 / 100; #X obj 175 112 / 100; #X obj 83 198 sphere 0.1; #X obj 131 17 r \$1-on; #X obj 24 55 mass2D \$0-mass 10 -140; #X connect 0 0 9 0; #X connect 2 0 4 0; #X connect 3 1 5 0; #X connect 3 2 6 0; #X connect 4 0 7 0; #X connect 5 0 4 1; #X connect 6 0 4 2; #X connect 8 0 2 0; #X connect 9 0 1 0; #X connect 9 0 3 0; #X restore 580 390 pd mass; #X obj 310 350 link2D link 30 1 1; #X obj 457 349 link2D link 30 1 1; #N canvas 306 123 299 280 mass 0; #X obj 24 23 inlet; #X obj 24 83 outlet; #X obj 83 138 gemhead; #X obj 84 85 unpack s f f; #X obj 83 169 translateXYZ 0 0 0; #X obj 129 111 / 100; #X obj 175 112 / 100; #X obj 83 197 sphere 0.1; #X obj 129 20
[PD] [PD-announce] patching in chinese?
http://sonicvariable.goto10.org/downloads/dd/dd_chinese.png _ _ __ ___ _ _ _ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada___ PD-announce mailing list [EMAIL PROTECTED] http://lists.puredata.info/listinfo/pd-announce ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
