Jitter 1.5.2 installed
? error: jit.gl.shader: unable to find CG framework.
coll: no file BatchFolders
? error: fpic: Audio_File_Chooser.jpg error -47 opening file
coll: no file SoundFolders
coll: no file QTFolders
coll: finished, 1 lines
coll: finished, 1 lines
Error set 2:
Jitter 1.5.2 installed
? error: jit.gl.shader: unable to find CG framework.
coll: no file BatchFolders
? error: fpic: Vinyl_Tracker.jpg error -47 opening file
coll: no file SoundFolders
coll: no file QTFolders
coll: finished, 1 lines
coll: finished, 1 lines
Error set 3:
Jitter 1.5.2 installed
? error: jit.gl.shader: unable to find CG framework.
? error: fpic: Doll_Head.jpg error -47 opening file
coll: no file BatchFolders
? error: fpic: QT_Movie_Controls.jpg error -47 opening file
? error: fpic: Audio_Settings.jpg error -47 opening file
coll: no file SoundFolders
coll: no file QTFolders
coll: finished, 1 lines
coll: finished, 1 lines
We installed the new update, and it worked PERFECTLY! We were so excited. It
had never worked so well. We were able to scratch the video back and forth
with only minor frame loss, and it played forward perfectly. After many
hi-fives and cheers, we called it a night.
The next day, we hooked up our USB midi foot controller, and we started to
experience the same problem we were having previously, with the frame rate
dropping. Assuming it was the foot controller, we unplugged the foot pedal
and re-started the program and the computer. Unfortunately, we were unable
to get it to work properly again.
Then, we started noticing the above errors when restarting the program.
Hopefully they help.
If we do not have our Final Scratch 2 interface hooked up to the computer,
the video in maxi-patch plays perfectly at full frame rate.
Also, in re-reading our other post, we noticed that we had not included our
in and out vector size. Any recommendations? We found our computer will
accept up to 2048 on the I/O Vector setting, and up to 1024 on the Signal
Vector size. We tried pushing the Signal Vector size to 2048, but it crashed
the program. Is there an ideal size? Will vector size the affect frame rate
in any way?
Thanks so much,
cb and Jesus
Bug report: Video slow down !!!!
-
- Site Admin
- Posts:1093
- Joined:Mon Jun 07, 2004 9:17 pm
Two more questions
Jesus-
Thanks for the detailed error reports. I will look into why the .jpg images don't seem to be found.... but that should not effect framerate at all. The errors that are being reported shouldn't matter at all to the program's framerate performance.
I still need you to answer these two questions:
1) Which version of OSX are you using? Hopefully 10.4.3 (or higher). If you're still using Panther (10.3.X) then you should upgrade to Tiger immediately.
2) What are your "Energy Saver" System control settings? Specifically, under the "Options" tab you will see a menu where you can select "Processor Performance". Make sure "Processor Performance" is set to "Highest". If it's set to "Automatic" that could explain why sometimes your framerates are high and other times they slow down.
Regarding "I/O Vector Size": It should work just fine if you set I/O Vector Size to 128 or 256. Also make sure that "Signal Vector Size" is set to the same value as "I/O Vector Size".
Thanks!
DLP
Thanks for the detailed error reports. I will look into why the .jpg images don't seem to be found.... but that should not effect framerate at all. The errors that are being reported shouldn't matter at all to the program's framerate performance.
I still need you to answer these two questions:
1) Which version of OSX are you using? Hopefully 10.4.3 (or higher). If you're still using Panther (10.3.X) then you should upgrade to Tiger immediately.
2) What are your "Energy Saver" System control settings? Specifically, under the "Options" tab you will see a menu where you can select "Processor Performance". Make sure "Processor Performance" is set to "Highest". If it's set to "Automatic" that could explain why sometimes your framerates are high and other times they slow down.
Regarding "I/O Vector Size": It should work just fine if you set I/O Vector Size to 128 or 256. Also make sure that "Signal Vector Size" is set to the same value as "I/O Vector Size".
Thanks!
DLP