I would like to make a portable directly...if I can get pdvst to work...but what is the best way to optimise and take along only the absolute minimum required?

Hi All
Been a while
Im wanting to simply use a midi plugin that simulates the guitar synth hold functions of old eg sustain vs hold and play over top of held notes (infinity hold) etc. Did it ages ago...works nicely.
So to make sure all was ok before I spent too much time on porting my own stuff for use as a vst plugin; I installed the pdmidi example.(PDVst)
No problems, installed fine
BUT
When it loads...the cpu in whatever host I load it into maxes out.

I tried turning of the inputs (setting the init file to inputs = 0) etc but no avail
I have the latest PD installed into the vst plugin directory using the new way of installation

Any ideas??

Cheers

PD version 0.61-4
Hosts
Kore 2 64 (last version)
Ableton 10.17 64bit

Hi All
Been a while since I was here...
Dont whether Im using the wrong search terms but I am wanting to build;
A play back sample module for a simple headless raspberry pi setup for my cajon (I use it with a wavedrum but it has no connectivity etc)
The sample module should have 8 velocity layer plus a round robin for max velocity of eg 4 samples
Primarily percussion etc
I am reasonable at programming/designing on Kontakt.
The trigger inputs would be 4 piezos plus a kick trigger (yamaha pedal) so 4 in total...inspired by this set up

V2
Would have positional info for 2 top triggers...the hpd20 has some nice positional instruments and I hooked the positional controllers up to the hand pan library...its brilliant fun.

So the question is...
Does anyone know of some resources/existing projects that might help
Anyone done any raspi only setups like this?

Thanks in advance and kind regs
Mark.

Hi All
A little bit of work to set up but forget midi mapping...google it if you dont believe me.
After a lot of time spent trying to get a simple but sophisticated way (using a minimal 8 button floorboard) to control Live on w10, I thought I would share this particular solution to possibly help others (especially after the help offered here on this forum). I tried a number of scenarios, even buying Max 4 Live, but it turns out a lot simpler than that. It needs 3 main areas set

FOOT CONTROLLER BEHAVIOURS/GESTURES
Create pd patch that gives you 'behaviours' per switch. Ill be happy to share mine but Im just cleaning them up atm.
eg I have 4 standard behaviours that dont take too much time to master

1. Action A: A quick click (less than 500ms) Always the primary action
2. Action B: Long click ie 1 click down and pedal up after 500ms. I use this eg always as a negative ramp down for things like lowering volume but if its just held down and released in a natural way, it is the secondary action of the switch
3. Action C: 3 Click ie 1 quick down, up and then hold down. I use this for a positive ramp eg as volume up
   4 Actiion D: Double click, Always a cancel
   These are all mapped to note/ctrl outs that match the 'Selected Track Control' below

PLUGIN
Use PD VST to create a plugin version of your patch. This is loaded into Live as a control track. Live manages the connection of your floor board etc into the actual track so you dont wrestle with the io. I always use track 1 for click (forget Live metronome, this is much more flexible and can have feel/swing etc) so I dedicate track 2 to control.
Use LoopMIDI to create a virtual midi cable that will go from this track and be fed into the remote script.

REMOTE SCRIPT: 'Selected Track Control'
Download latest from http://stc.wiffbi.com/
Install to live and make sure your notes/control conform.
Enable this as a control surface in live and connect midi in from the plugin. Think about giving the guy a donation...massive amount of work and he deserves it!

I use it to control 8 tracks x 8 scenes and is controlled by 3 switches

1. Scene control up and down (A = down, B = up)
2. Track control same as scene
3. Rec/Fire/Undo Volume up and down (A = fire/rec, B = Volume Down, C = Volume Up, D (Dbl Click) = Undo

The scenes and tracks wrap so there isnt too much foot tapping

There is quite a bit more to it of course...its and maybe no one else needs this but it would have saved me a couple of weeks of time so Im happy to help anyone wanting to achieve gigging without a massive floor rig and an easy way to map and remember.

HTH someone

Cheers
mark

Thanks @dxk. Looks good...but it's audio centric and midi out is experimental. What it does tell me is that it uses heavy tools to compile to c so it might be a way to compile, with tweaking, for arduino...

Before I spend any time doing it...from a noob perspective...can this be done? Would like to make a floorboard with all the PD behaviours that I have programmed but have it as an independent midi device and use surface control in Live.
Cheers

hehe...too true. Windows 10 is hideous for updates...metered connection seems to be the only saviour.

Max for Live seems to be ok...most of the PD stuff can be copied verbatim...mostly.

Understanding the Object Model is a little tough but just bought a book on it...dont have the time to fumble so its worth it.

Your help has been amazing David!

I didnt realise you could make a vst out of pd...that would have probably stopped me going further ie Live max.

Cheers
Mark

Thanks @bang; that sounds like a great solution. I have taken the plunge and bought max 4 live as it removes a whole bunch of issues and makes the simpler extremely simple. Now Im just hoping everything that was programmed works in M4L without too much trouble :-\

Cool...I'm not a c guy though...anyone else on the forum do a compile check? Does anyone have a w10 machine to confirm...maybe it's me???

Hmm. Just read that it's been removed. Weird. Anyway...input_event def seems dead...anyone out who can fix the dll? Or at least confirm the problem?