Quantize problem!

Hi,
I hope you people can help me with this problem.
I can´t get Quantize to work on my Logic Pro 8. When I create a new project it gets Offline or off automaticly. I can´t get anything in the right tempo.
Please help meeeee!
Problem number 2: Logic crashes when I timstretch files. What´s the problem?
I have the latest OS X and Audiophile USB.
Regards, Jacob Czitrom, Sweden.

Expecting Logic to work the same way Cubase does, is going to prove to be an exercise in frustration. Logic is a different program, so it will help the cause to spend time with the manual, and learn how quantization works in Logic, not the way you expect it to work from working in Cubase.
That being said, there are multiple ways of working with quantization in Logic. When a MIDI track or Audio Instrument track is selected (record ready), there is a parameter box up in the left hand corner. You can set quantization values here. The thing to remember (or learn in this case), is this value is affecting only the MIDI region selected, not the entire track.
If you would prefer to have Logic Quantize on input, place the track into record (but don't hit play yet), and set the quantize value. Now, when you do record, all MIDI events will be quantized on input.
You could also program everything unquantized, then select all the regions on the track, and select the quantize value. Or better still, open the Matrix editor, select all the MIDI events, and apply the quantize value there.
If, after a whole track has been quantized, you can still select individual noes, and unquantize them, if you so desire.
I'm sure others here have some other methods that work well...

Similar Messages

Digital Performer or Logic?

We have an old version of Performer (OS9, Pre-Digital Performer). The old Mac died, we'll be getting a new one and need to buy either Digital Performer or Logic Pro/Express(one of them). Does anyone have any comments about the pros / cons comparing these programs? Thanks for helping us upgrade.

Which program you get, may depend on what you need your software to do. I use both programs and like them both for different applications
Audio Recording: Both record audio and do a fine job. Logic is just a bit less of a cpu hog, meaning you may be able to have a couple more tracks in Logic over DP
Virtual Instruments: Logic wins hands down. I don't care for DP's VI's at all and think they are unusable. If you plan on using VI's, Logic has all you might need. If you get DP you will have to spend a few thousand more to get the kind of instruments that come with Logic
Plug-in's: Both have them, Logic has many more and most are real good. DP has a few good ones. Logic has a tons of presets to give you a starting point. DP has a few.
Channel strip settings: Logic has a ton of them. DP has none, nor the ability to save channel strip settings.
Scoring to film. I have never tried it, but I have a couple of friends that write for TV shows and have won awards for their work, and they work in DP. But then there are a few who contribute to this forum and do the same in Logic.
Midi recording and editing: Both do it and have sophisticated midi editing abilities. I prefer DP over Logic for midi editing. For me it is much more intuitive and easier to work with. Even though I prefer Logic's GUI I can build a midi song in DP much faster.
Are you using outboard synths? DP all the way! Logics way of addressing outboard gear in outdated, non intuitive, stupid and a total pain in the butt. Logic won't even fully utilize features of the Mac's Audio Midi setup. DP uses .midnam (midi name) and .midev (midi device) files stored in the Mac's AMS which are also easy to edit, to call up bank and patch names on your synths. In logic you have to manually set it up in the environment (took me about a week) and then save it as a template. if you call up another template then you have to drag the environment from the synth template because logic's environment import function is broken
Midi files. DP all the way. if you plan on importing and exporting standard midi files get DP, Logic's import and export functions for SMF's are very buggy and unreliable. Also when I import SMF into logic I get many inconsistencies, with notes not playing back properly. Exporting midi is a real nightmare. missing notes and quantization problems. DP is rock solid. never a problem importing or exporting, unless of course you import something created in Logic.
Live Performance. DP, hands down. The ability to save set lists is big for me. Logic cannot do it. virtual racks of VI's that all songs in the list work off of, so there is no load time. You can set it to auto play though the list or just call up the next and wait for you to start it.
So what do you need?
If you are a song writer and looking for a great and economical way to get your songs recorded, I think Logic would be best way to go. As a creative tool you can't beat it. It comes with everything you need right out of the box. Plus let's not forget all those great apple loops to get those creative juices flowing. DP will end up costing a lot more to get what comes in Logic
If you strictly do midi production and live performance get DP
If you can afford it, get both
my .02
Don

The problems with Logic (as I see them)

Hello Everyone,
Please keep in mind that I am writing this with the intention of expressing my frustrations, and what I feel would make Logic a better program. I realize not everyone will agree with the importance of what I say, but I am a firm believer of HAVING THE OPTIONS. Let the users choose what works for them and how they can best accomplish the tasks that they need to with their individual workflow.
That being said, here is my list of Logic's faults and why I often call Logic "Illogic".
General:
* Logic should have a feature to automatically save your song every X number of minutes. Final Cut Pro does this, why doesn't Logic? It should prompt you "Logic can automatically save your project if you save it" (assuming the current file is 'autoload') to remind users that they should create a project name and save their work.
* There should be a preference option for all windows to open as 'float'. Once upon a time holding option while double clicking parts would open them as a float (though having to hold down option every time in my opinion is an inconvenience, because I personally ALWAYS want my windows open as a float), however.. now in 7.2 that does not seem to work anymore. So, theoretically after you set your prefence to 'always float', then the when you hold option or control and click on a particular window, it will bring that window to the foreground...
* The loop region at the top of the screen is larger than the time-line ruler tab. This is the #1 annoying thing about logic. so many times, I click on an area of the ruler tab to start playing at a specific section.. and somehow I ACCIDENTALLY click on the loop area... If I could ask for ANYTHING it would be that there is an option to disable LOOPING turning on and off from clicking up there. My 2nd request would be that the ruler tab be re-sizeable so that it can be larger than the loop area. This is especially the case for the matrix window where it default opens up to a sizing where the actual time line is so tiny, and the loop region is HUGE.... Every time I open a matrix window I have to resize this and again the loop area is 2x as big as the timeline area, so I end up wasting screen space just to avoid the annoying loop feature being trued on. My suggestion is, require that the loop button on the transport be the only way to turn on the loop feature (other than key commands), and only when it's turned on can loop points to be set. Why is the loop area so big anyway?!?!
* Logic should offer a TALK BACK MIC button which will utilize the built-in apple microphone or iSight microphone and allow that to be sent to the audio interface. This would be an extremely useful feature for studio recording setups.
* Starting logic takes approximately 5 minutes for me. It says "scanning exs24 instruments" for the majority of the time, and I admit my sample library is huge. however, my sample library has not changed in over a year. Why does logic have to continuously scan it??? Can it not make a reference of how many files, compare and if its larger-- then scan???
Song Loading:
* When audio files are not found during loading a song, it asks you the first time what you want to do "search", "manual", and "skip"... if you click "skip", and then it finds another missing file, it no longer presents you with the "SKIP" option.. but forces you to either search or skip all.. Let's say you have a project that used 5 audio files that are all missing because you had them on a different hard drive, but have copied the data somewhere else. The first two files it asks for you don't need.. but you know where the 3rd file is.. So your plan is to skip the first two files and then click manually for the 3rd.. but oh.. YOU CAN'T DO THAT! You have to find your first 2 files if you want to even have the option to locate your 3rd file... Unless you are planning to locate the files within the audio window-- but still, Logic should not be so unfriendly.
Further, If you choose "manual", and what you're looking for isn't where you thought it was-- You realize you actually want to search for it.. So you click cancel and guess what.. It assumes you want to skip it, and so you either have to reload your project again, or deal with this in the audio window. Bottom line is this window should always have "Search", "Manual", "Skip", and "Skip All".
* When you open another project, Logic DUMPS all of the audio instrument data in memory. This is one of the worst things about logic. If you are working between multiple files-- such as when scoring a film, and you are using different files for different cues, then this becomes a complete nightmare and a waste of your time. Logic should be assessing "What instruments are in common between these two projects"... And utilizing all audio instruments to the best of the machine's memory capacity. There is no reason for Logic to behave like this.. I've had to revert back to previous versions of the same song because some data was different, and I am just trying to visually compare various settings one from the other.. Just clicking from one project's window to the other requires me to have to wait 3-4 minutes while Logic loads all these audio instruments (WHICH ARE IDENTICAL IN BOTH PROJECTS BY THE WAY!!!).. This is just incredibly dumb, and creatively stifling.
* BUG * -- Mind you, if you have two projects open, and you close one.. Logic begins loading all the audio instruments of the remaining project.. If you close that project as it's loading audio instruments, Logic will crash.
Matrix Stuff:
* BUG * If you have a part with lots of notes, and you begin to make a selection and scroll horizontally through all the content until then entire part is covered in the selection... After you release the mouse button and make this selection, quite often many random notes are unselected. This can be demonstrated by watching the following quicktime move:
http://www.collinatorstudios.com/video/logicbug.mov
* When you select a single note in the matrix window, it sounds.. This is a GREAT feature... However, when you make a selection of multiple of notes, they all sound at the same time.. This is just plain dumb. It once blew up my speakers... There is NO reason why a multiple selection would need to sound.. It's just dumb.. bad for your speakers, bad for your ears. The rule should be, if selection box = yes, then sound = no... else, sound = yes.
* When viewing the matrix window while recording, all note events disappear until after recording stops. This is highly annoying (and illogical) as it causes confusion if you are relying on watching the note events in that part to know where you are supposed to come in.
* The grid cannot be set to divisions other than 2 or 3. Musicians use 5 and 7!!! And also, can logic please offer an option to display the grid as NOTE symbols... It is much more musician friendly to see a 16th note with a 3 over it than "24". 24 means nothing to me as a musician.
* Quantizing should allow custom input for tuplets.. So that users can quantize odd figures such as 13:4 for example.
* If you move the song locator to a specific time location in the arrange window, and then double click a part to open it in the matrix window, the window is not opened to the locator's position. Thus causing annoyance and confusion as far as what the user is even looking at.
* During horizontal scrolling of the window, the locator temporarily disappears, making it difficult to find where the locator is-- which usually is a marker for us to know what we are trying to find-- ESPECIALLY WHEN YOU OPEN A WINDOW AND IT'S NOT EVEN DISPLAYING THE SONG LOCATOR'S POSITION!!!
* If you have two parts on the same arrange track, adjacent to each other and you enter the matrix window of the first part.. (assuming the link/chain icon is lit) When you scroll to the end of the note data, logic automatically takes you to the next part... The problem with this as it is, is that it does not take you to the FIRST note event of the text part, but rather continues to align the song locater with where ever it previously was (so you end up viewing somewhere further down in the next part).. To clarify, say you have a part what begins at MM-7 and ends at MM-14, the 2nd part begins at MM-15 and ends at MM-22.. If you begin scrolling the song locator past measure 15, then suddenly you see measure 22. When you really should be seeing measure 15. This is confusing and weird.
* Every time you enter the matrix window of a part, the chain/link button is on. For me, this is incredibly annoying. There should be a way to set this so that the button's default is OFF...
* When you move the mouse around the matrix window, whatever pitch corresponds to the vertical location of the mouse--- that particular key of the piano keyboard on the left side of the window should highlight so you could clearly see what note you are hovering over.. Logic tries to help with this by offering things like contrast options for C D E, but this clearly would be much more helpful.
* With the velocity tool you can (MOST OFTEN ON ACCIDENT) double click on empty space in the window and cause all note events in all parts to appear on the screen-- Yet once you do this, you can't double click on a particular part's note to only display that part again. You have to switch to the arrow tool to do this. This is inconsistent and ILLOGICAL...
ON A SIDE NOTE: PLEASE ENABLE A FUNCTION TO DISABLE THIS "ALL NOTES OF ALL PARTS APPEAR" when double clicking on empty space feature! I want NOTHING to happen when I double click within the matrix window... Make it a button within the window or just an option in the drop down menu only. * BY THE WAY * When you DO double click the background of the matrix window and multiple parts appear.. If you move notes of one part to match it up with other, it is incredibly slow. there is a 1-2 second pause each time you move a note move.. My g5 fan goes on each time I do this.. I'm sorry, there shouldn't be anything too CPU intensive to accomplish this simple task!!! I am only viewing 2 parts at the same time and it's slowing down my cpu...
* Occasionally when I adjust note lengths, I accidentally double click on an actual note.. This opens the event list editor, and there is an intermittent bug where this note sounds-- and for some reason when the event list opens, the note sounds on top of itself a million times, so the result is a super loud flanged note which again, almost blows up my speakers and hurts my ears... PERSONALLY, I would like an option that DISABLES the note event list from opening by double clicking. Preferences currently has "double clicking a midi region opens: <selectable>"--- why not also have "double clicking a NOTE in matrix window does: <selectable>"-- and please allow "DO NOTHING" to be one of the options.
* Why does the finger tool only change the end position of the note event??? Should this not be replaced with the bracket tool which appears automatically when using the arrow tool on closely zoomed in notes? This finger tool seems like an outdated old logic feature which has been replaced and improved upon. What would be nice is to have this bracket tool where we can be assured we are altering note start and end positions without moving things.
* In the hyper-draw >> note velocity section--- This is highly annoying to work with... It's far from user friendly. first of all, to move a note's velocity position, you have to click on the "ball".. if you click on the line, it does nothing.. Because the ball is so small to begin with, quite often the user is going to miss the ball and somehow begin to "START LINE"-- Which is weird because it's activated by holding the mouse button down briefly. There really should be a "line tool" for this, because "START LINE" is too easily accidentally activated-- this is frustrating for the user. Most important though, these 'velocity markings' should be adjustable by clicking on the line as well-- not just the ball.. there should be a 2-3% area around each ball/line which logic will recognize as part of the ball/line so that it can easily be moved. I also feel that there should be some specific features for this section, such as a way to select multiple note velocities and apply a random pattern to them, or apply a logarithmic curve to the line tool. Yes, you can accomplish this stuff somewhat with the transform tool-- but this way would be more user friendly, and allow a lot more creative flow.
Event list/Tempo list:
* When one event is selected, by moving down X number, holding shift+clicking SHOULD select all events between those two points. However, the shift key for some reason acts as the OPTION key does in the finder-- (meaning it will only add one additional selection at a time).. This is highly inconsistent with the actual behavior of a Mac... Open a finder window and hold shift and click on items that are not vertically next to each other and a group is selected... Now do it in logic, and it causes GREAT frustration and annoyance. What happens if you have a million note events that you want to erase? You have to go page by page and click with shift on each one?? Or drag a selection and wait for logic to scroll you to where you want to go?????????? No thanks.
Arrange stuff:
* "REGIONAL CONTENT" (meaning the visual representation of note events) does not accurately depict the event data as note lengths cannot be visually identified. Everything shows up as a generic quarter note... My #1 suggestion is that regional content should be customizable so that you can view it in a miniature matrix data style. The biggest problem for me is that I cannot see where my notes end-- I can only see where they start, this makes it very difficult to identify what I am looking at.
* Track automation data should only be inputable by the pencil tool. I cannot mention how many times automation data has accidentally altered when using the arrow tool. The pencil tool should allow you to raise and lower the lines reflecting automation data... What is the point using the pencil tool for automation if it's only function is to create "points" yet you can also create points with the arrow tool..??? Pencil tool should act as the arrow tool does in the sense that it raises or lowers automation data.
* Recording preferences do not offer the option to automatically merge new part with existing part when a region is NOT selected. How annoying is it to have to select a part every time you want to record something just so it will be included in that original part!
* Ruler at the top of the screen should also give an option for tuplets. 5, 7, etc.
* When in record mode, if you click on the ruler to another time position, all audio instruments cut out and it takes approximately 3-4 seconds before tracks begin playing audio. This becomes very annoying if you are trying to do a pick up and want to just start 1 measure before hand.
* There should be a way to EASILY (without having to cable two tracks together in the environment) temporarily link multiple tracks together so that automation data will be duplicated. So theoretically you can link 3-4 tracks together, and by adding automation data to one, you are adding it to all 4.
* If a part is soloed, and you hit record. The part stops being soloed and you can no longer hear it. This makes it impossible to record a pick up on a soloed track unless it's locked, but it shouldn't need to be locked.
* When you are zoomed in tightly, and you are trying to align notes within two parts on different tracks (meaning using the PSEUDO NOTATION DATA that appears in the part to align), there needs to be a VERTICAL line that snaps to the note closest to the mouse cursor. When trying to do this in parts that are a far vertical distance apart, it becomes VERY difficult to eye this alignment. Logic does this with automation data.. but for some reason they left it out for actual part alignment...
* There should be a way to force the downbeat of a measure to occur at any given moment... What I mean by this, is composing for film is an absolute PAIN in Logic. Scenes, last for odd amounts of time, and Logic's reference manual claims that you can solve this by using various tempo tricks, however it is ineffective for the most part. What Logic needs is the ability where you can click on a drop down menu item within the arrange window and FORCE that where ever the song locator is, the rest of the measure is eliminated and a new measure downbeat occurs right there. This will allow you to always have new scenes on the downbeat of a measure without having to mess with your tempo and meter.
Hyper Edit Window:
* I can't even begin to comment on this... The hyper edit window is one of the worst things I have ever seen in a music/audio program. It is a horrible interface, you can't get it to do anything correctly without messing everything up. This thing needs a complete overhaul... I mean, just try to create a simple crescendo with note velocity and it will take you all night.. Try to add pitch bend data, and it adds note velocity data as well.. It's a total nightmare, and I would love to hear someone's practical application of this window.
Score Window:
* The method that the song position locator moves along with the notation is very strange. It is not at all how a person's eyes function when reading music. A much more logical approach to this would be for a transparent colored block of some type to highlight an entire measure, and each note head will glow as it sounds. The current way is so strange, it speeds up and slows down-- makes absolutely no sense, and it is more disruptive than anything.
* When the Hyper Draw > note velocity area is exposed, if you use the velocity tool to increase/decrease a particular note's volume, the data in the hyper draw window does not update in real-time as you use the velocity tool. This behavior is inconsistent with the matrix > hyper draw's note velocity section-- where as in that area, the velocity ball/lines do update in realtime.
EXS24:
* when you are in many levels of subdirectories and you are auditioning instruments, it becomes very time consuming and annoying to have to continually trace through all the subdirectory paths. There should be a feature directly under the load instrument window that takes you to the subdirectory of the current instrument.
* Seems when SONG SETTING > MIDI > "chase" is turned on... When starting sequences using audio instruments, (I am using a harp sample within the exs24), there is a latency hiccup upon starting, which is very disruptive when trying to listen to a short isolated moment in a composition. And I do want to chase note events in general-- but this present situation makes it difficult for me to work. I would suggest that you can specify tracks to exclude chasing.. Or fix the latency hiccup issue.
Thank you.
-Patrick
http://collinatorstudios.com

this is excellent patrick. can you number your points so that the thread can be discussed?
1. yes
2. ok
3. great idea
4. even better idea. you could set something up with aggreagate device i suppose but it would be better to have the feature to hand.
5. you need to look into your project manager prefs. scan the paths and the links to the audio files will be saved meaning they will load up in a fraction of the time.
6. yes this is nuts. you can skip all and sort it out with PM but then you shouldn't have to.
7. this exists already. perhaps it ought to be a default but you need to set your esx prefs to 'keep common samples in memeory when switching songs'. then it will do just as you wish it to. you can also use the au lab in the devlopers kit which will allow you to load in au units etc seperately from logic, which logic can then access. this is a good way of getting around the 4 GB memory limit with logic too.
8. ok, don't know about this bug.
9. yep happens here too.
10. doesn't worry me this one. you can turn off midi out.
11. yes this is silly.
12. well, i think this is something we can get used to. i am a musician and i am used to seeing '24'.
13. you can already set up groove templates to allow for quantizing irrational tuplets. i do it all the time. i would like to see step input for irrational tuplets though.
14. yes this is silly. the button for the KC 'content catch' is getting very worn out.
15. ok.
16. not sure i understand this one.
17. yes this drives me nuts too. i have to lock screensets to get this to stay off.
18. you can use KCs for 'go into/out of sequence' - but yeah.
19. ok
20. there are a couple of features that use old technology that cause hangs and poor performance. score is a good example of that. maybe the matrix is too. the score is being updated we assume with newer technology maybe the matrix will too.
21. there are probably better ways of adjusting velocity than using matrix or hperdraw velocity. have you tried holding control-option and click dragging a note in score?
22. as i pointed out in 20, this is an old feature. you could change things to be consistent with modern macs and annoy long term users such as myself, or leave them and let them be inconsistent to confuse newbies. i think depending on what it is we oldies could upgrade our work habits.
23. this one doesn't worry me so much.
24. good point (no pun intended).
25. well, i find the opposite - that merging new parts to objects i have accidentally selected to be annoying. perhaps more detailed prefs?
26. yep.
27. this will be down to your audio settings. you can improve this lag but it will be dependant on the capabilities of your system.
28. i don't know why this feature doesn't work in logic. it is supposed to have ti already and i just don't understand why it doesn't. maybe it will be fixed in the next upgrade.
29. agreed.
30. ok - i have other work flows for this but it would be nice.
31. i don't agree that logic is a pain to score with to film, i do it nearly everyday. but you are discribing an interesting feature which might be worth discussing more. i think you might find yourself getting alarming and unmiscal results doing this that will end up having to be sorted out the conventional way. but its a good idea.
32. oh yes.
33. yeah - this could be improved.
34. ok, well i wouldn't go about it this way, but yeah there is generally sticky spots with regards to updating of information al around logic.
25. very very good idea.
26. there are lots of problems with the chase function. very annoying. i certainly agree with this.
in general, some of these could well be done as their own threads. some of the missing functionality may exist. if you can confirm a bug then you are on stronger ground when you submit feedback. but this list is full of fantastic ideas.

Is there a way of moving/quantizing multiple audio regions at once to the nearest bar/beat/division?

Hi,
I'm having trouble finding a solution which I hope turns out to be fairly simple. Here's my problem:
I often make drum beats from audio files that looks something like this:
What I'd like to know is if there is a way to highlight say all of the snare audio regions and snap or quantize the "audio region start" to the nearest beat or division. I've been looking everywhere and I just can't seem to find a way to do it to multiple regions at once. It seems like somehting that should maybe be fairly simple. Turning "Flex" on doesn't work as that quantizes the transients as opposed to just the start of each audio region.
The reason I ask is that sometimes when zooming in fully, it turns out some of the regions are not exactly on the grid line.
I hope I made sense there and I'd appreciate any help. Many thanks in advance.

Hi
The "traditional" way to quantise audio regions is to use the quantise functionality in the Event List.
CCT

Reason Rewire - serious problem with timing / sync

Hi - here's the problem....
I rewire Reason 4.1 to Logic Pro 8.02.
I try to record a basic drum beat (played in via midi keys) into bar 1 of Logic's sequencer.
I quantize the beat and verify visually that on the very 1st beat of the bar there is a high-hat and a kick drum that should play at exactly the same time - however when I play the sequence back the high-hat is delayed for no apparent reason!! (if i am in cycle mode - after the cycle point is crosssed the kick and hi-hat ARE played together!). If i try to bounce this section the same problem is apparent. Thus making rewire really useless!! It's as if the 1st beat of the bar can only be monophonic or something!
The same thing happens if I record a chord from a Reason instrument (Thor perhaps) - the notes that should all sound in unison on the 1st beat of the bar do not play correctly.
Anyone got any ideas what could be causing this or is it another pathetic bug?

I've had a slightly different but perhaps related problem with Reason in both Logic and Digital Performer. In my case using the Redrum drum machine in Reason and the pattern sequencer in Reason, when you start playback it will make kind of a cut-off squelch kick drum sound on beat 1, then complete silence for about 2 and a half beats, then the sound of the beat will kick in mid-measure.
I haven't done a lot of testing about when and where this happens in the sequence; I work around it by programming 2 measures of silence (pattern D-8 perhaps) into the Redrum before the start of the song and starting the playback from that. It seems like even doing that if you start playback at measure 1 beat 1 it will make that kick drum squelch on the first beat.
Sorry my comments are so vague as to be of little concrete help but I just wanted to point out that I've also had issues on starting up playback of drum beats in Reason when using it in ReWire mode.

Quantized 16th Notes in regions not playing correctly

I was tracking a 16th note riff into Logic - it was a MIDI string part that was quantized to 16th notes and locked to the quantize grid. It was playing back perfectly until I drew in a cc11 volume swell. After drawing in the cc11 curve, the rhythm didn't play back correctly. I checked in the piano roll window to see if the notes were still lined up to the grid and they were. I deleted the cc11 curve and decided to draw in a volume swell with the hyper editor in the arrange window. Same problem. When I went into the piano roll and clicked on a note, the message below popped up:
The channel numbers in the even edit list were ch1 and ch2. The strangest part was that in the pattern I played, the high notes (played with my pinky and accented) were all ch2, and the low notes (played with my thumb and index finger) were all ch1. After assigning everything to ch1 the rhythm issue within that region remained. You have any idea what might've caused this?
I'm on Logic Pro 9, OSX 10.7.5.

Sorry delete the post if someone can I don't know how to ..he he
found the answer......select all notes in piano roll an unmute
sorryyyyy ....

Can't turn off auto quantizing

I'm a little new to Logic, but from what I can tell, I've done everything I should. I'm trying to record 16th note triplets, and the notes show up as triplets in the piano roll while I'm recording, but then are automatically quantized to straight 16ths when I stop. In the screenshot below, you can see that I've got quantization turned off in the piano roll window and in the inspector at right. Am I missing something else? Thanks in advance.

Well sheesh. I figured it out myself, once I realized what the "inspector" actually is. So, if anyone else has this problem later on, click somewhere in a blank area on the track you're trying to record, so that you de-select any previously recorded regions. In the inspector (which will be to the left of the arrange area - click the "i" at upper left if you don't see the inspector), expand the "Region" section, and set the quantization there.

