Cycle mode bug???

Hi,
I'm working on a small song and have my cycle markers set to the beguining and end poins when I was composing the piece. However when I was finished I turned off cycle mode and played the piece and it kept on cycling!!!
I selected on cycle mode another part but it would only work on the first bars!!! In fact it behaves just as if cycle mode was engaged on my past setting. Can't play from anywhere elso on the song and always repeat itself.
Anyone noticed this?
By the way... how do I submit a bug to apple, I keep coming across them.

Hi Guezz,
I never had this problem!
Did you try the troubleshooting basics???
http://docs.info.apple.com/article.html?artnum=305927
Here is the feedback site.
http://www.apple.com/feedback/logicpro.html
Cheers Eddie

Similar Messages

Crackling and playback errors with cycle mode enabled

Hi Folks,
just noticed that sometimes when i use cycle mode, there's a crackling sound when i hit playback. The audio file itself is 100% clean and undistorted, as is the normal playback. Only if i enable cycle mode, the crackling, popping, even bigger playback errors as echos are there. However, it's only at the start of the cycle or when the cycle repeats (jumps back to it's start).
I fiddled around with buffer settings and the Cycle Algorithms in the preferences, but to no avail.
Anyone out there has a tip how to solve this?
Fox

Hi Erik,
Also try and answer some questions I probably haven't asked.
I did this and it helped WOW! Thanks!
However, here's the solution for future desperate questions regarding this bug: It was a corrupted region (anchor or something like that). The file itself was okay, but the region in the arrange was somehow corrupted. I solved the problem by deleting the region and re-dragging it into the arrange from the bin.
Cheers, Fox

I'm in cycle mode, and 'merge' is clicked in preferences. However, when I record, my previous track data keeps getting overwritten. Does anyone know what I'm doing wrong. Interestingly, I can still see the data in the region.

I'm in cycle mode, and 'merge' is clicked in preferences. However, when I record, my previous track data keeps getting overwritten. Does anyone know what I'm doing wrong. Interestingly, I can still see the data in the region.

jamestait wrote:
when I record, my previous track data keeps getting overwritten.
since you didn't specify, are you recording in a single take?
http://www.bulletsandbones.com/GB/GBFAQ.html#multipassrecording
(Let the page FULLY load. The link to your answer is at the top of your screen)

Cycle mode key command

Hi. I know this may be trivial but I've been searching everywhere for a key command for toggling cycle mode with no success. Anyone who knows would be so kind to help. Also, is there a list of default key commands anywhere that can be found? I looked for it in the manuals but couldn't find it. Thanks in advance.

Did you customise that yourself, or is it one of the language/region differences?
I've been with Logic since Logic 1.x. I've been known to customise my own key commands plenty (which is the key to a powerful, fast, efficient and bespoke workflow).
They evolve over time, of course. Like how they stopped letting you assign the tab key in LP8. Tab has been my "set rounded locators and play and cycle selection" for fifteen years until LP8... grr...
I set up what makes most sense to me, not what makes most sense to some random guy in Hamburg.
No one else works in Logic the exact same way as me, or uses the same functions in the same way. I set up the things I need to keys that make the most sense. I may constantly use function X and therefore assign to a single key, and never use function Y and so deassign it. You may rely on function Y but never user function X at all. So how can a generic set of key commands work optimally for every persons unique workflow and requirements?
If you already know where to look & how to search!
Yeah, of course. I'm just talking general cases really...
The main problem is often not knowing what something is called, therefore not having the ability to easily search the documentation. That's where other users can give a valuable heads up.
Eg type "key commands" into the search of the manual...

Blending modes bug

I want to report a bug in the program Premiere Pro CC 2014. it first appeared in version CC.
blending modes bug
Compound
Arithmetic
Composite
each time one and the same
Describe a situation in which there is this bug
I apply a preset, any of these effects, or similar so that the clip is mixed with himself blending mode screen. so I very gently increases the brightness of the image.
and sometimes there is a problem. clip is not blended with himself simultaneously. but with some time offset. it turns out that the image becomes lighter, but doubles, blended two different frame.
strict laws, I did not reveal.
but most often the bug occurs when the cut clip already applied effect. or when the effect is applied to the clips that are not on the first track. or when the effect is applied to multiple clips at once.
I found some solution, but it is not very convenient.
if you go to the drop down list with the names of the tracks and re-select the same track, the bug disappears.
for example, we had chosen the "video 1", we once again choose "Video 1" and everything is current, as it should be.
sorry for my english, I am Ukrainian.
and sorry for wedding too)))

