Set all clip levels to 0dB in a Multitrack project?

I'm using Audition CC2014, mostly to eq and finalise audio for Premiere Pro projects... When I bring all my audio into a Multitrack project in Audition I would love to be able to set all the clips and tracks to 0dB, getting rid of any rough keyframes and levels adjustments I did in Premiere (for the rough cuts)... Is there a way to do this?
Thanks for any help.

Yes, there is a way: simply open each clip in waveform view and choose to Normalise to 0dB! Not sure whether you can, as it were, "Batch Normalise" a group of files?
BUT, assuming you actually mean you are working in Multitrack view (which implies a number of audio clips on separate tracks but perhaps "playing simultaneously"), any balancing you have done to differentiate those clips (as per your comment re "keyframes and levels adjustment") will be lost and so will need to be redone.
Or have I misunderstood what you are asking?
Also, remember any changes made to your files in Waveform view are "destructive" - once the file is saved the "Undos" are lost. In Multitrack view the changes are not applied directly to the actual audio file; when you Export/Mixdown a "new" file is created but I don't think that you can "normalise" a file in that view.

Similar Messages

Clips in subtimeline not included in multitrack project

I have a movie that includes several sub-timelines throughout the projects. When I Send to Soundtrack Pro Multi-track Project, I get empty space whereever there is a sub-timeline.
How can I get all my audio clips into a single multitrack projects so that I can adjust and finetune my entire mix?

Yes, you can do those things by creating the quicktime movie and importing it into a new iMovie project.
The movie will be all one giant clip, so you will have to do 'split video clip at playhead' to be able to add titles and transitions. If you anticipate having LOTS of transitions, you might want to do as many as you can before exporting the movie. Otherwise, you will be splitting the qt movie into the same clips you already are working with.
Also, if you have already added audio clips, they will not be on separate tracks from the video as they were on the original. The audio will be within the video. The only thing that is difficult, if not impossible, to do is to redo titles that you already did in the first movie.
However, you can do some creative editing if you need to, as long as you still have the original footage. I sometimes will drag a video clip from my clips pane that has a part I think I might need in my qt iMovie to the desktop. If I need part of it, I can always drag it into my qt iMovie.
And, yes you can insert more clips.

I no longer have sound when playing my clips through adobe premiere elements 12. How to I correct this problem? I have checked all audio levels and there is no mute on etc. I have updated to 12.1. Still no sound.

I no longer have sound when playing my clips through adobe premiere elements 12. How to I correct this problem? I have checked all audio levels and there is no mute on etc. I updated to 12.1, but still no sound in any clips. Even not on old files which used to work.

bfun
What computer operating system is your Premiere Elements 12/12.1 running on? Can we assume that this audio plays back OK
on the same computer when you are using a computer player independent of Premiere Elements?
What are the properties of these clips that worked before but do not know with regard to sound
For now, I will assume that you are working on Windows 7, 8, or 8.1 64 bit.
Have you checked the Edit Menu/Preferences/Audio Hardware ASIO settings? Do you have any 3rd party audio devices incorporated in your computer environment?
Please delete the Adobe Premiere Elements Prefs file and, if that does not work, then the whole 12.0 Folder in which the Adobe Premiere Elements Prefs file exists. The Windows 7, 8, or 8.1 64 bit path is
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
12.0
and, in the 12.0 Folder, is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then delete the whole 12.0 Folder in which the Adobe Premiere Elements Prefs file exists. Make sure that you are working with Folder Option "Show Hidden Files, Folders, and Drives" active so that you can see the complete path cited.
Do you have installation files or installation disc with the purchased serial number in case we need to resort to uninstall/reinstall?
We will be watching for your follow up.
ATR

When I set all the tracks in the latest Garageband to the same volume levels and save, when I open the file again they've changed back to a previous setting?

I'm trying to mix a recording in the latest 2014 version of Garageband, but when I set all the tracks in the latest Garageband to the same volume levels and save, when I open the file again they've changed back to a previous setting? Does anyone know why it changes even after saving the file?
Below is my iMac settings.

Do you have a back up?
If not you're into using file recovery software like File Salvage - you can download a free trial and it will scan the disk for you and tell you with might be recoverable. Actual recovery will require that you purchase the app. There may be many files with the same or similar names. Always recover the largest file size.
There are other such apps. Search on Macupdate or the App Store

