I have an issue with OSMF player: in case you load a page with video, then send system to sleep - after system wakeup playback starts itself. This is valid if you are using f4m file or rtmp stream. Those issues are visible on OSMF demos:
http://www.osmf.org/dev/1.6gm/StrobeMediaPlayback.html - no issues, but here
http://www.osmf.org/dev/1.6gm/debug.html video starts itself after system wakeup.
It sometimes happen if you just open a browser and leave it for 15-30 mins. Commonly - any Mac or Win7, any chrome/firefox...
Changing source to flv allows to get rid of the issue.
Also, if you load page, than start it and pause it - the issue will not reproduce as well.
Control bar behaves also very strange: playback time and scrollbar are updated according to actual playback, but play button (not pause) is presented. on case i push play - video restarts.
Systems: MacOS (10.7.5, build 11G63), Firefox 20, Chrome 26, Flash (11.7.700.169); Windows 7: Firefox 17, Flash (11.6.602.180); our cluents also mentioned they have same issues on Win8 under Internet Explorer, Firefox and Chrome.
I guess that is osmf bug, but no help from adobe (http://forums.adobe.com/message/5246796#5246796), maybe someone has an idea?
Try to compile the 2.0 version of Strobe by downloading the OSMF source
I wouldn't spend a lot of time debugging the issue if that doesn't work. Strobe has not gotten any development support in ages and there is certainly things like this lurking around in the source code.
How to compile it has been answered before on stackoverflow.
I wouldn't spend a lot of time debugging the issue if that doesn't work. Strobe has not gotten any development support in ages and there is certainly things like this lurking around in the source code.
Related
My first stack overflow question, here we go.
Last week the computer on which a prototype vision application written in C#/.net was running crashed due to an unreleated reason. this resulted in the need to fresh install windows (windows 10 IOT). after installing windows, halcon 20.11 progress and setting the licenses the application starts, but no output is shown on the smart window control, even tho this worked beforehand?
i have been trying to debug this problem for the last day, but have had no luck, what i have allready tried:
used the remote debugging toe verify that the image is captured and processed and "displayed".
checked the system logs for any warnings, there were none.
Tried one of the example programs the come with Halcon, which also does **not **work.
Ran the application on my development PC, which worked flawlessly as it always did.
Reinstalling Halcon.
does anyone have had any similar experiences and/or any clue how to solve this problem?
problem has been solved. in the end a reset of the bios settings to there default values did the trick. Don't know what they exact cooperative was, but at least it works once again.
I'm making an application with WebVR using React VR. I'll test the application with my Oculus Rift and HTC-Vive. I'm using the browser Firefox Nightly to access the WebVR API's.
If I browse to my application using Firefox Nightly or Chromium, I arrive in an empty space with a loading message. A few seconds later I got this message on my Oculus Rift:
Sorry, firefox.exe/chrome.exe is taking a while to load. If this issue persists, please take off your headset and check this app on your computer.
On the HTC-Vive I got this message in Steam VR but it doesn't load at all.
(unresponsive) firefox.exe/chrome.exe
In the webbrouwser, I got the result I must see inside the headset with motion tracking.
I'm using this browsers
Version Firefox nightly: 55.0a1
Version Chromium: 56.0.2910.0
And this are my specifications:
GeForce: GTX 970
GeForce Game Ready Driver: 378.66
Processor: Intel® Core™ i7-6700 CPU # 3.40GHz
RAM: 15.87 GB
This isn't the Oculus software at all. The problem is an NVIDIA driver update that broke everything. You need to go to the NVIDIA site and download drivers from the "376" generation (Dec'16-Feb'17). Install those and the problems go away. I confirmed that things are working with Oculus 1.12, 1.14, and 1.14 beta channel.
It looked like Oculus broke things because 1.14 came out on almost the same day as the "381" NVidia driver update.
Downgrading my Nvidia driver to 376 worked as a charm for me, but I can't run the VR scenes on Nightly, just on Chromium.
I was able to get my Oculus to work with WebVR by enabling the Beta channel within the oculus app and letting it install an update. Seems like the current Oculus version might be broken.
Try installing SteamVR. SteamVR overrides the Oculus runtime and runs applications on its own.
Try closing Oculus Home before you launch your WebVR application using the WebVR button.
Make sure you are not in the Beta/Dash mode in Oculus
Try to disable the auto-opening of Oculus Home. Oculus home opens automatically on wearing the rift. To disable, select “Run as admin” field in the properties of the Oculus app. More specifically, go to /Oculus-Directory/Support/oculus-client/OculusClient, right click, select properties, check “Run as Administrator”.
Make sure that your Desktop and Rift are connected to the same Graphic card. You might need an HDMI to DVI converter for the same. This is what fixed the problem for me.
So I have Ubuntu 14.04 Installed on my system with a few "tweaks", mainly ccsm. I also have google chromium browser installed as well. I do a lot of work in the browser and usually have 10+ tabs open in my system.
I also like to use the multi-window (Workspace) and have 8 Workspaces (thus one of the reasons for ccsm).
Once I leave the computer and try to come back (before the screen locks), the computer is COMPLETELY frozen with my HDD running at very high speeds. I have a system monitor that monitors the CPU activity and HD activity and right before those things freezes, my RAM is at 100% and so is my HDD.
I'm wondering if anyone can help me FIGURE OUT what the problem is? I've been using ubuntu since '08 so I'm familiar with it. I just don't know where to start!
HELP!
I can not deal with the problem until I install the following packages as follows
sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal
You could get the detailed reason from http://www.howtoeverything.net/linux/hardware/random-freezes-integrated-hd-4000-graphics
Maybe you have to consider the Google Chrome or Chromium, whose two or more different Flash plugins conflict with each other, and the freeze problem disappear after you Disable the Flash plugins in the webpage opened by inputting
chrome://plugins
in the URL address of Chrome
Or another useful method of changing the chrome plugins is to uninstall the google-chrome completely,and then install the current chrome with newest flash plugin.
After all the above are done, the system need restart.
Hope it can help. Good luck!
I've done some research all over the net, I guess I am just looking for conformation.
Due to how Microsoft has put security on autorun in vista and above. Autorun from a usb no longer works. Correct? It seems like it will still bring up the options to run .exe but for some odd reason I cannot get it to run a .pdf. This site has suggested that I load up a pdf reader and run that and then call it to run the pdf. But a generic pdf reader would still have to go through the install prior to running it, something I am trying to avoid.
The other idea I came up with was cause of this specialty usb manufactures have stated that they their usb drives can autorun files because they are formated to be local disks.
So after some experimenting and doing this I converted my usb to a local to see if that would work and pasting the autorun.inf in there with the correct code...
[AutoRun]
shellexecute=mypdf.pdf
icon=mypdf.ico
label=mypdf
sadly it does't work
Also after thinking about it creating a local disk would only work with the driver software that I loaded up onto that usb... so say it is a 64bit and the client has a 32bit it wont run. (right?)
Can someone just confirm that there is no way to autorun a pdf from a usb? or even have it as an option to select from when it is plugged in for the first time. I cannot believe I have spent an entire day trying to just get autorun to work.
Thanks for taking the time to read this nub question
Try using a PDF viewer which does not require installation, eg:
http://www.snapfiles.com/get/sumatrapdf.html
From this site:
http://www.snapfiles.com/features/ed_usb_software.html
Using sumatraPDF portable installation you can launch that from the flash drive.
The way I did it is by creating autorun.inf with the following:
[autorun]
icon=autorun.ico
label=Label for Drive
action=Action Description
open=autorun.bat
And a autorun.bat file with the following:
start SumatraPDF.exe ../pdfname.pdf
However, if the user has autorun turned off it will not work and in Windows 7 and above autorun functionality for flash drives is restricted to label and icon only.
I m having trouble with AIR debug launcher(adl) under win 7 64 bits home familial with AIR SDK runtime 2.7. It sometimes crash and i have no posibilities to understand if its because of my software or not.
Does anybody know how I can get some logs to know why it crashed ?
When its crash, the debugger is going away and i dont know where my software bugged if it did...
I have been testing my software under different SDK under win7 and i still had some adl crash. The software is working correctly under winXP. I suppose it has something to do with win7 and AIR but how can I find any informations on what is going on...?
thanks for any tips...
i have been able to find windows crash dump files. Then i have download windbg. And started debugging air debugger launcher... but im stuck... not good debugging without symbol files... I guess cant do more then that. The error come from an attempt to convert an integer to a unicode string but i dont know why this function is called, by who and when...
sometimes it doesnt crash also.
Finally found some windows crash dump log files. Also started to debug with windbg the AIR. :))) lol