mindopera
-
Posts
230 -
Joined
-
Last visited
Posts posted by mindopera
-
-
I'm trying to understand the reasoning behind framerate choices, mostly because I receive so many different ones such as 30, 29.97, 25 and the one that is the most perplexing, 23.98. I know WO can play this different frame rates and filmmakers like the idea that they are matching the frame rate and stutter of old-school film (celluloid) and they will get the same look if played back at 23.98
- Is it better to film at 23.98 and output playback files (HAP-Q) for WO at 30fps?
- Is there any real advantage to achieving a film look or is this a myth handed around?
- Will there be any sync issues if 23.98 fps is changed to 30 fps and played back with a separated audio file and looped over a long time in WO?
- What has been your experience, thoughts, and solutions for the framerate question?
Thanks
0 -
That's good advice.
I will be doing 1080 across four channels on this build, so it sounds like I can expect good performance in the configuration on the WX5100.
Thank Rainer.
0 -
I am looking into building some Watchout ITX cases and want to use one of the two video cards to drive the video. Zotac GeForce GTX 1080 or AMD Radeon Pro WX 5100
I wanted to reach out to the forum to see if anyone has direct experience with these cards or their bigger brothers (full size GTX 1080 and WX7100) in terms of software issues and hardware issues. Things like drivers, features or OS issues, etc. Anything solid you have witnesses on your builds would be helpful.
I currently use Fire Pro 7100's and they have performed well, but I do have some issues when updating drivers.
Thanks
0 -
As far as I know QT is the only wrapper for the HAP family of codecs.
I'm surprised you're not using QT with WO. I always thought QT was an important install for WO.
The WO install software always asks you to download and install the latest version of QT. I have done this for years without any issue.
What type of support are you looking for that you don't get?
0 -
These look like they can be pretty handy.
Thanks for the heads up.
0 -
Do you have a WATCHOUT (WO) license dongle plugged into the USB port of each WO PC? WO requires that the Production PC and the Display PC have a physical license dongle (https://www.dataton.com/shop/watchout) in order to communicate with each computer. If you have the physical keys installed in a USB port, then you might try them in different USB ports to see if they are seen. You may have a bad USB port.
You should not have to run windows in Safe mode for WO to work.
0 -
In my experience, there is no solution to leave the looping video and enter the next piece of media without using a tween. Usually the opacity tween. If you don't dissolve out of the loop it will be a jump cut to the audience. I usually handle that limitation by designing the video's to look as though they are seamless with a tween in mind, but it all depends on what type of control you have of the original video.
For me, it's using visual techniques to hide the change.
Maybe someone knows a trick to get the looping video to end at an exact frame before sending the play-head forward. I'm always eager to learn something new.
0 -
That's a great explanation Miro. Thank you
0 -
Can you explain the difference between scan sync and frame sync?
And does having frame sync matter if there is no scan sync?
0 -
I would be interested in the results since the WX series seems to be where AMD is headed.
0 -
Here is the computer info.
- Intel I7 X980 @ 3.33 GHz
- 12GB of RAM
- Windows 7 Pro 64 bit (tweaked)
- OCZ-Vertex3 ATA SSD 240Gb (original)
- 2- 250gb 850 EVO - Raid 0 = 500GB (New)
- AMD FirePro W7100
Driver Packaging Version: AMD 15.201.2401-151104a-296716C-Retail_End_User
All connections were thoroughly vetted. I have 4 identical computers running it and each had the exact issue occur.
0 -
It happened originally in WO version 6.1.6 and the test I did in my office was in version 6.2.
When screen four goes black it is because it is no longer sending the video signal. If there are any other graphics above that image they drop out as well. I was using a simple version of my original file to test with an I will send that to you at the support email.
0 -
I had this issue back in October. I have never seen this before or after this particular show.
The issue was when the play-head reached a particular images or videos the fourth display output of four displays completely lost its signal. I had two images and one video that had this issue. Although I worked with Jim Kelner and Paul Johnson to isolate the issue before the show, we never pinpointed the exact cause of the signal drop. We were able to keep it from happening during the event by using the scale tween to flip the image or video horizontally. Once the media was flipped it behaved as expected.
I have spent some time today replicating the issue in my office and tracking down the problem. At first, I thought it was a file issue because I was able to get the display signal to turn on if I tweened the file to flip horizontally in WO as well as turning off certain layers in the original photoshop file of the media in question. Ultimately I believe I found what was causing the issue. I had not set the fourth display in the correct stage position. I had placed display four, 4 pixels (stage position 4808px should have been 4804 px) too far to the right and that's why in my video I'm able to snap the photoshop file in either direction. If it was set in the correct place it would only snap to the left. I went back to the original file with all the media and changed the pixel position, took the flip tween off and then everything worked perfectly.
https://www.dropbox.com/s/p78sv2hakzc0ow4/20171215_170053.mp4?dl=0
I am still stumped why certain files had the issue and other still and video files didn't.
Any feedback or ideas on this issue are appreciated.
0 -
That is my understanding as well. Dynamic Server is not meant to serve video content.
You do have several options.
- Simply download the video and put it on a timeline.
- Another is to put a capture card on your WO server computer (preferably Datapath capture card) then capture the live feed from the computer playing the video.
- This option should be released very soon. Using WO v6.2 NDI video feature. Add the computer as an NDI video and capture the screen at 1080@60. All it requires is a piece of software.
I did an example video of how this works below. I have been very impressed with results. Less than a frame latency and no need for a video capture card.
https://www.dropbox.com/s/8hlg7afag34oazq/20170727_143744.mp4?dl=0
0 -
What is the status of version 6.2 release? I'm eager to show my clients its capabilities.
0 -
Also make sure your not in standby mode. As that will be black as well.
0 -
We could use more detailed information of your issue before being able to help. Can you answer some or all of these questions?
Hardware?
Software versions?
What dialogue box is asking for pixel count?
Is that a windows dialogue box or a WO?
How many displays?
How many WO servers?
What are the pixel count of the displays?
What's the overall pixel count of then canvas?
0 -
Any word on the release of 6.2? Are we a month away or longer?
0 -
I completely agree with Thomas.
One thing you could add to the Aux Timeline is the use of Conditional Layers, commonly used for changing language in a program it may be useful in your situation.
Any individual layer in a timeline can be made a conditional layer. For instance you could have the main performer video on a layer in an aux timeline and in the same aux timeline on the layer above you could place the understudy video so it triggers at the same point in the timeline as the main performer. Enter the layer panel on the side the timeline and set the main performers layer condition to 1 then set the understudy layer as condition 2. Before you begin a program and know which performer will be performing that night you would go to the preferences menu then go to conditional layers and check that performers condition, refresh and play. If the understudy is going to preform that night then you would need to turn conditional layer 2 on, refresh and go.
This can also be done on the main timeline although it may get cluttered if you have a lot of performers to change, which is why aux timelines might make since.
Like Thomas said, test, test and test.
0 -
I had some Focusrite Scarlett 6i6's and they needed the driver in order to work. Once I loaded the driver they showed the channels in the WO player pull down menu.
Did you load the drivers?
0 -
Based on the information you are presenting it doesn't seem like you would need a scaler. WO can handle many different types of resolutions and the Virtual Display feature is a great way to deal with odd sized displays.
How you set up the displays and determine how the WO servers manage the pixel canvas will determine the amount of equipment you will need.
0 -
Hi Thomas, with much the same configuration as your computers running 6.1.6, I have had this issue happen to one of my computers twice on two different shows. One big variable is the upgrade to 6.1.6. I never had this occur before.
The first time WO crashed it was sitting on a still for about an hour then WO crashed (I don't know if it had launched other instances) then quickly recovered. Then it never occurred again during that show.
The second time was last week, WO crashed on the same computer running a looping video (3840x720) then recovered on its own. The first time it happened I checked the tweaks on all computers and there were a few items not tweaked on one computer, so I thought I had fixed it. The second time it crashed I couldn't hunt down any issue with computers or tweaks. Although it could easily be a computer related problem.
Most of the time I work in live update until I am getting close to being in the show then I switch live update off. So it most likely is happening when live view is on.
I'm not sure how to troubleshoot this since there are so many variables. All I can do is keep an eye on it pay attention to the circumstances and see if it happens again.
0 -
I had the same inconsistent stuttering with HAPQ files on a recent show using 4K resolution (3840x2160), I re-encoded the same files to mp4's and the stuttering went away. The possible issue might be that the HAPQ files in my case, had too high of a data rate for the single SSD I was using on each machine. Which meant the SSD couldn't keep up with the demand of playing back the HAPQ file.
I have added two new 256 Gb SSD's and placed them in RAID 0 doubling their read speed and also their memory capacity. I kept the original hard drive for the OS only and the WO program and all show files are all placed on the RAID 0 drives. Since the computers travel so much it's hard for me to test the performance of the new SSD's, so in theory, the HAPQ files should work better. I have a battery of tests to run in the next two weeks and will let you know if theory becomes fact.
0 -
In Quicktime, After Effects and Adobe Encoder there are few options available. The best option for coding in chunks is FFmpeg and I find the interface challenging, to say the least. The good news is if your hardware is high end and you have fast SSD's then the HAP and HAPQ files work well without chunking them. As with every solution in our industry the more you can test in a real situation the better your outcome will be when your live and in my humble opinion I seem to always have something to learn about video codecs for playback.
0
Unable to use built-in VNC server on Display machines
in WATCHOUT FORUM
Posted
Don’t give up on the vnc installed in WO. If everything is correct with the setup it will work.
Can you describe in greater detail what your server system is? Video card, processor, operating system, version of WO, etc.
Also, where and how many video displays is the server computer sending its video signals to, projectors, video wall, switcher and is the signal going directly to the displays?
What cables are being used? Are you using active display adapters?
Are your servers set to a different and static IP on the producer and the server computers?
Is the Firewall turned off on the producer and the server computers?
It kind of sounds like an EDID issue and more specifics could help.
I’m based in Seattle for future reference.