Color Quantization by Distinctiveness

If I do a save for web & devices, I can quantize the colors.
The problem that I am having is the Photoshop appears to be quantizing by frequency rather than by distinctiveness. The result is a color table with a lot of similar colors. Colors that are not so frequently used but are distinctive in the image get a radical color change. In my images sight color variations are not significant.
It is possible to get Photoshop to quantize colors by distinctiveness?
If would be great if I could edit the color table and specify that two colors are to be merged.

Quantization happens in Indexed Color mode, GIF or PNG-8. For the Web this reduction
is not necessary, but you may have your reasons.
I'm understanding your question like this: even a very small red flower on a meadow
should not be ignored. Therefore my test image contains an extra small red square.
Parameters are:
1) Number of colors. Reducing this number, similar colors are put together, probably
    averaged.
2) Quantization mode: Perceptual, Selective, Adaptive, Restrictive (Web colors).
    I don't know what happens in the background, but I found an interesting result:
    The red square is ignored in mode Perceptual and Selective, but retained in
    mode Adaptive.
Perhaps for your purpose an individually chosen number of colors in mode Adaptive
can be used.
Best regards --Gernot Hoffmann
P.S.: You may try as well Image > Adjustment > Posterize (n levels per channel)
Message was edited by: G.Hoffmann (P.S.)

