I tried to connect to the server using netsend, but the console sends me
this error message:
"netreceive: listen failed: Cannot assign requested address (99)"
[connect vrr.iem.at 7077(
|
[netsend -u -b]
[listen 7077 vrr.iem.at(
|
[netreceive -u -b]
My idea is to define the name of a call to be able to share control
messages with a remote computer
--
Óscar Santis
sculptor, painter, noise musician
https://oscarsantis.art
tel: + 56 9 75802965
Thanks Christof, I'll make some test with AOO.
I need to send control messages only.
There is the possibility of sending them remotely, peer to peer, without
configuring the firewall and using only vanilla objects?
Is there an open server like the one used by Quacktrip that is available
for this type of communication?
--
Óscar Santis
escultor, pintor, músico ruidista
https://oscarsantis.art
tel: + 56 9 75802965
Hi community:
I want to know if there's a tool for remote connection like Quacktrip but
for OSC messages.
I know tpf-server but I'm interested in something that runs without
externals libraries.
Best
--
Óscar Santis
escultor, pintor, músico ruidista
https://oscarsantis.art
tel: + 56 9 75802965
Hi, we're compiling camomile with externals from ELSE, the only issue I
have is that else/click gets in conflict with an internal "click" class in
Pd (which doesn't happen if it's an external), this happens because of this
line of code
https://github.com/porres/pd-else/blob/master/Classes/Source/click.c#L156
and the warning given by camomile is "*warning: old method 'click' for
class 'canvas' renamed 'click_aliased*"
My plan is to simply disable this external when compiling for camomile,
because it's just not really pertinent to camomile at all, at least I
believe so (this is used to react to clicks on non GOP
abstractions/subpatches). I also believe the conflict won't make a
difference to the functionality of Pd. What do you say?
One way or another, I wanna get rid of the warning and I wonder if there's
a way to not interfere with Pd itself instead of disabling the external. I
guess there's no way, but I hope it doesn't hurt to ask :)
thanks
Ja ja, autocorrect... XLR inputs.
> On Oct 7, 2020, at 5:22 PM, pd-list-request(a)lists.iem.at wrote:
>
> From: Christof Ressi <info(a)christofressi.com <mailto:info@christofressi.com>>
> To: Pd-List <pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at>>
> Subject: Re: [PD] RPI stereo USB audio was: audio interface with
> multiple ins on raspberry pi
> Message-ID: <8bee4a0b-e882-bf01-c31c-7856294a6b10(a)christofressi.com <mailto:8bee4a0b-e882-bf01-c31c-7856294a6b10@christofressi.com>>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
>> but I require XML
> In my experience, XML works just fine on all Raspberry Pi models :-p
>
> On 07.10.2020 17:06, Dan Wilcox wrote:
>> Yeah, I know a lot of these small mini-jack boards work, but I require
>> XML and jack inputs and stereo jack outputs.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
Well, I'll take your experience with a grain of salt. My particular device has worked well with everything *but* the RPI 2. I must have bought it around 2006 and have only needed to re-solder the USB port pads once. As it is usb-audio compliant, I imagine it will continue to do so as long as USB 1.1. is supported. :)
> On Oct 7, 2020, at 9:26 PM, Kylee Kennedy <kmkennedy(a)gmail.com> wrote:
>
> I’m going to 100% say it’s the Edirol device not the Rpi. I used another very similar device for Ms Pinky DJ system before Serato. And I literally spent months trying to get that Edirol piece of crap to work consistently on Windows/Linux/osX Is just never worked smoothly. I switched from USB to Firewire for audio interface and 99% of issues went away. Now USB speeds have caught up with Firewire and USB interfaces are actually truly class compliant. But Edirol was only really good for video mixers.
>
> Good luck with your setup, I’d recommend a newer audio device.
>
> Kylee
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
To add on to Chris's question with a tangent, have any of you had good experience with bog-standard stereo USB Audio interfaces and RPI 3 or 4?
Some years ago now, I tried to use an RPI 2 with my trusty USB 1.1 standard audio interface (Roland Edirol UA-25) which is full-duplex stereo, 2 in / 2 out. I could never get it to work well in full-duplex mode without dropouts, even with a low-latency kernel and other real-time tweaks. In the end, it seemed the USB driver on the RPI was simply not designed for the "isynchronous audio" this requires.
The same device worked well on my original wearable, a Pentium 3 500 MHz machine but with a dedicated USB controller chip.
In the end, I decided to move toward iOS for embedded/wearable (hence PdParty) and the same device works very well at low-latencies on iPads and my (now old) iPhone 5S.
I'd like to still be able to run the setup with alternate systems, so does anyone have experience that the USB drivers have been improved? Thanks in advance
> On Oct 6, 2020, at 12:00 PM, pd-list-request(a)lists.iem.at wrote:
>
> Date: Tue, 6 Oct 2020 10:48:48 +0800
> From: Chris McCormick <chris(a)mccormick.cx <mailto:chris@mccormick.cx>>
> To: PD List <pd-list(a)iem.at <mailto:pd-list@iem.at>>
> Subject: [PD] audio interface with multiple ins on raspberry pi
> Message-ID: <5f3198d4-6210-4b41-d3a6-2cccbd3aae0a(a)mccormick.cx <mailto:5f3198d4-6210-4b41-d3a6-2cccbd3aae0a@mccormick.cx>>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hey all,
>
> Same question as the previous poster but I was wondering about inputs
> rather than outputs. Ideal solution:
>
> * USB.
> * Low cost.
> * More than 2 channels in.
> * Headphone sized jacks.
> * Works with Raspberry Pi.
>
> I've searched but could not find such a beast. Any hints?
>
> Cheers,
>
> Chris.
--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>
Hey all,
Same question as the previous poster but I was wondering about inputs
rather than outputs. Ideal solution:
* USB.
* Low cost.
* More than 2 channels in.
* Headphone sized jacks.
* Works with Raspberry Pi.
I've searched but could not find such a beast. Any hints?
Cheers,
Chris.
--
https://mccormick.cx/