To repeat the request for help above, can anyone suggest why Adobe Camera Raw is not applying the lens correction profile built into the metadata of RAW files taken with the DJI Mini 5 Pro drone? I want to emphasise that I'm not asking for Adobe to create a lens correction profile for this lens (though that would be nice). I am asking why ACR isn't automatically applying the lens correction profile already built into the metadata of the RAW file, which is what it does with other lenses including for example the DJI Mini 4 Pro. Since the profile is already built into the metadata this does not require any work or input by Adobe. I would very much appreciate any help with this.    ... View more

DJI Mini 5 Pro please. ... View more

Thanks very much, SteveG, I found the pdf very informative and really appreciate your help. I doubt if I will ever understand FFT but the bottom line is, as you say, not to run anything this hot. I can see that downsampling an audio file that's already clippipng is asking for trouble. ... View more

Thank you so much, SteveG, for the extremely helpful reply.   It's certainly true that I do not have an undertanding of how FFT works but I do follow your simplified explanation and it does make sense to me.   The odd thing is that if I go back to the original 192/24 audio file, that too has the the same waveform shape at that particular point and yet a) it does not make a popping sound when played back through JRiver MC34 and b) when displayed in iZotope RX5, it does not have those alarming spikes.    A second oddity is that if I downsample the same audio file to 96/24 using software other than Adobe Audition CS6, the resulting audio file does not cause the popping sound when played back through MC34 or the spikes when displayed in iZotope RX5.   Do you think you could help me undertand why this is? I've been experimenting with home audio for a good many years now yet this is the first time I've come across this.          ... View more

Yes, perhaps there is some confusion over the number of channels on this particular disc. In reality, there are only five and the booklet says: "Technical note: For creative reasons, the surround mix was done in 5.0; the LFE is not utilized." Even that's ambiguous. There's a difference between "not utilized" and "not there". I've seen plenty of discs where channels are not utilised and yet are still there, completely empty. But in this case, the LFE channel is simply not there. ... View more

Thanks, SteveG. All very mysterious. I should caution against placing too much reliance on the tagging because the tagging on the version I uploaded was done by me after ripping, using the Mp3tag app. Not only that, but I "borrowed" the tags for this album from a two-channel version which I already had on my PC. So that could perhaps have introduced the two-channel metadata that you observed. Having said that, this problem still arises in exactly the same way even if I use a track in its un-tagged state, meaning a track that has not been tagged by me after ripping. So it's not my tagging that's creating the problem. I will be happy to help in any way I can. The disc is this one - there are some notes and credits if you scroll down: Link to Discogs page I extracted the audio from the DVD Audio disc using DVD Audio Extractor on my PC, then tagged it using Mp3tag. I should just mention that I keep all my music on my PC and the only reason for ripping this disc was to store the music on my PC with the rest of my collection. I  own and keep all the discs I rip and do not share the discs or rips with anyone else. ... View more

Edit: please could you ignore all of the following post and see my next post, below it! I am attaching a sample from the troublesome album. It has a total of five channels - it is 5.0, with no LFE channel. When I try to apply Voxengo CurveEQ to this album in CC, routeing only shows for the first two channels and the other three are shown as "Bypass". When I apply the effect, it modifies the first two channels only - the remaining three are not modified but the audio is displaced about 0.5 seconds to the left! CC has no problem with my 5.1 albums (total of six channels.) It also has no problem with my quad (4.0) albums - but I notice that in the quad albums, the channels are padded out with empty channels to make a total of six channels. So I wonder if CC only works with six channels or even numbers of channels, and that you can only edit an odd number of channels if they are padded out with an empty channel to make an even number? Just to repeat, I have no problem applying Voxengo Curve EQ to the troublesome album in Audacity so at this point this looks to me like a quirk with CC. Here is the link to the sample. It is in WAV format so may take a while to download: Click here ... View more

It's getting late here in the UK so I'll have to stop now but I did try various multichannels in CC and they all worked except this 5.0 album. In the routeing, it only shows left and right and all the other channels are bypass. So I don't know if it's something to do with this one album or what. Maybe tomorrow I will send you a link to a sample in Dropbox and see if you have any luck with it. Many thanks for all your help and I will say goodnight for now. ... View more