Here is another example. guys who have still a problem?

Punch in problem-Why does cycle mode activate and snap to somewhere else when I set up a punch?

Punch in problem-Why does cycle mode activate and snap to somewhere else when I set up a punch?

Because whoever programmed it must be ********, I've dealt with this issue long enough. I've sent Apple feedback on this issue long ago and nothing has been done yet. The only work around is to try and remember that every time you double click in the punch line to hit the c button to turn it off before you start recording or you have to drag your punch line around all the time, what a pain in the ***.

Logic Pro 7 & Reason 3.0 - Cycle Mode Sync

Hi Forum,
I am using Logic Pro 7 and reason 3.0 simultaniously via rewire. I am having a problem when playing back a song in cycle mode.
I select a section (let's say bars 1 - 8) to loop in cycle mode, but when I play the selected section it does not loop smoothly. When the SPL reaches the end of the cycle selection point (end of bar 8) and proceeds to start at bar 1 again, I hear a skip in the audio. It does not loop perfectly like I want it to.
Can someone please suggest why this is occuring and how I could correct this problem so that it loops smoothly and perfectly?
Thank you.

here ya go
http://docs.info.apple.com/article.html?artnum=300040

Logic Pro 9 why am I hearing the last take when I'm in cycle mode and trying to produce multiple takes?

Hi all,
More questions about recording in Logic Pro 9. Just wondered...is it called cycle mode when I have an area I want to record multiple takes at? And, why am I hearing the last take when it is cycling at take 2, 3 etc.? Please reply. Thank you.
David

Have a look here:
http://youtu.be/e5PbrWJrq4k
......and here:
http://youtu.be/M_SUrJRuENw
Have a nice day!

What is Cycle mode?

The "get started" part of Logic Express 8 says to "turn off Cycle mode if it is enabled" and then doesn't bother to explain what that is or how to do it. It doesn't say why it is, either. Well, what is it and how do I turn it off...why do I want to turn it off? I need to know about Cycle mode, however, because when I record something the phrase keeps repeating. How do I turn it off? All I want is simple multi-tracking. All these "features" are presently getting in the way. Someday I'm sure I'll appreciate them, but right now I just want to record real instruments totally dry, one at a time. Think 1978 and you get the picture. I'll get to the 21st century eventually, but not right now! Thanks in advance.
MGuilfoile

Unless you want to record multiple takes or have your phrase repeat itself then you need to disable cycle mode by going down to the right side of the transport bar at the bottom of the arrange window. The second button over on the right side that looks like two arrows going around an ellipse is the cycle mode button that you want to turn off.

No sound after recording MIDI using cycle mode take folder

I'm going through the Apple Certified training book "Logic Pro 9 and Logic Express 9". My project and global settings are pretty close to what comes with Logic when you install them. I.e. I haven't been messing with any settings not explicitly described in the book.
I'm at the chapter on MIDI recording, and am learning about MIDI cycle recording to a take folder. (I've already done this successfully for audio.) But, Logic does not seem to be behaving the way the book describes. I have recorded 3 takes. I see a MIDI take folder region after I've recorded, and I can double-click or click the arrow on the top left to reveal the 3 takes. All 3 take regions are white - as though none are selected. The region in the actual track (the take folder) above all three takes is green. When I try to play, in any combination (ie, Soloed, not soloed, other tracks all muted, no tracks muted) I cannot hear the MIDI take. I tried selecting the three different takes, both by clicking on them, and choosing from the drop down menu on the top-right of the take folder. I see the notes in the take folder display (the one that is green) changing when I select a different take, but the takes themselves always stay white. Although, the region header for the take becomes darker, as though the region is being selected, but the region is not green.
Is there something I'm missing here? Why can't I hear anything from these takes? I can open up each take in the Piano Roll editor, and click on the keyboard keys to hear notes, as well as clicking on the notes themselves and hear those. But when playing, I get no sound.
I tried "flattening" this take folder. It creates 3 new tracks below the current track. All regions are again white, and clicking on them does not make them turn green. I can play, and I hear all three takes playing at the same time. If I try to mute one of the tracks, ALL three tracks become muted, as though the mute button has been grouped to all these tracks. But I looked at the mixer and do not see any other channels have been created, not even for these new tracks. And they have not been assigned to a group either.
I'm not sure if I'm doing something wrong, or if this is a known bug?
Rob

