CPU utilisation is bumbling along between 50 and 60% Versions are Win4ICOM 1.3.9 and Win4Yaesu 1.3.8. These are both running on the same PC - Intel i3 with Windows 10 patched up to date. If I select the Win4ICOM window and hold down F10, tuning is slow and stutters. This is not due to the interface with the Shuttle - if I select the Win4Yaesu window and hold down the F10 key, it tunes up at the normal keyboard repeat rate and tuning is smooth. On the ICOM it is slow and tends to stutter. the tuning is smooth and real-time - pretty much the same as it is via the knob on the radio front panel. I'm also finding that the response of Win4ICOM to the shuttle is far slower than the response of Win4Yaesu. clicking the right button to select a fast tuning rate, spinning the dial to get to the other end of the band, then clicking the left button a couple of times to reduce the rate and fine tune to the wanted station. Opening the Shuttle Device Control Panel. ( Software/drivers installed fine but when I attempt to run the control panel (where you configure what the buttons do) I get a popup from Malwarebytes and it quarantines the 'C:\Program Files (x86)\Contour Shuttle\ContourShuttle.cpl' file. Can we have consistency between the two programs? The use of the left and right buttons on the shuttle to change the tuning rate is very ergonomic - I can operate it one handed. Control Panel ShuttleXpress Contour ShuttleXpress Manuals Manuals and User Guides for Contour ShuttleXpress. I just purchased a Contour Shuttle Pro V2. The first issue I've found should be easy to fix - Win4ICOM 1.3.9 does not recognise the NUM-MINUS key to reduce tuning rate! This is actually documented - if you go to the "Keyboard and Controllers" tab of the settings dialogue, it says quite clearly that the "plus" key will increase tuning rate until it wraps round to its slowest setting, but it makes no mention of the minus key. I installed the Shuttle control application and initially configured it for Win4Yaesu - put tuning on both the dial and wheel and set the two buttons on either side of the wheel to send NUM-Plus and NUM-MINUS to set the tuning rate - the result is absolutely excellent! I then made a copy of my Shuttle configuration and attached it to Win4ICOM and it works - but far less well. I run both Win4ICOM controlling my IC7300 and Win4Yaesu controlling the FT-991A. I remembered a few days ago and got my order in - it arrived today. I'm only able to test the installation on Windows here, so if anyone is able to check on OSX, that would be good.OK, after taking part in the discussion on the subject of using a Contour ShuttleExpress, I got distracted and didn't buy one. I'll add the prefs fixes when I've tested them a bit more. This has not been helped by the absence of documentation, so I've written the attached, which should prevent anyone else going through this. I've fixed hose issues, have notified Lightworks directly, and will be sending them the fixes. On three systems I have tried it one it usually chooses the wrong one, and telling it different doesn't stick.Ģ/ There are several issues with the Lightworks keyboard-prefs file that mean that the shuttle doesn't work properly, and that some standard Lightworks behaviour gets destroyed. I won't go into any detail, but there are two underlying problems:ġ/ Contour ships their driver with an old Lightworks settings-file that is wrong: when you import the new EditShare Lightworks one, it now has both and may choose either. I have now resolved the issues with the ShuttlePro. Can't watch the video because I have almost no bandwidth here. I've read all the threads that look like they could have been relevant, but not found anything. As I say, the system doesn't otherwise have any performance issues with any of this material. The ShuttlePro works perfectly on Premiere - video and sound are fast, responsive and in sync. The shuttle-control is a bit better, but still overshoots, and audio is only very occasionally to be heard. If I do this with a more complex edit and a timeline etc, even worse. With the ShuttlePro, and a single clip as the only thing on screen, if I turn the jog-wheel at more than about 4 frames a second, it won't keep up, and if I try to wind anywhere near playing-speed, it'll keep going for 15 seconds or more after I stop. Also, using the arrow keys is fine with no overshoot. The material is HD ProRes and I have no problems shuttling around it using a mouse at any speed I like. I've just installed a Lightworks-branded ShuttlePro, but jog and shuttle are not working usably.
0 Comments
Leave a Reply. |