I just tried with a 5.1 track and the plugin worked fine in CC. When I tried in CS6, it only worked on the first two tracks - the other four disappeared! So as far as I can see: 1. CS6 can't be used for multichannel with third-party VST plugins. 2. CC can be used with multichannel, but not in all multichannel. As you say, it works in 5.1 but not in 5.0. I haven't tried other channel configurations.. I suspect it's not Voxengo's fault because as I mentioned up-thread, the Voxengo plugin works without any problems in Audacity, regardless of the number of channels. Many thanks indeed for solving the riddle, Steve. Hopefully the devs will fix it one day and I can always use Audacity as a stop-gap. Thanks again, Richard ... View more

Sorry Steve, I am one post behind you all the time! So it doesn't work in 5.0? I will try a 5.1 and get back to you. ... View more

Sorry, SteveG, I didn't see your post before posting my last. I think you're on to something there. I have never seen that button before in all my years with Audition. Sure enough, when I click on it, there are five channels listed BUT channel one is marked left (in and out), channel two is marked right (in and out) and all the others are marked Bypass. If I try to change Bypass to left or right, which are the only options, it disables the existing left or right. This is all new to me and I've no idea what I'm doing so if you can help me at all... ... View more

In fact, it gets weirder. With both CS6 and CC, if I try to use the plugin on a five-channel track, the plugin only works on the first two channels, as I already said. It doesn't work on the remaining three channels - but what it DOES do is, it shifts the audio in those remaining three channels about 0.5 seconds to the left! ... View more

Well, I just downloaded the free trial version of Adobe Audition CC and tried it and exactly the same thing happens - the Voxengo CurveEQ VST plugin only modifies the first two channels out of five. (This is in the waveform editor.) I then opened Audacity (which I downloaded earlier today) and tried the same thing with the same files and same plugin and Audacity modified all five channels without any problems. I'm baffled. Are CC and CS6 unable to do this seemingly straightforward task or is something else going on here? ... View more

Oh, really? That's a disappointment if it's the case. The in-built effects seem to work across all channels of the multichannel so it's a pity if something's stopping VST plugins from doing the same thing. I'll just have to use Audacity unless anyone thinks there's a way around this. Many thanks for answering. ... View more

OK, well at least I know it's not just me. Many thanks and I'll leave it at that - unless I make any more startling discoveries! ... View more

Thanks, Steve, I'm sure that's right. Although I don't like being beaten, I think it's time to move on so I'm planning to use iZotope RX5 for recording and to keep CS6 in reserve for editing. The only thing with recording in iZotope is that it doesn't seem to display the waveform while you're actually recording - only when you've finished. I find this a bit disconcerting. Is that just how it is? (With apologies for going wildly off topic.) ... View more

Update: I installed PreSonar Studio One Prime again, in 32 bit and 64 bit. I tried them both with the 96 kHz ASIO stream but it was still no go: neither would work. They see the driver and try to start recording but the transport will not move. (Same as before.) So the situation hasn't changed that much. What I have is that Audition CS6 (32 bits), PreSonar Studio One Prime (32 bits) and PreSonar Studio One Prime (64 bits) will not work at all with this setup. iZotope will work in both 32 bits AND 64 bits. And Audition CC and NCH WavePad both work in 64 bits. I'm not sure what to make of this. I still like Steve's theory but it doesn't really explain why PreSonar Studio One Prime (64 bits) doesn't work or why iZotope RZ5 (32 bits) does. So I think the SPDIF connection is in there somewhere as well - I feel sure I wouldn't be having all these problems if the connection was USB. ... View more