Flextime - quantizing audio tracks??

I'm just wondering if there is a way to use Flextime to quantize live audio tracks (as opposed to sampled audio tracks). Example: I've got this wonderful accordion track, traditional music ... the tempo moves all over the place. I want to experiment with adding an untraditional rhythm track / bass. I've tried beat-mapping ... but even though I can track the accordion, the varying tempo of the added rhythm tracks just sounds weird.
Is there a way using Flextime that I can do the opposite: get the accordion (live-audio) track to quantize to a click track? Ideally all at once, as opposed to me having to rebuild it all note by note.
Any suggestions would be most appreciated,
Ben

Hi
Were the original audio recordings done in Logic 9? If they were, they will automatically have the 'original recorded tempo' (of the original project) embedded within the file. This can cause problems with Flex.
If need be, you can remove the tempo info using Options:Tempo:Remove Tempo Info...
If you have enabled Flex, the files are analysed and Transient Markers added. If you did this with the current project at the "wrong tempo", you may need to remove the transient markers and start again.
It is usually better to beat map 1st, to get the tempo/tempo changes close, then enable Flex to "pin" the Transients to the current tempo map. Once done, you can easily switch tempo maps to another (possibly static) tempo map, and Flex can do it's magic.
See here for more info:
http://support.apple.com/kb/HT3855
CCT

