hello!
can a touchscreen monitor be used connected to the Receptor?
?
Touch Screen for Receptor
-
- KVRist
- 82 posts since 28 Sep, 2007
at this time the answer is probably not. there is another thread from a year or so ago on this forum where it was debated and the fact that most touch screens tend to need to have drivers installed was the problem that prevented touch screens from working with the receptor. i don't think anything has changed since then.
i'm hoping that muse addresses this at some point.
http://www.kvraudio.com/forum/viewtopic ... uch+screen
i'm hoping that muse addresses this at some point.
http://www.kvraudio.com/forum/viewtopic ... uch+screen
-
- KVRer
- 8 posts since 5 Jun, 2007
I'm working with a touch screen company that has drivers for Windows, Mac and, most importantly, Linux kernel 2.4 and XFree86 4.2 - which is what the Receptor currently runs. They are willing to work with me on the driver, because *for the most part* it's mouse input and SVGA output - it's the configuration and "behavior" of the touch screen input that needs to be tweaked.
Am I missing something, or if a driver can be installed (of course I have root access, ssh et al to my box) is there any overt or obvious reason why I shouldn't be able to get this to work? I'm thinking it should be no more complex than, say, console mouse services with an X interface for configuration...
Thoughts? TIA,
/perk
Also, I'm going to document my progress at my forum, here:
http://www.perkiset.org/forum/music_tec ... 933.0.html
Am I missing something, or if a driver can be installed (of course I have root access, ssh et al to my box) is there any overt or obvious reason why I shouldn't be able to get this to work? I'm thinking it should be no more complex than, say, console mouse services with an X interface for configuration...
Thoughts? TIA,
/perk
Also, I'm going to document my progress at my forum, here:
http://www.perkiset.org/forum/music_tec ... 933.0.html
-
- KVRist
- 37 posts since 7 Nov, 2004 from Caspar, CA
Hey Perkiset - great project, please keep us apprised of your progress. What you are doing certainly should be do-able. I wonder why Muse isn't doing it (are they doing it?) - touchscreen seems a natural for Receptor. My fantasy is a touchscreen in a rack drawer. I looked into Unix compatible touchscreens when I first got my Receptor some months ago, but got into other projects and other gear investments.
Will follow with great interest. Rock on!
M
Will follow with great interest. Rock on!
M
-
- KVRer
- 8 posts since 5 Jun, 2007
@ apprised: will do, you can count on it.
@ Muse: They seem REALLY slammed working on 2.0 and want little to do with me, even though I was part of the beta for the KOMPLETE version (I got the second one created and had it built into a PRO version... it's just sweetness).
@ rack mounted touch screen - the company I'm working with has one! 12, 15, and 17 inch = they're great looking. Personally I'm going to go wall-mount and modify a piece of my keyboard rack for live performance - it will face me right at about C4 to my right rather than behind me in my rack.
I just want to be able to grab a slider and go, or touch the rotor speed lever in B4 without my Mac or a mouse or anything... I'm just itching for it.
If I pull this off, I'll post complete instructions and the drivers at my technology forum listed above. Thanks for the well wishes M.
/p
@ Muse: They seem REALLY slammed working on 2.0 and want little to do with me, even though I was part of the beta for the KOMPLETE version (I got the second one created and had it built into a PRO version... it's just sweetness).
@ rack mounted touch screen - the company I'm working with has one! 12, 15, and 17 inch = they're great looking. Personally I'm going to go wall-mount and modify a piece of my keyboard rack for live performance - it will face me right at about C4 to my right rather than behind me in my rack.
I just want to be able to grab a slider and go, or touch the rotor speed lever in B4 without my Mac or a mouse or anything... I'm just itching for it.
If I pull this off, I'll post complete instructions and the drivers at my technology forum listed above. Thanks for the well wishes M.
/p
-
- KVRer
- 8 posts since 5 Jun, 2007
I apologize all, I concede.
After spending about $1800 on hardware, software and working my butt off to get this touch screen to work with the Receptor, I have thrown in the towel. The problem has to do with the way the Receptor software runs, and my ability to run other things concurrently. The drivers for the screens that I worked with expect a much more vanilla OS and GUI layout, and although I am pretty competent with Linux and hardware, I just couldn't get it to float. I expect, that if I took the initiative to really break open the Receptor software itself I could have done more - but I'm afraid I just don't have that kind of time.
I have as since returned much of the hardware I purchased and have recouped much of what I spent, and I almost have my receptor back to normal. Because of the challenges, I have decided that, for my recording rig anyway, I'm going to go exclusively Mac and pull the Receptor. I'll be working on a new live rig with the Receptor, and have an idea for a monitor and trackball setup so that I can still see all I want to see on the Receptor while I'm live, yet without touchability.
Again, sorry to anyone following this thread in hopes - it has not been often in my 30 years of IT that I've had to call it quits.
/p
After spending about $1800 on hardware, software and working my butt off to get this touch screen to work with the Receptor, I have thrown in the towel. The problem has to do with the way the Receptor software runs, and my ability to run other things concurrently. The drivers for the screens that I worked with expect a much more vanilla OS and GUI layout, and although I am pretty competent with Linux and hardware, I just couldn't get it to float. I expect, that if I took the initiative to really break open the Receptor software itself I could have done more - but I'm afraid I just don't have that kind of time.
I have as since returned much of the hardware I purchased and have recouped much of what I spent, and I almost have my receptor back to normal. Because of the challenges, I have decided that, for my recording rig anyway, I'm going to go exclusively Mac and pull the Receptor. I'll be working on a new live rig with the Receptor, and have an idea for a monitor and trackball setup so that I can still see all I want to see on the Receptor while I'm live, yet without touchability.
Again, sorry to anyone following this thread in hopes - it has not been often in my 30 years of IT that I've had to call it quits.
/p
-
- KVRist
- 82 posts since 28 Sep, 2007
Thanks for your efforts and for keeping us up to date. I, too, threw in the towel trying to get receptor to work with a touchscreen. I've since gotten an OpenLabs Neko, which includes a touch screen already built in and configured and it works great. Best of luck to you in your future musical endeavors.
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Everyone,
I'm following the logic of a previous thread where the iphone was VNC'd to a Receptor giving it a touch screen UI:
Couldn't any touchscreen computer (linux, windows) act as a Touch Screen to Receptor? It seems that you could launch a VNC in the touch screen computer, and connect it to Receptor's UI in the same manner that your Receptor Remote software can create a remote screen.
The only problem that you would have to solve is wireless connect. If the touchscreen computer has a wireless card, then you simply need to hookup a wireless router to the receptor, and get the network settings correct.
Of course, a touchscreen computer may be more expensive then a simple touchscreen directly connected to the Receptor, but it has wireless advantages that could be useful on stage too.
Just a thought.
Regards,
Kevin L
I'm following the logic of a previous thread where the iphone was VNC'd to a Receptor giving it a touch screen UI:
Couldn't any touchscreen computer (linux, windows) act as a Touch Screen to Receptor? It seems that you could launch a VNC in the touch screen computer, and connect it to Receptor's UI in the same manner that your Receptor Remote software can create a remote screen.
The only problem that you would have to solve is wireless connect. If the touchscreen computer has a wireless card, then you simply need to hookup a wireless router to the receptor, and get the network settings correct.
Of course, a touchscreen computer may be more expensive then a simple touchscreen directly connected to the Receptor, but it has wireless advantages that could be useful on stage too.
Just a thought.
Regards,
Kevin L
-
- KVRer
- 17 posts since 15 Feb, 2008
As I've posted before I am using a "TC1100" umpc (HP) with active tuoch screen (with a stylus pen) and controling my Receptor using the remote software and an ethernet retractable cable.
I assume that it'll work just the same with any other laptop with passive touch screen (no need to use a pen) so this is probably the best solution.
I must say though, that I consider a real controller to be much better for live use.
I assume that it'll work just the same with any other laptop with passive touch screen (no need to use a pen) so this is probably the best solution.
I must say though, that I consider a real controller to be much better for live use.
-
- KVRist
- 96 posts since 2 May, 2004 from USA
yo yall i remember someone asking me this question 2 years ago on youtube in my email.
as of right now...
we use a so-called almost stock vanilla version of "kernel 2.4"and we use DEV_FS and PROC_FS
with that being said and you DONT trust yourself rebuilding it from source or using a vanilla 2.6 source (which has everything builtin!).
if you deside to use 2.6 dont forget to enable DEVFS or receptor wont load!
the only route you (we) have is to:
plug in the touch screen directly into the receptor.
start it up.
login as root.
do a: cat /proc/devices
if its too fat for you and want more control to space between pages;
do a: less /proc/devices
and dmesg
if your a little hardcore: watch -n1 'cat /proc/interrupts'
what your looking for is: model#, Serial#, X-Y coordinates,aspect ratios.
you need this info for inside:
XF86Config or if you have a newer receptor firmware: Xorg.conf
if you dont know what your doing... or have NEVER edited X11 files, or any UNIX configs
please do NOT attempt
if i were you i would clone my drive and practice on a clone NOT your working drive
BEKEN ONE
as of right now...
we use a so-called almost stock vanilla version of "kernel 2.4"and we use DEV_FS and PROC_FS
with that being said and you DONT trust yourself rebuilding it from source or using a vanilla 2.6 source (which has everything builtin!).
if you deside to use 2.6 dont forget to enable DEVFS or receptor wont load!
the only route you (we) have is to:
plug in the touch screen directly into the receptor.
start it up.
login as root.
do a: cat /proc/devices
if its too fat for you and want more control to space between pages;
do a: less /proc/devices
and dmesg
if your a little hardcore: watch -n1 'cat /proc/interrupts'
what your looking for is: model#, Serial#, X-Y coordinates,aspect ratios.
you need this info for inside:
XF86Config or if you have a newer receptor firmware: Xorg.conf
if you dont know what your doing... or have NEVER edited X11 files, or any UNIX configs
please do NOT attempt
if i were you i would clone my drive and practice on a clone NOT your working drive
BEKEN ONE
myspace.com/bekenone