Would I be correct in assuming that the pi is the best platform for MIDI piggy now?

osx works pretty good as well.

turboninja wrote:

<yes, I tried with behringer uca202  it worked perfect with pi2. No more with piggy on pi 3.

Someone should try building it natively on a pi, I think there is a make file in the repro.

windows seems to handle midi fine as well, though some people have reported some latency issues but that would likely vary a lot based on your setup

e.s.c. wrote:

windows seems to handle midi fine as well, though some people have reported some latency issues but that would likely vary a lot based on your setup

The problem has always been audio and midi sync, if you want to do midi only its fine imo.

i've only tested it using my mackie onyx 1220i as my soundcard and didn't have any trouble with that but most people don't use firewire

e.s.c. wrote:

i've only tested it using my mackie onyx 1220i as my soundcard and didn't have any trouble with that but most people don't use firewire


Oh thats interesting! I have a firewire card too I should give it a shot...

e.s.c. wrote:

i've only tested it using my mackie onyx 1220i as my soundcard and didn't have any trouble with that but most people don't use firewire


Oh thats interesting! I have a firewire card too I should give it a shot...

herr_prof wrote:
e.s.c. wrote:

windows seems to handle midi fine as well, though some people have reported some latency issues but that would likely vary a lot based on your setup

The problem has always been audio and midi sync, if you want to do midi only its fine imo.

I've never been able to get a consistent clock sync out from windows piggy. And the Pigfather confirms this:
http://chipmusic.org/forums/post/183575/#p183575

Interesting. I would've figured that the desktop versions would have been the most stable. Raspberry it is!

from my experience, all piggy midi platforms have a slight drift in their clock signal (except possibly osx, only because i havent tested it).. it's not enough to really sound wrong, but 1-3 bpm up and down changing very quickly.. seems to average out correctly over each phrase.. i only notice it because the edirol v4 has the bpm in nice big bright numbers

Future double post

Last edited by Domu (June 28, 2016 7:56 pm)

Mmmm vj porn. I wish I had one of those

Last edited by Domu (June 28, 2016 7:54 pm)

turboninja wrote:

Hello , someone has managed to run lgpt on a raspberry pi 3 ? I've got a crapy glitchy slowly sound.

Hey turboninja. I'm having this exact issue and have been trying to crack it in my free time but keep finding that I'm missing a piece. I've sort of resolved that the key is to either swap the Pi 3 for a Pi 2 or install Wheezy on the Pi 3, which has proven much more difficult than I anticipated. Or if some smart person comes in a ports it to Jessie, but that might lead to other problems since I haven't been able to get my interfaces working in Jessie anyway.

I have found this image that claims to boot up wheezy on your Pi 3, but I just get the rainbow screen: https://sourceforge.net/projects/raspbian-wheezy-pi/

I've also found this thread, which has a technique that claims to work and has confirmations from a couple of users. I look at it and scratch my head though because I am a new user and don't know anything hahahaa.

https://www.raspberrypi.org/forums/view … p;start=25

I get lost at steps 4 and 5, what easily looks to be the most important step. I think I might just see if my friend wants to swap his 2 for my 3.

Last edited by Cartoon Bomb (June 30, 2016 10:22 pm)

how do i atually run the rpi lgpt executable? //n0ob

@cartoonbomb don't try too hard on this tutorial. You will end up with problem in the future : the package manager will be a mess...
This thing should work, but you will be better with a non hacky system.