Verizon & Loop Length

I ordered the 3mbps plan and are scheduled to be activated on the 7th. I thought this is wierd becase they said my loop length is 0ft. and I don't see any box, this would be my 4th time trying to get the service and last time All my lines including my neighbors were to far ect. This road is a Dead end road Iam the second to last house and we both qualify for 3mbps yet the 3 houses infront of us don't then the raodf that comes up at the end of mine all the people there qualify all the way up the hill and beyond.
Now, Iam just wondering if anyone knows anything or has been in a similar situation as me.
Also, if it doesn't work this time I wondering if I could pay for an amplifier/repeater or even a small 4 port remote terminal or the smallest available. If we miss it again we are only missing it by 1000 to 2000ft. This is our only option hughes is pathetic my mom can't work at home because of the cap.

The distance is determined by how far your house id from the Central office supplying dialtone to your area. You have to be within 3.5 miles, roughly 18000 ft. I"ve been sent out to hook up customer who "Qualified" only to have to tell them the signal would never reach their home 5 miles away. Keep your fingers crossed.
Another option you can consider is cellular broadband. One of our employees just got it recently. He lived too far from the Central office to get Dsl and it was an inexpensive alternative compared to Hughes.

Similar Messages

Loop length for multiple tracks

Is there a way to set the length of loop repitition, for different tracks?
I tried this the other day, with two tracks that I set up to loop, and when I adjusted the loop length in the top of the arrange window, both tracks were affected.
I want to have one track loop 5 measures, and the second track only 3 but am not sure how to do that.
Is there a way to do this?
Thanks
RH3906

This is how I do it. Select the track, click on the midi/audio file you have dragged to the track. Then click the 'loop' check box (top left). This will loop the sample all the way to the 'end'. Now simply hover your pointer over where each loop sample is joined and the pointer should change to a different icon - kind of an arrow in a half loop. Now if you click on the sample when you have this pointer you can now drag back and forth where you want the loop to end. Do this for the other track, you can choose how many bars you want it to loop.
What you cant do is set up a loop all the way to the end and make 'holes', that is parts where the loop doesn't happen.
If you want a loop to start again in a different place, simply drag the sample to the new starting location and repeat above.
Hope this helps.

Automating loop length

Hi is it possible to automate the length of a loop in logic's arrange (to emulate the shortening of a loop as on a cdj). Or is there a sampler alternative (I've tried the Elastik player but cant automate the loop length or seem to add my own samples)

thanks

Loop length

I am creating looping soundtracks for short looping animations. I'd like the loop length of the audio to match the animations. Can I stretch loops or somehow alter them to match the length of the movie? I repeat a loop but as the movie goes back to the beginning before the end of the second loop you hear an obvious glitch in the result.
Intel imac Mac OS X (10.4.7)

thanks

Extending a loop length in a simple way

Hi guys and I'll start my first post by thanking you all for all the posts on here, I find this very helpful and use the forum search function a lot to increase my knowledge.
But to the point. I work with short seamless loops of around 10seconds or so in motion but often find that I want to be able to burn a DVD with the same loop. As you get the dreaded hickup when the laser refocuses I tend to want to copy the 10sec loop and copy paste until I have created the 12minute loop.
Currently I will go to the timeline and select the various components and basically cut and paste dragging them to the correct position one after the other until I achieve the length required.
Quite a tedious process and I'm sure there is a much simpler way for this novice to work.
Thanks again for your assistance
Joakim

New Discussions ResponsesThe new system for discussions asks that after you mark your question as Answered, you take the time to mark any posts that have aided you with the tag and the post that provided your answer with the tag. This not only gives points to the posters, but points anyone searching for answers to similar problems to the proper posts.
If we use the forums properly they will work well...
Shane

How to alter loop length of sample while playing exs24 ?

Hi there, what I want to do is change the length of the loop set to the audio region that is used as part of an instrument in the EXS24 mk II. I would like to be able to control this while playing or automate it.
If anyone can think of a way to do this I would be very pleased to hear it!
Thanks

You'd have to use two loops to traverse them all:
SQL> declare
2    l_2d_grid twodim_aa.array_t;
3 begin
4    l_2d_grid (1) (1) := 100;
5    l_2d_grid (1) (2) := 120;
6    l_2d_grid (2) (1) := 120;
7    l_2d_grid (3) (1) := 200;
8    for i in 1..l_2d_grid.count
9    loop
10      for j in 1..l_2d_grid(i).count
11      loop
12        dbms_output.put_line('l_2d_grid(' || i || ') (' || j || ') = ' || l_2d_grid(i) (j));
13      end loop;
14    end loop;
15 end;
16 /
l_2d_grid(1) (1) = 100
l_2d_grid(1) (2) = 120
l_2d_grid(2) (1) = 120
l_2d_grid(3) (1) = 200
PL/SQL-procedure is geslaagd.Regards,
Rob.
Message was edited by:
Rob van Wijk
Made the example a little clearer.

Need to loop a 0 0 2 0 length region every 0 1 0 0 interval......

Hello, I need to loop a 0 0 2 0 length region every 0 1 0 0 interval. Is there an easy way to do this without adding silence to the region to match the region length to my loop length?

I found a way by packing the region into a folder, setting the folder length, then looping. This works, but just seems like a lot of unnecessary steps....

Treo 700p Updated Versamail to 3.5.4 and immediately went to a restarting loop...