How do you set the zoom level to Inherit Zoom for all bookmarks in a pdf?

How do you set the zoom level to Inherit Zoom for all bookmarks in a pdf?

beatngu13
I made an account just to "like" your comment and say that you are a god among men.
I've been searching for hours about how to make the zoom level persistent throughout following links in various PDF's I have, and most sources were saying to just buy acrobat pro and edit the bookmarks manually with it.
I saw that it was possible to write an application to change the property, and considered doing it after the only pre-existing custom application I could find was asking for $50.
Thanks to you, I no longer have to worry about re-zooming every time I click a bookmark, and I'm not out $50 or the time it would take to code an app myself!
From the bottom of my heart, thank you!

Setting in Query Designer to close all the levels in hierarchy

Hi,
I got a hierarchy with upto 8 Levels.
In Query Designer i had a Selection Restrictions on hierarchy,I selected few nodes (each will have upto 7 level).
When i execute the report the first node is expanding upto the Level 7 and other nodes are stay close...
I checked and tried all the setting Expand to level 0....etc
Its not working.
How can i achive
When the user executes the report...data will be dispayed and all the restricted nodes will be displayed as closed...and option to the user to expand.
Thanks

Hi SDBI,
Thanks for the Update...
Go to RSH1 transaction. Go to your Hierarchy. Choose your hierarchy in change mode press Hierarchy attributes buttion. Enter 00 as drilldown start level in the new dialog appearing when your press Hierarchy attributes button.
It worked..but not for 00....it worked for '01'.
Could you please explain me in bit detail what is the functionality of that setting...
Thanks in advance

I have to make a light modification on EQ setting an all clips

I assembled about 40 min. of a film, and I put en EQ audio (from Logic tab) an all clips (same setting for all clips). Now, playing back the film, I realized that I have to make a light modification on EQ setting (an all clips). Which is the quickest way to do it?
Thanks in advance

