KVR Audio

Tronam · Post by **Tronam** » Wed Oct 16, 2013 10:38 pm

chk071 wrote:
pdxindy wrote:
They are 'evil' because of their efforts to control users. Like fighting hard to stop people from jailbreaking their iDevices.
Not sure about it atm, what is the law situation with jailbreak? Does Apple forbid it explicitely in their terms of usage, and is it legal for them to do so? Only thing i know is that you mess up your warranty if you do so, as on any Android device when you break those to use a custom rom.

Jailbreaking was never illegal, but didn't become officially upheld as legal until 2010. People can do whatever they want with their phones. I've had several iPhones over the years and always jailbroke them. Apple can't possibly hate the JB community that much though, since most of the new features in their iOS updates usually existed previously as jailbreak tweaks.

chk071 · Post by **chk071** » Wed Oct 16, 2013 10:45 pm

Interesting.

Well, it's sort of the same with Android. Google has to accept custom roms due to the amount of open source stuff they use i guess. The only obligation the makers of custom roms have to obey to is not to package the google apps (which are closed source) with their custom roms. It's also sort of a give and take, i mean the popularity of Android devices is also down to the openness of the system to modifications. Which is again good for Google, as they can profit from the ads.

valhallasound · Post by **valhallasound** » Fri Oct 18, 2013 1:21 am

Tronam wrote:I can only partially agree with this. A standard that never changes can also hamper innovation, especially in the technology sector. There needs to be some kind of balance so that the standards can evolve. I can't imagine anyone saying they'd be happy if we were all still using MIDI and hadn't migrated to high speed connectivity like USB/FireWire/Thunderbolt. Would you really want to go back to floppy disks and serial ports?

Nothing is wrong with new standards. Just call them new standards, and see if people adopt them. Don't break the existing standards.

Sean Costello

valhallasound · Post by **valhallasound** » Fri Oct 18, 2013 1:39 am

Tronam wrote:Forcing 3rd party developers to *only* use the Mac App Store is what we're talking about in this thread

I'm a bit more upset about the non-hypothetical short term effects, which will be that a bunch of Audio Units, that conform to the Audio Unit standard as it currently stands, will just STOP WORKING in some future update of Logic. This is what I mean about changing a standard.

It is one thing to change a standard in the early days of a standard, when things are still getting ironed out (i.e. Audio Units in the early 2000s, VST before 2.4, early versions of AAX). It is also understood that moving to a new processor architecture, or from 32-bits to 64-bits, will involve some changes to the standard. The idea that non-sandboxed Audio Units won't work in a future version of Logic X is a major change to the de facto Audio Unit standard (which is defined by most developers as "it works in Logic" - other AU hosts don't cough up the AU validation errors).

Sean Costello

Tronam · Post by **Tronam** » Fri Oct 18, 2013 3:24 am

valhallasound wrote:
Tronam wrote:Forcing 3rd party developers to *only* use the Mac App Store is what we're talking about in this thread
I'm a bit more upset about the non-hypothetical short term effects, which will be that a bunch of Audio Units, that conform to the Audio Unit standard as it currently stands, will just STOP WORKING in some future update of Logic. This is what I mean about changing a standard.

It is one thing to change a standard in the early days of a standard, when things are still getting ironed out (i.e. Audio Units in the early 2000s, VST before 2.4, early versions of AAX). It is also understood that moving to a new processor architecture, or from 32-bits to 64-bits, will involve some changes to the standard. The idea that non-sandboxed Audio Units won't work in a future version of Logic X is a major change to the de facto Audio Unit standard (which is defined by most developers as "it works in Logic" - other AU hosts don't cough up the AU validation errors).

Sean Costello

Yeah, that kind of already happened with Apple's blunt dropping of 32-bit support in Logic X. They have a long history of being the first to callously drop established standards without much warning (serial/parallel ports, floppy disks, optical drives, etc...). Microsoft was generally much better about maintaining backward compatibility.

Has it been officially confirmed now that non-sandboxed AU will simply no longer work in Logic?

dayjob · Post by **dayjob** » Fri Oct 18, 2013 5:08 am

Tronam wrote:
Has it been officially confirmed now that non-sandboxed AU will simply no longer work in Logic?

i guess we'll find out w/the next version.

Ogopogo · Post by **Ogopogo** » Fri Oct 18, 2013 6:06 am

Whoops wrong thread.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Oct 18, 2013 4:07 pm

[DELETED]

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Oct 18, 2013 4:09 pm

[DELETED]

Alfalfa · Post by **Alfalfa** » Mon Oct 21, 2013 2:45 am

In-app purchases coming to Garageband for iOS.

http://www.macrumors.com/2013/10/20/gar ... ork-icons/

The right steps are being made to suggest sandboxing is a potential future.

Tronam · Post by **Tronam** » Mon Oct 21, 2013 2:49 am

Alfalfa wrote:In-app purchases coming to Garageband for iOS.

http://www.macrumors.com/2013/10/20/gar ... ork-icons/

The right steps are being made to suggest sandboxing is a potential future.

iOS apps were always sandboxed from the beginning back in 2008 and in-app purchases have been part of the iOS App Store for years now. It's nothing new and is the main way developers work around the inability to provide app demos. They offer a crippled version for free with in-app purchases to add new or full functionality. Whether this shifts over to OSX is the question we're most concerned about.

Alfalfa · Post by **Alfalfa** » Mon Oct 21, 2013 2:53 am

I'm aware that this is iOS, but it is also Garageband, which is iOS and OSX. I think this is the first Apple product with in-app purchasing. First Garageband iOS, then Garageband OSX as a testbed for in-app purchasing for OSX, then Logic X. It's merely plausible.

Tronam · Post by **Tronam** » Mon Oct 21, 2013 3:03 am

Perhaps so, but it might also be as simple as this...

GarageBand will, however, include in-app purchase content from Apple, with additional instruments and sounds available for a fee. Licensing fees associated with some of those sounds had been the presumed reason why GarageBand was left out of the original move to make Apple's iLife and iWork apps for iOS free of charge, and it appears that the company has settled on in-app purchases as a way around this issue, offering basic functionality for free and then premium content through the paid upgrade options. ~ MacRumors.com

I suppose we'll find out soon enough when Apple unveils the last of their updated products next week, which I suspect will include new versions of GarageBand, iLife and Aperture.

accentaudio · Post by **accentaudio** » Mon Jan 19, 2015 2:51 pm

So I assume the OP was wrong and that this sandboxing thing is a non-issue now, as here it is 2015?

masterhiggins · Post by **masterhiggins** » Mon Jan 19, 2015 3:15 pm

I remember emailing u-he about it as they were one of the developers to submit a letter to apple indicating the follies of sandboxing AUs in Logic. They indicated that the plan has been postponed until Apple can find a viable solution for Logic. I'm paraphrasing of course.

Perhaps one of those developers can verify it for us? I'd hate to think I was just tripping on shrooms.

-Sam

"Logic Pro X will eventually be sandboxed"