• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

Bug when using Nobe Omniscope software

Explorer ,
Oct 21, 2023 Oct 21, 2023

Copy link to clipboard

Copied

Problem in the beta version of Premiere Pro 24.1.0 (build 64)

When using Nobe Omniscope software from Timeinpixels.

 

If Mercury Transmit is enabled and Nobe Omniscope Transmitter is checked, the Premiere Pro application closes when the Project Timeline is displayed. 

Simply deactivate Mercury Transmit in production before launching the project, and all is well. You can then activate Mercury Transmit and launch the Nobe Omniscope application.

This problem does not exist in the official PP Version 2024.0.0 (build 58).

There is simply an error message that does not close the application: "21/10/2023 low-level exception occurred in: Nobe OmniScope Transmitter (Transmit::QueryVideoMode)".

 

Another problem with the beta version is that the Mercury Transmit function is no longer visible in Lumetri/Settings. There are only checkboxes for the various links, whereas this line is visible in the official version!

 

Best regards

Christian Goubier

Bug Unresolved
TOPICS
Bug , Error

Views

506

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
10 Comments
Adobe Employee ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard

Copied

I'm running PPro 24.1 beta with a BMD Ultrastudio 4k Mini, without issue.

I also don't see Omniscope actually doing anything; it just says 'connecting', forever. 

Screenshot 2023-10-24 at 6.34.07 AM.png
The Omniscope installer also does not install any Transmit plugins, so I'm confused as to where/how they think they're going to get video or audio, from PPro...?

Votes

Translate

Translate

Report

Report
Explorer ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard

Copied

Nobe Omniscope works very well with the official version. It also works with the Beta version, but you need to activate mercury Transmit only after Nobe Omniscope has been launched (which is not the case with the official version).
The transmission plugin is installed in the plugin directory "..\commun\Plug-ins\7.0\MediaCore\NobeOmniScopeTransmitter.prm".

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard

Copied

Both PPro and PPro beta use the same /plugins directory, and the Nobe installer didn't put any plugins there. Perhaps it's because I'm running a trial, and didn't purchase...?

Votes

Translate

Translate

Report

Report
Explorer ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard

Copied

I've updated the Nobe Omniscope application and it doesn't change anything.
See the error message that appears on version 20.0 when mercury transmit is activated but without crashing the application.Error msg on PP 24.0.png

On PP 24.1 (beta) under the same conditions, the application crashes.

MercuryTransmit.png

Further information: the problem occurs on differents projects when I launch them directly. If I open production first and then one of the projects, there's no crash!

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard

Copied

That low-level exception is happening in the Omniscope transmitter plugin, which the nice folks at Nobe are helping me find/install...

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard

Copied

Figured out how to install the plugin. 
did see a crash on startup, but the next time I launched PPro, the Nobe transmit plugin seemed to function correctly; I could see PPro's program monitor contents in the "input strip", within Omniscope.

 

Tom @ TimeInPixels will investigate further. 

Votes

Translate

Translate

Report

Report
Explorer ,
Oct 24, 2023 Oct 24, 2023

Copy link to clipboard

Copied

It's just a problem at launch. If you proceed in the order PP project startup, Mercury Transmit activation and then Nobe Omniscope launch, everything works fine.
This Nobe tool is a real plus for doing colo with PP and I couldn't do without it 😉

Votes

Translate

Translate

Report

Report
Engaged ,
Feb 04, 2024 Feb 04, 2024

Copy link to clipboard

Copied

Did you find any solution?

I have the exact same issue here. 

I am running Verion 24.1.0 (Build 85) on a Macbook Pro Max M2 32GB Ram.

I am using a "normal" premiere project with a Blackmagic Ultrastudio 3g Plus the Omniscope transmit activated.

It works fine sometime but then I get random crashes and the Omniscope video freezes, the Blackmagic output still works.

I can only restart premiere to make it work again then.

Votes

Translate

Translate

Report

Report
Engaged ,
Feb 08, 2024 Feb 08, 2024

Copy link to clipboard

Copied

The recommendation from Omniscope was to use NDI to transmit from Premiere. But unfortunately NDI does not support interlaced (which is broadcast standard). Its detected as 1920x540p and thus stretched to an aspect ratio of16x4,5. I am afraid I cannot use it at all. Maybe I will try Hedge Scopebox and see if that works better.

Votes

Translate

Translate

Report

Report
New Here ,
Feb 11, 2024 Feb 11, 2024

Copy link to clipboard

Copied

LATEST

any one know how to fix source signal when video vertical size 

Votes

Translate

Translate

Report

Report
Resources