Hi list, is it possible (for an external) to have a signal and messages going into the same inlet? (apart from the leftmost) I tried some things with proxy objects but an inlet seems to have either a "signal" or message symbol specification, right?
thanks! Thomas
Hi, I'd like somebody to review the attached patch and let me know if you've experienced similar problems.
I'm simply trying to create a wav file of a MIDI sequence (in this case, my "click-track" patch that I submitted yesterday). This patch WORKED last night...but now it doesn't. The only thing I've changed is - I've added "send" and "receive" objects so that I could send the "open" message to writesf~ from another location in the patch.
In any case, it seems that writesf~ isn't writing a normal wav file. When I play back the file in another player, I'm warned that I don't have the proper codec installed - but as I said...this worked last night.
Anybody have any advice?
Many thanks, Dave Sabine
----- Original Message ----- From: "Thomas Grill" t.grill@gmx.net To: "Pd-List" pd-list@iem.kug.ac.at Sent: Monday, March 18, 2002 1:49 PM Subject: [PD] signal and message inlets
Hi list, is it possible (for an external) to have a signal and messages going into the same inlet? (apart from the leftmost) I tried some things with proxy objects but an inlet seems to have either a "signal" or message symbol specification, right?
thanks! Thomas
Just a thought - are you _closing_ the file when you're done?
Larry
On Mon, 18 Mar 2002, David Sabine wrote:
Hi, I'd like somebody to review the attached patch and let me know if you've experienced similar problems.
I'm simply trying to create a wav file of a MIDI sequence (in this case, my "click-track" patch that I submitted yesterday). This patch WORKED last night...but now it doesn't. The only thing I've changed is - I've added "send" and "receive" objects so that I could send the "open" message to writesf~ from another location in the patch.
In any case, it seems that writesf~ isn't writing a normal wav file. When I play back the file in another player, I'm warned that I don't have the proper codec installed - but as I said...this worked last night.
Anybody have any advice?
Many thanks, Dave Sabine
----- Original Message ----- From: "Thomas Grill" t.grill@gmx.net To: "Pd-List" pd-list@iem.kug.ac.at Sent: Monday, March 18, 2002 1:49 PM Subject: [PD] signal and message inlets
Hi list, is it possible (for an external) to have a signal and messages going into the same inlet? (apart from the leftmost) I tried some things with proxy objects but an inlet seems to have either a "signal" or message symbol specification, right?
thanks! Thomas
-- Larry Troxler -- lt@westnet.com -- Patterson, NY USA --
Just to say that i have something strange too with writesf~ theses days. It cannot record again a file with the same "open foo.wav" message. And yet the precedent recording is stopped.
I have to delete or change the name of the existant recording to be able to record again. I remember that before, I could redo a record with the same file name. The previous file was erased.
I use PD-0.34-4
Linium
I'm simply trying to create a wav file of a MIDI sequence (in this case, my "click-track" patch that I submitted yesterday). This patch WORKED last night...but now it doesn't. The only thing I've changed is - I've added "send" and "receive" objects so that I could send the "open" message to writesf~ from another location in the patch.
In any case, it seems that writesf~ isn't writing a normal wav file. When I play back the file in another player, I'm warned that I don't have the proper codec installed - but as I said...this worked last night.