hi, i'm a little new to pd and i'm having a little trouble installing/getting it to work on the daw. anyone here can give me some good instructions?

it would help to know, where you have problems with pdvst. i just tried it out one time and i got it work quickly. i found the installation instructions of pdvst were easily understood.

Sorry can't help but, wish pdvst worked on os x!

I've had some success running Jack as an insert effect on OSX. Probably a little more setup than PdVST (I'm guessing), but it gets the job done.

well, the installation and creating the vsts from the patches.. an (amplified?) version of "how to install and use"

@Maelstorm said:

I've had some success running Jack as an insert effect on OSX. Probably a little more setup than PdVST (I'm guessing), but it gets the job done.

what was the latency scenario like may i ask? just wondering how you overcame it..

so........

ummmmm......yes?

haha, i was asking for some help in installing pdvst

Oh, perhaps we could help each other ! I've been desesperatly looking for Pdvst the last two days but the dl link seems down. Could someone link one's version ?
Then I'll help as much as I can...

it is, yeah. but i reckon it should be up and running soon...

mhh, it seems to be not that easy to get it work. first time i used it, i ran it in vst-host (a simple vst host and chaining app) and only used the simple example patches that came with pdvst. that worked quite well, but i tried to get one of own patches to run in sonar, and i stuck... sorry, no help a the moment!

the download here : http://crca.ucsd.edu/~jsarlo/pdvst/ is working fine (again?).

there are quite a lot of angles in this to screw up. i haven't worked with this for ages, but remember, that i got a quite simple audio-plugin to work in cubase years ago.

if you are certain to have everything correct in the pdv file, your plugin.dll and the plugin.pd and pd running in the right place, try different hosts.

i tried it in with live, cubase and reaper.. it just doesn't recognise the ".dll" file

i just tried the whole thing with a simple reverb during my lunchbreak and it worked (for me) as follows, using ableton live 7:

• put "pdvst" folder (the whole unpacked thing from the download, including the custom pd program) in C:\Program Files\Ableton\Live 7.0.3\Program

• copied the PD_Gain.pd and PD_Gain.pdv to my pd installation to edit it. (at least i can't really edit with the pd version in the pdvst folder, it's obviously just meant to run in the backgorund, when the DAW starts)

• edited the .pd and .pdv files to make them what you see in the attachment. i threw out the gripd stuff to erase a possible error-source. maybe comparing your pdv file to mine, you find if there's something wrong with it.

• copied the finished, now named PD_freeverb.pd and PD_freeverb.pdv back into the pdvst folder within the ableton live folder. since my patch uses the external "freeverb~.dll" (which comes with pd-extended), i copied that file into the pdvst folder as well. - the according line in the pdv file needs to point to this lib.

• made a copy of the template dll and named it PD_freeverb.dll

• put the PD_freeverb.dll into my vst-plugins directory (the one monitored by live)

started live - the plugin shows up as a (audio) vst plugin. all fine.

since i set the line

# Display Pd GUI or not
DEBUG = TRUE

in the pdv file, i get the full patch and surprisingly can even edit it, while having it running as a plugin. i doubt, that this is a safe way of working though. ^_^

i hope that all helps somehow.

attached are the PD_freeverb.pd, PD_freeverb.pdv, PD_freeverb.dll and freeverb~.dll (from the newest pd-extended installer)

edit: the only thing "suspicious" is that when i start live, a messagebox comes up, telling me that pd has crashed/exited. (pd was not run by me at that point)
however, observing the taskmanager, whenever i load the plugin into a track in live, pd.exe is started and fully quit, if i remove that plugin again.

http://www.pdpatchrepo.info/hurleur/pdvst_PD_freeverb.zip

thanks! i'll just try this in a bit..

Interesting - does it receive timecode from the host. What version of Pd does it run?

I really think this is something that should be more integrated into the Pd-extended package. Currently it only exists for windows...

@ boonier: that's a good question, i was wondering about that too. i couldn't figure out how to get this work. i think, there has to be a special object that can receive timecode or something!? i don't know such an object, does someone?

i suppose, a timecode or clocksync would be achieved, just like one would do in "normal" pd. the plugin-patch could start a certain midi-in channel when openend and the host could send its clock out on a certain midi-device.

this would be a bit of a dirty workaround, since the host sends outside - maybe to midiyoke - and then back into the the host to the plugin.

i once tried to make a clock with a midi-track in the DAW, which had a note set on every bar, so it would be like a metronme to pd.
stop and start is received by pd through midiin, so it basically worked.

unfortunately the latency between both programs was unbareable and i couldn't compensate it.

@ toxonic & boonier: may i ask what the use of such a timecode would be? i was just fiddling with a small sync patch to get a mini-sequencer inside a pdvst plugin, when it occured to me, that every parameter is already automatable/editable along the timeline within the host.
... which then would be a precise timecode for any parameter one would want i n the plugin.

or are you wondering about a mini timeline within the plugin, like i.e. dblue_glitch has? then, a seq, that rewinds itself on stop is enough? that should be easy.

i am at a loss though, when it comes to a real timestamp/songposititon being sent from the host.

there is stuff missing in the patches i posted in #15.

the controls, that show up in your host are not connected to the patch. so the values can only be controlled by the pd-gui sliders.

however, if you attach a [r rvstparameter0], ,[r rvstparameter1] and so on to the sliders (inlets) in the patch, you can control the values from within the host.

sends a value from the patch to the host, so the patch should be edited to have the host controls receive the values, if the sliders are being moved in the patch.