[quote=“invisible_acropolis, post:948, topic:4742”]
as far as who will pay for a new OS… who paid for OctaEdit? [/quote]
So bugger all people?
People can pay me up front for coding a new OS for the Octatrack, and Elektron can give me their source code for the existing OS, and a waiver against any legal action, otherwise I’m not releasing it publicly.
You know the JJOS cat(s) were ex Akai employees/contractors working for Akai on the MPC os?
yeh but you seem pretty capable tho… and OctaEdit seems to indicate a reverse engineering of the existing OS to a certain (large) extent, which is a great start
anyways i wont presume to know the best way for you to spend your time
i think that only by looking at OctaEdit’s manual one can get an idea of how much work and effort Rusty has put into this project…and that’s without considering what’s in the backstage, that’s where not too many people look at…
keep up the good work Rusty and let those bunny rabbits run around happily …moonbeams will follow
No, I’m afraid not. On Macs, only OSX 10.9 Mavericks, OSX 10.10 Yosemite and OSX 10.11 El Capitan at present.
Versions of OSX prior to and including OSX v10.8 are currently not supported. Backward compatibility is on the “to-do” list, but low priority.
Basically, due to Apple/OSX and certain restrictions/limitations that are in place… I can do it, but requires modifying certain parts of OctaEdit to adhere to previous OSX’s…
@MonstreJumo Just to manage expectations, backward compatability for OSX versions prior to and including OSX10.8 is a long way down my list of priorities, if ever.
OctaEdit and OSX : Waiting on backward compatability? / A show of hands.
If you are interested, but are waiting on compatibility for earlier OSX version, either comment on this, like the post, drop me a message or something, and I’ll see about bumping backward compatibility up the development pipeline.
Ok, did some quick intial testing… and I can do a seperate build for OSX versions prior to OSX10.9; at the expense of losing a small bit of functionality… mainly in the Samples module. Unfortunately, there is nothing I can really do about that, because its a limitation with Apple/OSX; well, I can, but I wouldn’t be able to justify the effort tbh.
(needed to add a tl;dr) - you have limited resources, spend it on moving forward.
Even though my music Mac is on 10.6.8, I think I’d rather see a one-man shop spend time moving forward and continuing to develop/fix/polish what’s there. Opening up the backwards-compatibility can of worms might be something to do if you had more resources helping you maintain the codebase.
I lug my OTs up to the Windows PC for OctaEdit interaction when needed. Yeah, it’s a slight hassle, but not bad. Even though I deal with computers and programming all day long, I’m very reluctant to upgrade that music machine since it’s got stuff like Tracktion 3.0 and drivers/apps for my Weiss AFI-1 AES->Firewire converter and other crap like that. Researching drivers, pulling down updates, etc is not something I’m comfortable with in the Mac world, so I leave that machine alone.
The real answer is to learn about Time Machine, buy an SSD and copy the drive and swap in the SSD and upgrade and see what happens, but I just don’t have the heart to start that whole thing right now.
[quote=“oldgearguy, post:967, topic:4742”]
Even though my music Mac is on 10.6.8, I think I’d rather see a one-man shop spend time moving forward and continuing to develop/fix/polish what’s there. [/quote]
I think I should be able do do 10.5 and greater, can flick you over a build of that if you want to check it out on OSX?
I have two cats. They can’t code for shit though. So thats three of us, like the three amigos, or is that stooges?