BEC

Thanks for the reply David I have found since I posted my original question that in some of my other Logic projects, the green cursor does not vanish when it reaches the red recording bar and I ran a test by opening and closing the original project that had the problem and the projects where it was ok , without shutting Logic down - so the problem seems to be project specific, rather than a global setting I did find that on the score page in the menu along the top - right at the end is 'view' and one of the choices in this drop down menu is 'Scroll In Play' but there is no indication to show whether this is selected or deselected and I have yet to test whether this has any effect on the problem of the cursor vanishing when recording.

Hi, can anyone on this forum help with a problem that has (seemingly) just appeared for me in Logic Pro 9? When I'm recording a cellist or violinist, I produce the score for them using a software instrument channel and the EXS 24 sampled instruments plug-in. I play in the cello/violin part via a midi keyboard, which creates a midi region on this track and I then select the midi region and open a new score window by going to the Logic menu bar along the top and choosing 'window/score'. I then move this score window over onto a separate screen in front of the cellist, replacing their sheet music. In the Logic Arrange window, I use the green 'cycle' bar along the top to select the section I want to record into, including a lead -in of several bars before the recording kicks in. I use the red 'autopunch' function to set where the actual recording starts and stops. Record enabling my audio tracks, I then press record and I watch the green cursor move along the score in the score window - giving my cellist a guide to when to come in, but when it reaches the red autopunch bar and the recording starts, it vanishes! When I stop recording, the green score cursor appears again, in the location it should be at the point in the project where I pressed stop. This problem has only just started to happen I believe because for years now the cellist has commented on how useful it is to have the green cursor move along the score in time with music in his headphones. Can anyone suggest a solution to this problem please? Many Thanks

Ok - thanks for clarifying that.

I think the original WAVE bounce remains at 88.2k - I've just bounced two WAVE files at 88.2k, one with an mp3 which triggered the 48k conversion. Both WAV files are the same size .

Ah I've sussed it - thank you for bringing my attention to that. I was bouncing to WAVE 24bit at 88.2k but I was simultaneously bouncing to mp3 as well - it was the mp3 conversion bounce that was producing the message. - I just tried bouncing a WAVE 24bit 88.2k on it's own and no problem - didn't get the message, then did another bounce with mp3 selected as well and up comes the message - I obviously didn't realize that the mp3 format must be limited to 48k. So I'm guessing that every time I have bounced my project files to WAV and mp3 simultaneously, Logic has converted my 88.2k WAV file to 48k to then make an mp3? - but is my original WAV file bounce still at 88.2k or is it now at 48k? Maybe if I want to save my project bounces at the original project sample rate of 88.2k, I'll have to forego creating an mp3 at the same time?

Hi I've been working at a sample rate of 88.2k in my Logic projects now for a few years. All my Logic projects are stored on an external hard drive connected via USB so when I bounce a mix out to the 'bounces' folder in each respective project I'm getting a warning message: 'The destination format does not support sample rates above 48k. Logic Pro can convert the bounced data's sample rate - do you want this?' I have to agree because I don't have any other option but I'm not sure what the Logic sample rate conversion is doing to the audio and as I'm working at 88.2k sample rate I'd like to keep the bounced files the same, at least until the final conversion to 44.1 for CD. I'd be interested to know what other forum members thoughts are on this issue - whether they think it matters and if anybody has a workaround. Thanks BEC