I have big problem with battery, It's not working good just two hours and stop without any warning when the battery in 50% then reach 30% in the same moment, then the iphone stopped,what I can do for that and I live in Egypt???any help

My Iphone 4 is very good until last Thursday, I used it from sep 2011 without any problems, My problem is the battery is down without any warning and working after 100% then 82% then 50% then 30% and down these things throw less than two hours
what can I do with that??
Also, I live in Cairo,Egypt
waiting your recommendations

Hi,
"But it didn't work it's just turning them to black gray scale colors not what i was thinking about."
If you want it to be colored, you'll need to create a color-palette for the 8bppIndexed bitmaps. The keyword for this process is "Color-Quantization".
The whole yellow-green pie you get is from the wrong format. If you convert the 32bpp bitmaps to 24 bpp bitmaps, you loose the alpha channel ("transparency"). You can manually set one color to "transparent" with the mMakeTransparent-method
of the Bitmap class, or simply use gif-images (they are 8bpp with a transparent "key"-color)
Regards,
Thorsten

Need help in quantizing an image(using adobe photoshop CS3)

Hi All,
I am using window and adobe photoshop CS3 extended. I had an image whereby i had already perform histogram equalization. I would like to quantize the image obtained into 2 bits per pixel, per channel. Can anyone advise me? The image is a 24 bit colour BMP file whereby the bit depth is 24 bits. Pls advise.