Oh no - it gets even more complicated. I just realised that iZotope had installed TWO versions of RX5 on my Windows 10 64-bit PC - the 32-bit version AND the 64-bit version. So of course, I had to try both! Now, the 64-bit version worked flawlessly - no problems at all. If Steve's theory is correct, we would expect the 32-bit version to fail And it did - up to a point, Here's what happened. When I hit the record button, the transport wouldn't move and I received the following error message: "Recording is disabled because the clip's sampling rate is not supported by the selected input device." Oh no, I thought. Was that the problem all along? I'd been trying to record at 176.4 kHz, which is supposedly supported by my sound card. But maybe there's an error in the driver and 176.4 kHz only works with the 64-bit driver and not with the 32-bit driver? That would explain why Audition wouldn't work. So I tried a different setup, plugging the optical cable into the 96 kHz optical digital output of my BD player. I then tried RX5 (32-bit) again and yes, it worked, recording flawlessly. Obviously 96 kHz wasn't a problem for the sound card's 32-bit driver, even if 176.4 kHz was. So of course, Audition should now work in 96 kHz too. So I closed RX5 (32-bit) and opened Audition, selected the ASIO device class and tried to open my sound card's ASIO driver. But - still no go. The same old error message: "Device could not be opened." I'm not sure what to make of all this. It does seem that there could be an error in the sound card's 32-bit driver with regard to the 176.4 kHz sampling rate. Even so, RX5 is able to use the sound card's 32-bit driver at 96 kHz (and probably most other sampling rates) while Audition CS6 is not. I suppose I ought to give PreSonar Studio One Prime another shot, this time at 96 kHz, but I've uninstalled it now. Maybe later. ... View more

That sounds like a very plausible theory, Steve. It's certainly true that in my few experiments, I haven't been able to find a 32-bit DAW that would run the ASIO driver successfully on my 64-bit PC. The only fact that doesn't quite fit is that the 64-bit version of PreSonus Studio One Prime wouldn't run the driver on my PC either, at least in my brief experiment. But maybe that was for some other reason. Drivers, eh - dontcha luv 'em? BTW, I need to modify my statement that CS6 won't work in ASIO with only one SPDIF cable attached  - clearly it worked for you with your 32-bit PC so I'll confine that theory to 64-bit PCs. ... View more

I downloaded another DAW with interesting results. This time it was PreSonus Studio One Prime. First I downloaded it in the 32-bit version to mimic as far as possible CS6. Studio One was able to see and load the 32-bit driver in my sound card without any problem and looked as though it was going to work. However, when I hit the record button, the transport would not move. I then downloaded the 64-bit version of Studio One. This time it saw and loaded the 64-bit driver in my sound card without any problem. Again, everything looked fine and it looked as if it was going to work but when I hit record, the transport would not move. I then downloaded a completely different DAW - this time iZotope RX5. This loaded the soundcard driver without any problem and recorded flawlessly. My takeaways from this are: 1. It's not the driver that's causing the problem. The correct version loads with 32 or 64 bit programs. 2. Some DAW software programs just will not work in ASIO mode when only one S/PDIF cable is connected. Adobe Audition CS6 is one example and PreSonus Studio One Prime is another. However, other DAWs will work quite happily in this mode, including Adobe Audition CC, the free NCH WavePad and iZotope RX5. It does not seem to matter whether it's a 32-bit or 64-bit program. So I think that probably wraps it up. Whatever the reason, CS6 just will not work in ASIO mode with only one S/PDIF cable attached and that's that. If there are any other comments I'd be delighted to hear them but I think it's just a case of using a different DAW. Many thanks for all the help given here. ... View more

Oh, I see what you're saying now. That's very interesting and it sounds to me like a probable diagnosis for the problem - though unfortunately, without an accompanying cure! First of all, the StarTech sound card is the PEXSOUND7CH StarTech PEXSOUND7CH and it uses the CM8828 chipset by C-Media Electronics CM8828 chipset The chipset uses the CM8828 driver supplied on StarTech's website. This comes with Xear software. The software allows you to choose input device, output device, and sampling rate for each input and output but as far as I know, the Xear interface only applies to MME audio and is by-passed when you're in ASIO mode so it's really irrelevant. I have tried various combinations of sampling rate settings and inputs and outputs but nothing makes any difference to my inability to open the ASIO driver. When you ask if the card manufacturer supplies any software for the ASIO driver, there is just one thing. In the Xear software, there's a small ASIO button and if you click it, it opens a pop-up window and offers you the chance to change the buffer size (nothing else). The pop-up is headed "C-Media High Definition Audio Device (x64)" and that's what started me worrying about 32-bit and 64-bit. But I think it only says that because 64-bit is the default on my system and the driver has never yet been opened in 32-bit because Audition CS6 won't open it! The reason why I currently hold CS6 responsible is that CS6 has this problem with all ASIO drivers, not just the C-Media driver - meaning, CS6 cannot open any ASIO driver to a device connected with only one SPDIF cable. I seem to remember that CS6 always had a peculiarity with syncing that was unique to CS6. I can't remember the exact details but I remember running up against this in the past and I think that's why I'm having all these problems. I don't have these problems using this sound card with any other DAW. ... View more

