logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

4 Pages«<234
Options
Go to last post Go to first unread
Rinsky  
#61 Posted : Thursday, November 12, 2020 7:55:38 AM(UTC)
Rinsky

Rank: Advanced Member

Groups: Registered
Joined: 8/2/2013(UTC)
Posts: 414

Thanks: 31 times
Was thanked: 30 time(s) in 29 post(s)
Sorry for double posting...but..

I think a major issue is the "automatically play events to program" function. This should be disablable.

So the main Vmix window should still be for mixing/putting things in preview and program, while doing, but the instant replay system (when another person is controlling it) should be it's own entity.

If you're a single user and do graphics, mixing and replay all alone, then it still makes sense to do things the way they were, but you'd put a glass ceiling on the new and improved instant replay system if it's can't be controlled like a standard replay system.


Edit:
I saw the "ReplayPlayEvent" and "ReplayPlayEventToOutput" shortcuts, because I thought that maybe there is a way to make this work with shortcuts. But I don't see any difference in those two shortcuts, both play the Events to the output. Is this by design or a bug?
admin  
#62 Posted : Thursday, November 12, 2020 12:37:04 PM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 4,591
Man
Location: Gold Coast, Australia

Was thanked: 2912 time(s) in 1189 post(s)
That would be a bug!
Rinsky  
#63 Posted : Sunday, November 15, 2020 3:32:39 PM(UTC)
Rinsky

Rank: Advanced Member

Groups: Registered
Joined: 8/2/2013(UTC)
Posts: 414

Thanks: 31 times
Was thanked: 30 time(s) in 29 post(s)
We've testet it yesterday on a production and we came up with more input:


1. Audio meters take up too much space, especially if there are more than 4 inputs:

UserPostedImage

It takes so much space, because it shows all recorded audio channels on all 8 inputs and the A and B channels,.

This combined leads to tiny windows and really, really makes it hard to work with.

An option to hide them (just like in the normal Vmix window), would be great, but this and having them as an overlay on the right hand side, on top of those videos would be even greater and would safe a lot of space!



2. The other thing is that it automaticall jumps to 4 colums of monitors, even if you just use 5 inputs.

It would be great to have 1 row for up to 2 inputs, 2 rows for up to 4, 3 for up to 6 and 4 for up to 8 replay inputs.



3. Regarding the bug I previously found:

It would also be great to have a visible button for "Play Event" that actually just plays the event and another one that says "Play Event to Output"
Dist  
#64 Posted : Tuesday, November 17, 2020 10:53:04 PM(UTC)
Dist

Rank: Newbie

Groups: Registered
Joined: 12/19/2019(UTC)
Posts: 3
United Kingdom

Was thanked: 5 time(s) in 2 post(s)
While the list of activators show support for cameras 5 to 8, `ReplayCamera`, `ReplayACamera`, and `ReplayBCamera` don't send activator messages for cameras 5 to 8. When switching between cameras in that range it still sends a 0 value for cameras 1 to 4 to indicate they are not selected, but there's no way to tell (using activators) the status of cameras 5 to 8.

Also, I'm just checking the `ReplayChangeDirection` and can't figure out what the correct name is for the param when calling the function programmatically. The shortcuts window shows a `Replay Channel` option, with `Current`, `A`, or `B`, values, but I can't seem to find the querystring param so my requests just default to `current`.
admin  
#65 Posted : Wednesday, November 18, 2020 12:33:26 AM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 4,591
Man
Location: Gold Coast, Australia

Was thanked: 2912 time(s) in 1189 post(s)
Originally Posted by: Rinsky Go to Quoted Post


It takes so much space, because it shows all recorded audio channels on all 8 inputs and the A and B channels,.

This combined leads to tiny windows and really, really makes it hard to work with.


This is not related to audio channels at all. If you look closely the space is limited by aspect ratio, that space is effectively unusable
because to do otherwise would stretch the video outside of 16:9.
RichDanby  
#66 Posted : Wednesday, November 18, 2020 1:22:40 AM(UTC)
RichDanby

