[Bernie Lademann]

Caleb has provided me with a update to Titler Pro 6. I can now confirm that the issue appears to be resolved for me too.

Cheers,
Bernie.

[Bernie Lademann]

It would be interesting to know whether the issue is really resolved, or whether it was resolved by moving all of the project files to local drives? Only the developers can answer that for sure.

I’m still waiting on a response from NB with regard to my open case on this matter.

Cheers,
Bernie.

[Bernie Lademann]

Hi Bart,

Just quickly, here is my 2c.
Question 1.

If you are creating a 1920×1080 project and want to use the 2K footage at 1920×1080 then use the “match output aspect”. It will then scale down the whole image to fit. If you want to frame a 1920 x 1080 part of your 2K footage, use “match source aspect”. This will now display pixels 1:1 and allow you grab a 1920×1080 from from the source.

Question 2.

Vegas converts the frame rate of the source media to match the project settings. I have had success in importing 30fps footage and 50fps footage into a 25fps project with no slipage. I have never tried the other frame rates.

Question 3.

The last number normally represents the color depth x colors. For example 32 = 8bit Red + 8bit Green + 8bit Blue + 8bit alpha channel
If there is no alpha channel, the it will come up as 24, rather than 32.
I am not sure whether 12 is correct, as I highly doubt that you have 4bit color channels. You need to check the source media to see what your file really is and then see if Vegas is representing the wrong information.

Cheers,
Bernie

[Bernie Lademann]

Hi Edward,

I am not sure what you are saying. Caleb and your support staff had full access to my machine for two days. During the time that they were connected, they firstly determined that the 3 faults I was witnessing were real and that they had enough logs and machine info etc. that they could take back to the developers for action. The last comment was “we will get back to you”, not “we will close the issue and tell us when you see it again”.

Telling me that the software works fine on your machine, is comforting but totally unrealistic.

The term intermittent used in software engineering is too often used as an excuse for inaction.

When I contacted NB support, your staff connected directly into my system. We repeated the same actions and found that the outcome was correct one out of the three times attempted. We then changed the system configuration by placing the source video clips on a “local” drive and found that it worked 5 out of 5 times .

Having worked for years in software development, I know that this is valuable information in isolating the fault. The first clue is that if changing the location from a network drive to the local drive involves different function calls in the code, it also generally takes longer for responses from the network, than a high speed local SSD. My guess. There are timing issues. As a developer/tester, I would ensure that the system test included scenarios where all of the project files and/or data files were located on NAS devices and if that didn’t show up issues, I would slow down the network and repeat. I am pretty confident that you will see our issues then.

The second issue I demonstrated was the fact that closing the TP window and switching back Sony Vegas window quite often results in a locked up application, resulting in having to go to the task manager to kill TP and VP. This again hint very much at a timing issue where the two applications do not do the appropriate handshakes and they wait indefinitely for a response from the other application.

I hope this issue is taken more seriously now, as I feel a bit like Rich at the moment.

Remember that a production environment is not an isolated machine.

It is not uncommon to have multiple drives for storage of data and project files. This is done for either speed, or for better customer project management, or for secure storage (NAS).

Anyway, when I last contacted support, I offered NB that if they needed a system to verify that their proposed fix, I would happily try it out provided that I could rapidly revert back to a working system if it didn’t work.

Cheers,
Bernie.

[Bernie Lademann]

I find it interesting that Edward (who seems to be working for NewblueFX), responded with “please contact NewblueFX support”, when the very nature of this thread is that NewblueFX support are not doing anything to help the issue.

I have a lot of respect for small companies with limited staff on the payroll. It is hard to deal with lots of customers and provide feedback. However, forums such as this, is a good way to get information out back to the public.

From what I can see is this problem has been around from at least Titler Pro 4 days and may still be Titler Pro 6. I also see that there are at least 6 different people who have reported this exact same issue and have had technical support contact them, accessing there machines, etc. and then doing nothing.

If I owned NewblueFX, I would put an end to this issue by supplying a free full licence of the latest version of Titler Pro Elite to each of the 6 people on this forum. This will have the following consequences.

1. It will tell us that NewblueFX care about their customers and are listening.
2. The 6 people here have demonstrated a willingness to try out the new software on commercial projects, to see if the problem has been fixed.
3. The 6 people will all be happy to report back to NewblueFX and/or this forum, the results of their finding.
4. It will have cost NewblueFX, the price of a few coffees (in real dollars).
5. You will end up with 6 advocates for your potentially stellar product.

NewblueFX have all of our email addresses on record as we have all had our machines accessed by their technical support staff over the last 2 years, so there should be no administrative issues involved here.

How about it?

Cheers,
Bernie.

[Bernie Lademann]

This issue seems to have been around for a long time. I have NBTP 4 and Vegas Pro 13 and have exactly the same issue. In October last year, technical support from NB logged into my computer and verified that there was a genuine issue and captured information for their developers to work on. It is now Feb 2018 and NB have released a new version of TP and there is still no word on whether this issue has been resolved, or can still be expected after installing the new version. Has anybody upgraded to Titler Pro 6 and can confirm that the issue no longer occurs in that version?

I’m finding it hard to run a business based on using software tools which are this flakey.

Cheers,

Bernie.

[Bernie Lademann]

Hi Denis,

In Vegas Pro 12, you have the option of “Event FX” on each event and “Media FX” on the source. In order to get Twixtor to use the source fps, you need to apply Twixtor to the “Media”. Either use the right mouse button on your event and select “Media FX”, or go into the media explorer and do it from there.

[Bernie Lademann]

Thanks John. That’s very clear now.

[Bernie Lademann]

I have a copy of twixtor and am getting my head around getting good slow motion as well.

Twixtor does a fantastic job of producing intermediate frames for slow motion, provided that the footage meets the design criteria for Twixtor. It is a pixel vector mapping application which tries to determine where the pixels are traveling from frame to frame and then positions them accordingly.

If you have footage which doesn’t meet some fairly strict guidelines, it will produce a very horrible output (lots of warping artifacts). To produce good “Twixtor” slow-motion shots, you need to lock the camera position, so that you get minimum movement of background elements, you need to ensure that most of the movement stays within the frame and a number of other strict guidelines. So I would recommend that you trial the software before trying to use it on your specific project.

As many other people have pointed out, Sony’s frame blending solution does not work for blending “double speed” frames, ie, 60fps in a 30fps project, or 50fps in a 25fps project, etc. It ghosts the frames for no apparent reason and looking back in the forums, has always had this behaviour. So it back to “No Blending” I’m afraid.

[Bernie Lademann]

I love the clarity in John’s answer. It does raise a number of other related questions, especially with the tendancy to use newer cameras running at 60fps and to include slow motion in video.

1. If all the footage was captured at 60fps, would you still set the project settings to 30fps to match the delivery media (eg. YouTube)?

2. How do you slow the footage down for emotive effect without producing ghosting when you “disable resample”? From what I understand Vegas will just repeat frames to extend the time, which doesn’t look very smooth.

Any thoughts?