Hi, I managed to find the refresh cached option. However there is still one thing which i need some clarification on.
The problem for me is to quantize the image into 2 bits per pixel per channel. I understand from the previous post that i need to use posterize and set it to 4. My questions are as follow.
1) why must the value be 4? if the value is 4 then there should be 8 bits, but my question require a total of 6 bits only
2) After saving my quantized image, the properties of the image still show me the bit depth being 24, thus is there any where whereby i can check that each color pixel is exactly represented by 2 pixels?
Hope you can advise. Tks

Separate Display Quantizations for the same part in Notation

I'm having a hard time with something that seems like it would be easy to fix. How can I set up a part in the notation editor and use one display quantization setting for say, bars 3 and 4, and another display quantization setting for bars 5 and 6. (For instance, if I wanted eighth notes in one and sixteenths in another). I remember reading somewhere that you need to split the measures into separate regions, because display quantization can only be applied to a region as a whole, but when I do that another treble clef or entire bracket appears in the midst of my score in the score editor. How can I get rid of this extraneous clef appearing? I know that you can adjust individual quantizations when working with the actual MIDI events, but I only want to change the display quantization.
Also, what workflows do you all use to deal with Logic's over-indulgence in cut away scores? I know you could create a bunch of empty regions on top of your project's and then merge them, but I believe then you would lose your display quantization (related to above).
Thanks!