Rank: Advanced Member

Groups: Registered
Joined: 2/23/2019(UTC)
Posts: 36
United Kingdom

Thanks: 4 times
Was thanked: 5 time(s) in 4 post(s)
Originally Posted by: admin Go to Quoted Post

This is not related to audio channels at all. If you look closely the space is limited by aspect ratio, that space is effectively unusable
because to do otherwise would stretch the video outside of 16:9.

Do the preview and label have to be locked into a 16:9 box? There are layouts of the instant replay window where previews could be larger if the labels could move down. For example: -
UserPostedImage
I feel the audio meters the same width as in the main window would be sufficient.
pm  
#67 Posted : Wednesday, November 18, 2020 4:43:02 AM(UTC)
pm

Rank: Advanced Member

Groups: Registered
Joined: 11/28/2015(UTC)
Posts: 133

Thanks: 4 times
Was thanked: 26 time(s) in 21 post(s)
There is no use of audio level meters in replay interface for me. There are level meters on the input itself and in the audio mixer.

Better would be using the emtpy space for larger preview pictures.
ask  
#68 Posted : Wednesday, November 18, 2020 7:40:10 AM(UTC)
ask

Rank: Advanced Member

Groups: Registered
Joined: 10/13/2012(UTC)
Posts: 1,075
Australia
Location: Melbourne

Thanks: 173 times
Was thanked: 184 time(s) in 169 post(s)
Maybe just an issue on my system, but on a .24 test build vmix.avi files cannot be converted by Media Convertor. It reports "Video format not Supported"

admin  
#69 Posted : Wednesday, November 18, 2020 12:25:46 PM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 4,591
Man
Location: Gold Coast, Australia

Was thanked: 2912 time(s) in 1189 post(s)
Originally Posted by: pm Go to Quoted Post
There is no use of audio level meters in replay interface for me. There are level meters on the input itself and in the audio mixer.

Better would be using the emtpy space for larger preview pictures.


As noted, the space there is free anyway due to aspect ratios, so the audio meters are not taking up space that could be used for bigger previews.
If you look carefully the preview is actually the Replay MultiView cut in two and displays side by side.
So there isn't any way to improve the preview sizes without either distorting them or completely removing the labels.
ruudboon  
#70 Posted : Friday, November 20, 2020 4:19:08 AM(UTC)
ruudboon

Rank: Member

Groups: Registered
Joined: 7/3/2020(UTC)
Posts: 14
Netherlands
Location: Amsterdam

Looking forward to the update!
Noticed I Can't enter numbers in Color Adjust input fields. Only the scroller works.
Besides that it would be great if you can use arrow up and down when having focus in a numeric input field.
kross  
#71 Posted : Saturday, November 21, 2020 6:47:54 PM(UTC)
kross

Rank: Newbie

Groups: Registered
Joined: 10/31/2020(UTC)
Posts: 8
United States

v24 is a nice upgrade to 23, thank you very much!

However, I am unable to get my ShuttlePro v2 to work with v24. The existing shortcuts don't work. The jog and shuttle wheels do nothing.

When I try to add a new shortcut, when I hit the Find button, button presses on the Shuttle show as MIDI presses, and not the usual ReplayA-ReplayO.

Reinstalling v23 restores functionality.

Is this expected? Do I need to re-do the shortcuts with the MIDI values now instead? That's easy enough. What about the jog and shuttle wheels? Any tips on how to set those up?
kross  
#72 Posted : Saturday, November 21, 2020 7:50:44 PM(UTC)
kross

Rank: Newbie

Groups: Registered
Joined: 10/31/2020(UTC)
Posts: 8
United States

I think I got the jog/shuttle wheels working, setting them to JogWheel mode, and using the ReplayChangeSpeed and ReplayJumpFrames shortcuts. Hopefully when v24 is released, it will have updated templates included, to save people having to go through this extra setup.
Rinsky  
#73 Posted : Saturday, November 21, 2020 11:08:47 PM(UTC)
Rinsky