I'll tell you the whole story so you can feel sorry for me and help.
I was trying to update my step-mom's versamail so she could get her office e-mails for her trip today. Well, she had never plugged in her treo into her computer before, so I had to install palm desktop, etc. The phone synced and it said it was backing up a lot of stuff, but I noticed it didn't update versamail. So I ran the installer, and everything appeared to install fine. The phone reset itself, showed the access powered (i think) screen and then the palm screen, and then it reset it self and did it again.
This went on for a good 5-10 minutes before I called it quits. I tried taking the battery out and putting it back in, but still did the restart loop. Well it came time for her to go, and she absolutely needed the phone. So I had to do a hard reset so she could use it this weekend. After the hard reset I synced it again to see if I could get the backup data on there. After it loaded everything it went back to the reset loop. So I hard reset it again, and gave it to her. She brought her laptop that I used to do the syncing, so I'm hoping I can have a fix for her soon.
Basically my questions are:
- What happened to cause the loop?
- How do I get all her info back on her phone without it causing the loop? (most important question)
- How do I install versamail without it causing the loop?
Thank you.
Post relates to: Treo 700p (Verizon)

Looping resets are caused (Most of the time) by corruptioncoming over from the PC. The way to prevent this is to rename the backupfolder. (C:/Program Files/Palm/Hotsync username/Backup)
Then try to reinstall VersaMail.
Post relates to: None
Post relates to: None

Array looping

