-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProTools with x jadeo #38
Comments
I'm also having problems here. It appears that pro tools is outputting the MTC correctly. I went to an older version of windows 10 and it worked, maybe its a problem between windows and xjadeo. I don´t understand how to manually choose the midi port. Sorry, but I'm kind of a newbie in programming. Thanks a lot for any help! :) ** EDIT ** Still trying to figure out how to make Xjadeo follow my cursor when not playing back. Maybe some setup in pro tools, but any hint is appreciated. ** EDIT 2 ** Having the ability to select the midi channel would be really awesome! |
I think i figured it out! finally i discovered how to use the commands on the manual to control the xjadeo. I think the problem was that xjadeo was not connecting to the right midi port. so here is the (temporary) workaroud:
then you have to check and take note of what port you want to use and select it. -close the xjadeo and redo everything but instead of "-v -m -1" you now tell xjadeo to select the port you want: Then it worked with me. Now the question is, how to make this permanent? I dont get where i should put the "xjadeoorc" confirguration file. (i assume its a .txt) Any helps on the matter? |
so far the only (terrible) work around i could find ist to make a shortcut or batch file with CMD commands to open the xjadeo with the right midi port selected. just create a blank shorcut and specify the path to: |
Has anybody told you you are a genius?! |
Again, you are a genius!!! A sincere thank you for saving my workflow!! Protools video engine is fantastically bad |
can't get it to work. anyone have recipe?
The text was updated successfully, but these errors were encountered: