• spacedad

    when i select my usb keyboard,i get this warning...
    'Warning: midi input is dangerous in Microsoft Windows\; see Pd manual'
    and if i load a patch synth,my keys don't play the synth.
    i'm sure pd can alow midi in,is there something i'm doing wrong?

    posted in technical issues read more
  • spacedad

    hi,
    i'm a pd newbie(winXP SP2),but before i start,i'd like to get it looking nice.(how shallow ;))i did a quick search but couldn't find any icons.could anyone point me to some?
    (there was a link for sourceforge about pd icons i saw on google,but it wasn't connecting for some reason)

    anyway,thanks for setting up this forum,i'll no doubt be back asking more newbie questions.
    my first attempt at pd was using pdvst,with some help from a kind fellow at kvr i got it working and tried out the example synth+polysynth patches inside my host(energyXT).that's as far as i got.look fwd to trying some simple patches next.
    cheers,spacedad.

    posted in technical issues read more
  • spacedad

    hi domien,
    yes i have tried pdvst,sorry i should have mentioned it.
    i did get it working in energyXT after a bit of a struggle,tried a couple of synth examples out,worked fine,though i couldn't save presets unless the synth had built in patch system.
    pdvst was what got me to try pd really,i'm hoping to get my own creations working, once i get past the basics.
    still,save as vst would be nice as it allows you to share your creations further afield.
    not really sure why gripd isn't good,i've not got as far as gui's yet and the synth i tried didn't have one anyway.

    posted in technical issues read more
  • spacedad

    thanks i'll have another look,with se there's modules(both native+3rd party) like osc,math etc,then you can things together into a container or put loads of containers together and save as a prefab(also save as vst which is nice).so it's a bit similar,not quite as low level,though you can code modules if you know how.
    once i learn the jargon and some basics it should get easier.i find it easier to make things from scratch rather than make sense of someones brain.there's loads of examples of se creations,but when you open them up it's a shocking mess to me!
    i'm a simple lofi guy,so it's only little noise machines i'll be messin with.
    do you think pd will ever have 'save to vst'?

    posted in technical issues read more
  • spacedad

    hi hardoff,sorry to hear about your puter.
    i'm not sure i get it still,though i found obiwanabe's synth tutorials,which have been very good for me(only half way through the first one).
    so maybe things will become clearer as i reach the end.
    pd seems deeper than synthedit,are you familiar?

    posted in technical issues read more
  • spacedad

    i was just googeling for pd help,when i came across obiwannabe's site.the six simple synths look like a good start to me.thanks for them.
    i use synthedit (and i'm only new at that!)and pd is a bit different.

    posted in technical issues read more
  • spacedad

    it's confused me,it now has 2 parts 'in' and 'out' how do i connect it to a synth?
    cos the 's $0-transpose' and the 'outlets' don't have any connecting pins. :s

    posted in technical issues read more
  • spacedad

    yay!thanks hardoff! :D

    posted in technical issues read more
  • spacedad

    thanks for the tips,
    now i get,
    'kee (x)...couldn't create.'
    i thought i had it working but when i reloaded it,it didn't.hmm.

    posted in technical issues read more
  • spacedad

    well i still get the warning message,but now i got my keyboard working.
    after trying to cut+paste various things that looked like it could be to do with notein,the only one that worked was the 'notein/pack/r syn-midinoteon/unpack' objects from the '1.poly.synth' example,then pasted that and connected it to the 'doc-3 classicsynth' -'poly 1 1' object.(deleting the 3 objects previously connected to 'poly 1 1')!

    hope that made sense,i've no idea what it means yet,but it worked.
    maybe it'll help some one with a similar problem.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!