If this is possible it is going to be a simple question for the Gem people. I've been asked to do some VJ'ing for a friend's gig, and I've tried this with Jitter before, and I familiar with Pd, so I thought I would give Gem a shot. But before I start learning a new environment I wanted to ask a few questions.
Is it possible to do a full screen Gem window, on a second monitor/projector? I can't seem to to find an option for it.
And are there any issues I should be aware of using video together with Gem?
That is actually it. I've skimmed through the manual and there doesn't seem to be anything terribly different from pd in there, so there's only the full-screen thing that could really be problem.
I seem to be missing the control version of multiplex from the ZEXY package. The tilde version works fine, as does both control and tilde versions of demultiplex. The multiplex object just doesn't appear (i.e. it's created as a comment box).
I'm using fc3 ccrma setup. Has anyone come across this before?
I'm currently working on a sequencer, and wanted to know if anyone could help with how I could timestretch samples.
I'm using sfread~ to play sampled loops. Changing the playback speed changes the pitch, so I want to timestretch them so that I can do modulation on the fly without having to make a new loop.
I recently installed jack 0.38-4... the only version I found that will compile cleanly on a 64bit system. However when I try to boot pd I get this message:
pd: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory
I have jack installed and it runs fine. Any ideas?
Is there anyone who can help with compiling pd for an x86_64 processor. I have used the instructions in the install.txt with it. I using Fedora Core 2 with the latest upgrades (asuming this also means ALSA) and JACK.
Everything is fine untill the make install command after which it gives me loads of warning saying something to the effect of:
x_gui.c: In function `savepanel_new':
x_gui.c:233: warning: cast from pointer to integer of different size
After lots of these it ends with:
bonk~.c: In function `bonk_perform':
bonk~.c:481: warning: cast to pointer from integer of different size
make: *** [bonk~.pd_linux] Error 1
make: Leaving directory `/home/cocteau/download/pd-0.37-1/extra/bonk~'
make: *** [externs] Error 2
Can anyone tell what this means?
Thanks in advance
As far I as know it is usually a latancy problem. Try media/Audio settings and increase the delay. I really depends on your soundcard how low you can change this and whether or not you run pd through jack, but try and experiment with a few different settings. 50 is usually a good 'safe' number.
Having a high latency can be a real pain though as it will make respons times slower and real-time manipulation very hard.
I still get a few sync errors, but it's not so bad that I can't live with it. And the planet has a whole section about how to optimize your fedora box for the lowest latency.
Hope this was helpful.
i've heard about trigging pd events from the computer' s keyboard...
key, keyup and keyname. See their help for more explanation.
I'm on an AMD64 with fedora core 3 ccrma kernel. The soundcard is Edirol UA-25. I would have liked to have M-Audios Firewire 410 but I don't have a six-pin firewire connection.
I recently bought a Radium 49 keyboard (4 octaves, 16 controllers) which is fine for my needs for now. I'm hoping to aquire a midi footswitch, as I will use that setup next year at university for my BA.
I have an AMD64 right now, and I don't think I can really that headaches it has caused me. Although the distros has inproven a lot for 64 bit, it's still not at a place where I would recommend you use it for audio work.
Since kernel 2.6.10 lots of things were easier to compile (I have no idea if this was just my perception or if actual improvements had been implemented). Pd 0.38 will compile in a 64 bit fc3, but not many externals will Maxlib definately wont. TAP plugins are fine but SWH plugins wont. The newest Ardour will but Muse wont. Oh, and audacity is actually compiled for 64 bit.
The hard thing is, that it is really a trial thing to find out, and you still have to know that most audio programs is written for 32 bit anyway, so you won't actually be using the extra processor power for them.
Even though I would love to be experiment with the extra computer power I took some advice from the CCRMA mailing list and just switched to 32 bit fc3 with the CCRMA kernel. You will just get more work done instead of continuingly struggling to just getting things to work and that's what it's about at the end of the day anyway.
There's some hope however. There's something called 64 studio or something to that effect. It's still in the developing stage and I believe it's a commercial product, but check it out.
Should you decide to give it a try, I would like to know if have any more luck than I did.
Kind of freaky, but I changed all the sfplay~ to tabplay~ shortly after I posted this, as tabplay~ seems to give a quicker and cleaner response than sfplay~. Don't know why, though.
I'll get right on, and post any results. Seems that timestretching is one the harder things to do, that many people require.
Oh, and going a bit off topic. Does anyone know of a place to post patches? I could be cool to get some respons of the stuff I've been working on.
I have managed to work out the problem but I have no clue as to why this was one to begin with.
I used the jackd executable found in /usr/bin instead of one in /usr/local/bin. This made all the difference as jack, pd, qjack and everything else now works fine.
After having struggled with getting this computer set up as an audio workstation for the past four months I'm psyched that it's now up and running.
However, I do apologize for having taken up space here with a problem I solved myself.
I found this possible solution from planet ccrma, as the same problem accours when upgrading jack, which suggests removing the installtion and trying again. If you're interested you can read about it here:
[url=http://ccrma-mail.stanford.edu/pipermail/planetccrma/2002-September/000099.html ]http://ccrma-mail.stanford.edu/pipermail/planetccrma/2002-September/00 0099.html
However, since I didn't use a package install, I have no clue how to remove something I compiled myself, so I tried to create new links which worked.
It seems somehow part of the 64 compatability mess, since pd will work when you physically place the links in the corrosponding 64 bit libraries.
Now it's possible to run pd as root, but not as a standard user. If I try I get this error:
[cocteau@localhost lib64]$ pd
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Application initialization failed: this isn't a Tk applicationcouldn't connect to display ":0"
I've absolutely no idea what that means... it seems to be more of a problem with jack than with pd, as I get the same error when I try to run qjack as a standard user.
Thank you for this. It compiled without problems and almost without warnings. Gave me a couple of typecast warnings but they weren't many. Also I could only find two places in the makefile to change but hey, it's working.
I don't know what objects are using the soundfiles as examples, so I can't help you with that. They play fine in xmms here, if that's any help and I didn't find any warnings regarding them when compiling.