I downloaded a free DAW called Wavepad and that worked flawlessly with my SPDIF input too. So I'm ready to call Adobe out on this one. Unless or until anyone can demonstrate otherwise, there is a bug in Audition CS6 as follows: Audition CS6 will not open any ASIO device if Audition CS6 is connected to the device only by a single SPDIF cable (either input or output). ASIO will only work with SPDIF if you are able to connect an input AND output cable to the SAME device.  Notes: 1. This bug has been corrected in Audition CC. Audition CC will play or record using only a single SPDIF connection.. 2. The bug does not apply to MME recording/playback in CS6. Only ASIO. 3. The bug does not affect USB recording/playback in CS6. Only SPDIF. I would be extremely happy if someone can prove me wrong but if not, I'm going to have to use a different DAW to record in ASIO via SPDIF. I wish I could buy CC but there's no way I'll sign up to a subscription model so I'll either invest in something else or just carry on with CS6 and use Wavepad or another free DAW for SPDIF recording. ... View more

Thanks but I honestly don't think it's sample rate matching because: 1. The driver refuses to open before it has any idea what sample rate you're planning to input or record at. You never even get that far because the driver won't open in the first place. 2. It wouldn't explain why Adobe Audition CC is able to run flawlessly with the same setup. 3. It wouldn't explain why other devices don't have this problem if connected with two S/PDIF cables, but do have this problem when connected with one. Also, I have spent a lot of time trying different sample rates and nothing makes any difference. What I really need to know is if anyone else is able to load and play through an ASIO driver using only one S/PDIF cable in CS6. Then I'll know for sure whether it's a CS6 problem or a problem with my setup. ... View more

OK, there's been another big development. It's nothing to do with bits, after all. I tried deleting the entire preference folder for CS6 and although that did indeed make CS6 launch in plain vanilla flavour, it didn't make any difference to its inability to load the ASIO driver. However, I then had an idea. I tried connecting other ASIO devices by a single SPDIF cable - and they didn't work, either. That showed it wasn't the driver that was at fault, after all. I then had another idea. I tried connecting these other ASIO devices by two SPDIF cables, one for input and the other for output - and they worked flawlessly! What I have found is that if I connect any ASIO device by a two-way street - either a USB cable or two SPDIF cables, in and out - it works. If I connect any ASIO device by a single SPDIF cable, either in or out, it doesn't work. This is true of my CS6. But it is apparently not true of CC, where a single SPDIF cable does work with an ASIO device. I wonder if anyone using CS6 with Windows is able to verify or refute this? My contention is that it's impossible to use any ASIO device with CS6 if it's connected only with a single SPDIF cable - you must have either twin SPDIF cables or USB. ... View more

OK, things have moved forward a bit. I downloaded a trial version of Audition CC and tried the same setup. It works flawlessly with my soundcard in ASIO mode! I then went back to CS6 and tried reinstalling CS6 from my old installation disc. As a result, I have now gone back from Version 5.0.2, Build 7, to Version 5.0, Build 708. (I also uninstalled the soundcard drivers beforehand and reinstalled them after doing the fresh CS6 installation, with lots of reboots along the way.) However, this older version of CS6 still refuses to load the ASIO driver for my soundcard. I'm wondering if CS6 can't find a 32-bit ASIO driver for the sound card. And yet... CS6 can SEE the ASIO driver for the soundcard because it appears in the list of available ASIO devices in the Device Class drop-down list. Surely, it wouldn't even see the driver if it was only available in 64 bits? Second, as far as I can see, the driver installation folders do include both 32-bit and 64-bit versions of the ASIO drivers and so the 32-bit driver does appear to be available to CS6, though I can't be certain about this. Any thoughts? ... View more