Rob Ross wrote:
I tried this again on the same track, a few bars away. It worked this time. I've tried it 3 times now, and each time worked as expected. So I'm thinking this is a bug in Logic that caused the problems the first time?
The "white" takes are muted >>regions<<, not tracks.
You should be able to unmute (demute?) then using the "mute" tool.
And... I believe you are correct, this is a bug in Logic that's been around for a while.
pancenter-

Full screen mode bug in Safari?

In Safari, running in full screen mode, if a link opens a file (eg an Excel workbook), sometimes the Excel (non full screen) window will open over the top of the Safari full screen window. When that happens it's impossible to get access to the Excel window, as clicking on it will jump to the desktop "space" (where the window should have opened?). The only way out of the problem is to move to the Safari full screen "space" and take Safari out of full screen mode using the button in the top right corner (Esc doesn't work in this case). After that I can access both Safari and the Excel window no problem.
This doesn't always happen, but it has happened enough times to be annoying, and also happens with other apps (eg Preview), not just Excel.
Anyone else had the same problem?

It is a bug. If you start to search for something with the Safari not in full screen mode the history and predictive search functionality is there. If you then expand the application window to full screen it the search field will continue to work as expected. However, if you open the application and first expand it to full screen view before using the search field it will not work properly; the history will be inaccessable and the predictive search will fail. In order to restore functionality, hit 'control+command+F' to return to non-full-screen mode, type something in the search field or access your search history via the hour glass and then return to full screnn mode. The search field will now function normally again. This is definitely a bug and this behavior explains why the search seems to be fixed at times, and broken at others.

Flash Builder Design Mode Bug Workaround (!!!)

