Jerkiness/CPU problems when looping videos forward/reverse with pix_film
Just as an update: the problem I was having wasn't CPU related in the end. The compression on the .mov files I was using was causing GEM to freak out when I tried to play the video backwards or at a random frame rate. Changing the file compression from H.264 to Apple ProRes solved this problem. I haven't experimented with other suitable compression formats yet but using ProRes seems to do the trick for now.
As a side note, using [pd~] to create a sub-process was still a great idea to do because it's freed up my CPU a lot to do more complex things in my patch(es). It just didn't solve the immediate problem I was having.
User Interface to PureData Code for my Bachelor Project
I will! But first I have to find out and understand what the problem was in detail. Today I had the next problem: There is an error message "The document could not be saved as..." So I'm not able to connect my editor work with my pd file... Has anyone an idea how to solve that problem?
Load Libraries, plug-ins
Maybe still a problem with Gem being 32-bit?......... but more likely a graphics card problem. Gem and many other video programs, and most PC Games rely on OpenGL. You might find out more by trawling the "Gamers" sites for OpenGL errors + win10 + your graphics card.
Microsoft pushed hard to move everyone to directX11. As I understand it the graphics chip manufacturers went along at first, but the backlash was furious and they were forced to re-write their drivers for OpenGL. You might just need a different driver. If so, the next problem would be keeping it... avoiding automatic updates.
AHHH! sorry...... just spotted that you tried 0.94-test3. Yes, that works for win7 as well, but not everything is there. You will need some other dependencies probably.... maybe msvcr110.dll or others? may-be.zip . Also it didn't work for me (at all) until I dumped the contents of the QT folder into the main 0.94-test3 folder. Also not all Gem objects are present. I started, but I didn't finish.....it is on-going.
You might need "quicktime" as well for some things to work. Is it available for win10?
Jerkiness/CPU problems when looping videos forward/reverse with pix_film
So I've been making a patch that plays videos using GEM, I want to play a video forwards and then play it backwards once the total number of frames is reached. The idea is to have a video that loops on repeat forwards and backwards. However, I've found that CPU rises dramatically when the video plays in reverse and everything slows down and gets jerky. I've also found a similar problem when I use [random] or [drunk] to change the frame number of the video. CPU rises dramatically and everything gets jerky. I'm also running audio at the same time but the problem persists even if audio is not playing.
I'm wondering if there's a simple solution to fixing this problem. It seems like GEM should be able to handle incoming frames that are not moving forward sequentially.
I'm running on a Macbook Pro (late 2011) with 16GB of RAM.
problems with installation
@Houselover If you are using Sierra look here........ http://forum.pdpatchrepo.info/topic/10543/problem-running-pd-extended-on-64-bit-macbook-pro
You will see that it might be possible to run extended, even though it is 32-bit, but maybe not.
If you are using osx 10.7+ this might help........
Other users that have had the same problem will reply as well, so keep coming back to this thread if you have no success...... and please come back and tell us how you fixed it..... when you get it working.
You should tell your teacher immediately. It is possible to download the latest version of "Vanilla" and add many of the features of "extended" using the "Deken Plug-in" that is included in the download, but some things might not work. Your teacher can maybe help you with this...
OR......... Purr Data has been released today, and could be what you need?....... http://forum.pdpatchrepo.info/topic/10569/purr-data-finally-released
Noob Trying to Create a MIDI Chorder/Harmonizer
Yet more progress!
But still stuck on sending noteoff messages to a note after its number has changed. Maybe there’s something to do with a cold inlet, working as memory? Wait! Might have found part of the solution…
Followed the first two parts on the synth creation tutorial on Libre Music Production,
(The third and last part of the LMP tutorial has to do with filters and UI, so it shouldn’t have an answer to my noteoff issue.)
Through that tutorial, was able to make a simple polyphonic synth which takes MIDI in and outputs ADSR-enveloped notes to the DAC. So far, so good.
Added a fifth to the mix. Still works. No stuck note.
Then tried adding a third note which progressively goes up with a counter… Boom, noteoff problem again. It does make some sense: need to trigger a velocity of zero to the previous note, But this is where memory would come in handy.
Found part of a solution in using the right inlet of a [
Now, the synth produces the correct effect, even with multiple incoming notes.
In fact, doing this with [
poly] may bring us closer to the original effect created by Robby Kilgore on the Oberheim Xpander! Adding more polyphony than the notes which are produced internally, getting a rotation of notes… and a comeback of the noteoff problem.
So, getting closer, but my learning path is still winding around. Will search for known solutions, as it’s surely a common problem. Don’t necessarily want to go all the way to a minimal sequencer with [
tabwrite] and [
tabread], but it could be a solution and would have the added advantage of leaving a trace on which notes have been generated.
Will get it eventually!
Compiling Pd-extended on Windows
I created a new thread as the older post [Problem compiling on windows] (http://forum.pdpatchrepo.info/topic/967/problem-compiling-external-on-windows/16) seems to have ended and my problem has a different nature.
Moreover. I have not been able to find an answer on the puredata sites (puredata.info or puredata.org).
My end goal is to play with the 'grid' external in pd-extended/externals/unauthorized/grid but since I do not get this one working and I have never compiled an external before I started with the simpler tutorials in Pd/doc/6.externs.
My steps and error are as follows:
**1. **Adap path in 'makefile' in Pd/doc/6.externs to 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC'
(this path contains a /lib folder with .lib and .obj files on my machine)
**2. **Start ( Admin) Visual C++ 2008 64-bit command prompt
**3. **Locate directory Pd/doc/6.externs
**4. ** run 'nmake pd_nt' command
**5. ** gives error in locating the libc.lib file
(LINK: fatal error LNK1181: cannot open input file 'C:...\VC\lib\libc.lib'
When I remove this instruction from the makefile, I does not find the kernel32.lib file also.
When I finally remove the former instruction, I get an error creating the library obj1,lib and object obj1,exp as I have 6 unresolved external symbols ex. obj1.ob : error LNK2019: unresolved external symbol __imp_post referenced in function obj1_float
Could someone help me solve these issues and help me succeed in making this external work?
Then, any additional explanation in getting grid to work afterwards?
Any additional info regarding Pd's treatment of externals/libraries etc is appreciated as well.. I just can't get a grip on it,
Referencing argument array names in PD subpatches / abstractions?
Consider the following trivial patch (testing on Pd 0.45.4 on Ubuntu 14.04):
In it, I have a
[pd mysubpatch A]. As far as I remember, the
A is now an argument of/to the subpatch, in particular it is the first argument - and references to
$1 inside the subpatch should expand to
So, I've decided to place an array inside the subpatch, and call it
$1-array, similar to how in abstractions, arrays are/can be called
$0-array - except there the
$0 doesn't expand to any arguments, but instead expands to a random number (Dollar signs in objects and messages | PURE DATA forum~). My expectation is that the
$1 in my case would expand to the first argument,
A, and thus the array name at instantiation time of the object
[pd mysubpatch A] would expand to
The idea is thus to be able to put multiple subpatches in a patch, and control their internal arrays' names by supplying unique arguments. So, I try to copy/duplicate the
[pd mysubpatch A] into a
[pd mysubpatch B], expecting its array would ultimately be called
B-array. So far so good, because I can do this without any problems.
Now consider a slightly more complicated case where I also have a
tabwrite~ in the subpatch:
Now that I have
[tabwrite~ $1-array] referencing the
$1-array in the subpatch, as soon as I turn on DSP/audio, I get a ton of
warning: $1-array: multiply defined messages. As I don't get this message when I have only the
$1-array in the subpatch, I'm assuming it is not the logic in naming the arrays
$1-array via subpatch arguments that is the problem, but instead it is the reference in the
[tabwrite~ $1-array] which is causing the warning message.
Note that exactly the same happens, if I save the subpatch as an abstraction
mysubpatch.pd, and use it as two objects
[pd mysubpatch.pd A] and
[pd mysubpatch.pd B]:
But then, in this case, how would I reference such a subpatch/abstraction array, named through an argument, from inside the subpatch/abstraction itself? Note that I need fixed, explicit, known names of arrays, so a workaround like
$0-$1-array wouldn't work for me, since the
$0 would expand to a random number, which I in principle do not know from the outside (and I'm not sure
$0 even applies to subpatches).
udpsend and receive
@toddak If you have installed extended then it will be a path problem...... or an argument problem....... for some objects Pd needs to be told where they are, and some objects will not create without their "arguments". [dumpOSC] needs its port number, and if the number is already in use it will not create anyway!..... (you would get path problems with vanilla as well, but the following would not solve the problem because the objects would not be there at all!).........
Put [import mrpeach] in your patch first for the [packOSC] object....... or put........
[dumpOSC 1234] normally works, but you could try..........
[oscx/dumpOSC 1234]......... don't forget the port number..... 1234 or whatever....
Pd crashes at startup (after working fine for days)
Since today I have strange crashes on Windows 7 64bit.
Either pd.exe or pd.com crashes when executed.
I had Pd-extended 0.43.4 installed and it worked for days without problem. Today I've tried to load a .pd which I worked on at another computer (same version): pd.com crashed. I've tried to start Pd normal: pd.exe crashed.
I tried an uninstall and re-install, it's installing without problems, but doesn't create shortcuts.
I've tried running it as administrator, rebooted computer.
What's wrong here?!
"Problem details" by Windows:
Problem Event Name: APPCRASH
Application Name: pd.exe
Application Version: 0.43.0.0
Application Timestamp: 5100f299
Fault Module Name: pd.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5100f298
Exception Code: c0000005
Exception Offset: 0005300a
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1031
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789