Are you using BORIS MOCHA Pro 19?

Grazie wrote on 9/19/2019, 4:54 AM

More to the point, are you using BORIS MOCHA Pro 19 as an OFX plugin in MAGIX Vegas Pro17? How has your experiences been with regard to getting any whiteouts/crashes and then Previewing Speed back in VP17?

Oh yeah, I met up with the BORIS Crew at IBC19 in Amsterdam.

 

TIA - G

Comments

Martin L wrote on 9/19/2019, 6:30 AM

Yes sir, I have Mocha Pro 19 and Continuum 19 installed on my new machine with Vegas 17. But I haven't had time to open it yet.

How about you?

Dexcon wrote on 9/19/2019, 6:42 AM

Same as Martin L … additionally, I'm not really touching VP17 at this time, not until the 1st update comes out. I'm still working in VP16 but mainly in the scripting/audio recording and mixing stage. Mocha Pro usage was done some time ago so I haven't had the need, as yet, to use the latest Mocha Pro update in either VP16 or 17.

Dell Alienware Aurora 11

Windows 10 Home

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: 1TB M.2 PCIe NVMe SSD

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

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

Grazie wrote on 9/19/2019, 7:09 AM

I have Mocha Pro 19 and Continuum 19 installed on my new machine with Vegas 17. But I haven't had time to open it yet.

How about you?

@Martin L - Yes, been bashing MP19 since I purchased it. Please get around to driving it off of the Lot I want to get a set of data I can relate to.

Mocha Pro usage was done some time ago so I haven't had the need, as yet, to use the latest Mocha Pro update in either VP16 or 17.

@Dexcon - Thanks. Now, if you have the time to kick the tyres, I’d reeeealy appreciate your input. You do tell it as it is 🤔.

TIA - G

Dexcon wrote on 9/19/2019, 7:33 AM

@Grazie ... No probs. I'll do some testing over the weekend. Cheers. Conrad.

Dell Alienware Aurora 11

Windows 10 Home

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: 1TB M.2 PCIe NVMe SSD

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

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

Dexcon wrote on 9/22/2019, 4:19 AM

@Grazie

I've given Mocha Pro OFX (19.5 build 6.1.2-41 - the latest build) in VP17 and, at first, I experienced no problems.

On an already stabilised (in Merc4SAL) of a street scene (looking down Rue de Rivoli - camera on the pavement so it was a 'tapered' view of about 1 km down the Rue), a passing motorcyclist was successfully removed in Mocha Pro using the Remove tool without any drama.  The video event was 4K with the original footage from an AX100 at 3840x2150 25 fps 100 Mbps.

On another shot using the original camera footage (handheld camera), I tried stabilising in Mocha Pro using the Stabilise tool. Not getting the spline node points in the best positions, as well as trying various Track and Stabilise settings, I made many attempts to stabilise the shot. Each attempt involved saving and closing MP and then waiting for the MP Render settings to take effect. After about 4 or 5 attempts at stabilising, I found that VP17 would lockup when I tried to play the event, and the little blue wheel would just spin and spin and spin. Any mouse click or ALT-TABing away from VP17 and then ALT-TABing back to VP17 resulted in the whole VP17 window going opaque white - and the little blue wheel just kept on spinning.

Rebooting the computer and then trying stabilising another video event proved successful without any further render problems or white-screening from VP17. I'm getting the feeling that Mocha Pro might be taking up resources somehow after an indeterminate amount of use which then compromises VP17.

Timeline performance on the MP FX'd events is slow and staggery in VP17, but then it also was in VP16 with previous MP versions. I often create a new veg project just for dealing with systems intensive FX like Mocha Pro, and then render them out to an intermediate which can then go on to the main project's TL

During the tests today, I didn't get any black frames in Mocha Pro, though I have many months ago in VP16 with Mocha Pro, but then that was only on one occasion tot he best of my memory.

I hope that this helps in some way.

Dell Alienware Aurora 11

Windows 10 Home

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: 1TB M.2 PCIe NVMe SSD

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

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

Grazie wrote on 9/22/2019, 6:04 AM

@Dexcon - Yes, this helps tremendously. You’ve set me a successful DATUM. I’m using the exact same MP19 Build as you.

ISSUE: Post MP “Remove” Staggering FrameRate: I’ve prepared a 1080p 30 Remove Project in MP19. Back in VP I am NOT getting full FPS. Preview is staggering, waiting for the Frame Rate Build. I’m using the MP Render of the Remove. Your comments concerning MPs usage of memory, is adding to my concerns too. Needing to create separate Veggies JUST to accommodate for MPs OFX lack of ability to “get with the program” indicates to me a real need in my opinion for further BORIS QA improvement.

Something to consider, MP19 and VP17 had “similar” release timings. If this is the case, then there’s that possibility that nobody was at home in both the BORIS and MAGIX BETA Teams to challenge this. I know I wasn’t. However, @Dexcon, I was at the BORIS Booth at IBC19 where I discussed these matters with the Team. They all agreed that my MONSTA! is up to muster.

Apart from your Exo-Project suggestion, can you think of what I can do to improve? I’m assuming my MONSTA! is up to muster. 😎

And again, @Dexcon, you’ve been very helpful with the Black Frame issue appears to have been resolved too.

Dexcon wrote on 9/23/2019, 5:33 AM

@Grazie

I did another Mocha Pro test, but this time in HitFilm Pro 13 (latest build). Using exactly the same video event as yesterday, I removed the travelling motorcyclist from the street scene. In Mocha Pro, it worked exactly as it did within VP17. After saving, closing and rendering (the MP render that is), the timeline playback rate in HF was, very surprisingly … zero fps. If I moved the cursor to another point within the event, HF would do the scrolling blue line (working on it) thing under the preview window for about 20 seconds, but still 0 fps.

In comparison, the staggering playback in VP17 is much better than the 0 fps in HF, but obviously not ideal to say the least.

I went to try the same test in daVinci Resolve but, for me, AVCHD TL playback is dreadful even without any FX added, so there didn't seem much point in proceeding.

Apart from your Exo-Project suggestion, can you think of what I can do to improve?

Given that your MONSTA is a 'Ferrari' compared to my 5 years old 'Ford Mondeo' computer, the similar TL performance experiences with Mocha Pro suggest that the difficulties lie with the interaction with the NLE osts rather than with the computers.

Last changed by Dexcon on 9/23/2019, 5:42 AM, changed a total of 1 times.

Dell Alienware Aurora 11

Windows 10 Home

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: 1TB M.2 PCIe NVMe SSD

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

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

Grazie wrote on 9/23/2019, 5:40 AM

@Dexcon - Nasty. OK, I've got a MOCHAPRO19 Forum request to get this remedied or at the very least and update on where MAGIX<>Imagineer stand on getting this resolved. In the meantime we're stuck on the LEFt><Righthand cludge of the respective company engineers.

@Dexcon Do add your voice to the Forum.

Dock wrote on 12/9/2019, 12:02 AM
I often create a new veg project just for dealing with systems intensive FX like Mocha Pro, and then render them out to an intermediate which can then go on to the main project's TL

The issue I face with this work around is that the colors of the rendered Mocha project are now different from the colors of the other similar clips on the timeline that have not been rendered yet. I tried the color match FX (VP14), it is useless.