I've been fighting this annoyance since FB4 came out, and while I still don't think that custom/embedded fonts in design view are fixed by this, I've been able to reproduce this "fix" (workaround) to get design view to show fonts/theme correctly under some very specific circumstances on two separate PCs.
If anyone from Adobe sees this I'd like to know whether this sounds familiar or is possibly logged as a bug already somewhere in JIRA.. if not I could probably do that as long as it won't be a wasted effort.
The problem:
You're using a Halo theme but certain CSS settings (specifically and possibly limited to FONTS) don't work properly in design view even though they work fine in Flash. Essentially this makes design view practically useless since choice of font family, size, and weight can effect component sizing if you aren't hard-coding component sizes (ugh)... ruining your efforts to use design view for UI design if your UI has any level of complexity (or uses absolute positioning at all).
The specific circumstances seem to be:
You're using the Halo theme (you have no special 'skinning' requirements and want Halo defaults w/only CSS customizations)
You've upgraded a Flex 3 project to Flex 4 SDK (not sure if this is needed to reproduce the issue)
Using a regular non-embedded font (embedded fonts still do crap out, but even this 'workaround' doesn't fix that problem)
You're using swc library files such as the Swiz lib, Mate, Flexlib, etc. (I think it's ANY swc, not specific to any one)
This may also only apply when using an "mx only" project (no Spark), since we're using Halo here
The two part fix (as far as I can tell you need BOTH before design view works correctly):
In .actionScriptProperties, add the following bolded line after the compiler tag like so:
</compiler>
<theme themeIsDefault="false" themeIsSDK="true" themeLocation="${SDK_THEMES_DIR}/frameworks/themes/Halo"/>
<applications>
(I think this may only apply to 'upgraded' projects, as the line does seem to be present in newly created FB4 Halo projects. My guess is that an "upgraded" project should have such a line added, but doesn't get it due to an oversight/bug.)
The somewhat painful, and definitely odd part. Remove all your SWC library files from /libs. Grab the source code for the libraries and drop them into your project's /src folder as if you'd written them yourself. (This may require some research and knowledge on special requirements to build the libs, such as with Swiz's compiler metadata compiler settings which you need to put into your project's settings.) After you get things set up right and the project compiles again, doing a refresh of design view should finally give you proper looking Halo controls and fonts so they look identical to the Flash runtime view.
Why this works, I've no idea. I suspect it has something to do with that stupid and annoying (and supposedly 'harmless') design mode warning message you get when you include a library like Swiz or Mate in your project. (Design mode could not load xxxxxxxxxxxxx.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)) - this warning doesn't break your application, people seem to think it's just a harmless warning..but is it breaking design view?
If anyone has any idea what's going on here, why this 'fixes' the problem (a better work around), or has any other insight I'd love to hear it. The combo of needing to do two things (in my specific case) to fix the problem really made this a ROYAL PAIN, I still can't believe I found it.

Hi Fernando, sorry for the delayed response. CSS Design Mode is not available for Flex 4 projects, but it is still available in Flex 3 projects. The reason for this is that designing components in Flex 4 is often a lot different, since it relies highly on the new spark skinning architecture. There is, however, an Appearance panel available in design view which supplies a set of the main inheriting styles. Setting these styles in the Appearance panel will result in assigning values to a global style selector.
I hope this helps,
Rob

Photoshop CS3 Actions Batch mode bug?

I posted this in the Mac forum but received no responses after a couple of days, so I am trying it here.
Photoshop CS3 Actions seem to have a bug such that when used in Automate > Batch mode it will use the name of the first file opened in the batch session for every file processed in that session. Since that name is used in Save step, this means having to deal with the "File Already Exist" dialog for every file in the batch because it is attempting to save at the designated location with the same file name. If the continue option is chosen each time, the final result is one file with the first opened file name, but with the contents of the last processed file.
To confirm that this is a problem particular to the opening step, I have disabled all processing steps as well as the saving step by toggling them in the Actions panel. I then ran the action in batch mode on a folder containing 4 files. This resulted in 4 opened files all with the same name but different image content.
This was with the "Override 'Open' Action Commands" checked/not checked, and the "Suppress File Open Options Dialogs" checked/not checked. The problem described also occurs when using a Droplet.
By comparison, Photoshop CS exhibits the expected behavior: when an action is used in batch mode to process an entire folder of files, the name of each file is retained after opening and used after processing in the save or export step.
The above described behavior of CS3 is a change acquired along the way to the CS3 version (I do not have the CS2 version to test). But more importantly, can someone please report if the CS4 version behaves as I described for CS3, or if it has been returned to the CS behavior?
OS X 10.4.11
G4 800 MHz 2 MB L3/processor 1.25 GB SDRAM
Is this a known bug?
Al

Hello Miguel,
I was going to come back to post some of my findings, one of which relates to your staement:
"- The open command created by Photoshop 6 doesn't keep the file's name, it is a much simple open command, and so it opens the file with the own file's name."
In my case I found that my CS version of the "same" action worked, while the CS3 version failed, precisely because the earlier one records less detail for the open step.
My need is to convert dozens of Quark pdf files to GIF and JPEG files for the web. What I found after several days of testing is that it is best to record the opening step in CS3 NOT using a pdf file, so that the "Open As Generic Pdf with 'Name____' " would not be coded into the opening step. Instead I recorded the whole action using a PSD file. Then I can proceed to run it in Batch mode choosing a folder of Quark pdf files as the source location with "Override 'Open' Action Commands" checked, and the "Suppress File Open Options Dialogs" checked, and it opens all the pdf files just fine in some background process, not getting stuck in the details of the file name, and proceeds to cary out the flattening, saving, and closing steps to my chosen target location and uses the finder file name of each pdf files in the source folder to save a filename.ext in the Target folder.
Contrary to what I stated in my original post, "Override 'Open' Action Commands" checked/not checked does indeed make a difference. If it is not checked, the files do open in batch mode, but the other steps are not performed. There is much more about this that I would like to know, and this may not be a general solution for all types of files that a user may wish to process in batch mode, but it works for my case. The main trick is to use as simple an opening step as possible when recording the action, and then letting Photoshop use whatever background process it requires to open a particular file type. I tested this by manually saving a pdf file to each of the twenty some odd formats available in the save as dialog to a Source folder, and then proceeded to batch process that folder with the action described above, and it worked for all except one.
So while there may not be a bug involved in this problem, there certainly is a lack of documentation about how the "improvements" in the opening step in newer versions of Photoshop affect using Actions in Batch mode.
Please comment if you can further explain any of the reported results. In particular, what is the situation in CS4?
Thanks,
Al

Disk Mode Bug

Here's the situation: the "Enable disk use" in the iPod preferences within iTunes is disabled (not checked). I plugged in my nano after putting it in Disk Mode by holding the Center and Play button simultaneously while it's resetting.
The nano will show up in the Finder for a moment and then it gets unmounted. The nano screen now shows "OK to disconnect" but the nano is still "mounted" within iTunes.
I believed this is a bug for a)the user has the intention of using the nano's storage space in the Finder by placing it in Disk Mode and the nano's state should take precedence over the iPod preference in iTunes. b)Inconsistency and possible data loss/corruption is also introduced with the nano showing "OK to disconnect" on its screen but iTunes still has ability to interact with the nano.

