A/V Config error "Object reference not set to an instance."

Please report bugs in this group. We will maybe populate a list of known bugs with a possibly modified description at a later time.

Moderator: Support

Post Reply
User avatar
shermanpat
Posts: 122
Joined: 21 Feb 2012, 22:03
Location: SLC Ut USA

A/V Config error "Object reference not set to an instance."

Post by shermanpat » 10 Feb 2016, 04:44

We have been running in to this issue for a while now one of our guys posted the error in the director forum a while back http://forum.ventuz.com/viewtopic.php?f=26&t=3847

We are unable to create and or edit A/V configs when we have the our BMD Decklink quad using BMD version 10.5.4 with Ventuz 4.070.01.280.

Our fix is still to downgrade Ventuz to 4.06.1.

Or we can disable the Drivers for the inputs in Device manager. Which doesn't really help as we need the inputs.
One of our other techs tried to test other version of the BMD drivers and went pretty far back with no luck.

Log message when trying to create new A/V Config:
2016-02-09 20:10:05.2 [Info ]: (MainWindow|) Begin editing A/V configuration test 3
2016-02-09 20:10:10.0 [Error ]: (MainWindow|) Unexpected error during menu navigation: Object reference not set to an instance of an object.
<Exception Type="System.NullReferenceException">
<StackTrace> at Ventuz.Video.VideoPipe..ctor(MachineHardware machineHardware)
at EditConfig.App.ConfigEnvironment.AVConfigEnvironment.BeginEdit()
at EditConfig.MainWindow.OnNavigateTo(Object sender, NavigateToEventArgs e)</StackTrace>
<ToString>System.NullReferenceException: Object reference not set to an instance of an object.
at Ventuz.Video.VideoPipe..ctor(MachineHardware machineHardware)
at EditConfig.App.ConfigEnvironment.AVConfigEnvironment.BeginEdit()
at EditConfig.MainWindow.OnNavigateTo(Object sender, NavigateToEventArgs e)</ToString>
</Exception>

I am running:
Win 8.1 64bit
AMD W8000
2x BMD Decklink Quad with driver version 10.5.4
Ventuz 4.07.1.280
-Sherman
Meru Interactive

User avatar
Karol
Posts: 530
Joined: 10 Jan 2012, 12:07

Re: A/V Config error "Object reference not set to an instanc

Post by Karol » 10 Feb 2016, 10:21

Hi Sherman!

I issued a bug ticket for that.
Probably we will be able to fix that for 4.8.0.
But we are pretty much focused on Ventuz 5 release right now...

Best Regards
Karol

User avatar
shermanpat
Posts: 122
Joined: 21 Feb 2012, 22:03
Location: SLC Ut USA

Re: A/V Config error "Object reference not set to an instanc

Post by shermanpat » 10 Feb 2016, 17:29

Thanks for the response.

Very excited about V5 myself loving the new updates. Can't wait to see some demo scenes and a manual.
-Sherman
Meru Interactive

DominicBout
Posts: 1
Joined: 27 May 2016, 08:26

Re: A/V Config error "Object reference not set to an instanc

Post by DominicBout » 27 May 2016, 08:30

I've managed to work around the problem bij disabling a 'Generic Bluetooth Radio'-device in the Windows Device Manager. This device was causing the hardware configuration screen to crash during instanciation. Why? No idea, but maybe Ventuz sees it as a candidate media device.

User avatar
shermanpat
Posts: 122
Joined: 21 Feb 2012, 22:03
Location: SLC Ut USA

Re: A/V Config error "Object reference not set to an instanc

Post by shermanpat » 28 May 2016, 16:40

ate response, but yes bug is fixed in 4.8.0
-Sherman
Meru Interactive

Post Reply