Rank: Advanced Member

Groups: Registered
Joined: 8/2/2013(UTC)
Posts: 414

Thanks: 31 times
Was thanked: 30 time(s) in 29 post(s)
Originally Posted by: admin Go to Quoted Post
Originally Posted by: pm Go to Quoted Post
There is no use of audio level meters in replay interface for me. There are level meters on the input itself and in the audio mixer.

Better would be using the emtpy space for larger preview pictures.


As noted, the space there is free anyway due to aspect ratios, so the audio meters are not taking up space that could be used for bigger previews.
If you look carefully the preview is actually the Replay MultiView cut in two and displays side by side.
So there isn't any way to improve the preview sizes without either distorting them or completely removing the labels.


So for performance reason it has to be the same as the replay multiview output or is there a chance to make it different?
ask  
#74 Posted : Sunday, November 22, 2020 10:22:15 AM(UTC)
ask

Rank: Advanced Member

Groups: Registered
Joined: 10/13/2012(UTC)
Posts: 1,075
Australia
Location: Melbourne

Thanks: 173 times
Was thanked: 184 time(s) in 169 post(s)
Originally Posted by: ask Go to Quoted Post
Maybe just an issue on my system, but on a .24 test build vmix.avi files cannot be converted by Media Convertor. It reports "Video format not Supported"



Sorted. Can confirm all Ok. Tested on multiple systems. Must have been a rogue recording. :-)


nomski  
#75 Posted : Monday, November 23, 2020 8:42:57 PM(UTC)
nomski

Rank: Advanced Member

Groups: Registered
Joined: 10/14/2016(UTC)
Posts: 43
Location: Sheffield

Just been using 24 for some internal stuff to help test. Not a major one but the "Auto gain" tick box and any VST's in the list are lost whenever the VT list is emptied. The way we use the list is to add VT's as and when we need them, and the list is emptied every time the VT transitions out. It would be great if it retained the audio settings.
doggy  
#76 Posted : Saturday, November 28, 2020 9:32:05 PM(UTC)
doggy

Rank: Advanced Member

Groups: Registered
Joined: 12/27/2012(UTC)
Posts: 2,525
Belgium
Location: Belgium

Thanks: 141 times
Was thanked: 454 time(s) in 373 post(s)
SetDynamicValue and SetDynamicInput work with shortcuts
Say SetDynamicValue1 as ANAME & SetDynamicInput1 as 2

If there is a title as input 2 and the shortcut SetText is used with Input = Dynamic1 and Value = Dynamic1 all works well

First question would be why they are both recalled with the same name Dynamic1 ?

Next step trying it within a script (same scenario)
While one can Set the DynamicValues and DynamicInputs and use a shortcut as before (SetText) will respond to both dynamic variables
BUT he SetText function (as example) will work with recalling the Value with Dynamic1 , The Input is NOT respomding at all with a Dynamic1 specified

Why is there no way to retrieve either Dynamic Values or Input say to a local variable to test with within a script or retrieve it from th API XML?

Thanks

Code:
API.Function("SetDynamicValue1",Value:="ANAME")
API.Function("SetDynamicInput1",Value:="2")
API.Function("SetText",Input:="Dynamic1",Value:="Dynamic1")  'does not work
API.Function("SetText",Input:="2",Value:="Dynamic1")         'does work


'Or

Function=SetDynamicValue1&Value=ANAME
Function=SetDynamicInput1&Value=2
Function=SetText&Input=Dynamic1&SelectedName:="Headline.Text"&Value=Dynamic1  'does not work
Function=SetText&Input=2&SelectedName:="Headline.Text"&Value=Dynamic1         'does work

thanks 2 users thanked doggy for this useful post.
DWAM on 11/29/2020(UTC), clafarge on 11/30/2020(UTC)
Users browsing this topic
4 Pages«<234
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.