I put my iPod in Disk Mode on some occasion when I need to use it for temporary storage or putting notes in the iPod. Since I don't use Disk Mode all the time, I left it off in iTunes preferences and I would use the iPod's state to determine whether I'm in Disk Mode or not.
The bug I mentioned above seems to be caused by iTunes 5 for my 3G iPod is now exhibiting the same behavior.
The diagnostic or debug mode for the iPod has different button combinations.

Possible CVI13 Debug Mode Bug

I have found a possible bug in Debug mode in CVI13. The issue is a bit complicated. It has to do with returning a struct from a function, then referencing a char pointer in that struct in a call to sprintf. The basic code is:
struct TEST_STRUCT
char *StructString;
} TestStruct =
"Struct String"
struct TEST_STRUCT TestFunction(void)
return TestStruct;
// somewhere in the code...
sprintf(Buff, "%s", TestFunction().StructString);
When executed in Debug mode, the sprintf line generates the runtime warning, "Attempt to read beyond end of string". If you select Continue the string in Buff is incorrect. If you run the same program in Release mode it works as expected. I found this when trying to debug a project previously built in CVI 12. CVI 12 does not generate this warning. I also tried refercing the string directly in CVI 13:
sprintf(Buff, "%s", TestStruct.StructString);
This works correctly. I also tried using an array in the struct instead of a pointer:
struct TEST_STRUCT
char StructString[50];
} TestStruct =
"Struct String"
This also works correctly. I also tried using strcpy instead of sprintf:
strcpy(Buff, TestFunction().StructString);
This also works correctly. The issue appears to be specific to returning a struct and then referecing a char pointer in that struct as a parameter to sprintf.
A sample project is attached.
Tony G
Attachments:
Debug String Problem.zip ‏52 KB

Thanks for pointing this out, I'll go ahead and file a Corrective Action Request on this.
Rob S
Applications Engineer
National Instruments

Cycle mode bug???

Similar Messages

Maybe you are looking for