hey keith i just saw your reply and further question - there are two things that would help:
1 - if you are just wanting to creating multi rests, then the quantize tool is not correct.. you need to drag the little sign in the Inspector which looks like a multi rest and calculate the open bars eg.. if it matters to you that the instrumentalist needs to be able to count in 8 or 4 or 16 bar sections then make sure that you have a double bar line breaking up the blank bars, That way when you drag a multirest it will go up to the double bar line
On the other hand you might be writing for hot orchestral musicians who have no problem counting 63 and a half bars before they come back in in which case you can have one long multi rest.. does this make sense
2 -for the 'cutaway' thing you are talking about - I think I know what you mean .. a big blank space on the part where the system stops. I like doing this too .. and the way I do it is to just leave a big gap in the linear placement of the regions .. say your first part goes from bar 1 to bar 32 then you want a cutaway.. leave a gap of 4 bars and then start the next region from bar 36. When you look at the score in Print View.. you will see the gap
The only problem with this method is that it messes up the bar numbers .. as logic will still think that the bars exist.
ZZZ - Hello Score Editor fiends and programmers: official request for a new Score Editor feature
Re Assign Bar numbers: this would enable the user to name the bar numbers according to the logic of the part/score ... and not be tied to logic's sequence to crank out mindlessly linearly the bar numbers
An idea feature would be to insert a 'memory hole' - so the user could over ride the sequencer.
This combined with Johannes Pritchls little used system where by the sequencer could follow repeats and signs and DS and to Codas... would make Logic Score Editor a MUCH MORE BRILLIANT tool
PS not forgetting Global Rehearsal letters .. my old bug bear

