MOTUnation.com

monkey man wrote: Yup, it does seem to be the full mix that rises in volume for a second or so.

Ah! Thanks for confirming this.

Nicky wrote: A surf of the Logic boards (!) could yield less pain.
Besides, if it was an OSX issue, we'd surely have heard something from SOS and various other commentators.

Maybe you're right, but it's likely that the calibre of comments about any Logic/DP comparisons over there will be close to 12-gauge. Besides, it would be nice to do a hands-on side-by-side in house just to eliminate as much spec as possible.

No, we're not happy about the notion of installing Logic on the new machine. I *am* enjoying the concept of having only one DAW installed for the moment.

Nicky wrote: Look at it this way, if it rears its ugly head during a critical pass, the chances of its happening immediately thereafter are practically zero, meaning you'd then have a window in which to do the bounce, recording or mix.

Monkey-thoughts for the Fwogster.
Nicky

Yuppers. As mentioned earlier, it's won't be mission-critical for a few weeks yet.

Hanging tough,
B. Foote

I posted before about being so happy about the faster save times.

Now, something has changed.

The save time is now much longer than 5.11.

I am flushing undo etc.

What is up with this?

5.12, fixed bugged audio drivers and went back to audio 1.4.1 as per tech support so that my old cue mix setting would load..(there iis an acknowleged bug in audio 1.4.3 where it doesnt allow you to load old cue mix set ups...)

and as of now..all's working well.

toodamnhip wrote:5.12, fixed bugged audio drivers and went back to audio 1.4.1 as per tech support so that my old cue mix setting would load..(there iis an acknowleged bug in audio 1.4.3 where it doesnt allow you to load old cue mix set ups...)
and as of now..all's working well.

Way to go, Hipster; that's good to hear.

Fwoggy B Foote wrote:

Nicky wrote:A surf of the Logic boards (!) could yield less pain.
Besides, if it was an OSX issue, we'd surely have heard something from SOS and various other commentators.

Maybe you're right, but it's likely that the calibre of comments about any Logic/DP comparisons over there will be close to 12-gauge.

Ha! 12-guage.

Fwoggy B Foote wrote:Yuppers. As mentioned earlier, it's won't be mission-critical for a few weeks yet.
Hanging tough,
B. Foote

Good luck, Fwoggy; be careful not to break the branch, eh?
You don't want the green-furred Gestapo all over you; they once gave me the only geen rash I ever had.

Try re-entering the Zoo at 3:00AM after a night on the town with said rash; it's not a pretty scene.

toodamnhip wrote:5.12, fixed bugged audio drivers and went back to audio 1.4.1 as per tech support so that my old cue mix setting would load..(there iis an acknowleged bug in audio 1.4.3 where it doesnt allow you to load old cue mix set ups...)
and as of now..all's working well.

Way to go, Hipster; that's good to hear.

I just had a "crash on save".

I had recorded 2 audio passes and I hit save.

DP 5.12 vanished.

No warnings or info boxes.

I reopened DP and it didn't ask me about finding lost audio.

The audio was gone.

I'm very worried now.

Audio usually is never "gone". Try to go to the Audio Files Folder for that project, select ALL of the files (in the Finder) and then drag them into the Soundbites Window of that Project. DP should re-register all the files and they should show up. This has saved my arse many a time!

waterstrum wrote:I'm very worried now.

Don't worry, waterstrum; the hammerhead shark's correct.
Just drag 'em back into the SB window.

There was a thread in which we discussed this at some length a week or two ago, but the advice you've been given is all you need to know.

Thank you gentlemen for saving my day.

You are both correct.

The audio is still in the Audio Files folder.
I always thought the soundbites window was a direct reflection of the AF folder.

I dragged the missing files back and I'm very relieved.

Thanks monkey and hammer.

Just don't give a hammer to a monkey!

Giv'em DP instead!

hammerman wrote:Just don't give a hammer to a monkey!

Or a monkey to a hammerhead. Not pretty.

hammerman wrote:Giv'em DP instead!

Like hammers through the power-farts, so is the glaze in my eyes.
You really know how to warm a monkey's fart, er, heart, don't you hammer?

Say, do you know MC?
MM

I guess I experienced my first 5.12 specific problem last night (all of my other problems have been related to OS 10.4.9 and/or other products).

In Region Edit mode for MIDI data, I couldn't get certain combinations of Velocity change to work properly. This was last night and I lost a lot of time over it while trying to beat a deadline, so didn't have time to write it up then and by now do not remember all of the specifics.

As I recall, it specifically happens when one selects the randomise parameter, and only occurs with questionable MIDI data from foreign sources (in this case, a web sequence that I gave up on and started over from scratch doing my own).

If the "note off" values are zero (first time I've encountered that!), DP randomises the "note off" values instead of the "note on" values every time, regardless of which option is selected.

If I first set all "note off" values to 80, DP correctly applies randomisation, note range limiting, note velocity setting, and any other single or multiple parameters from the Velocity Editor, to the "note on" values when that option is selected.

I have never experienced a problem like this in DP in ANY of its versions, but I suppose the circumstances are obscure enough that it might have happened in earlier versions to, given the same set of weirdo MIDI data.

I thought "note off" velocity was fairly important and had to do with how quickly you release the note, but a little bit of research that I did indicated that this is not universally accepted as the interpretation of that MIDI CC, and that there are other ways that this information can be gotten across.

For instance, a fair number of my VI's seem to ignore "note off" velocities. Of course, this is different from a "note off" event, which MANY synths ignore, preferring a "note on" event with velocity=0. But no matter how I try to evaluate the possible scenarios, I cannot think of any reason why a file should have "note off" = 0... and certainly it didn't play very musically until I redid the whole thing from scratch on my own.

Sorry for long-windedness; this is mostly a placeholder un til I have time to edit it, so I don't forget again to alert people to the problem with certain MIDI velocity editing scenarios.

monkey man wrote:

waterstrum wrote:I'm very worried now.

Don't worry, waterstrum; the hammerhead shark's correct.
Just drag 'em back into the SB window.

There was a thread in which we discussed this at some length a week or two ago, but the advice you've been given is all you need to know. :D

That happened to me a couple of nights ago; I created a track, recorded a guitar part, hit save, and POOF....empty screen.

After restart/relaunch, I dragged the new gtr file from the Project/Audio Files folder into the Tracks window and DP created a new track with the soundbite in it.

Luckily it was just one soundbite, with no edits and layers in the track.

Dbuddle has identified a possible bug introduced in 5.1.2. See "Audio Cycle recording with Punch-In Punch-Out" thread. http://www.motunation.com/forum/viewtop ... sc&start=0
I have confirmed that this feature does not work in 5.1.2 (at least on my system.)

Phil

Phil O wrote:Dbuddle has identified a possible bug introduced in 5.1.2. See "Audio Cycle recording with Punch-In Punch-Out" thread. http://www.motunation.com/forum/viewtop ... sc&start=0
I have confirmed that this feature does not work in 5.1.2 (at least on my system.)
Phil

Thank you Phil; I was about to post the link when I saw your entry.

Whilst it's all a little disappointing, the good news is that the Unicorn guinea pigs are doing a bang-up job.