{ "numMessagesInTopic": 21, "nextInTime": 1469, "senderId": "_Z7YeVDUBMXbeWw7XxLLbU8zXQ6WxIwbWmD-dlnRju876onXPh9TECvemxjq9gyyyPJJzFZpVx9MCW5CBJ5_4vqif9wNVzJCk__LQabW", "systemMessage": false, "subject": "Re: [01v96] Re: Wireless Studiomanager", "from": "Michael Haertl <michael.haertl@...>", "authorName": "Michael Haertl", "msgSnippet": "... Maybe this would do the trick (add a WLAN access point instead of bluetooth then): http://www.s-connect.ltd.uk/html_e/produkte/ionetworks/anywhere.html ", "msgId": 1468, "topicId": 1435, "spamInfo": { "reason": "0", "isSpam": false }, "replyTo": "LIST", "userId": 24337049, "messageBody": "
> Digitak Mastering <digitakmastering@...> said:Maybe this would do the trick (add a WLAN access point instead of
\n>
\n>> Tom, the trick is to have a transmitter and receiver with duplex USB
\n>>ports. USB cable to transmitter input from Reco or other remote device with
\n>>screen and USB out port on receiver to go to the V may do the trick, but I
\n>>mentioned duplex, because SM and the V may not work if the USB isn't duplex.
\n>>It shouldn't matter what type of wireless signal the transmitter outputs as
\n>>long as the receiver and transmitter have USB. Certainly somebody has
\n>>developed a similiar product. Could even use a true diversity type
\n>
\n> I honestly don't think such a product exists. There's not much of a market
\n> for one because wireless peripheral interaction is headed firmly in the
\n> bluetooth direction right now. In order for bluetooth to be an option, either
\n> the V96 would have to have bluetooth built in (which it doesn't, of course),
\n> or to have a peripheral-side bluetooth USB interface, which no one makes as
\n> far as I can figure out.
\n
\n