Eclipse problems

Hi good Morning, I have a problem importing import com.sun.image.codec.jpeg.*; in the eclipse IDE,I get this error the import com cannot be resolved,
there part of my code, package gui;
import javax.swing.event.*;
import java.awt.image.*;
import java.awt.event.*;
import javax.swing.*;
import java.text.*;
import java.awt.*;
import java.io.*;
import jj2000.j2k.quantization.dequantizer.*;
import jj2000.j2k.image.invcomptransf.*;
import jj2000.j2k.wavelet.synthesis.*;
import jj2000.j2k.fileformat.reader.*;
import jj2000.j2k.codestream.reader.*;
import jj2000.j2k.entropy.decoder.*;
import jj2000.j2k.image.input.*;
import jj2000.j2k.codestream.*;
import jj2000.j2k.decoder.*;
import jj2000.j2k.image.*;
import jj2000.j2k.util.*;
import jj2000.j2k.io.*;
import jj2000.disp.*;
import com.sun.image.codec.jpeg.*;
import colorspace.*;
please, help me

Are you sure that package exists? Looks like one of the Sun private APIs that aren't for general use, and, more pertinently, aren't guaranteed to be present in different versions of Sun's Java implementation. They won't be present at all in non-Sun distros. What leads you to want to import it?
From the javadocs of JPEGCodec, in that package:
Note that the classes in the com.sun.image.codec.jpeg package are not* part of the core Java APIs. They are a part of Sun's JDK and JRE
* distributions. Although other licensees may choose to distribute these
* classes, developers cannot depend on their availability in non-Sun
* implementations. We expect that equivalent functionality will eventually
* be available in a core API or standard extension.>
In short, try and avoid using it directly

