Forum Replies Created
-
Posts
-
Per-frame metadata would not be in sync with the surface (if you query metadata it may be out of date by the time you come to use the surface). I appreciate that it makes some things more complicated, but it also makes Syphon very fast and means apps can’t screw each other up by holding on to (or worse, crashing in) shared locks.
A Syphon server presents a single live surface, and you shouldn’t think of it as a series of frames. If, as you do here, you draw twice into the server then the second draw is likely to replace the first one before a client has seen it.
If you have to split the fields inside your app, then you’d be best drawing them in to a Syphon server side by side and splitting them again in QC – or if you can draw the entire interlaced frame then do that and perform the entire split inside QC.
That make sense?
We can’t give general programming tips (try Stack Overflow).
This question was asked very recently http://v002.info/forums/topic/content-of-nsview-disappear/#post-58719
Hi
There are a few problems with your approach – more than I am going to detail, as you should start with a clear method in mind: what is the final intention of your app?
If, as this code tries to do, your intention is to display an image from a file on disk and also output that image via Syphon, then you could consider minimising the amount of rendering to pixel buffers and texture uploads which occur. A good strategy would be to load the image to a buffer and then load that buffer to a texture once, and use that texture for drawing in your view and publishing to Syphon (assuming you are comfortable enough with OpenGL).
Alternatively, something like OpenFrameworks might simplify the task for you considerably.
If you just want to record a movie of the desktop, why use Syphon at all? QuickTime Player does screen recording.
I’m guessing you’re on an old version of Simple Server and the window is hidden when you switch to VDMX, which triggers an OS feature called AppNap on Mavericks.
Update from https://github.com/Syphon/Simple/releases and let us know if that solves the problem.
I suspect you’re recording to a MS-DOS (FAT) formatted disk. This archaic format has a 4GB file size limit. Try recording to an HFS+ (MacOS Extended) formatted disk.
Hi
Presumably you are talking about Syphon Recorder..? File size shouldn’t be a limitation.
Can you
1. Make sure you’re using the latest version from http://syphon.v002.info/recorder/
2. Post a picture of your Preferences window so I can recreate the settings you’re using
3. Post a picture or the exact text of the error message you get
Thanks
Soz. It’d be much less cool for Syphon to ignore AppNap and have hidden servers stop functioning for no discernible reason.
Hi
https://github.com/Syphon/Syphon-Framework/issues/13
Once modern GL is supported, Syphon will work between legacy and core profile contexts no problem.
If you’d like to contribute (which would be great) perhaps that issue would be a good place for discussion.
It looks like it requires a complete path, eg
/Users/josh/Desktop/raincoat.psdI also had to shift the File Read Offset to get it to notice changes in the file path.
Unfortunately the answer is that you must compile on 10.9. We will post a new SDK with a compiled framework soonish.
Perhaps you could check how this build works for you – it will reduce the sample-rate for AAC if it’s higher than the AAC encoder can handle. It also adds support for more than two channels for LPCM audio.
For now, change the sample-rate on the device to 48 or 44.1. A future update will down-sample if you attempt to use a higher sample-rate for AAC.
