Val Brown

I'v also noticed that LV8.2 has an icon for the Media Player Object on the .Net/ActiveX pallete and it has the same operational characteristics. It seems like, perhaps, NI didn't really test that function very deeply.

I've downloaded the trial version VideoCapX and it looks very interesting -- and complete. Do you have any sample VIs? esp ones that support audio playback and/or playlists?

I'm really wanting to use as much of the native capabilities of WMP as possible -- that makes things far easier for my users. This is also important because I'm not just playing back video; I'm really using all of the multimedia capabilities of WMP including visualizations and need to programmatically change control settings "on the fly", with no user input. Going to another media player isn't that appealing because it isn't WMP and that will be "off putting" to some users. Thanks for the idea though and I will look at it just to see how it might work.

I've tried this implementation but the problem is that the source code is built around the use of Picture Controls -- they have "DrawAreaSize" and ZoomFactor" as available properties. M code is built using an ActiveX container -- because I'm embedding WMP in the VI -- and the ActiveX Container does not have those properties. Or perhaps I need to set up some kind of further invoke/property node or... :headbang: I'm still evolving from Event State Machines built around polling While loops instead of Event structures and I'm not so familiar with all of the Pane/Panel etc references. So that means I greatly appreciate the time and effort of those who are posting on this issue.

I hope to post a more in-depth response later tonight as I'm still knee deep (well eye brow deep) in an on-site consultation today; however, this thread is very helpful to me. The current code IS an old style polling process ESM with an idle state and various "operate" states. The problem occurs when this VI is called elsewhere (eg sending a Play command to the embedded WMP ActiveX object). It is at that point that the ActiveX container is resized by the WMP object. This has to do with default parameters of the media object being passed to/operated upon by WMP in the Play (or other) operation. So I have two possible paths, as I see it. 1. Some version of the examples given. 2. Prepare ASX files as the media input to the WMP object and embed in them commands for proper sizing etc. This solution involves making certain that ONLY such ASX objects are used by the WMP and so has other serious limitations. Again, thanks so much for all of your help. This is ALSO assisting me in understanding Event Structures more thoroughly.

You all are awesome! I'll take a look at these ideas and let you know. Thanks for the info.

Yes, good idea. I'm just about out the door on a brief trip so we'll post a "condensed" example presently and would definitely appreciate all comments.

Nope, that has no effect regardless of how it's set. But what does help is to use a property node to set the container bounds of the ActiveX containter to a set value AFTER making any control call to WMP (eg Play, Pause). It's very strange to me but that's just because I don't understand it, I'm sure. Any other ideas? I'm sure there's something I'm just "leaving out".

Thanks for the tip but, when I tried to get/set "Pane" for an ActiveX container via a reference node for it I get an error code of 1057 from the "To more specific..." operator.

I'm not finding the scale object option in the Edit menu in LV8x. Am I missing something -- literally?

You might want to include the TD_MS_WIN_DRIVES_INFO.ctl since it's a TD.

Actually I don't know about that as these are deployed systems -- ie out "in the field" with customers. I have no direct access to them, although I can do Remote Desktop to control their system. I wonder if it's possible to use MAX in that way or to do a remote install so that it does run on the deployed systems.

I have a large legacy-code based LV Project (now in v8) and I'm having some problems after building an EXE. The problem manifests on older systems (eg P IV 2.4 GHz, 1 MB RAM and slow FSB) when attempting to access the serial port. With the migration to LV8 I had to finally let go of the legacy serial i/o functions. I had successfully maintained them during the migration to v7.11 but v8 simply will NOT support them. So I had to migrate to VISA as well -- not a trivial task given the overall project. In any event VISA 3.6 works well on many systems but on older systems I am consistently generating a -1073807343 error when trying to configure the serial port. I KNOW that the port assignment is correct because, when I revert to my legacy software, the exact same settings are used and the device connected to the assigned port is seen with no errors. So the migration from LVRTE 7.1 to LVRTE 8 coupled with the introductin of VISA is creating the problem. Any ideas would be welcome.

I have LV code that calls two out-of-proc servers. In my deployed v7 and earlier apps, these out-of-proc servers were shut down when using the built app closed using the Quit LabVIEW function. After migrating to LV 8, developing a Project for the code, and migrating the BLD file, I was able to build the app; however, closing the app using the Quit LabVIEW function orphans the two out-of-proc servers. Invoking the APP_EXIT method(?) via the run-time menu File/Quit method or by clicking on the red X (upper right corner) not only shuts down my built app, but also the two out-of-proc servers. It seems that the current Quit LabVIEW function no longer implements APP_EXIT. I've searched the documentation and this forum but can't find any particular information on implementing APP_EXIT programmatically. Any good ideas?

Actually I had a similar problem -- error type 2200 -- but then the problem resolved when I copied the latest lvanlys.dll to the support folder for my deployed app.