Patching ON the organelle remains the best and most reliable way to patch, but can also be cumbersome when mouse, keyboard and HDMI monitor are needed.
Could a program like Team Viewer or similar be a solution?
I suggest this for selfish reasons, I’m currently travelling for several months with a laptop and an organelle and want to get down to some patching but don’t have space left for keyboard/mouse in my bag or have access to a monitor.
While I love this idea. I think the issue for most people adept enough to program in pd are probably on the thought basis of, If you have a laptop then you can write pd.
Not to minimize the idea itself. Or sound offensive. Just an assumption as to why it most likely hasn’t been done. that someone makes it though. Because that would be fantastic!
I tried to be clear in my post that the inconvenience this would overcome is the need for a keyboard, mouse and monitor to patch PD ON the organelle. Obviously, patching PD is possible on a laptop. But controls such as the encoder are not as yet supported on the mother desktop patch, so for proper testing - using the organelle is the only way.
sorry, i dont remember much more, and dont really have the time to sort this out properly at the moment.
(… i think it was quick to setup though, as i got it working only out of idle curiosity, rather than needing it)
ideally what we would do is create a installer for it so we know it works for everyone, or perhaps even add it to and OS update, as I think its potentially useful for anyone that has a wifi stick.
yeah, I use remote X all the time - it works for me with minimal fuss, but I saw on that thread a few others had issues. its best for macOS/Linux as it basically works ‘out of the box’.
remote X can be made to work with Windows, but there is more software/fussing about, so i think for windows VNC is easier, but then needs stuff on the Organelle… so pays your money, takes your choice.
the other option, if your interested in this just for developing patches is to use OSC proxying, as i described here:
this means you can develop the patch locally on your machine, but just using the Organelle controls.
it takes a bit of figuring out, but once you have it working its works really well… this is what i do most of the time except for ‘final patch testing’ which has to happen on the organelle.
(the downside is you need to make sure you have all the externals you need also on your desktop/laptop)
I had a go at tigervnc, but it has a bunch of dependencies and some were conflicting. I’m guessing because of the version of ArchLinux?
:: xorgproto and compositeproto are in conflict. Remove compositeproto? [y/N] n
Now, assuming I’m working on a spare SD card running the 3.1 image and /sdcard for my patches, any changes - even to the OS are just to the SD card, which I can reformat anyway and start again, correct?
yes, the OS is run completely off the sdcard, so if you ‘brick it’, you simply need to install a new system image onto the sdcard.
(of course if you have installed other things, these will need re-installing)
as mentioned above, i do have tightvnc on my organelle, but I can remember if i got any warnings at the time - and if i did, what i did about them.
im thinking about resetting my ‘development’ organelle back to a stock image, this would let me redo some of these things, and keep some notes this time
I was thinking. I am using a pretty big usb stick with my Organelle. Would it be easy to make an image of the sdcard with all my stuff installed (like serialosc and so on) and put that on the usb stick for a backup?
So I guess tigervnc is now the preferred thing. Even if I let it remove the dependencies, things fail:
[root@organelle ~]# sudo pacman -S tigervnc
looking for conflicting packages...
:: xorgproto and compositeproto are in conflict. Remove compositeproto? [y/N] y
:: xorgproto and damageproto are in conflict. Remove damageproto? [y/N] y
:: xorgproto and fixesproto are in conflict. Remove fixesproto? [y/N] y
:: xorgproto and fontsproto are in conflict. Remove fontsproto? [y/N] y
:: xorgproto and inputproto are in conflict. Remove inputproto? [y/N] y
:: xorgproto and kbproto are in conflict. Remove kbproto? [y/N] y
:: xorgproto and randrproto are in conflict. Remove randrproto? [y/N] y
:: xorgproto and renderproto are in conflict. Remove renderproto? [y/N] y
:: xorgproto and scrnsaverproto are in conflict. Remove scrnsaverproto? [y/N] y
:: xorgproto and xextproto are in conflict. Remove xextproto? [y/N] y
:: xorgproto and xf86vidmodeproto are in conflict. Remove xf86vidmodeproto? [y/N] y
:: xorgproto and xineramaproto are in conflict. Remove xineramaproto? [y/N] y
:: xorgproto and xproto are in conflict. Remove xproto? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: libice: requires xproto>=7.0.18
:: libxau: requires xproto>=7.0.18
:: libxdamage: requires damageproto>=1.2.0
:: libxfixes: requires fixesproto>=5.0
:: libxfont: requires fontsproto>=2.1.3
:: libxrandr: requires randrproto>=1.5.0
It appears that a whole bunch of these dependencies are old. I believe this goes along with what @thetechnobear was saying about this being a very old Arch Linux.
I’ll keep fiddling with the dependencies as I have time, but I’m not up on Arch Linux myself. Never seen it before.
I couldn’t get X working properly from macOS 10.13, and I think vnc would be very useful for the wider audience of users.
hmm, I don’t remember having this many issues when I did it…
ive a suspicion probably its been updated, and this is the issue with arch linux being a ‘rolling release’, when they update things, all the dependencies update…
the idea is your suppose to keep your system with the ‘latest and greatest’ but that’s often unrealistic.
ive a suspicion if you carry on down this route, your X will get broken
hmm, i’ll see if Ive still got it installed, if I do then then I should have the package file…
(but its possibly Ive rebuilt the organelle since I installed it)