The other way, and what I now do all the time, is to add the audio clips to a "Role" (eg "Interview Speech") and then export the audio as a separate file (using the Export features).
Then add the EQ/effect in Logic or even import the clip straight back in and *then* put the effects on it in FCPX and disable all the original clips (using the Role features again, this is easy).
If timing changes, you need to re-export/import but I find this less troublesome than using compound clips just for audio.
The problem with using compound clips just for adding audio effects is that it can degrade the editing experience or the quality of your project (not the output quality, the usability of your project). I can no longer line up other clips against the audio clips or connect them individually (because they're hidden in their own compound clip).
And the option to temporarily undo the audio compound clip, basically doesn't exist because then you lose your effects and you'd have to "find/remember" all the clips you needed grouped again.
Word has it, that this problem will be solved by FCPX adding a "mixer". Maybe you'd still use "Roles" but the mixer will allow you to add effects to "Roles". Something like that, anyway.

Setting uniform volume level

Is there a way in Pr Pro to set the volume of all clips to the same level aside from directly adjusting each clip's volume?

You are correct, normalize sets the peak level of the clip to whatever value you select.
This does not necessarily do what you want - a clip which is mostly fairly low level audio, with a single loud burst (eg a shot of a peaceful lake where a Mallard suddenly lets rip close to the camera) will not fit with other normalized clips taken at the same lake where there is just the usual background chatter of the waterfowl.
In the first clip the duck's shout will be set at say -6 dB, whilst the background may be at -20 dB. In the other clips, the background will be at -6 dB as this is effectively the peak level.
What I usually do is use Audition to set the background level of each clip to the same value, and for the occasional overloud burst, selectively apply a cut in level to keep the peak within bounds.
Beware also of the "pumping" effect that you get when automatic gain control is on in the camera - after Donald's outburst there will be a clearly audible short term drop in audio level.

How to apply an effect to multiple/all clips

I'm sure I'm missing something elementary here, but I can't find a way to apply an effect to multiple clips at once in PE7. Specifically I'd like to apply the Auto Levels adjustment effect across all clips in my project (makes sense because they were all recorded at the same time), but at best can onely copy the effect from one clip or section on the timeline to another; one at a time. When working with a project that has upward of 100 scenes, copy and pasting to each individual clip seems like a lot of tedious work that should be easier.
Does anyone have any suggestions or information that could point me in the right direction?
Thanks!
Dale

Dale,
You have discovered one of the little "gottchas" with Copy/Paste Attributes - it does it for all.
I do not know of a way to eliminate Effects globally, i.e. multiple Clips in this case. Unless there's a neat workaround, or secret switch, I think it will be by hand. That is the way it is in PrPro. Don't know about PE, but In PrPro one can select some of the Effects to Copy/Paste Attributes (for many Effects, but not all).
Side note: Render your Clips and watch them closely with Auto Levels. I find that it "pulses" and that manually setting Levels (not the Auto one) is better.
Good luck,
Hunt

CS4 NOT capable of sharp displays at all zoom levels

I must have been asleep, until now, and missed the significance and importance of what follows.
In post #11 here:
http://forums.adobe.com/thread/375478?tstart=30
on 19 March 2009 Chris Cox (Adobe Photoshop Engineer - his title on the old forums) said this, in a discussion regarding sharpness in CS4:
"You can't have perfectly sharp images at all zoom levels.". Unfortunately, my experience with CS4 since its release late last year has repeatedly confirmed the correctness of this statement.
What makes this statement so disturbing is that it contradicts an overwhelming amount of the pre- and post-release promotional advertising of CS4 by Adobe, to the effect that the OpenGL features of CS4 enable it to display sharp images at all zoom levels and magnifications. What is surprising is that this assertion has been picked up and regurgitated in commentary by other, sometimes highly experienced, Ps users (some unconnected with, but also some directly connected with, Adobe). I relied upon these representations when making my decision to purchase the upgrade from CS3 to CS4. In fact, they were my principal reason for upgrading. Without them, I would not have upgraded. Set out in numbered paragraphs 1 to 6 below is a small selection only of this material.
1. Watch the video "Photoshop CS4: Buy or Die" by Deke McClelland (inducted into the Photoshop Hall of Fame, according to his bio) on the new features of CS4 in a pre-release commentary to be found here:
http://fyi.oreilly.com/2008/09/new-dekepod-deke-mcclelland-on.html
Notice what he says about zooming with Open GL: "every zoom level is a bicubically rendered thing of beauty". That, when viewed with the zooming demonstrated, can only be meant to convey that your image will be "sharp" at all zoom levels. I'm sure he believes it too - Deke is someone who is noted for his outspoken criticism of Photoshop when he believes it to be deserved. It would seem that he must not have experimented and tested to the extent that others posting in this forum have done so.
2. Here's another Adobe TV video from Deke McClelland:
http://tv.adobe.com/#vi+f1584v1021
In this video Deke discusses the "super smooth" and "very smooth" zooming of CS4 at all zoom levels achieved through the use of OpenGL. From the context of his comments about zooming to odd zoom levels like 33.33% and 52.37%, it is beyond doubt that Deke's use of the word "smooth" is intended to convey "sharp". At the conclusion of his discussion on this topic he says that, as a result of CS4's "smooth and accurate" as distinct from "choppy" (quoted words are his) rendering of images at odd zoom levels (example given in this instance was 46.67%), "I can actually soft proof sharpening as it will render for my output device".
3. In an article by Philip Andrews at photoshopsupport.com entitled 'What's New In Adobe Photoshop CS4 - Photoshop 11 - An overview of all the new features in Adobe Photoshop CS4',
see: http://www.photoshopsupport.com/photoshop-cs4/what-is-new-in-photoshop-cs4.html
under the heading 'GPU powered display', this text appears :
"Smooth Accurate Pan and Zoom functions – Unlike previous versions where certain magnification values produced less than optimal previews on screen, CS4 always presents your image crisply and accurately. Yes, this is irrespective of zoom and rotation settings and available right up to pixel level (3200%)." Now, it would be a brave soul indeed who might try to argue that "crisply and accurately" means anything other than "sharply", and certainly, not even by the wildest stretch of the imagination, could it be taken to mean "slightly blurry but smooth" - to use the further words of Chris Cox also contained in his post #11 mentioned in the initial link at the beginning of this post.
4. PhotoshopCAFE has several videos on the new features of CS4. One by Chris Smith here:
http://www.photoshopcafe.com/cs4/vid/CS4Video.htm
is entitled 'GPU Viewing Options". In it, Chris says, whilst demonstrating zooming an image of a guitar: "as I zoom out or as I zoom in, notice that it looks sharp at any resolution. It used to be in Photoshop we had to be at 25, 50 , 75 (he's wrong about 75) % to get the nice sharp preview but now it shows in every magnification".
5. Here's another statement about the sharpness of CS4 at odd zoom levels like 33.33%, but inferentially at all zoom levels. It occurs in an Adobe TV video (under the heading 'GPU Accererated Features', starting at 2 min 30 secs into the video) and is made by no less than Bryan O'Neil Hughes, Product Manager on the Photoshop team, found here:
http://tv.adobe.com/#vi+f1556v1686
After demonstrating zooming in and out of a bunch of documents on a desk, commenting about the type in the documents which is readily visible, he says : "everything is nice and clean and sharp".
6. Finally, consider the Ps CS4 pdf Help file itself (both the original released with 11.0 and the revised edition dated 30 March 2009 following upon the release of the 11.0.1 update). Under the heading 'Smoother panning and zooming' on page 5, it has this to say: "Gracefully navigate to any area of an image with smoother panning and zooming. Maintain clarity as you zoom to invididual pixels, and easily edit at the highest magnification with the new Pixel Grid." The use of the word "clarity" can only mean "sharpness" in this context. Additionally, the link towards the top of page 28 of the Help file (topic of Rotate View Tool) takes you to yet another video by Deke McClelland. Remember, this is Adobe itself telling you to watch this video. 5 minutes and 40 seconds into the video he says: "Every single zoom level is fluid and smooth, meaning that Photoshop displays all pixels properly in all views which ensures more accurate still, video and 3D images as well as better painting, text and shapes.". Not much doubt that he is here talking about sharpness.
So, as you may have concluded, I'm pretty upset about this situation. I have participated in another forum (which raised the lack of sharp rendering by CS4 on several occasions) trying to work with Adobe to overcome what I initially thought may have been only a problem with my aging (but nevertheless, just-complying) system or outdated drivers. But that exercise did not result in any sharpness issue fix, nor was one incorporated in the 11.0.1 update to CS4. And in this forum, I now read that quite a few, perhaps even many, others, with systems whose specifications not only match but well and truly exceed the minimum system requirements for OpenGL compliance with CS4, also continue to experience sharpness problems. It's no surprise, of course, given the admission we now have from Chris Cox. It seems that CS4 is incapable of producing the sharp displays at all zoom levels it was alleged to achieve. Furthermore, it is now abundently clear that, with respect to the issue of sharpness, it is irrelevant whether or not your system meets the advertised minimum OpenGL specifications required for CS4, because the OpenGl features of CS4 simply cannot produce the goods. What makes this state of affairs even more galling is that, unlike CS3 and earlier releases of Photoshop, CS4 with OpenGL activated does not even always produce sharp displays at 12.5, 25, and 50% magnifications (as one example only, see posts #4 and #13 in the initial link at the beginning of this post). It is no answer to say, and it is ridiculous to suggest (as some have done in this forum), that one should turn off OpenGL if one wishes to emulate the sharp display of images formerly available.

Thanks, Andrew, for bringing this up. I have seen comments and questions in different forums from several CS4 users who have had doubts about the new OpenGL display functionality and how it affects apparent sharpness at different zoom levels. I think part of the interest/doubt has been created by the over-the-top hype that has been associated with the feature as you documented very well.
I have been curious about it myself and honestly I didn't notice it at first but then as I read people's comments I looked a little closer and there is indeed a difference at different zoom levels. After studying the situation a bit, here are some preliminary conclusions (and I look forward to comments and corrections):
The "old", non-OpenGL way of display was using nearest-neighbor interpolation.
I am using observation to come to this conclusion, using comparison of images down-sampled with nearest-neighbor and comparing them to what I see in PS with OpenGL turned off. They look similar, if not the same.
The "new", OpenGL way of display is using bilinear interpolation.
I am using observation as well as some inference: The PS OpenGL preferences have an option to "force" bilinear interpolation because some graphics cards need to be told to force the use of shaders to perform the required interpolation. This infers that the interpolation is bilinear.
Nothing is truly "accurate" at less than 100%, regardless of the interpolation used.
Thomas Knoll, Jeff Schewe, and others have been telling us that for a long time, particularly as a reason for not showing sharpening at less than 100% in ACR (We still want it though ). It is just the nature of the beast of re-sampling an image from discrete pixels to discrete pixels.
The "rule of thumb" commonly used for the "old", non-OpenGL display method to use 25%, 50%, etc. for "accurate" display was not really accurate.
Those zoom percentages just turned out to be less bad than some of the other percentages and provided a way to achieve a sort of standard for comparing things. Example: "If my output sharpening looks like "this" at 50% then it will look close to "that" in the actual print.
The "new", OpenGL interpolation is certainly different and arguably better than the old interpolation method.
This is mainly because the more sophisticated interpolation prevents drop-outs that occurred from the old nearest-neighbor approach (see my grid samples below). With nearest-neighbor, certain details that fall into "bad" areas of the interpolated image will be eliminated. With bilinear, those details will still be visible but with less sharpness than other details. Accuracy with both the nearest-neighbor and bilinear interpolations will vary with zoom percentage and where the detail falls within the image.
Since the OpenGL interpolation is different, users may need to develop new "rules of thumb" for zoom percentages they prefer when making certain judgements about an image (sharpening, for example).
Note that anything below 100% is still not "accurate", just as it was not "accurate" before.
As Andrew pointed out, the hype around the new OpenGL bilinear interpolation went a little overboard in a few cases and has probably led to some incorrect expectations from users.
The reason that some users seem to notice the sharpness differences with different zooms using OpenGL and some do not (or are not bothered by it) I believe is related to the different ways that users are accustomed to using Photoshop and the resolution/size of their monitors.
Those people who regularly work with images with fine details (pine tree needles, for example) and/or fine/extreme levels of sharpening are going to see the differences more than people who don't. To some extent, I see this similar to people who battle with moire: they are going to have this problem more frequently if they regularly shoot screen doors and people in fine-lined shirts. Resolution of the monitor used may also be a factor. The size of the monitor in itself is not a factor directly but it may influence how the user uses the zoom and that may in turn have an impact on whether they notice the difference in sharpness or not. CRT vs LCD may also play a role in noticeability.
The notion that the new OpenGL/bilinear interpolation is sharp except at integer zoom percentages is incorrect.
I mention this because I have seen at last one thread implying this and an Adobe employee participated who seemed to back it up. I do not believe this is correct. There are some integer zoom percentages that will appear less sharp than others. It doesn't have anything to do with integers - it has to do with the interaction of the interpolation, the size of the detail, and how that detail falls into the new, interpolated pixel grid.
Overall conclusion:
The bilinear interpolation used in the new OpenGL display is better than the old, non-OpenGL nearest-neighbor method but it is not perfect. I suspect actually, that there is no "perfect" way of "accurately" producing discrete pixels at less than 100%. It is just a matter of using more sophisticated interpolation techniques as computer processing power allows and adapting higher-resolution displays as that technology allows. When I think about it, that appears to be just what Adobe is doing.
Some sample comparisons:
I am attaching some sample comparisons of nearest-neighbor and bilinear interpolation. One is of a simple grid made up of 1 pixel wide lines. The other is of an image of a squirrel. You might find them interesting. In particular, check out the following:
Make sure you are viewing the Jpegs at 100%, otherwise you are applying interpolation onto interpolation.
Notice how in the grid, a 50% down-sample using nearest-neighbor produces no grid at all!
Notice how the 66.67% drops out some lines altogether in the nearest-neighbor version and these same lines appear less sharp than others in the bilinear version.
Notice how nearest-neighbor favors sharp edges. It isn't accurate but it's sharp.
On the squirrel image, note how the image is generally more consistent between zooms for the bilinear versions. There are differences in sharpness though at different zoom percentages for bilinear, though. I just didn't include enough samples to show that clearly here. You can see this yourself by comparing results of zooms a few percentages apart.
Well, I hope that was somewhat helpful. Comments and corrections are welcomed.

Is there a way to adjust the volume on all clips so they all have the same volume?

I'm making a highlight film of my two children, and wonder if there is a way to make all clips have the same volume. I know I can adjust the individual clips decibel niveau, but ven though I adjust them to the same level i.e -6 decibel, the clips volume are not the same. Any suggestion, or do I have to adjust each clip with different decibels niveaus and try to make the volume the same, like one clip can have -6 decibel, one light have 3 decibel and so on in order for the volume to be Aamodt the same.

On the Time Line you can copy the clip (Command-c) that has the levels you want. Select the other clips and hit Shift+Command-V to paste effects. Check the Audio attributes.
Russ

Setting minimum order level in BC?

Is there an easy way to set a minimum total order level in BC and enforce it by not allowing Check Out at lower $ amounts?
I've tried setting all of my shipping options to a $150 minimum level and then setting the shipping validation in the buy button to "true".
The shipping options don't appear unless the cart has $150 in it but the user can still proceed to the Registration Buy page at any dollar level with zero shipping by hitting Checkout.
I think the system must be recognizing $0.00 as a "valid" shipping amount.
Please help.

Hey techstoryteller,
At this stage it is only possible to set a minimum and maximum quantity of a particular product via eCommerce > [select a product].
For setting a minimum for an order, it would be possible through JavaScript to implement a script that could check the value of the {tag_invoicetotal} tag and if less than 150, will hide the checkout button using CSS. I don't have any JavaScript samples available, however I will leave this discussion open in order for possible suggestions from our community.
Cheers.

How can I check and change the system set events trace level?

Dear all:
How can I check the system set events trace level? I don't want the alert_log so big.
Regards
Terry

Hi Terry;
Please check :
How to determine which system events are currently being set? [ID 845043.1]
How To List All The Named Events Set For A Database [ID 436036.1]
How to set EVENTS in the SPFILE [ID 160178.1]
Also check:
http://www.dba-oracle.com/t_grid_rac_events_in_Oracle.htm
http://www.akadia.com/services/ora_events.html
Hope it helps
Regard
Helios

JS that applies all clipping paths at once?

Hello,
I found the thread that contains the Applescript for this, but would love to have a Javascript that works the same. Anyone have or know of one for ID CS5 that will apply all clipping paths for a group of objects at once?
Thanks in advance, as always
Andy

So it's all Photoshop paths? Yes, it ought to work. Perhaps you also need to specify which path ... Try with this line added:
app.selection[i].images[0].clippingPath.appliedPathName = app.selection[i].images[0].clippingPath.photoshopPathNames[0];
inside the try { .. } catch block. This ought to set the clipping path to the very first one in the file.
It's important to do operations such as these inside a try .. catch block, because this construction shields you from errors. Without the try .. catch, the script would issue an error for the very first image it encounters that has zero paths (and thus "the first", which is numbered #0, is not valid) and then stop with the error alert. Now it will still signal the error but the 'error handler' (the second curly-bracketed part) ensures it does nothing with that information, and so it will ignore the error and continue with the next image.
And yes, a Javascript needs to be saved as ".jsx" to work. Otherwise InDesign doesn't recognize it as a valid script.

One set of clips won't sync when trying to create a Multicam clip

I am trying to create a multicam clip using one long audio track, several clips from one camera and several clips from another camera. All three have audio recorded from the same shoot. One camera angle successfully synchronises with the audio track, placing the clips in the correct positions and leaving blank spaces where I don't have a clip. The other set of clips do not sync. It puts them in order by not synchronised. I have named camera angles and camera in the meta fields. Can anyone help? The camera which seems to sync ok was a canon XA10 the camera which doesn't is a canon 60D. The 60D took its audio teach from the linear PCM recorder I used for the Audio track. (It's still a little noisy in case anyone wants to know why I'm still using the PCM track). Can anyone help? I tried to call apple but seemingly they won't help unless I get an error message.

You could probably generate the content of the end file
separately, before including it in the final file to be accessed by
the user.
You could do this using CFSAVECONTENT
<cfquery name="getprinthtml" datasource="#dsn#">
SELECT abstractDirectory
FROM Abstract_tbl
WHERE (Abstract_ID IN (#url.abslist#))
</cfquery>
<cfsavecontent variable="theBody">
<cfoutput query="getprinthtml">
<cfinclude
template="/uploads/#getprinthtml.abstractDirectory#/#getprinthtml.abstractDirectory#_prin t.html">
<hr>
</cfoutput>
</cfsavecontent>
then use
theBody as a variable containing the entire contents at one
time when you generate the final Word doc so it does not have to
run any looping at that time.
Other than that, is there any chance the query is really only
picking up one row based on the cirteria ?

Set all clip levels to 0dB in a Multitrack project?

Similar Messages

Maybe you are looking for