Hi,
I need to run several nested loops. Problem is, I only know how many nested ones to do at runtime (not compile). eg. want to do something like this
imagine I have an int[] array.
int[] r;
Someone else initialises and populates this. Now I now that r is 7 dimensional, but do not know at compiletime.
for (int a = 0;a<5;a++) {
for (int b = 0;b<6;b++) {
for (int c = 0;c<6;c++) {
for (int g=0;g<4;g++) {
r[0]=a;
r[1]=b;
r[6]=g;
etc.
How can i do this without hard coding in the looping structures such that this can handle an array of an arbitrary dimension (just single array though - not [][]).
Thanks for help.

My code above will have 5 nested iteration with 4 x 2 x 3 x 5 x 4
But one thing I don't get it.. when you compile, it won't compile because I note some part of code are messed up with the Jive syntax highlighting.
For example:
counter<i>++;
should be
counter[ i ]++;Gosh!
So here I re-post the code again:
public class x {
void doLoop(int[] looper) {
    int counter[] = new int[looper.length];
    int r[] = new int[looper.length];
    boolean keepLooping = true;
    while(keepLooping) {
       int i=0;
       while (true) {
           counter[ i ]++;
           if (counter [ i ] <= looper [ i ])
              break;
           else {
              counter=0;
if (i+1==looper.length) {
keepLooping = false;
break;
i++;
if (keepLooping) for (i=0; i<looper.length; i++) {
r[i] = counter[i];
System.out.print("r[" + i + "]=" + r[ i ] + " ");
// now do something with r[]
System.out.println("");
public void doSomething() {
int[] looper = new int[] { 4, 5, 3 ,2 ,4 };
doLoop(looper);
public static void main(String[] s) {
new x().doSomething();
Hope it would be all right this time...

Logic 10.0.5 is out! Three new drummers, LOADS of fixes.

I have not yet finished reading the release notes, it is almost 5,000 words...
http://support.apple.com/kb/TS4498
Logic Pro X 10.0.5: Release notes
Symptoms
Logic Pro X 10.0.5 is an update to Logic Pro X. Logic Pro X is a new paid version of Logic Pro.
Resolution
Logic Pro X 10.0.5 update
New features and enhancements
Includes 3 new Drummers and 11 new Drum Kit Designer patches.
Significant enhancements to Channel EQ and Linear Phase EQ plug-ins, including:
Redesigned, easier-to-use interface that's also accessible within the Smart Controls area
Double Precision processing provides more accurate filtering, especially for low frequencies
Oversampling option improves high-frequency clarity
Option to apply EQ only to stereo left, right, middle, or side signals
There is now an option to set the Piano Roll to a light background color.
Selected notes in the Piano Roll are now highlighted by a selection frame.
When Logic is stopped or in Play mode, the glyph on the Metronome button in the control bar now illuminates to indicate that “Click while recording” is enabled.
The Shuffle commands are improved (see Logic Pro X Help for details).
User interface
There is now a command to assign region names to track names.
The waveform size in an audio region now adapts to the value of the region gain parameter.
Loops that belong to the same family can now be selected and changed using a new control in the region header.
Logic Pro X now assigns region and Mixer channel colors that are closer to the original colors when opening a project created in an earlier version of Logic.
Option-clicking a disclosure triangle in the Project Audio window now toggles all disclosure triangles in the window.
The Windows menu again lists all currently open windows.
The Mixer can now be reliably resized when in All mode.
Renaming multiple selected Mixer channels now reliably renames all channel strips in the selection.
When creating a duplicate track, the correct track icon and color are now assigned to the duplicate.
The song title is now automatically populated in the Share to iTunes dialog when sharing a song created in Logic 9 or GarageBand for iOS.
It's once again possible to browse or load patches onto the Output channel strip via the Library.
The View menu items One Track and Selected Regions in the Piano Roll are now disabled when Link mode is disabled.
Performance
Improves processor balancing for multi-output software instrument configurations.
Improves handling of multiple displays on OS X Mavericks v10.9.
Resolves an issue that in some cases might cause audio clicks and pops when scrolling.
Moving an automation line while playing no longer spikes in CPU usages, or clicks and pops in the audio output.
Resolves an issue that could cause clicks and pops in the audio output when adjusting the gain or output level settings during playback in the various plug-ins.
Logic's interface no longer freezes when using the Native Instruments Maschine controller to adjust two macro controls simultaneously.
Fixes an issue in which a warning about not enough memory might be displayed when performing Undo after editing a protected track.
Adjusting the frequency controls while playing audio through the Stereo Spread plug-in no longer causes audible zipper noise.
Improves the performance of scrolling when dragging regions in the Tracks area beyond the currently visible section.
Playing notes live into the Arpeggiator plug-in no longer sometimes leads to spikes in CPU usage.
Fixes an issue that could cause a spike in CPU usage when recording near the end of a project.
Logic 9 projects that contain a macro object in the Environment now behave more reliably when opened into Logic Pro X.
Multiple instances of the Scripter plug-in no longer have the potential to cause stuck notes.
The Scripter plug-in is no longer prone to causing stuck notes when using the Delay Note Until Next Beat preset.
Switching between presets in the Space Designer plug-in no longer sometimes results in noise.
General
Regions copied from a Track Stack can now be muted as expected even when they are within a Track Stack that is muted.
Deleting an audio Track Stack while it was soloed no longer leaves all the remaining tracks muted.
Entering a new crossfade value in the Region inspector for multiple selected regions now works as expected.
Region-based automation data beyond the end of a region is now chased properly even when playback is started after the last automation node within the bounds of the region.
Logic now maintains the correct relative levels when automation on multiple tracks belonging to the same Group are copied by dragging.
Resolves an issue in which track automation might be deleted when switching patches.
The default display setting when showing automation on Track Stacks is now Volume, instead of Display Off.
A track is now created as expected when using a control surface to set the automation mode of a channel strip not previously assigned to a track.
Moving a SMPTE locked region can no longer cause the automation on the track to move.
The position of the automation line no longer jumps unexpectedly when it is selected after creating 4 automation points with a Marquee selection.
Adjacent automation points of the same value are no longer sometimes inadvertently deleted when moving automation points on a grouped track.
The Repeat Section Between Locators command now includes automation on tracks that contain no regions in the repeated section.
When using Touch mode, Logic no longer writes unneeded automation points at the held value when holding a fader at the same position where there is an existing automation ramp.
Writing automation to an Aux not assigned to a track can no longer potentially cause tracks in a Track Stack to be rerouted to that Aux.
Copying multiple regions where only some affected tracks contain automation no longer activates Automation Read mode on the channel strips that have no automation.
Chase now works as expected for MIDI controllers on channels other than channel 1.
Takes are now shortened as expected when the take folder containing them is shortened by an edit operation and No Overlap mode is enabled.
Fixes an issue in which the visible area might jump unexpectedly when comping in a take folder that was not on the selected track.
Fixes an issue that caused some audio regions to be immovable when duplicate regions are packed into a take folder.
Packing regions with names containing non-ASCII characters into a take folder no longer creates garbled take names.
Numbers assigned to MIDI takes now increment reliably.
Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
When using OS X v10.9, the playhead in the Audio Editor now consistently maintains the correct position when switching from Flex Time to Flex Pitch mode.
It's now possible to set a loop to a length of less than 1/16 note.
The position of beat markers in the Global Beat Mapping track are now updated appropriately when using the various Cut/Insert Time commands.
Inserting a beat marker in the Beat Mapping track no longer creates unexpected tempo events in some circumstances.
Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
Resolves an issue in which some MIDI notes might unexpectedly change position when Beat Mapping.
Adding a Beat Mapping marker no longer intermittently removes existing tempo events.
Inserting a fade-in using Shift-Control and the Pointer tool now works consistently.
Using the Fade tool to set fade-ins on multiple regions in a set of grouped tracks now works reliably.
Dragging regions on multiple grouped tracks with the Drag Mode set to X-Fade no longer potentially results in crossfades of varying lengths.
The Delete command now works as expected on selected regions that are inside a collapsed Group in the Project Audio window.
It's now possible to add a green Apple MIDI loop to the Tracks area as an audio loop by dragging it from the Loops browser while pressing the Option key.
Logic Pro X no longer creates separate tracks for non-overlapping regions when unpacking folders in projects created by earlier versions of Logic.
Using the menu that appears when pressing the Metronome button in the Control Bar, it's now possible to set the metronome to sound only during count-in.
Improves the reliability of Undo in several areas.
The Mixer window no longer intermittently moves when scrolling past the minimum or maximum value of the fader using a scroll wheel or gesture.
It's now possible to select or open folder tracks in the Mixer.
Right-clicking an Aux or Output channel strip in the Mixer and selecting Create Track now behaves as expected even if the channel strip is not initially selected.
Command-click again works reliably to deselect a Mixer channel within a selected group of channels.
The display of audio waveforms of regions in a track no longer change unexpectedly when enabling or disabling the Groove status on a track.
Looped regions inside a folder now update the point they are supposed to stop playing after extending the length of the folder.
Overwriting an existing project no longer potentially leaves assets from the original project in place.
When creating a new project from a Logic 9 template, the default save path is no longer the location of the template.
Improves the mapping of Smart Controls to channel strip settings created in Logic 9.
The Follow Tempo parameter in the Region inspector is no longer incorrectly disabled for Apple Loops in songs last saved in GarageBand 6 or earlier.
Clicking and holding down on the upper-right corner of a region no longer unexpectedly enables looping in the Region inspector, with a loop length of zero.
The Region Inspector no longer displays a Loop checkbox for selected Track Stack folder regions.
It's once again possible to disable Quantize in the Region Inspector for a region on a track slaved to a Groove Master track.
Saving a song created from a template no longer resets the tempo to 120 BPM.
Text for alert messages now always displays correctly on control surfaces.
Changing Region inspector parameters for MIDI regions on the main track of a Track Stack now behaves as expected.
It's again possible to change the Transpose value in the Region Inspector using the + and - keys.
Logic now consistently responds to Play or Stop key commands when a floating Region inspector window is open.
It's no longer possible to give the same name to more than one project alternative.
MIDI played from the Musical Typing Keyboard and Logic Remote is now routed through the Physical Input object in the Environment, which allows Environment processing of MIDI as it is being played into Logic from these sources.
Logic no longer adds 2 extra frames to the value when entering a SMPTE position in a project set to a non-drop frame rate.
Regions copied by option-dragging in projects with a start position earlier than bar 1 now end at the desired position.
Moving the first arrangement marker in a project no longer inadvertently moves other arrangement markers.
Resolves a rare issue that could cause the timing of a track in a project with many tempo changes to be altered after turning Flex on and then off.
Logic now asks the user to save the project when closing a project immediately after entering text into the Project Notes area.
It's now possible to consistently add, remove, or edit plug-ins on tracks that were frozen in Source Only mode.
Pressing the Control key while dragging a region with the Snap Mode set to Bar now moves the region by beats instead of ticks, as expected.
Editing the left border of an audio region now behaves as expected when the Snap setting is set to “Snap Regions to Relative Value”.
Resizing a region with the Snap setting set to “Snap Regions to Absolute Value” now behaves as expected.
Resolves an issue that caused an event in the Event List to move later than expected when editing its position.
The “Capture as Recording” command now works as expected when multiple MIDI tracks are record-enabled.
It's now possible to preview sections of an audio file outside the current region borders by clicking the area in the Project Audio window.
The tap-to-click option for trackpads now works reliably with all drop down menus.
The “Discard Recording and Return to Last Play Position” key command now reliably discards the recording.
It's again possible to use the Tab key to navigate to the next control while working with plug-ins in Controls view.
The MIDI Activity display now shows chords as they are played when using Musical Typing.
All currently found audio files are now reliably saved with a project when using Save As or Save a Copy As with a project in which one or more audio files are missing.
The name of a project is now correctly updated after saving a project created from a template.
Fixes an issue in which clicking on the level LED in the track header did not select the track.
Resolves an issue in which changes made to the setup for Mackie Control and other MCU-compatible control surfaces were not saved by Logic Pro X.
Setting the Display Time preference to “SMPTE/EBU with Subframes”, “SMPTE/EBU without Subframes,” or “SMPTE/EBU with Quarter frames” can no longer cause the time display to jump unexpectedly.
Saving a project for the first time no longer resets the record path when it was previously set to an external path.
Performing undo in the Piano Roll or after deleting a flex marker no longer has the potential to unfreeze currently frozen tracks in the project.
Sample rate, tempo, and key information is now reliably stored within template files.
Fixes an issue in which the Repeat Regions dialog did not have key focus when opened, making it necessary to click it with the mouse before pressing Return to confirm the operation.
Individual MIDI Draw points in the Piano Roll are now easier to grab.
Deleting a track no longer has the potential to inadvertently delete regions on other tracks.
Cut/Insert Time edits no longer add unexpected tempo changes.
Scrubbing the SMPTE display in the LCD no longer moves the playhead to the wrong position.
Copying an arrangement marker to a position between two other arrangement markers now moves the end-of-song marker to accommodate the new section, as expected.
Audio
Audio regions now appear as expected in the Audio Editor, even when cycle is enabled and there are no audio regions within the cycle area.
Flex Pitch now correctly detects notes for take regions that have manually inserted flex markers.
The timing of notes played during the count-in on EXS24 or Drummer tracks is now more reliable.
Pasting an audio region into a take folder now correctly places the region on the selected take lane.
When saving an EXS instrument, the default save location is now ~/Music/Audio Music Apps/Sampler Instruments.
Editing the start point and anchor in the EXS audio editor now consistently alters playback as expected.
Logic no longer overwrites an existing audio file of the same name when performing a bounce with the option to create a split stereo file enabled.
Audio tracks assigned to output to a bus now consistently maintain that assignment when imported into a different song.
User-defined controller assignments now work as expected to control MIDI plug-in parameters.
The Record Repeat command now deletes the previous recording when used after recording in Cycle mode.
Quantize now operates reliably on takes that are displayed in the Audio Editor.
The Tuner window is no longer affected by the Content Link setting of other plug-in windows.
Audio now plays for multiple cycle iterations when using marquee selection to define the cycle area.
When the Edit command “Analyze Audio for Flex Editing” is used, Logic now properly resets any existing pitch edits on the selected audio files.
Command-clicking a selected note in Flex Pitch mode in the Audio Editor now deselects the note, as expected.
Setting a track to Flex Edit mode with the Slicing algorithm no longer processes the track with Flex if no edits have been applied.
It's again possible to set Software Instruments to mono.
Logic no longer creates an extra audio file when merging or format-converting audio files.
Resolves an issue in which the Mixer did not show the 8th bus send on a channel strip.
Changing the input format of a stereo output channel strip to mono now creates a second mono output channel strip on the Mixer for the other channel in the stereo pair.
Setting an external recording path now reliably resets the Audio Assets setting. Conversely, enabling the Audio Assets setting now disables an externally set recording path.
The compressor meter in the channel strip is now in sync with the meter in the plug-in window.
Drummer
Improves the translation of articulations when an Ultrabeat-based patch is assigned to a Drummer track.
When a project starts on an upbeat, a Drummer region at the project start now automatically creates a fill at the beginning.
Changes to Drummer regions are now reliably applied when the regions are set to follow a flexed audio track.
MIDI editors
The Link mode button is now available for the Piano Roll editor.
The “Limit Dragging to One Direction” setting now works as expected in the Piano Roll.
It's now possible to grab notes shorter than 15 ticks for editing in the Piano Roll.
Double-clicking a region with MIDI Draw enabled now consistently opens or closes a MIDI editor.
Resolves an issue in which recently recorded MIDI notes might disappear from view in the Piano Roll when recording with cycle engaged.
It's again possible to alter the pitch of notes in the Piano Roll via MIDI input.
Using Option-Shift to edit the end points of multiple selected notes to the same position in the Piano Roll Editor now works as expected.
In the Piano Roll, it's again possible to use Option-Shift in conjunction with the Velocity tool to set all selected notes to the same velocity.
An Event Float window that is linked no longer switches unexpectedly to the Region level when using arrow keys to move from note to note in the Piano Roll.
Pasting events in the Piano Roll when the playhead is to the right of the region border will not trigger the error “Illegal Region number”.
It's now possible to copy a note in the Piano Roll to a different pitch at the same position when the note starts before the left edge of the region.
It’s now possible to move notes in the Piano Roll by increments smaller than 13 ticks when the “Limit Dragging to One Direction” setting is enabled.
User-inserted rests no longer incorrectly appear as notes in the Piano Roll.
Copying a muted note in the Piano Roll now creates a muted copy of the note, as expected.
Fixes an issue in which some note events might not be selectable in the Step Editor.
The contents of the Event List are now updated properly when deselecting a region from a multiple selection while Content Link mode is enabled.
The Event List now displays the correct LSB values for 14-bit pitch bend events.
Editing Release Velocity values in the Event List now behaves as expected.
The “Copy selected events” option in the MIDI Transform window now behaves as expected.
Score Editor
Fixes an issue that could cause the menu option for switching between Parts and Score view in the Score Sets window to disappear.
Double-clicking a region with the All Instruments filter setting active now reliably reveals all regions on that track, rather than just the single region.
The contents of the Event List editor are more consistently updated when changing the region selection from the Score window.
Newly inserted key signatures no longer display “xx Major” in some circumstances.
The Chord Grid Editor now correctly names Add 9 chords.
The clef menu no longer disappears for a Mapped Instrument staff style set to “No Clef”.
It's again possible to create a new Chord Grid library that uses an alternate tuning.
It's now possible to adjust the Velocity setting in the MIDI Meanings settings window by scrubbing the value with the mouse.
The length adjustment in the MIDI Meanings settings window can now be adjusted via a pop-up menu.
In the Staff Style window, the check marks indicating that a style is used in the current song now reliably update to reflect changes when Content Link mode is off.
Grace notes now scale properly when the scale setting of a Score Set is less than 100.
Resolves an issue that prevented reassigning instruments assigned to a Score Set after performing certain other edits.
Fixes an issue that prevented naming a floating score Part box set.
Plug-ins
Solo now works as expected on channel strips using an external I/O plug-in
Ultrabeat can now find samples that have been relocated from the default install location.
Ultrabeat now correctly applies the Fine Pitch adjustment to all triggered samples when trigger mode is set to Multi.
It's now possible to halve/double the current rate of the Arpeggiator plug-in by clicking the Slow/Fast buttons.
The ES1 synth plug-in can now be set to offer 32 and 64 voices per instance.
The Scripter plug-in now allows System Realtime MIDI events to pass through.
The Scripter plug-in now offers an option to keep current control values when recompiling a script, rather than resetting all values back to their defaults.
The Scripter MIDI plug-in now includes a Set Parameter function.
Switching between Vintage Electric Piano patches while holding notes no longer potentially results in momentary jumps in level.
The Vintage Electric Piano no longer potentially creates audible pops when switching patches when the Drive is enabled and set to Type II.
It's now possible to continue working with the Scripter editor window when Logic Pro X is not in focus.
The Surround Compressor plug-in now properly shows all the new circuit types available in Logic Pro X.
It's again possible to copy or paste settings in the Space Designer plug-in window.
The order of controls in the Retrosynth Filter Envelope and Amp Envelope sections has been reorganized to improve usability.
The plug-in window no longer appears empty for Waves plug-ins opened in projects created in Logic 9.
Fixes an issue in which inserting a plug-in on multiple stereo Software Instrument channel strips would insert mono versions of the plug-in on some channel strips.
EXS24 or Kontakt settings are no longer removed from a song if the Audio Device buffer size is changed before saving the song.
Resolves an issue in which adjusting parameters on the Channel EQ while playing back might cause minor clicks and pops in the audio signal.
Moving an Amp Designer instance to a different plug-in slot no longer sometimes changes its sound.
“Save as Default” for Audio Unit presets again works as expected.
Video
It's now possible to exchange movie files in a project by dragging a new movie file into the Movie window or the Movie inspector.
Logic Pro X can now work with the following professional video codecs, if OS X Mavericks v10.9 and the codecs are installed: Apple Intermediate Codec, Apple ProRes, AVC-Intra, DVCPRO HD, HDV, XDCAM HD / EX / HD422, MPEG IMX, Uncompressed 4:2:2, XAVC.
There is now a Show/Hide Movie Window command in the View menu when the current project contains a movie.
Resolves an issue in which some movies that were compatible with QuickTime X did not play in Logic Pro X.
Exporting audio to a movie with a portrait orientation no longer causes the movie to rotate 90 degrees.
Logic is now able to export surround AAC audio to a movie even if the original audio in the movie was originally kept.
The visible frame of a movie now updates as note lengths in the Piano Roll are changed.
Import/export fixes and improvements
XML projects imported from Final Cut Pro X now contain volume and pan automation when opened in Logic Pro X.
Exporting a project as an Final Cut Pro/XML file with the “Export as Final Cut Compound Clip” option enabled now behaves as expected.
Includes several improvements to the way Logic handles audio sample-rate conversion when importing Final Cut Pro XML.
Logic now shows a progress bar when importing large Final Cut Pro XML projects.
32-bit float audio files in Final Cut Pro XML projects are now converted to 24-bit files during import so they play properly when imported into Logic.
The start time of imported Final Cut Pro XML projects is now consistently correct.
It's now possible to export Music XML when the Score window is in linear view mode.
Logic no longer shows multiple alerts when importing a Final Cut Pro XML project containing videos in a format not supported by Logic.
Songs created in GarageBand 6 no longer load in Logic Pro X with an extra channel in the Mixer.
Fixes an issue in which audio in a song imported from GarageBand 6 might play back too fast in Logic Pro X.
Logic now offers to include embedded tempo and marker information when using Track Import to bring an audio file into a project that contains no other audio regions.
Simultaneously dragging multiple MIDI files into the Tracks area now behaves as expected when using No Overlap mode.
The default destination path for exported MIDI files is now the project folder instead of ~/Music/Logic.
When importing projects, there is now an Add All button in the Aux import dialog.
The user settings in the Bounce window are now retained after sharing to iTunes.
Split stereo SD2 files no longer incorrectly import as AIFF files when the WAV file option is enabled.
The “Share Song to iTunes” command now creates a playlist with the name entered if there is not already an iTunes playlist with that name.
MIDI events that precede the start point of a region are no longer included when the region is exported as a MIDI file.
Stability and reliability
Includes several fixes related to stability and reliability, including to resolve issues that could cause Logic to quit unexpectedly in these circumstances:
When changing the length of a time-stretched region
When importing tracks from another project
When recording with the color palette open
When bypassing an instance of the Maschine plug-in
When exporting Music XML after applying Enharmonic Shift to some notes
When changing the range on an Environment fader whose style was set to Text
When quitting a project that has a Surround Compressor inserted on a channel strip
When removing a control surface from the Control Surface setup window when the Logic Remote is also present
When changing the range value of a Smart Control during playback.
When reapplying a Time and Pitch operation after undoing a previous one
When dragging an audio region from a take folder to a new song

Thanks Erik,
If nothing else, this huge list of updates and fixes, shows clearly that the Logic Dev team is working hard on fixing and improving LPX to a major degree.... and from the list of fixes done.. show they do read the bug reports submitted!
As an aside....
I recall how all the 'naysayers' prior to LPX (and in some cases, since...) were proclaiming how Logic was dead, the team was being disbanded, we won't see any further development, the Dev team doesn't listen or care... and so on....... I wonder where those people are now?

Reason beat tempo not syncing with Logic Tempo???

Hi,
Made a beat in Reason 5
Exported loop at 137 bpm and saved to external hard drive.
Imported loop into Logic with Logic tempo set at 137 bpm.
Set the metronome on for recording. Pressed record and and beat & metronome are out of sync.
I used beat detection to try find the tempo (said it was 137.1672 or something) yet still the metronome & beat go out of sync...
Any ideas?
I'm going to try saving the beat to the internal harddrive and see if that is the problem.
The external hard drive is USB not firewire.
Hope you can help me...

to bring your reason audio into logic in perfect sync, open reason as a rewire slave to logic and set up a logic aux track input to reason L&R. Set your locators in logic to the loop length and bounce (with "add to audio bin" enabled so its easy to drag it into your song). This locks the 2 clocks together. Which drive your audio is on is irrelevant.

Optional attributes in XML to ABAP transformation

Hi,
I have to deserialize (transformation xml to abap) an xml input file.
I want to use SAP ST (Simple Transformations).
This xml format is using attributes
Such attributes can be transformed in ST with
<tt:attribute name="item_id" value-ref="MATNR"/>
I realized 2 problems:
1. If the xml file does not contain every attribute which is in the transformation.
This can be solved by tt:cond
Sample
          <tt:cond>
            <tt:attribute name="uom" value-ref="BASE_UOM"/>
          </tt:cond>
Now attribute uom is optional. Without the tt:cond the ST prragrom would throw exception if it is not in the file.
2. If the xml file contains an attribute which is not used in the transformation.
I tried to use tt:skip but it is not working for "<tt:attribute name= ... value-ref=... name" but only for "<tt:value-ref=...".
I only want to get the values I need out of the parameter list.
How can I achieve this without defining a transformation for every parameter in the xml file?
Thanks and regards
Michael

Hi,
thanks for reply. It took me into the right direction. You have to distinguish between elements (ordered structured nodes) and attributes (unordered structured nodes). In my case they are using attributes for the values of a material master.
Here is a snippet (sample of the XML):
<?xml version="1.0" encoding="utf-8"?>
<TcPLMXML>
<TCifEngPart item_id="1-3000-3630-00"
               seMaterialType="HALB"
               uom="ST"
               seWeight="2000.0" seWeightUnit="KG">
</TCifEngPart>
<TCifEngPart item_id="1-30000-41002-00"
               seMaterialType="HALB"
               uom="ST"
</TCifEngPart>
</TcPLMXML>
and my transformation:
      <tt:loop ref="MATERIAL_LIST">
        <TCifEngPart>
          <tt:attribute name="item_id" value-ref="MATNR"/>
          <tt:attribute name="object_name" value-ref="MATL_DESC"/>
          <tt:attribute name="seMaterialType" value-ref="MATL_TYPE"/>
          <tt:attribute name="uom" value-ref="BASE_UOM"/>
          <tt:cond>
             <tt:attribute name="seLength" value-ref="LENGTH"/>
             <tt:attribute name="seWidth" value-ref="WIDTH"/>
             <tt:attribute name="seHeight" value-ref="HEIGHT"/>
          </tt:cond>
          <tt:skip>
             <tt:attribute name="seWeight" />
             <tt:attribute name="seVolume" />
          </tt:skip>
        </TCifEngPart>
      </tt:loop>
Length, width and hight are optional in the XML and will be transferred to the corresponding SAP fields if they are in the input file Weight and volume will be ignored.
This means all attributes I don't need I have to put within the tt:skip.
Without this skip the transformation throws an error.
In consequence if the partner system add new attributes I have to enhance the transformation in SAP.
Is there any other way?

MainStage 2.1.1 released

This update delivers improved compatibility and numerous fixes.
Issues addressed in MainStage 2.1.1 include:
- Improved stability of the 32-Bit Audio Unit Bridge
- Fixed problems that caused audible artifacts when using the Playback or Loopback plug-ins[/list]

MainStage 2.1.1 Update
This update improves overall performance and provides numerous fixes. This update is recommended for all users of MainStage 2. Issues addressed include but are not limited to:
64-bit Mode Issues
[*] It is now possible to run FXPansion's BFD2 plug-in in the 32-bit Audio Unit Bridge.
[*] Fixes several issues with the graphical user interface and controls of third party Audio Units running in the 32-bit Audio Unit Bridge.
Stability Issues
[*] In 64-bit mode, a 32-bit Audio Unit plug-in quitting unexpectedly no longer causes MainStage to also quit unexpectedly.
[*] Working with multiple concerts with open plug-in windows no longer causes MainStage to sometimes quit unexpectedly.
[*] MainStage no longer quits unexpectedly if a Patch increment button is assigned to a sustain pedal, and MainStage is switched from Layout mode to Edit mode while receiving continuous sustain messages.
[*] Resolves an issue that could cause MainStage to quit unexpectedly when removing or changing an audio device.
General Issues
[*] Resolves an issue that could cause loss of audio output when “Display audio engine overload” messages were enabled.
[*] Resolves an issue that could cause an unexpected sound when rapidly switching patches in a concert that contains more than one multi-output Ultrabeat instance.
[*] Duplicate MIDI events no longer sometimes lead to stuck notes.
[*] Resolves an issue that could cause MainStage to stop responding when simultaneously adjusting parameters for multiple controls.
[*] Resolves an issue where MainStage could stop responding when opening an auto-saved copy of an already open concert.
[*] Sustain pedal events with values between 1-126 no longer cause multiple triggering of mapped actions.
[*] Switching out of Layout mode while sending a note to a drum pad screen control no longer results in stuck notes.
[*] Drum pads now correctly display all parameter values.
[*] “Do not pass through” now works as expected with screen controls set to send to a specific MIDI destination.
[*] The Keyboard window now sends MIDI notes with velocity values of 100, as expected.
[*] The Layer Editor for external MIDI instruments is available again.
[*] Resolves an issue in which there could sometimes be audio "pops" when auditioning patches while notes are sustaining.
[*] Keyboard assignments are now reliably maintained for non-auto assigned keyboards when opening concerts created in MainStage 1.x.
[*] The right arrow for setting the high range in the Parameter Graph for mapped knobs now works as expected.
[*] The screen no longer flashes if a second concert is opened while a plug-in window is open, and Do Not Close is chosen for the original concert.
[*] Resolves an issue introduced in MainStage 2.1 that could lead to an accidental overlap of split points.
[*] Resolves an issue in which the left side key range of a split made no sound in some rare cases.
[*] MIDI note-off events are no longer handled as MIDI note-on events with a velocity of 0.
[*] Velocity scaling is now correctly performed with drum pads.
[*] The workspace aspect ratio now immediately updates to follow changes to the Layout mode aspect ratio.
[*] Using pitch bend on the Musical Typing Keyboard no longer causes a constant stream of erroneous pitch bend messages to be sent.
[*] The vertical scroll bar controls in the Template Chooser grid view now remain fully functional at all zoom levels.
[*] The items in the Help menu now remain available when the Template Chooser is open.
[*] If the preference for Silence Previous Patch is set to “Immediately,” MainStage no longer plays back unexpected segments of audio when switching away from and then back to a Software Instrument patch that has a plug-in with a long decay.
Screen Controls
[*] Pickup mode no longer behaves like Jump mode when assigning a hardware control that is at a higher initial value than selected screen control.
[*] Waveform screen control mappings are now reliably maintained when the sample rate is changed.
[*] The Screen Control Inspector now properly shows the status of the Mod Wheel control when reselecting it after it has been set to Block, and then another screen control has been selected.
[*] Meter screen controls now follow changes to channel strips that change between mono/stereo.
Parameter Mapping
[*] Number keys mapped to commands now reliably trigger the commands instead of patch changes in Edit mode and Performance mode.
[*] The Current Set action now reliably recalls a specific set when the min and max ranges are set to the same set name.
[*] The Current Patch action now works reliably when the Invert checkbox is selected.
[*] Range settings are reliably maintained for the Current Patch Number action.
[*] The Range pop-up for Current Patch Number mappings no longer show duplicate values.
[*] Undo after changing a mapping and then deleting a pedal from the Pedalboard now works as expected.
[*] Mappings of alias patches are now handled correctly when a plug-in on the parent patch is changed.
Playback Plug-in
[*] Resolves a rare issue where the Play button on the Loopback and Playback plug-in could remain lit with playback stopped.
[*] Resolves an issue that prevented a file that had been loaded and then removed in the Playback plug-in from being loaded again.
[*] If files containing tempo changes are imported into Playback, the following warning only appears once per session: “File contains tempo changes. One or more of the files you are importing contains tempo change markers. This version of MainStage does not support importing files with tempo changes.”
Loopback Plug-in
[*] The Position field in the Loopback GUI now reliably displays all positions at all loop lengths.
[*] After using Undo to remove previous recordings in the Loopback plug-in, recording a loop that crosses the cycle point no longer removes a portion of the loop.
[*] Using Undo to remove a take in the Loopback plug-in no longer removes crossfades at the cycle point.
[*] In the Loopback plug-in, Fade-out now works properly when applied to an overdub performed over reversed material.
[*] Resolves an issue in which enabling Reset to Saved could lead to recording in Loopback starting automatically when a concert was opened.
[*] Resolves an issue in the Loopback plug-in where immediately triggering a Software instrument after going into record could cause an unexpected sound.

[AS] How to test the presence of at least one table?

Hello everyone,
I would like to test for the presence of at least one table in a document before starting a process (on edge strokes).
I found this, but I do not know if this is really effective:
                              set CountOfTables1 to count of tables of every story
                              set CountOfTables2 to every table of every story
The first gives me a list of the number of table in each story; the second gives me the objects reference of every table.
Is there another way?
TIA.
Oli.

Marc
The test I did for nested tables stank (table pasted in rectangle and that rectangle pasted in a table ). It does not work for nested tables
I tested .isValid and it's a lot slower.
Uwe
Yes, I noticed that difference after posting my eeakk comment.
Using slice(0) after the getElements can make a big difference but still the simple length going to be quicker in this case.
Also the getElements without the slice(0) will return "too many elements" if there are to many elements (between 1500 - 15,000).
On the other hand for repeated access of the variable (looping) it's as know normally quicker to use the getElements().slice(0).length than just length
In summary
1) Your anyItem() method is going to be very quick on a document which has a high ratio of stories containing tables.
2) Although your method could and possibly probably be 100 times quicker than mine I would definitely use my method in terms of typing time and space verses the 1/2 second it might save on execution time per 10,000 tables.
3) The only accurate method (in this thread) for counting the tables including nested and footnotes is Marc's Grep method.
So I guess the 3 of us can share first place.
I just wonder if using the same technique as Marc used in our discussion sometime back on nested buttons might get to a quick count than using the Grep method here.
Clearly needs to be repeated on different types of document setups one can try the below
if (!app.properties.activeDocument) {alert ("Really!?"); exit()};
var scriptCount = 1;
// Script 1 table.length
var doc = app.activeDocument,
      start = Date.now(),
      t = doc.stories.everyItem().tables.length,
      finish = Date.now();
$.writeln ("\rtable.length Script (" + scriptCount++ + ") took " + (finish - start) + "ms\r" + ((t) ? t + " Table" + ((t>1) ? "s" : "") : "Diddlysquat"));
// Script 2 getElements
var doc = app.activeDocument;
var start = Date.now();
var t = doc.stories.everyItem().tables.everyItem().getElements().length;
var finish = Date.now();
$.writeln ("\rgetElements Script (" + scriptCount++ + ") took " + (finish - start) + "ms\r" + ((t) ? t + " Table" + ((t>1) ? "s" : "") : "Diddlysquat"));
// Script 3 getElements.slice(0)
var doc = app.activeDocument;
var start = Date.now();
var t = doc.stories.everyItem().tables.everyItem().getElements().slice(0).length;
var finish = Date.now();
$.writeln ("\rgetElements.slice(0) Script (" + scriptCount++ + ") took " + (finish - start) + "ms\r" + ((t) ? t + " Table" + ((t>1) ? "s" : "") : "Diddlysquat"));
// Script 4      isValid
var start = Date.now();
var t = doc.stories.everyItem().tables.everyItem().isValid;
var finish = Date.now();
$.writeln ("\risValid Script (" + scriptCount++ + ") took " + (finish - start) + "ms\rThe document contains " + ((t) ? "tables" : "no tables"));
// Script 5   Marc's Grep
var start = Date.now();
var t = countTables();
var finish = Date.now();
$.writeln ("\rMarc's Grep Script as said only accurate one but slow (" + scriptCount++ + ") \rtook " + (finish - start) + "ms\r" + ((t) ? t + " Table" + ((t>1) ? "s" : "") : "Diddlysquat"));
// Script 6 very lot of anyItem
var start = Date.now();
var myResult = atLeastOneTableInDoc(app.documents[0]);
var finish = Date.now();
$.writeln ("\rUwes Anyone for Bingo Script (" + scriptCount++ + ") took " + (finish - start) + "ms\rThe document contains " + ((myResult) ? "tables" : "no tables"));
// Script 7 anyItem length
var start = Date.now();
var myResult = detectATable();
var finish = Date.now();
$.writeln ("\ranyItem length Script (" + scriptCount++ + ") took " + (finish - start) + "ms\rThe document contains " + ((myResult) ? "tables" : "no tables"));
// Script 8 anyItem elements length
var start = Date.now();
var myResult = detectATable2();
var finish = Date.now();
$.writeln ("\ranyItem elements length Script (" + scriptCount++ + ") took " + (finish - start) + "ms\rThe document contains " + ((myResult) ? "tables" : "no tables"));
//FUNCTION USING anyItem() EXTENSIVELY:
function atLeastOneTableInDoc(myDoc){
    var myResult = 0;
    if(myDoc.stories.length === 0){return myResult};
    var myStories = myDoc.stories;
    //LOOP length == length of all Story objects
    //using anyItem() for checking length of Table objects
    for(var n=0;n<myStories.length;n++){
        if(anyStory = myStories.anyItem().tables.length > 0){
            myResult = 1;
            return myResult;
    //FALL-BACK, if anyItem() will fail:
//EDIT:    if(!myResult){
        for(var n=0;n<myStories.length;n++){
            if(myStories[n].tables.length > 0){
                myResult = 2;
                return myResult;
//EDIT:       };
    return myResult;
}; //END function atLeastOneTableInDoc(myDoc)
function detectATable(){
    s=app.documents[0].stories;
     if(s.anyItem().tables.length){
        return true; // Bingo
   for(var n=0;n<s.length;n++){
        if(s[n].tables.length) return true
    return false
function detectATable2(){
    s=app.documents[0].stories;
     if(s.anyItem().tables.length){
        return true; // Bingo
    var sl = app.documents[0].stories.everyItem().getElements().slice(0);
   for(var n=0;n<s.length;n++){
        if(s[n].tables.length) return true
    return false
function countTables()
    app.findTextPreferences = null;
    app.findTextPreferences.findWhat = "\x16";
    var t = app.properties.activeDocument||0;
    return t&&t.findText().length;
P.s.
Marc,
A bit of homework. I didn't test it on the above but I found the your highRes function trimmer seems to have a large favoritism to the first function to compare.
I was testing 2 prototypes and swapping the order swapped the result. One can make the prototypes the same and see the time difference.

Internet Connection Loss Repeatedly

So for past two days my modem(the internet light) keeps turning off every 20-50 mins. I've turned the whole thing off and tried reseting it and still this problem persists. I came on the forum looking for similar problems, and I'm wondering if this rain has caused an outage near York, PA which is causing my connection to drop so often. I;ve had this problem in the past and it eventually got to point where it dropped every other 3 mins.

Johnvolt, is it only the Internet light going out? Or the DSL light as well? As suggested posting some tranceiver stats would help a lot.
@Bk_Bridge Both your dowload and upload speeds aren't running at full bit rate. You are also on a range extender card for the DSL. A loop length (length from the Central Office to you) would also tell you a lot about your service. Based on the attenuation numbers though you seem to be close enough the office to support your service. Also creating your own post will help draw attention to the issue you are experiencing.
@Josieedvl Tranceiver stats would be a great start to your problem. Also as suggested above creating your own thread would help generate responses.

Verizon & Loop Length

Similar Messages

Maybe you are looking for