Propellerhead Recycle 2.2 Mac Crack Apps
Teodolinda Mattson
Hi,can anyone out there clear this confusing/worrying matter up for me? i heard somewhere that .aif files are not the same as .AIFF files in that there is a degree of compression in the former and none in the latter also that this is the default encoding in OsX when importing audio files from CD via drag & drop into the finder. In fact some apps such as recycle will not import them until they are un-compressed back into AIFF format. are .aif files basically just AIFC encoded files and if this is indeed OsX default import option is there any way I can change it without having to import every audio file using quicktime or 3rd party app?
I just did a little experiment with Amadeus Pro (simple waveform editor program). I dragged a file off a CD, which has the suffix .aiff, opened it in Amadeus, and saved it as a new file. Amadeus will save all of its AIFF files with the suffix .aif. Looking at the two files they are identical in size, which means they are exactly the same.
Here is something from Wikipedia: 'The file extension for the standard AIFF format is .aiff or .aif. For the compressed variants it is supposed to be .aifc, but .aiff or .aif are accepted as well by audio applications supporting the format.'
Here is my conclusion: there is no difference between the suffix .aiff and the suffix .aif. They are both AIFF files. That being said, you can have an AIFF file that is compressed or uncompressed, but the suffix alone, .aiff or .aif, will not tell you whether that AIFF file is compressed or not.
so basically they're the same except (Little Endian) are compressed and (Big Endian) are un-compressed? something very weird is going on here because all my old commercially released sample cd's are being imported as compressed (little Endian) aiff's and as a consequence rendered unreadable by some apps which never used to happen in Os9. Could OsX be converting them on the way in? they're showing up that way when i get info directly from the CD via the quicktime inspector.
Anything from a CD that can play in a CD player (as opposed to a data or mp3 cd) is going to be uncompressed. If you drag a track off of a CD and onto your desktop, it will be uncompressed. Doesn't matter whether the suffix is .aif or .aiff, they're both exactly the same.
In fact, I"ve never come across any AIFF file, whether it has a suffix of .aif or .aiff, that is compressed. All audio samples, CD's, etc. that are AIFF files are uncompressed. When you bounce a file from Logic that is an AIFF file, the file ends up with a suffix of .aif, but is also a fully uncompressed AIFF file. The only time I've seen or used compressed AIFF files is when I saved them that way on purpose.
Again, if you're copying a file from a CD onto your machine, it will be uncompressed. Unless your importing a CD into iTunes, it will copy the file in the same format it's in on the CD. If an application can't open it because it has a suffix of .aif instead of .aiff, it just means that that application is confused about the tag of .aif, not that the file is different or compressed in some weird way. Just manually change the suffix of the file to .aiff if that's the problem, and you apps should be able to read them.
hi, sorry if I lost you a bit, but that is exactly what i have always thought, an aif is an aiff is an aif.. but there appears to be two types: aiff or .aif (Big Endian) and .aiff or .aif (LIttle Endian) the latter being the problem 'compressed' file that won't import into say 'recycle.
When i get info with the quicktime inspector directly from the CD, the files are showing up as .aif (Little Endian) files. I then have to re-encode them using a 3rd party app converting them to .aif (Big Endian) before recycle will read them? welcome to the twilight zone....??
phew, now thats clearer. i guess this is an issue with propellerhead/recycle software and to a degree peak pro's confusing status bar which reads 'importing compressed file' when importing these files.
Thanks for all your help in clearing that up guys, looks like ill have to carry on batch converting whenever i'm using these apps. I will leave some info on the propellerheads forum on this one because tech support there seem to think this is a compression issue too.
Yeah, I mean I get it though. Everyone knows you shouldn't put money into something for what it will be but I think with how much Korg asks of us that its hard not to be a little butt hurt when they seem to be heading in a direction contrary to what most users want. Korg can suck a few hundy out of you, when garage band is looking more versatile you can start to feel betrayed a tad.
Unfortunately, some people made a poor buying decision and want to blame Korg. I bought Gadget years ago. Once I decided it worked for me, I bought the IAPs. I've been using it the same way here and there ever since, while benefitting from all the free updates, and buying more IAPs as I wanted them. If Korg added nothing since, I'd have gotten my money's worth.
It was years ago that I and others posted on this forum that Gadget was unlikely to go AUv3, that it was designed as a simple and reliable closed system, to sell Korg IAPs, and that Korg would stick to how they view the product. So far, that's held. People still expecting different.
Maybe Doug was referring to a Gadget Pro release in the game changers thread about a new app coming out...? A Gadget that supports AUv3 synths and fx!! Certainly be a game changer - but I kinda doubt it - too much energy and focus put into Gadget ... but we like to dream about such things here so...
Anyways - disappointed in the update here - but I still love Gadget a lot. I guess since the new Gadget is not much interest I should take advantage of the sale and finally pick up the Oddessei or Vancouver ones ... I have enough left for 1 or the other in my iTunes account. Oddessei??? Leaning towards that... convince me (don't need much convincing but I'm listening)
Even as an admitted Korg fanboy, I've got to say, the presets they give us with their sampler apps defy the definition of anything close to musical. Going off the stock presets alone, had I paid full price I would definitely feel that I paid too much. So does Korg know best? With their presets, I have serious second thoughts. Then there's their demo songs. Like what demographic besides some old Japanese game developers are they trying to appeal to?
I've seen many comments about battery drain and heating up iPads from using gadget ... but I've personally not experienced this. On both my old iPad 4 and new 2018 ipad - I can use it for an hour or so and maybe use 10-15% on new iPad - maybe 20% on old one - and iPad not any hotter than using a bunch of synths in AUM or other setups ... wonder what's up with that? Before I got my new iPad I thought it might've been a 32 bit vs 64 bit issue ...
Apologies if this has been answered already but this was added a while ago, if yours isn't working take a look the in the main settings of your device where you can enable the native modes for gadget. Mine are all enabled and I only have one of the listed controllers.
I've never tried to import anything into Gadget before, so perhaps I'm doing it wrong ., but when I just tried to import some rex files , they are all greyed out. Tried copying them to dropbox from my PC and selected dropbox under import in ipad stockholm. Also tried opening dropbox on ipad, making them available offline, etc.
Perhaps it's an incompatible version of rex file? It's from a Big Fish Audio sample pack I own ., .rx2 file extension.
How'd you import from audioshare? I'm trying everything I can think of -- my .rx2 files show up in dropbox but are greyed out ... I tried copying to audioshare but still trying to figure how to import into gadget.
I don't have any tools at hand at the moment to create rex-files so it's strictly a playback device for now.
(If anyone knows of an iOS app that can create REX files I'll be happy to get informed).
This s a missed performance performance opportunity, swipe up/down on the pad to adjust playback pitch of the slice and left/right for direction etc. would have created a pretty expressive instrument.
7fc3f7cf58