Sophia

Is there a way send something like a "voc DVI" message to jit.qt.movie? I'm using a DVI to composite video adapter for my Macbook Pro and am looking for a way to send 1080i60 video to it, while still displaying an interface on my laptop screen. I can't just use the monitor like a second display because the hd looks awful in a jitter window, and if I use mirroring and the digital cinema desktop I can't show my interface. What are my options?

Is there a way send something like a "voc DVI" message to jit.qt.movie?  I'm using a DVI to composite video adapter for my Macbook Pro and am looking for a way to send 1080i60 video to it, while still displaying an interface on my laptop screen.  I can't just use the monitor like a second display because the hd looks awful in a jitter window, and if I use mirroring and the digital cinema desktop I can't show my interface.  What are my options?

dvi-as-voc

what method are you using that makes HD look awful in a jitter 

window? you're definitely missing something.

you simply cannot send 1080i60 to a composite display. period. you 

are limited to basically 480i. that's NTSC for you.

On Oct 25, 2008, at 9:26 PM, Zach Gold wrote:

> Is there a way send something like a "voc DVI" message to 

> jit.qt.movie? I'm using a DVI to composite video adapter for my 

> Macbook Pro and am looking for a way to send 1080i60 video to it, 

> while still displaying an interface on my laptop screen. I can't 

> just use the monitor like a second display because the hd looks 

> awful in a jitter window, and if I use mirroring and the digital 

> cinema desktop I can't show my interface. What are my options?

what method are you using that makes HD look awful in a jitter  
window?  you're definitely missing something.

you simply cannot send 1080i60 to a composite display.  period.  you  
are limited to basically 480i.  that's NTSC for you.

>
> Hi,
>
> Is there a way send something like a "voc DVI" message to  
> jit.qt.movie?  I'm using a DVI to composite video adapter for my  
> Macbook Pro and am looking for a way to send 1080i60 video to it,  
> while still displaying an interface on my laptop screen.  I can't  
> just use the monitor like a second display because the hd looks  
> awful in a jitter window, and if I use mirroring and the digital  
> cinema desktop I can't show my interface.  What are my options?
>
> Many thanks,
> Zach


Well, the composite is going to an old CRT tv that needs an rf modulator, so I understand very well that I'm getting far from hd in the end result and could probably just use 720i compression or less (it's in apple intermediate codec, by the way). However, the video renders so poorly in either a jit.window or jit.pwindow that you do see the difference on the tube. I did some reading and I thought the problem was that I sent it through patchcords instead of straight to a device where it is rendered in hardware (not sure if it would do the same thing to view it on a jit.gl.videoplane). So for instance, when I send a voc message to use the digital cinema desktop it looks great. Furthermore, there is a simple aesthetics issue that I want to have controls on my laptop screen and video on the tv, but if I use the tv as a second display, it appears with a menu bar at the top. I was hoping there was a simpler way to send the video from jitter straight to the tv.

Well, the composite is going to an old CRT tv that needs an rf modulator, so I understand very well that I'm getting far from hd in the end result and could probably just use 720i compression or less (it's in apple intermediate codec, by the way).  However, the video renders so poorly in either a jit.window or jit.pwindow that you do see the difference on the tube.  I did some reading and I thought the problem was that I sent it through patchcords instead of straight to a device where it is rendered in hardware (not sure if it would do the same thing to view it on a jit.gl.videoplane).  So for instance, when I send a voc message to use the digital cinema desktop it looks great.  Furthermore, there is a simple aesthetics issue that I want to have controls on my laptop screen and video on the tv, but if I use the tv as a second display, it appears with a menu bar at the top.  I was hoping there was a simpler way to send the video from jitter straight to the tv.


are you using jit.qt.movie going into a jit.window via a patch cord, 

or jit.qt.movie going into a jit.gl.videoplane, or @window attribute?

if you don't know what i'm talking about, follow this link:

On Oct 26, 2008, at 2:08 PM, Zach Gold wrote:

> Well, the composite is going to an old CRT tv that needs an rf 

> modulator, so I understand very well that I'm getting far from hd in 

> the end result and could probably just use 720i compression or less 