Marquee tool problem

I've been searching message boards and google alike for tips on drum quantizing. One method has you highlight your drum tracks after grouping them and then using the marquee to tab to each transient, and split by locator to separate out the transients. For some reason when doing this my split by locator icon and key command both don't work. The computer just beeps when I try to use it. I havent read anywhere of anybody having this problem before so I am stumped on what to do exactly. Anyone have any advice?

Don't use the Marquee Tool; try using the Ellipse Tool set to "Paths".
Don't forget strokes in Photoshop are made of pixels and will never look like a line of similar weight drawn as a vector.

L8 Bug: Quantize value display

Is this a bug:
The new Piano Roll Editor displays the currently selected quantize value (FINALLY !) . In L7 you always had to click hold on the "Q" button to see it. That is all good.
BUT
if you use the key command to select the next or previous quantize value, that display doens't get updated and therefore displays the wrong value.
Example
1) Set the popup menu to 16th
2) Use the select previous quantize value key command
3) The popup menu still displays the 16th
4) When you open the popup menu, it has the correct 12th value selected.
Any confirmation on that?

I found the problem:
The "Link" button in the Mixer window affects what channel strips are displayed in Arrange mode:
*Arrange button + Link button on*: displays all tracks from the Arrange window minus the hidden tracks
*Arrange button + Link button off*: displays all tracks from the Arrange window regardless if they are hidden or not.
Although it works, I'm not sure if that is the most intuitive GUI solution for that feature.

Quantize problem!

Similar Messages

Maybe you are looking for