|
|
Post by billrigby on Sept 14, 2020 19:58:16 GMT -8
Is there a way to get V control to consistently be one of the first apps to load on bootup.
I have to Shut down and startup a couple of times.
Usually on my first boot V control loads up last, which invariably causes the classic HUI communication error in Protools.
Pretty annoying.
Any ideas Brains trust?
|
|
|
|
Post by jameyz on Sept 15, 2020 9:51:50 GMT -8
Is there a way to get V control to consistently be one of the first apps to load on bootup. I have to Shut down and startup a couple of times. Usually on my first boot V control loads up last, which invariably causes the classic HUI communication error in Protools. Pretty annoying. Any ideas Brains trust? When you launch the RAVEN software it will automatically open V-Control Pro. Usually on my first boot V control loads up last, which invariably causes the classic HUI communication error in Protools. Just hit "don't show again" and you won't see that error anymore. |
|
|
|
Post by billrigby on Sept 15, 2020 17:49:39 GMT -8
Sorry , I don't understand.
When I first boot my Mac, along the top right of the Mac the various processes icons line up in theoriser they are instantiated in. (ie, looking at it now , the order is , Audio Device Speaker Icon, Eject symbol for drives , Bluetooth, Motu Audio Control, Lulu Firewall Protection, Logitech Camera, UPDD Daemon, UPDD TIO, UAD Audio Console, Soundsource Audio Router for native audio, Raven, Dropbox, V Control, Avid Link.
When I boot the Mac the order of these processes will change.
If V control is one of the last processes in order to load I will get the HUI communication error.
If it is one of the first in order I do not get this error.
In the land of PC Windows you can change the startup order of processes (Startup Items).
Is there a Mac version of this that you know of so I can get the UPDD, UPDD TIO , Raven and V control to be one of the first processes as far as low priority ( say directly after Bluetooth)Is my description of the problem clear?
Cheers,
Bill
|
|
|
|
Post by jameyz on Sept 16, 2020 9:18:55 GMT -8
If V control is one of the last processes in order to load I will get the HUI communication error. Which error? What if you hit "don't show again" ?? |
|
|
|
Post by billrigby on Sept 17, 2020 4:58:34 GMT -8
The error is the standard cannot communicate with device, go to peripherals tab.
The Raven does not communicate with protools . It operates as a standard touch screen ,but none of the Raven GUI functions at all.
What actually happens is that there is no V Control Input devices in the Pro Tools Midi input devices folder.
Therefore, when you go into peripherals the three tabs are full, but if you click on them to re-select them , they are not in the list to select.
Whereas if the V Control is early in the Mac boot sequence, the midi input devices contains the V Control devices and everything works fine.
What do you reckon?
|
|
|
|
Post by jameyz on Sept 17, 2020 8:35:11 GMT -8
What actually happens is that there is no V Control Input devices in the Pro Tools Midi input devices folder. Therefore, when you go into peripherals the three tabs are full, but if you click on them to re-select them , they are not in the list to select. Whereas if the V Control is early in the boot sequence, the midi input devices contains the V Control devices and everything works fine. Something seems very wrong with that as I don't open V-Control Pro at startup ever. I just wait until I launch the RAVEN Dashboard for it to open V-Control Pro and Pro Tools and I have never had an issue with the Midi Peripherals not showing. I would probably reach out to Slate, V-Control Pro, or Avid support about this. Maybe also a re-install of Pro Tools and V-Control Pro. Here is the link to start a support ticket for the Raven. slatemediatechnology.zendesk.com/hc/en-us/requests/new |
|
drumah
Junior Member
Posts: 60 
|
Post by drumah on Sept 17, 2020 10:21:31 GMT -8
Not sure there is a way to select what starts first/last (maybe there is, but I don't know). However, you can delay your startup items .. Maybe delay everything except v control. Check out: www.makeuseof.com/tag/add-remove-delay-startup-items-mac/However, I'm with jamey and never had to touch v-control on startup. Boot my mac, then launch pro tools from the raven app. no probs |
|
|
|
Post by billrigby on Sept 17, 2020 16:43:15 GMT -8
Thanks Jamey,
I have reinstalled both.
I don`t open up V Control either. It just loads in sequence with the other processes.
I use the Raven launcher and everything operates as it should until it gets to loading controllers , after loading audio in the Pro Tools boot sequence.
Then the HUI communication error occurs.
The reason it occurs, I believe, is because the VControl is not in the midi Input devices.
When V Control is one of the first in the Mac sequence the V Control is in the Midi input devices.
I think this all could be avoided if V Control showed up in the Mac Audio and midi settings.
Thanks for you suggestion Drumah, I will investigate that link.
CHeers,
Bill
|
|
|
|
Post by jameyz on Sept 18, 2020 8:11:37 GMT -8
When V Control is one of the first in the Mac sequence the V Control is in the Midi input devices. I think this all could be avoided if V Control showed up in the Mac Audio and midi settings. Thanks for you suggestion Drumah, I will investigate that link. CHeers, Bill Pretty odd, I think this needs to go to V-Control Pro support as I have never seen this issue.. |
|
|
|
Post by billrigby on Sept 21, 2020 23:03:15 GMT -8
Hmmmm,
V Control support ,
have you got a contact I can speak to?
|
|
|
|
Post by jameyz on Sept 22, 2020 11:45:18 GMT -8
Hmmmm, V Control support , have you got a contact I can speak to? Pretty sure it is just Paul Neyrinck and Josh over there. |
|
|
|
Post by billrigby on Sept 24, 2020 20:04:14 GMT -8
Thanks Jamey,I`ll let you know how I go.
|
|
|
|
Post by leitweight on Sept 25, 2020 11:37:41 GMT -8
Just a thought Bill, but in your Mac System Preferences, under Login Items, you should NOT see that V Control is loading at startup. If V Control is in this list, select it and click the Minus button on the bottom left below the list. The Raven Dashboard will load V Control automatically, so it does not need to load at system startup.
|
|
|
|
Post by newcity on Sept 30, 2021 7:01:17 GMT -8
Just a thought Bill, but in your Mac System Preferences, under Login Items, you should NOT see that V Control is loading at startup. If V Control is in this list, select it and click the Minus button on the bottom left below the list. The Raven Dashboard will load V Control automatically, so it does not need to load at system startup. I was having the same issue as Bill. "leitweight" was correct about the V-Control loading at start up! That fixed my problem and I've rebooted several times to confirm that this works consistently. One more piece of information about locating the Login Items. The Login Items are found under the "Users & Groups". Thanks for posting everyone! |
|
