|
Post by Nerohellbrigade on Dec 30, 2017 8:59:03 GMT -8
Hi,
I'm having many troubles on Windows 10 partition with the Raven software.
Just a few days ago I upgraded Raven software to version 3.3.2 available on the slatemt.com download section.
After doing that it turned out that I'm not able or got any chance of making Raven software and Pro Tools 12 communicating each other.
After first attempts of installation I wasn't able to get the Raven touch drivers working correctly(the UPDD pointer was telling me that no Raven MTi2 was detected,even changing in turn all the available USB ports),but after uninstalling 3.3.2 and installing the 3.2.0 legacy version and then reinstalling 3.3.2 finally I was able to get the correct touch drivers,but still no luck with Pro Tools 12. As follows is what I do in the right order:
a)run PT 12 as administrator;
b)run Raven software(V-Control Pro is set to launch at start up)
c)set up the V-control ports in the peripherals menu as port#1 HUI V-Control,port#2 V-ControlXT2,port#3 V-Control XT3 and port#4 V-Control XT4.
At this point sometimes the touch drivers are giving some random response,but when I give raven the commands to control PT 12 nothing major happens: no sync between edit and mix windows,it stucks with the opening window:if the project opens with the mix layout and I tell Raven to switch to edit window nothing happens;so vice versa,if on edit window when opening project and I tell raven to switch to mix window. Furthermore and most important,when I press play or any other transport command it lights up for 10 ms and the pointer slips away in another part of the screen. Unfortunately when I downloaded the new drivers I lost the previous ones as I overwrote 3.3.1 version,which they seemed to work better than the latters.
I'm getting so nervous,I overpaid a touch screen for 1.200,00€(I'm in Italy) and it does nothing more than it was supposed to do,and I'm just thinking to sell it if I won't be able to get it working right:the Windows drivers are a mess, so far!!
Please, help me getting through or I'll dismiss this so called "Holy Grail".
Thank you so much.
|
|
|
Post by jameyz on Dec 30, 2017 12:50:08 GMT -8
Hi, After first attempts of installation I wasn't able to get the Raven touch drivers working correctly(the UPDD pointer was telling me that no Raven MTi2 was detected,even changing in turn all the available USB ports),but after uninstalling 3.3.2 and installing the 3.2.0 legacy version and then reinstalling 3.3.2 finally I was able to get the correct touch drivers,but still no luck with Pro Tools 12. As follows is what I do in the right order: Probably not good going back to 3.2 as you just installed "NeyFi" where as the RAVEN 3.3.2 has been updated to use V-Control Pro. Please un-install Neyfi as RAVEN is probably confused which version to use. NeyFi or V-Control Pro. If you are getting a one way HUI communication between PT and Raven, you should try trashing your PT prefs. Here is an article on how to do it. slatemt.zendesk.com/hc/en-us/articles/222025687-Windows-Pro-Tools-No-HUI-Communication-Raven-Transport-not-workingYou will need to re-configure all the HUI peripherals and Pro Tools Preferences after trashing the prefs.
|
|
|
Post by jameyz on Dec 30, 2017 12:50:23 GMT -8
|
|
|
Post by jameyz on Dec 30, 2017 12:52:08 GMT -8
c)set up the V-control ports in the peripherals menu as port#1 HUI V-Control,port#2 V-ControlXT2,port#3 V-Control XT3 and port#4 V-Control XT4. You also shouldn't use the V-Control Pro XT4 as that would make PT think there is a 32 channel controller and not a 24.
|
|
|
Post by Nerohellbrigade on Jan 1, 2018 8:03:08 GMT -8
Hi Jameyz,
thank you for your prompt answer!!
The point is that I've already tried all of your suggestions,but still no luck so far!
The reason for which I've been forced downgrading to Raven 3.2.0 is that it's the only way to make the UPDD drivers working under Windows 10!
In fact,as long as I run a fresh 3.3.2 installation, after rebooting, the UPDD drivers are incomplete and an error comes out everytime I try calibrating the Raven Monitor,telling me that "No UPDD device Connected",even changing all the USB ports available! The real problem is that the actual Raven 3.3.2 software seems to be incomplete or incorrect under Windows 10(I tried on a clean OS installation); the next problem is that when I apparently solved the UPDD drivers issue(installing first 3.2.0 and then 3.3.2) Pro Tools 12 and Raven don't communicate,or as you were correctly saying,there is only one way communication (trashing PT pref as well)!!
I don't really know what to do,I cannot use the Raven software in no way,it's driving me crazy since 20 days or so.
Please help me or I'll be forced to sell this useless thing as fast as I can: Slate MTi2 is a total failure...so far!! I was asking myself: is it really 1000$ worth??(I paid for it 1.200€ in Italy!!!)
May you or someone else send me the previous Raven 3.3.0 so I can make a real test?
Thank you so much!!
|
|
|
Post by jameyz on Jan 1, 2018 11:21:07 GMT -8
Hi Jameyz, thank you for your prompt answer!! The point is that I've already tried all of your suggestions,but still no luck so far! The reason for which I've been forced downgrading to Raven 3.2.0 is that it's the only way to make the UPDD drivers working under Windows 10! In fact,as long as I run a fresh 3.3.2 installation, after rebooting, the UPDD drivers are incomplete and an error comes out everytime I try calibrating the Raven Monitor,telling me that "No UPDD device Connected",even changing all the USB ports available! The real problem is that the actual Raven 3.3.2 software seems to be incomplete or incorrect under Windows 10(I tried on a clean OS installation); the next problem is that when I apparently solved the UPDD drivers issue(installing first 3.2.0 and then 3.3.2) Pro Tools 12 and Raven don't communicate,or as you were correctly saying,there is only one way communication (trashing PT pref as well)!! I don't really know what to do,I cannot use the Raven software in no way,it's driving me crazy since 20 days or so. Please help me or I'll be forced to sell this useless thing as fast as I can: Slate MTi2 is a total failure...so far!! I was asking myself: is it really 1000$ worth??(I paid for it 1.200€ in Italy!!!) May you or someone else send me the previous Raven 3.3.0 so I can make a real test? Thank you so much!! Here is the link to start a support ticket for the Raven and I will get you some new touch drivers. slatemt.zendesk.com/hc/en-us/requests/new?ticket_form_id=61177
|
|
|
Post by jameyz on Jan 1, 2018 12:06:01 GMT -8
or send me an email and we will get you up and running.
|
|
|
Post by Nerohellbrigade on Jan 2, 2018 4:45:43 GMT -8
Yeah thank you very much! You can send me drivers to doubleheadroomstudio at g m a i l dot com
Looking forward to receivig your message.
|
|
|
Post by jameyz on Jan 2, 2018 14:06:51 GMT -8
Yeah thank you very much! You can send me drivers to doubleheadroomstudio at g m a i l dot com Looking forward to receivig your message. I was asking for you to send me an email or start a support ticket. But I started a support ticket with this email you gave, so you should see an email with new installer.
|
|
|
Post by Nerohellbrigade on Jan 2, 2018 15:56:53 GMT -8
Hi Jamey,
thank you,I received your new installer on my email,so here is an update: I ran the new UPDD installer you sent me and it seemes to have solved the previous faulty driver; aside from that,I always get stuck when opening Pro Tools 12. I trashed the PT Preferences before the first PT launch after new drivers installation:all is loaded, PT and Raven panel,but as soon as I set up the HUI ports in the periherals menu (V-Control,V-Control XT2 and V-Control XT3) and get back to the windows,there still is no communication between Raven and Pro Tools,or I should say, no two way communication! When switching between EDIT and MIX window only the Raven rack changes their status,but the PT window remains locked on its opening state. Moreover,when pressing some of the transport buttons(i.e play and/or stop,rewind or FF),nothing happens than an instant flashing status. I removed many and many times the drivers and re-installed from scratch,but still and always no luck!! Maybe some other procedure that I'm desregarding? On my Mac partition all is up and running (still there 3.3.0 drivers),so the same procedure is to be applied on WIN partition,but all statistics and events are definitely against me. What to do now?
|
|
|
Post by jameyz on Jan 3, 2018 8:50:05 GMT -8
Hi Jamey, thank you,I received your new installer on my email,so here is an update: I ran the new UPDD installer you sent me and it seemes to have solved the previous faulty driver; aside from that,I always get stuck when opening Pro Tools 12. I trashed the PT Preferences before the first PT launch after new drivers installation:all is loaded, PT and Raven panel,but as soon as I set up the HUI ports in the periherals menu (V-Control,V-Control XT2 and V-Control XT3) and get back to the windows,there still is no communication between Raven and Pro Tools,or I should say, no two way communication! When switching between EDIT and MIX window only the Raven rack changes their status,but the PT window remains locked on its opening state. Moreover,when pressing some of the transport buttons(i.e play and/or stop,rewind or FF),nothing happens than an instant flashing status. I removed many and many times the drivers and re-installed from scratch,but still and always no luck!! Maybe some other procedure that I'm desregarding? On my Mac partition all is up and running (still there 3.3.0 drivers),so the same procedure is to be applied on WIN partition,but all statistics and events are definitely against me. What to do now? You may need to set V-Control Pro to run as admin, or perhaps your computer is stopping Bonjour from launching which is an app that is needed to run for V-Control Pro to work. Lets setup a screen share and we will get it working for you.
|
|
|
Post by Nerohellbrigade on Jan 4, 2018 11:20:22 GMT -8
I already set both V-Control Pro and PT to run as admin and Bonjour service is up and running in the Task Manager. As I previously said,I tried and made all the recommendations on how to set up a Raven software,but still had no luck to get it working. The most weird thing that I noticed is that when Raven is open and ready to control PT,almost all the buttons and commands work but the Play,Stop,Rec buttons. Batch commands are working right,the edit/mix switch button works but in a strange manner,as I wrote in the previous replies: PT window doesn't change its status,or I should say that the only window changing is raven software while PT window remains in its opening layout. If I switch the edit/mix window from PT shortcut the raven follows PT,but not from Raven to control PT,and the same thing on play/stop/rec buttons.
|
|
|
Post by jameyz on Jan 4, 2018 13:51:43 GMT -8
I already set both V-Control Pro and PT to run as admin and Bonjour service is up and running in the Task Manager. As I previously said,I tried and made all the recommendations on how to set up a Raven software,but still had no luck to get it working. The most weird thing that I noticed is that when Raven is open and ready to control PT,almost all the buttons and commands work but the Play,Stop,Rec buttons. Batch commands are working right,the edit/mix switch button works but in a strange manner,as I wrote in the previous replies: PT window doesn't change its status,or I should say that the only window changing is raven software while PT window remains in its opening layout. If I switch the edit/mix window from PT shortcut the raven follows PT,but not from Raven to control PT,and the same thing on play/stop/rec buttons. Probably just need to fully trash the PT prefs, else may need a clean install of PT.. slatemt.zendesk.com/hc/en-us/articles/222025687-Windows-Pro-Tools-No-HUI-Communication-Raven-Transport-not-workingYou will need to re-configure all the HUI peripherals and Pro Tools Preferences after trashing the prefs. Lets setup a team viewer and I will get it going for you..
|
|