10.01 is in
Posted: Wed May 01, 2019 2:01 pm
Get your copy !
Sounds like they got a lot of bugs. Good.
Mike
MOTUnation.com
MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
https://www.motunation.com/forum/
10.01 is in
Page 1 of 3
Re: 10.01 is in
Posted: Wed May 01, 2019 3:44 pm
Re: 10.01 is in
Posted: Thu May 02, 2019 12:14 pm
https://cdn-data.motu.com/site/docs/dp/ ... ReadMe.pdf
I'll do the upgrade tonight or tomorrow, but don't see the three bugs that have affected me the most adversely (nor had I taken the time to report them yet, as it wasn't until this week that I noticed how persistent they are, as I've been focused on gigging).
1. Horizontal Scrolling in Tracks Overview, frequently shows the wrong bar range, and only resets properly when playing back and getting to the next auto-scroll event (if enabled), or after toggling the timeline to be real time and then by the bar.
2. In a multi-chunk project, it seems the only sure-fire way to get the correct content in the Event View to show up is to close and re-open the project -- ongoing for many versions now, but more prevalent than before, and quite annoying when trying to edit tempo or key/time signatures and constantly getting the Conductor Track for the wrong chunk.
3. While repeatedly hitting Undo, the labeled action frequently repeats itself from the first Undo instead of showing the correct action label for the current slot in the Undo History, which can cause data loss or other errors unless one somehow has enough views open to carefully observe what happens after each Undo action.
The first and third are new to DP10, but are probably performance related like the second one, as there have always been various ways to consolidate a project's status, toggle some settings or the active chunk, etc. that will get the project and its views back into a sane state.
I'll do the upgrade tonight or tomorrow, but don't see the three bugs that have affected me the most adversely (nor had I taken the time to report them yet, as it wasn't until this week that I noticed how persistent they are, as I've been focused on gigging).
1. Horizontal Scrolling in Tracks Overview, frequently shows the wrong bar range, and only resets properly when playing back and getting to the next auto-scroll event (if enabled), or after toggling the timeline to be real time and then by the bar.
2. In a multi-chunk project, it seems the only sure-fire way to get the correct content in the Event View to show up is to close and re-open the project -- ongoing for many versions now, but more prevalent than before, and quite annoying when trying to edit tempo or key/time signatures and constantly getting the Conductor Track for the wrong chunk.
3. While repeatedly hitting Undo, the labeled action frequently repeats itself from the first Undo instead of showing the correct action label for the current slot in the Undo History, which can cause data loss or other errors unless one somehow has enough views open to carefully observe what happens after each Undo action.
The first and third are new to DP10, but are probably performance related like the second one, as there have always been various ways to consolidate a project's status, toggle some settings or the active chunk, etc. that will get the project and its views back into a sane state.
Re: 10.01 is in
Posted: Fri May 03, 2019 6:15 am
Caution! VCA Bug!!!
Each time a project is opened, all tracks within the group add to the values of their faders the current VCA fader value (if the VCA is not 0).
The same thing happens if you turn the group on and off.
Each time a project is opened, all tracks within the group add to the values of their faders the current VCA fader value (if the VCA is not 0).
The same thing happens if you turn the group on and off.
Re: 10.01 is in
Posted: Fri May 03, 2019 9:49 am
Wow, that could be headache inducing on multiple levels. Thanks for the heads up. Did you post a Tech Note at MOTU.com? They probably oughta know about this one...Drumwizard wrote:Caution! VCA Bug!!!
Each time a project is opened, all tracks within the group add to the values of their faders the current VCA fader value (if the VCA is not 0).
The same thing happens if you turn the group on and off.
Re: 10.01 is in
Posted: Fri May 03, 2019 11:59 am
Yes, I post a Tech Note.Helen wrote: Wow, that could be headache inducing on multiple levels. Thanks for the heads up. Did you post a Tech Note at MOTU.com? They probably oughta know about this one...
Re: 10.01 is in
Posted: Tue May 07, 2019 6:58 am
Just installed 10.01 and was able to open a project that had been continually crashing 10. Mixed for about 4 hours and no problems or crashes. Only weird thing is I set an input at the bottom of the mixer window sometimes it just remains blank, even though its actually assigned correctly. Not a big problem but just annoying if I'm checking assignments. Outputs seem okay. Loads faster for this project.
UPDATE: the track name issue only happens in mixer narrow view, regular view is fine.
`
UPDATE: the track name issue only happens in mixer narrow view, regular view is fine.
`
Re: 10.01 is in
Posted: Tue May 07, 2019 7:10 pm
Although the issues I listed were not in the update sheet, I have not experienced them since the upgrade, yet it might be early yet to draw conclusions.
Re: 10.01 is in
Posted: Wed May 08, 2019 1:21 pm
I'm experiencing an issue where my continuous data preferences are not being stored. I make the various reassignments in the editing prefs and all is fine when I hit "Done". But the changes get reverted to default if I relaunch DP.
Re: 10.01 is in
Posted: Tue May 14, 2019 10:16 am
I often "patch" flawed takes by snipping a good phrase of an otherwise bad take, dropping it on the mostly-good take, and cross-fading. But if the two takes weren't played at exactly the same speed, I need to change the length of the "patch" so that it matches the length of the material I'm patching over.
I found that in 10.0, if I time-stretched the "patch" soundbite, DP trimmed the soundbite precipitously at the new crop points and deleted the cross-fades. This meant that, since I need audio to cross-fade with, I'd need to drag the endpoints of the patch outwards before time stretching, then drag them back after time stretching, so that I could re-create the cross-fades.
In 10.01 it seems to scale time past the end of the cropped soundbite, and it leaves the cross-fades in place. Nice!
I found that in 10.0, if I time-stretched the "patch" soundbite, DP trimmed the soundbite precipitously at the new crop points and deleted the cross-fades. This meant that, since I need audio to cross-fade with, I'd need to drag the endpoints of the patch outwards before time stretching, then drag them back after time stretching, so that I could re-create the cross-fades.
In 10.01 it seems to scale time past the end of the cropped soundbite, and it leaves the cross-fades in place. Nice!
Re: 10.01 is in
Posted: Tue May 14, 2019 9:13 pm
I keep forgetting to post, that I am still experiencing one of the earlier glitches big time, and it's quite annoying but has an easy workaround.
Scrolling in Tracks View is often getting stuck and showing a hybrid of bars from different parts of the song, until you play or record and it needs to paginate.
As with the initial DP10 build, if you go between real time and bars, using the mini-menu at the top of the tracks, it clears itself up.
I now forget the other two glitches, as I posted them in another thread, but this probably means they are now fixed in 10.01.
Scrolling in Tracks View is often getting stuck and showing a hybrid of bars from different parts of the song, until you play or record and it needs to paginate.
As with the initial DP10 build, if you go between real time and bars, using the mini-menu at the top of the tracks, it clears itself up.
I now forget the other two glitches, as I posted them in another thread, but this probably means they are now fixed in 10.01.
Re: 10.01 is in
Posted: Tue May 14, 2019 9:22 pm
Yeah, if I zoom in AT ALL the piano roll gets screwed up if i manually scroll with the cursor. Clicking on a note or using the transport fixes it, but it's busted. Time for DP 10.12.
They grow up so quickly...
They grow up so quickly...
Re: 10.01 is in
Posted: Sat May 25, 2019 6:18 am
I can duplicate this. I think this makes VCA faders unusable until it is fixed. I hope they get this fixed soon as I'm seeing workflow advantages to VCAs and would like to start incorporating them.Drumwizard wrote:Caution! VCA Bug!!!
Each time a project is opened, all tracks within the group add to the values of their faders the current VCA fader value (if the VCA is not 0).
The same thing happens if you turn the group on and off.
Thanks for the heads up!
Phil
Re: 10.01 is in
Posted: Sun May 26, 2019 6:44 am
Has this one been reported in technote?Phil O wrote:I can duplicate this. I think this makes VCA faders unusable until it is fixed. I hope they get this fixed soon as I'm seeing workflow advantages to VCAs and would like to start incorporating them.Drumwizard wrote:Caution! VCA Bug!!!
Each time a project is opened, all tracks within the group add to the values of their faders the current VCA fader value (if the VCA is not 0).
The same thing happens if you turn the group on and off.
Thanks for the heads up!
Phil
Re: 10.01 is in
Posted: Sun May 26, 2019 7:07 am
Yes:labman wrote:Has this one been reported in technote?
Does it help to post from multiple users, or do you think one post is enough?Drumwizard wrote:Yes, I post a Tech Note.Helen wrote: Wow, that could be headache inducing on multiple levels. Thanks for the heads up. Did you post a Tech Note at MOTU.com? They probably oughta know about this one...
Phil