Comments

Grazie wrote on 10/9/2015, 12:38 AM
Thanks Andy.

I checked for any Upgrade for Mercalli4 Plug for my PC.

"Sony Vegas Pro: In some cases Mercalli was not listed in Vegas. The cause is an outdated DirectX. By updating, Mercalli is always listed. Please Update DirectX too: "

There was one an update, BUT that was to allow the listing for Merc4 to be shown, well it is shown. So that also confirms no issue around DirectX too. In the wish to make my playability blindingly sure, I also ran a dxdiag session to establish any latent issues with those drivers. Result? Nothing there relates to this Merc<>NBTP4 conflict.

I really hope we ain't going to get into that Left-Hand<>Right-Hand blaming game.

So, back to square-1 .

Grazie

Dexcon wrote on 10/9/2015, 4:57 AM
Before installing the 151002 TP4 version, I thought that 'd uninstall the previous version. Even though TP4 was running on my W10 system, TP4 was not to be found under 'Uninstall or Change a Program'. Odd. I reinstalled the old version and found that it now appeared under 'Uninstall or Change a Program', so I went ahead and uninstalled it and then installed 151002. But on clicking on the icon to open TP4 SAL, it continually stalled on opening, there only being a white screen where the work space should be. Task Manager showed TP4 to 'not responding'. So it was back to 'Uninstall or Change a Program' and uninstall TP4 151002 and reboot the computer.

But TP4 was still on the desktop as an active icon, and it now opened properly. Even though I had uninstalled the program it now worked - weird! I suspect that the program also updated TP3 in NB Total FX which is a separate program under 'Uninstall or Change a Program'.

So the procedure is to install and then uninstall TP4 if you have Total FX installed in order to get it to work - or so it seems.

Meanwhile, Mercalli 4 Vegas plugin still works, but it results in a vertical judder again that makes the resulting image worse than the original. But I'm quite comfortable using the SAL version, so I'll probably continue to use the SAL process.

Now for some really good news with TP4 151002 - the eps problem that I experienced (see the 3rd post in this thread)and raised with NBFX support, has now been solved - an eps file with more than 1 eps element is now handled by TP4 in the way it should when you want all the elements treated globally. So a really big thank you to NBFX for fixing this.

It's obviously too early to tell if the TP4 update solves the reliability issue as I experienced crashes with TP4 in VP13 every 3 or 4 times I used TP4. Fingers crossed.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Grazie wrote on 10/9/2015, 5:14 AM
Thanks Dexcon.

As they say in Latin a real: Ganza Megillah Mishegas! ( A truly long winded crazy story!)

And when I attempt to get a MercSONY Plug update I get the WRONG one!



Grazie

andyrpsmith wrote on 10/9/2015, 4:19 PM
NewBlue have suggested the following which works for me.

Andy,

Can you please try going to C:\Program Files\NewBlueFX\Common and move or rename OFXBridgeB64.dll?

Then you should be able to run Titler with Mercalli installed.

Caleb
NewBlueFX


Hope this fixes it for you.

Andy

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

Dexcon wrote on 10/9/2015, 5:17 PM
Thanks for posting the workaround, Andy. It has worked for me as well. After reinstalling TP4 151002 and changing the name of the dll, TP4 SAL now opens straight away, as does the VP plug in.

Cheers

Conrad

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Grazie wrote on 10/9/2015, 11:29 PM
Yup, followed Caleb's instructions. Each Update I've needed to rename the next repeated Bridge thingy.

Latest NPTP4 Uli working like silk, on the slippiest slippy slope on Planet Slip!

Just to be a complete nuisance, I decided to add both Merc4 Plug AND NBTP4 Uli to the same event - working too.

Notice that NB have added multiple Framerates, which has always been a concern of mine in NBTP3.

Things are looking up.

Grazie

Dave McCallister wrote on 10/10/2015, 12:53 PM
Titler Pro 4 Ultimate user
Old version was 150529
Downloaded 151002-269
Installed 151002-269
New Blue Application Manager demands serial number
Enter my number in the box by copying and pasting to insure accuracy
Number not accepted: OK button grayed out

New Blue, at some point, REALLY needs to get its act together

Caleb: now what do I do?

R0cky wrote on 10/12/2015, 2:49 PM
Mercalli 4 plugins caused me all kinds of grief. Once installed vegas projects with mercalli V2 plugins wouldn't open. Uninstalling Mercalli 4 fixed it. I contacted Mercalli and go the same we can't repro message.

Mercalli updated the V4 plugin a few days later and now my projects with V2 will open. However, the Mercalli V4 plugin is worthless with my GTX 960 video card. It takes about 100 times longer to analyze a clip than the standalone version of V4. If it doesn't hang vegas completely. The GPU is not being used according to a GPU monitor and obviously something is hanging in Mercalli.

So all in all Mercalli V4 plugins are a waste of money right now. Maybe they'll get them fixed.

I'm unable to repro the issue with NB Titler 4 standalone. Haven't tested it as a plugin with Mercalli V4 plugin. I have found that the frame rate is fixed at 29.97 if you use it as a media generator. If you use it as an FX on an empty event the frame rate works correctly. I have a ticket in at NB on this.

rocky



Grazie wrote on 1/29/2016, 12:23 PM
Crashing again after update. Fool.....

Caleb has sent me an update to try out. S/A works fine, plug crashes. Getting a later update today. Caleb is working on this and next week if there isn't an improvement then the engineers are going to get their digital spanners and wrenches out.

G