Rank: Advanced Member
Groups: Registered
Joined: 6/4/2013(UTC) Posts: 308  Location: Germany Thanks: 1 times
Was thanked: 57 time(s) in 49 post(s)
|
I had the controller in use with Studio One and Reaper. In both programs I never had any problems like this. But that was on Windows 8.1 and I don't have them installed after the update to Windows 10. I will do some checks, stay tuned.....
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 6/4/2013(UTC) Posts: 308 Location: Germany Thanks: 1 times
Was thanked: 57 time(s) in 49 post(s)
|
When there is no template you can't use a template ;-)
Just use "Current" instead and set-up your own custom shortcuts for MIDI.
Go to "MIDI Settings" and activate your controller. Then set-up the first shortcut by clicking "Add", click "Find", press the button or move the fader/knob on your controller and select the function it should operate in vMix.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 6/4/2013(UTC) Posts: 308 Location: Germany Thanks: 1 times
Was thanked: 57 time(s) in 49 post(s)
|
Please check that it's in MIDI mode. From the manual: Quote:2.3.1 Native NHL Mode
In Native NHL mode TRAKTOR KONTROL X1 will communicate directly with TRAKTOR over
USB using the Native Instruments proprietary NHL protocol, which features high resolution
translation of the TRAKTOR KONTROL X1 knobs superior to MIDI.
For normal TRAKTOR control, you will use this mode.
2.3.2 MIDI Mode
The TRAKTOR KONTROL X1 is preconfigured to also be used as a standard MIDI controller
and can control any hardware or software that supports the MIDI standard.
► To access MIDI mode, hold SHIFT and press both Load Left and Load Right buttons. The
TRAKTOR KONTROL X1 will then transmit MIDI data like a normal MIDI controller.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 6/4/2013(UTC) Posts: 308 Location: Germany Thanks: 1 times
Was thanked: 57 time(s) in 49 post(s)
|
ovinas wrote:I had the controller in use with Studio One and Reaper. In both programs I never had any problems like this. But that was on Windows 8.1 and I don't have them installed after the update to Windows 10. I will do some checks, stay tuned..... Seems to be a driver and/or Windows 10 issue. I deinstalled the Korg MIDI driver to run the nanoKONTROL2 with the standard Windows MIDI driver. That's doing the trick for now...
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/12/2015(UTC) Posts: 482 Location: Kansas City, MO USA Thanks: 151 times
Was thanked: 75 time(s) in 57 post(s)
|
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,215 Location: Gold Coast, Australia Was thanked: 4304 time(s) in 1524 post(s)
|
Hi Steve,
Do you have any other ASIO apps known to work with the virtual sound card on that computer?
The error would indicate that Dante is not connected yet or configured as the error is coming from the driver itself.
Regards,
Martin
vMix
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,215 Location: Gold Coast, Australia Was thanked: 4304 time(s) in 1524 post(s)
|
New update (16.0.0.55) has been uploaded to the same download link
* New MultiView layouts
* Added dropdown menu next to Add Input for easy access to recent files
* Added support for IP Streams to Instant Replay
* Added new right click "Create Virtual Input" menu option
* Added "Always Play First Item with Transition" List Input option
* Added support for new YUAN High Tech cards
* Virtual Inputs now default to copying the settings from the source Input
* SetImage API can now be used via shortcuts, also excepts blank filenames
* Fixed Replay loop button error
* H264 Low Latency format option when adding cameras that use hardware encoding (such as from YUAN High Tech)
I've now moved to feature complete, bug fix mode for this release. Please continue to report
any bug fixes. Documentation is now being worked on for a final vMix 16 release at the end of August!
|
 3 users thanked admin for this useful post.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 10/13/2012(UTC) Posts: 1,162  Location: Melbourne Thanks: 220 times
