-
midiguru
Yes, it's a fresh install.
This appears now to be an intermittent problem. Today things are working (such as creating a bang button via Ctrl-1 and typing "bng") that failed to work two days ago. The cyclone folder is in the extra folder, as expected, and coll-help opens and creates a coll object.
I have no guesses as to the reason for the problem disappearing. If it recurs, I'll try to isolate the conditions and report it.
-
midiguru
Re-learning Pd after a couple of years. Downloaded 0.43.4-extended, installed it in a Windows 8.1 machine. It runs, but apparently some or all of the extended functionality is missing. Objects including atoi, coll, button, and beatpipe (selected at random from the Floss manual list) get a "...couldn't create" message in the Pd window.
Ditto for a bunch of seemingly essential stuff. If I hit "About Pd" in the Help menu, I get "couldn't create" messages for things like bng, expr, del, and lgl, all of which are evidently used in the About pop-up.
Plainly there's something wrong with the install. But what?
-
midiguru
I've used Pd in the past, but not lately. Tonight I installed a fresh download of Extended to my Win7 64-bit PC. After installing, I ran it and tried the very first "Start Here" patch in Help Browser > Manuals.
Below are the error messages I get in the console. Needless to say, the Start Here patch is not functional. I'm sure this is something simple to do with paths or environment variables or something, but I have no clue how to troubleshoot it. Thanks for any tips!
--Jim Aikin
********************************
(The first message is on start-up. The others are when I load "Start Here.")
Could not delete 'HKEY_LOCAL_MACHINE\Software\Pd-extended':
unable to delete key: Access is denied.cnv 16 40 16 empty pddp_dsp_canvas dsp 7 8 0 14 -233017 -33289 0
... couldn't create
tgl 18 0 THIS_IS_HERE_TO_GET_RID_OF_THE_OUTLET GLOBAL_PDDP_DSP_TOGGLE empty 1 8 1 9 -233017 -33289 -33289 0 1
... couldn't create
grid grid1 200 0 199 200 0 199 1 1 1 10 10 197 212
... couldn't create
nbx 5 14 -1e+037 1e+037 0 0 empty empty empty 0 -8 0 10 -262144 -1 -1 177 256
... couldn't create
nbx 5 14 -1e+037 1e+037 0 0 empty empty empty 0 -8 0 10 -262144 -1 -1 107 256
... couldn't create
filmQT: Could not initialize quicktime: error -2093filmQT: Could not initialize quicktime: error -2093
[pix_film]: DirectShow support
cnv 15 300 40 empty empty empty 124 20 0 12 -228856 -66577 0
... couldn't create
bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1
... couldn't create
tgl 15 1 empty empty empty 17 7 0 10 -262144 -1 -1 0 1
... couldn't create
button Open
... couldn't create
openpanel
... couldn't create
cnv 15 300 40 empty empty empty 124 20 0 12 -228856 -66577 0
... couldn't create
tgl 15 1 empty empty empty 17 7 0 10 -262144 -1 -1 0 1
... couldn't create
bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1
... couldn't create
cnv 15 300 40 empty empty empty 124 20 0 12 -228856 -66577 0
... couldn't create
delay 200
... couldn't create
dac~
... couldn't create -
midiguru
I was a little suspicious of the fact that Pd's default installation was in Program Files (x86). So I uninstalled it and reinstalled to the root C:\ drive. Now it launches without an error message, and the "Start Here" patch loads with only one error:
filmQT: Could not initialize quicktime: error -2093
I can live with that, since I have no current plans to use the video stuff.
Whoever is maintaining the Windows installer might want to look at this issue.