Hi Krister Well, as for the why, think of it like the VO cursor versus the keyboard focus. You can have one positioned somewhere while marking out positions with the other. As for why your cut didn't work, from your steps you did not route the insertion point to the play head. There's two ways to do this, either route the insertion point to the play head with cmd-y, or use option +left and option+right to move the insertion point to the correct marker and then extend the selection in the desired direction. From there, do whatever you wish to do with the selected audio. One recommendation, in Amadeus preferences, set the "when selection is empty" setting to "play from insertion point." This will let you here where the insertion point is by playing when you move (note though that this will also move the play head). This is a useful option, however I don't believe it is the default. hth
Krister Ekstrom wrote: > Hi there. > I was trying to edit a podcast that is about to go out soon when i > encountered a problem in Amadeus Pro. First, before i ask my questions, i > have to say that this rant is due to the fact that i think i don't understand > the concepts of Amadeus and how it works as well as i would like to. > My problem was that i couldn't cut a selection i had done. I placed a mark at > the play head and then extended the selection from the play head position to > the previous marker and then i tried to cut the selection, this didn't work > for some odd reason and i don't know why. The question i ask myself and any > gurus of Amadeus pro is why is the insertion point and the play head two > separate entities? What do you actually gain by this approach? For me it only > gets more confusing and more time consuming to edit a sound this way. Since i > don't understand the logic behind this, the editing gets random. Sometimes > placing markers work, sometimes not, sometimes selecting things work and > applying operations to a selection works as expected and other times the > whole thing gets screwed up and i can't seem to see a rational explanation as > to why and there's nothing that i can find in the manual about this so any > help would be very much appreciated. > My second question is this: Is there a list of keyboard shortcuts available > in either text or html with the table correctly rendered? As it is in the > manual now, and if it is shown in Preview, i see the shortcut keys in one > list and the asociated functions, i.e what the keys do in a separate list, > making it useless in practise since you see every single shortcut in a neat > little row and then in a totally separate list you see the actions, I would > have wanted keys and actions next to eachother. If there's no text or html > file with keyboard shortcuts and actions rendered correctly, is there a way > for Preview or Skim to show me the shortcut list like that? > Thanks for any help. > /Krister -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionar...@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