Was thanked: 199 time(s) in 181 post(s)
|
I like the Recent list! :-)
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 10/13/2012(UTC) Posts: 1,162 Location: Melbourne Thanks: 220 times
Was thanked: 199 time(s) in 181 post(s)
|
Error generated when trying to use the new features to connect to daCast. When you enter the username and password the attatched message is displayed. Error report sent. Manual login to a channel works without issue. ask attached the following image(s):  vMixDaCastError.png (28kb) downloaded 2 time(s).You cannot view/download attachments. Try to login or register.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/7/2012(UTC) Posts: 2,637 Location: Canada Thanks: 33 times
Was thanked: 506 time(s) in 475 post(s)
|
Quote:To answer Madness, how I did it the way we want it. I created two identical Multiviews, and then modified one of them to full frame zoom of the layer I wanted to be full frame. Then Merged from one of the Multview to the other Multiview. Actually, for a double box (two videos side by side on a common background, you need three Multivew inputs. One for both, one for left box full frame, and one for right box full frame. Furthermore, for one of the latter you need to flip the layers so that the one going into full frame is at the top layer. Otherwise it will be obscured during the zoom (sorry, the dissolve as a fix just looks bad). One issue here is that it is challenging for the operator to quickly distinguish between the "single source" input, and the Multiview with that input full frame on top. Both inputs look the same...
It would be much easier if it was possible to MultiZoom in/out between a single source Input (eg a camera) and a Multiview, using only one Multiview (instead of three). Pondering about this for a couple of days, I summarize how I think this could be done.
If going from/to a single source to/from a multiview, temporarily make that single source the top layer (make sure it is not obscured by other layers during the transition). On completition, assign it's layer as defined in the Multiview.
Leave Inputs in Output that does not exist in Preview as they are, until the transition is complete, then remove non matching Inputs. And for Inputs in Preview that does not exist in Output, these would be cut in, at the very start of the Merge. It is up to the user to make sure that non-matching inputs are layered correctly, eg under merging layers. (And as aboe, for single sources its layer is put on top automatically).
Thanks Richard for the description, and I agree with 'possible' solutions although it doesn't solve every situation. I have played around with it a bit and it is indeed the upper most layer that maintains full opacity during the 'Merge' transition, but a potential issue would be if the merging input is cropped or partially hidden behind another input in the 'MultiView' input (e.g. I typically put inputs behind the "MultiViewHD" template with a slightly larger image than the opening, in which case, the image needs to be cropped when placed on top and thus an extra time consumming step)  Input behind Template  Input On top of Template (un-cropped) Ice
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 2/18/2014(UTC)
Posts: 1,837
Location: Stockholm
Thanks: 144 times
Was thanked: 297 time(s) in 250 post(s)
|
Love all the additions in 16.0.0.55!
It is not possible to right-click Create a Virtual input, if it's done in a Virtual input. But it is possible to create one via the Coq wheel.
Creating a Virtual input from an Input with name set by vMix (eg "image.jpg" is named "Virtual - image.jpg".
If created from an Input which name is changed by user (eg to "MyImage") is named "MyImage - MyImage".
Suggestion: have vMix set the name "VirtualNN - original", where NN is sequence 01 and so fort, and "original" is the name of the Input from which the virtual one is created. Unique names are important as they now can be used for shortcuts.
I think a warning "Preset has been changed, save first?" is needed for New, Open and Last.
An old thing: In Settings/Output it is possible to specify an Input that does not exist. I am not sure why, would prefer that it was not. And that the user gets a warning if an Input that is used for an Output is removed.
(Even older thing/request: that the names should be included in the drop-down selection of Inputs for Outputs).
I thing an indication of dB/liniar setting would be useful on the Main meter. (Right-click on meter to change?)
Just noting that among all the new Audio processing features, we still don't have an indication of how much the compressor kicks in (an old feature request).
Will dig into the ASIO, Midi and ShuttleProV2 features next week. Scripting and other features later on...
Thanks.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 2/18/2014(UTC)
Posts: 1,837
Location: Stockholm
Thanks: 144 times
Was thanked: 297 time(s) in 250 post(s)
|
IceStream wrote:Thanks Richard for the description, and I agree with 'possible' solutions although it doesn't solve every situation.
I have played around with it a bit and it is indeed the upper most layer that maintains full opacity during the 'Merge' transition, but a potential issue would be if the merging input is cropped or partially hidden behind another input in the 'MultiView' input (e.g. I typically put inputs behind the "MultiViewHD" template with a slightly larger image than the opening, in which case, the image needs to be cropped when placed on top and thus an extra time consumming step) Ice, Not really understanding why you crop and why you put the PiPs behind (and not over) the MultiHD template. As an experiment I did a new recording with 16.0.0.55 and uploded it to YouTube. I started out with two Inputs, each with a video animation. Then I Added a Title Input using MultiViewHD. Next I made it a MultiView with the first input to the left on Layer1 (slightly cropped on all sides and zoomed to fit), and my second to the right (uncropped zoomed to fit). Now, in the video I start by Merging from the Multiview (Input3) to the right video (Input 2, which is on top in the Multiview). It seems to me that during the Merge the other layers are dissolved (this is where I want no dissolve). Then when Merging back two things strikes me. First that the other layers seems not to dissolve. Second, that the cropping of the second layer is ignored until the Merge is complete (bug?). Continuing in the video I then Merged from the MultiView to the left video (Input 1, whis is layered under Input 2). It is clearly visible how the right video is slightly obscuring the left one, this is why I would like the Merge to temporarily move the corresponding one to the top. Same thing when I Merge back. Again, the right video is visible (dissolving in) before I want it. Actually, I am kind of confused which layers are dissolving when - it is hard to see. Then I started to build my workaround by creating two new Virtual Inputs from my MultiView - easy fix nowadays :). But, I gave up when I had to swap the two layers in one of them before making a full zoom. Too complicated to move layers. Instead I filed a feature request for moving layers in a MultiView.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/7/2012(UTC) Posts: 2,637 Location: Canada Thanks: 33 times
Was thanked: 506 time(s) in 475 post(s)
|
richardgatarski wrote:
Ice,
Not really understanding why you crop and why you put the PiPs behind (and not over) the MultiHD template.
Essentially, better framing within the template borders (as per image above, especially convenient when using and setting up different sized inputs quickly). With the new "Create Virtual Input" option on right click, it's a lot easier to set up two additional 'MultiView' Inputs for each 'Merge' option, but that is back to the same scenario of requiring multiple "copies" of the same input to perform the transition as desired. I hope your request gets some traction. Ice
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guests
Joined: 9/15/2013(UTC) Posts: 168 Location: Barbados Thanks: 14 times
Was thanked: 14 time(s) in 13 post(s)
|
richardgatarski wrote:IceStream wrote:Thanks Richard for the description, and I agree with 'possible' solutions although it doesn't solve every situation.
I have played around with it a bit and it is indeed the upper most layer that maintains full opacity during the 'Merge' transition, but a potential issue would be if the merging input is cropped or partially hidden behind another input in the 'MultiView' input (e.g. I typically put inputs behind the "MultiViewHD" template with a slightly larger image than the opening, in which case, the image needs to be cropped when placed on top and thus an extra time consumming step) Ice, Not really understanding why you crop and why you put the PiPs behind (and not over) the MultiHD template. As an experiment I did a new recording with 16.0.0.55 and uploded it to YouTube. I started out with two Inputs, each with a video animation. Then I Added a Title Input using MultiViewHD. Next I made it a MultiView with the first input to the left on Layer1 (slightly cropped on all sides and zoomed to fit), and my second to the right (uncropped zoomed to fit). Now, in the video I start by Merging from the Multiview (Input3) to the right video (Input 2, which is on top in the Multiview). It seems to me that during the Merge the other layers are dissolved (this is where I want no dissolve). Then when Merging back two things strikes me. First that the other layers seems not to dissolve. Second, that the cropping of the second layer is ignored until the Merge is complete (bug?). Continuing in the video I then Merged from the MultiView to the left video (Input 1, whis is layered under Input 2). It is clearly visible how the right video is slightly obscuring the left one, this is why I would like the Merge to temporarily move the corresponding one to the top. Same thing when I Merge back. Again, the right video is visible (dissolving in) before I want it. Actually, I am kind of confused which layers are dissolving when - it is hard to see. Then I started to build my workaround by creating two new Virtual Inputs from my MultiView - easy fix nowadays :). But, I gave up when I had to swap the two layers in one of them before making a full zoom. Too complicated to move layers. Instead I filed a feature request for moving layers in a MultiView. Is the dissolve is really needed...if there is a way to turn that off, it would be great.....I would have to do that effect at a rate of about 250 or 300.....to avoid that being so noticeable.....but other than that, it is a feature we requested long time ago.... I am still wishing for the ability to turn off the 'Preview' window when it is not needed and becomes a distraction......or have it used for titling of some other function so as to keep the GUI layout.....It is really distracting when using a very large monitor.....as sometimes I have to do, and in the video, it really is distracting..... I also noticed that your CPU usage was over 55 %...like I said in another post, vMix is now becoming CPU hungry......
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 2/27/2013(UTC) Posts: 312  Thanks: 8 times
Was thanked: 78 time(s) in 43 post(s)
|
Are you only using the Dante Virtual Sound Card? Dante can be a bit of a beast to get configured correctly. What is the sample rate of your Dante input? I'm not sure if it may not work if its higher than 48,000khz.
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,215 Location: Gold Coast, Australia Was thanked: 4304 time(s) in 1524 post(s)
|
Bardos wrote:
I also noticed that your CPU usage was over 55 %...like I said in another post, vMix is now becoming CPU hungry......
Hi Bardos, This is not the place for feature suggestions, and there have not been any reported issues with CPU usage besides one caused by a faulty webcam driver. A while back you started a discussion on the CPU usage and it was determined that it was a combination of an underpowered PC and you using higher quality settings than in the past. If you would like to continue that discussion please start a new thread. Regards, Martin vMix
|
1 user thanked admin for this useful post.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 261 Location: Finland Thanks: 120 times
Was thanked: 15 time(s) in 13 post(s)
|
admin wrote:New update (16.0.0.55) has been uploaded to the same download link
* New MultiView layouts
* Added dropdown menu next to Add Input for easy access to recent files
* Added support for IP Streams to Instant Replay
* Added new right click "Create Virtual Input" menu option
* Added "Always Play First Item with Transition" List Input option
* Added support for new YUAN High Tech cards
* Virtual Inputs now default to copying the settings from the source Input
* SetImage API can now be used via shortcuts, also excepts blank filenames
* Fixed Replay loop button error
* H264 Low Latency format option when adding cameras that use hardware encoding (such as from YUAN High Tech)
I've now moved to feature complete, bug fix mode for this release. Please continue to report
any bug fixes. Documentation is now being worked on for a final vMix 16 release at the end of August! Very nice Virtual Input additions and fixes! Thanks. Hopefully the transiton duration issue will be fixed before relase (transition duration 10000 ms or longer not working and vMix forces it to 1000 ms duration. And vMix should put the max value to the duration field if user inputs too large number). Kind regards, Jan Program mixed in vMix 15 Turn English/Frensh subtitles on. Tally and Intercom Solution: http://tally.fi
|
1 user thanked jet for this useful post.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 10/30/2013(UTC)
Posts: 290
Location: The Netherlands
Thanks: 6 times
Was thanked: 21 time(s) in 15 post(s)
|
I am missing the 'show input numbers' option in settings/display.
I like to hide the input numbers because my input devices have there own numbering, cam1, beamer1, desktop1 etc.
edit: I see the whole designation is changed ('virtual' inputs etc.)
I will learn to live with it.
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 5/4/2015(UTC) Posts: 26 Location: Germany Thanks: 3 times
Was thanked: 2 time(s) in 2 post(s)
|
Hi Martin,
did a short recording test with Prores, settings 1920x1080 50i Prores SQ.
It´s playing back in VLC, but in QT 7 and QT X on Mac there´s no sound at all, even Final Cut Pro refuses the file as not comliant.
Just to let you know,
Cheers
Jens
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,215 Location: Gold Coast, Australia Was thanked: 4304 time(s) in 1524 post(s)
|
jens wrote:
It´s playing back in VLC, but in QT 7 and QT X on Mac there´s no sound at all, even Final Cut Pro refuses the file as not comliant.
You'll need to select MOV (Indexed) as the file format for use with most editors. It won't be fault tolerant, so loss of power or crash means loss of recording, but it will be more compatible.
|
1 user thanked admin for this useful post.
|
|
|
|
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.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
