Something I have always been curious about is the ezdac~ GOP feature/anomaly. When I open ezdac~, the toggle and hslider GUIs are not situated anywhere close to one another. When I return to the abstraction, everything seems to situate itself into a simple GOP. Re-opening the abstraction, if I move the GUI objects around, they always seem to find their way into the GOP red-outlined field. But, wait, there is no GOP field there!

I copied the entire contents of the ezdac~ abstraction into a new abstraction with a different name. The new abstraction loads, but with GOP not activated. Activating the GOP function places a red field in the patcher window, but not in a place where it could encompass both GUI elements. In addition, the GUI elements do not reorient themselves into the GOP box as before. My next theory is that the actual file, the text that defines the ezdac~ abstraction must have some special voodoo in it to place the GUI elements in the right place (which would be a powerful bit of knowledge, indeed), but searches for ezdac~.pd brings up nothing on my Mac. Strange. I seem to remember similar behaviour under Ubuntu.

What's up with this?

Jgeist

Isn't there an object that will report the folder/directory my patch is in? I am trying to feed this 'home' directory to openpanel (via a [symbol $1/samplepool< message) so when I bang openpanel, it opens the subdirectory samplepool.

Thanks

Hello:

What is going on with the Chicago PureData community? Is there even such a thing? If not, maybe we can start something.

All the best,

Jason

Hello:

I am using mp3cast~ to stream to an Icecast2 server. I can play the stream in VLC player and I can play the stream on my iPhone, no problem. However, iTunes will not play the file. I don't know if the problem is with mp3cast~, Icecast2, or iTunes -- or a conflict amongst all 3.

My initial inkling was that the problem had to do way that the url is being formulated, possibly with how mp3cast~ creates the mount point? To date I have tried:

xxx.xxx.xxx.xxx:port/mystream.mp3
xxx.xxx.xxx.xxx:port/mystream.mp3.m3u
xxx.xxx.xxx.xxx:port/mystream.m3u

with mp3cast~ mounting on:

mystream.mp3
mystream.mp3.m3u
mystream.m3u

respectively. iTunes refuses to play the stream, and VLC plays anything I throw at it.

As a second experiment I used NiceCast to stream to the server and iTunes had no problem playing the stream. This last test leads me to believe that there is something about mp3cast~ (encoding) which iTunes simply does not find agreeable.

This question runs somewhat along the same lines as: http://puredata.hurleur.com/sujet-3736-mp3cast-quicktime

As the previous poster received no answer and I have a similar situation, I thought I would put it out there again.

Have you had any experience with this?

Thanks,

Jason

This is a weird one.

On launch of PD 41.4 on OSX Tiger a message box appears that states 'Required software extension are missing. Click on the OK button, and you will be transferred to the PACE web site where an installer can be downloaded." The message box will not go away when I click CANCEL or OK and delays the loading of PD by about 20-30 seconds.

I did have to install PACE to get a Digidesign/Mbox Universal driver to run a while back, but forgot about. It has never been an issue until this morning.

Removing PACE appears to be a nightmare, but I think I got most of it. I even trashed the MBox drivers which required PACE in the first place. Still, cannot seem to kill PACE and performance appears to be suffering throughout.

Any ideas? I fear a backup and wipe the drive might be in order.

Jgeist

Mod:

Thanks for the clarification. About three years ago I was demonstrating GOP functionality to a student when, all of a sudden, I grabbed ezdac~ as an example. Who knew? I have been perplexed until today.

Appreciate the follow up. Case closed.

Jgeist

EXACTLY! This is why the behavior is so strange. I will try to walk through what I am experiencing, if you are so inclined, try this:

1. Create an ezdac~, notice how the hlsider and toggle are next to one another. You would expect they would be similarly configured when you open up the abstraction, as you say, YOU have to move them there yourself, but the objects are not located within the GOP field.

2. Right click on the abstraction, open it up. Those objects are no where near one another. In fact, there is no way these should be visible in the GOP because the GOP field is at these coordinates, as you note, #X coords 0 0 1 1 90 55 1 100 30;

3. Move the GUI objects around, in fact, make the patcher the size of the entire screen and put the GUI objects in separate corners. Close the abstraction. When I do this, the GOP is somewhat resized, but the objects do realign themselves to be within the visible GOP space. Wierd, huh?

4. If you create a new object in the abstraction, like a text box, the behavior is broken, the GOP field appears, and the object is broken as well.

5. I don't think it is possible to create an ezdac~ object, like the one which comes with Pd, which has the same lay out.

6. Perhaps this is a bug/feature which only happens with my version of Pd.

Thanks,

Jgeist

OK, that's great, that certainly answers the second part of my question, where the GOP area is and how it is encoded into a file . . . but, how do the GUI objects know to reorient themselves to that space? What I am getting at is that there seems to be two display modes, one for presentation (GOP abstraction closed) and one for programming (when you are working in the GOP). I guess, similar to what Max has adopted.

So, the GUI objects seem to exhibit two sets of coordinates depending on where you are in the patch.

Just curious,

Jgeist

Aha, of course once you ask, it shows up . . .

http://puredata.hurleur.com/sujet-2436-packaging-patch-sounds

[getdir] returns the local directory.

Jason

UPDATE:

Had to remove the DigiDioMidiDriver.plugin and all went away.

JG

You have seen this?

http://puredata.hurleur.com/sujet-4055-rate-object-like-max

Jgeist

[random] will give you integer values, as opposed to [randomF]. Check out the help file and don't forget the 0 offset.