> (it's in apple intermediate codec, by the way). However, the video 

> renders so poorly in either a jit.window or jit.pwindow that you do 

> see the difference on the tube. I did some reading and I thought 

> the problem was that I sent it through patchcords instead of 

> straight to a device where it is rendered in hardware (not sure if 

> it would do the same thing to view it on a jit.gl.videoplane). So 

> for instance, when I send a voc message to use the digital cinema 

> desktop it looks great. Furthermore, there is a simple aesthetics 

> issue that I want to have controls on my laptop screen and video on 

> the tv, but if I use the tv as a second display, it appears with a 

> menu bar at the top. I was hoping there was a simpler way to send 

> the video from jitter straight to the tv.

are you using jit.qt.movie going into a jit.window via a patch cord,  
or jit.qt.movie going into a jit.gl.videoplane, or @window attribute?

>
> Well, the composite is going to an old CRT tv that needs an rf  
> modulator, so I understand very well that I'm getting far from hd in  
> the end result and could probably just use 720i compression or less  
> (it's in apple intermediate codec, by the way).  However, the video  
> renders so poorly in either a jit.window or jit.pwindow that you do  
> see the difference on the tube.  I did some reading and I thought  
> the problem was that I sent it through patchcords instead of  
> straight to a device where it is rendered in hardware (not sure if  
> it would do the same thing to view it on a jit.gl.videoplane).  So  
> for instance, when I send a voc message to use the digital cinema  
> desktop it looks great.  Furthermore, there is a simple aesthetics  
> issue that I want to have controls on my laptop screen and video on  
> the tv, but if I use the tv as a second display, it appears with a  
> menu bar at the top.  I was hoping there was a simpler way to send  
> the video from jitter straight to the tv.


If you haven't already, take a look at the help file for jit.window. If I understand your issue right, you can get rid of the bar with a "border 0" message. Also are you scaling your jit.window to match your output resolution? I think the default is 320x240 unless you specify otherwise, same with qt.movie, too.

If you haven't already, take a look at the help file for jit.window.  If I understand your issue right, you can get rid of the bar with a "border 0" message.  Also are you scaling your jit.window to match your output resolution? I think the default is 320x240 unless you specify otherwise, same with qt.movie, too.


Thanks, Joshua. I guess the "direct to window" method is all I had to use. I got this confused with the voc messages for dv thing described in the jit.qt.movie help file. Now, I'm not sure what that is for.

Anyway, I'm still not sure what the best way is to get this to the external display. Do you guys just hook it up as a second display, expand the jitter window, and drag it to the right? Seems like there must be a better way than that. Also, when I turn the border off, I can't expand or move around the window, so would I have to specify its size and position as arguments to get it to show up on the second display?

Thanks, Joshua.  I guess the "direct to window" method is all I had to use.  I got this confused with the voc messages for dv thing described in the jit.qt.movie help file.  Now, I'm not sure what that is for.  

Anyway, I'm still not sure what the best way is to get this to the external display.  Do you guys just hook it up as a second display, expand the jitter window, and drag it to the right?  Seems like there must be a better way than that.  Also, when I turn the border off, I can't expand or move around the window, so would I have to specify its size and position as arguments to get it to show up on the second display?


the jit.qt.videoout is primarily useful for output to firewire or old 

if you want to have your display be fullscreen, use jit.displays to 

get the rect of the second monitor, and set the @rect attribute of the 

On Oct 26, 2008, at 4:18 PM, Zach Gold wrote:

> Thanks, Joshua. I guess the "direct to window" method is all I had 

> to use. I got this confused with the voc messages for dv thing 

> described in the jit.qt.movie help file. Now, I'm not sure what 

> Anyway, I'm still not sure what the best way is to get this to the 

> external display. Do you guys just hook it up as a second display, 

> expand the jitter window, and drag it to the right? Seems like 

> there must be a better way than that. Also, when I turn the border 

> off, I can't expand or move around the window, so would I have to 

> specify its size and position as arguments to get it to show up on 

the jit.qt.videoout is primarily useful for output to firewire or old  
matrox video systems.

if you want to have your display be fullscreen, use jit.displays to  
get the rect of the second monitor, and set the @rect attribute of the  
jit.window to those values.

>
> Thanks, Joshua.  I guess the "direct to window" method is all I had  
> to use.  I got this confused with the voc messages for dv thing  
> described in the jit.qt.movie help file.  Now, I'm not sure what  
> that is for.
>
> Anyway, I'm still not sure what the best way is to get this to the  
> external display.  Do you guys just hook it up as a second display,  
> expand the jitter window, and drag it to the right?  Seems like  
> there must be a better way than that.  Also, when I turn the border  
> off, I can't expand or move around the window, so would I have to  
> specify its size and position as arguments to get it to show up on  
> the second display?


DVI as voc