Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
Nero 2016 Wave Editor ver 14.0.0050 song editing issue
I upgraded to the above version of Nero WE and now when I "cut" a song and "fade" the end of the remainder, the "fade" often jumps to the middle of the song instead of the end. It also re-inserts the cut automatically. This never happened with previous versions. I have W10 version 1511 and use the full version Nero 2014. I removed all traces of previous WE versions and did a clean load of WE 2016, but no luck.The only work around I have found is to do the "fade" first, and then do the "cut" carefully, then do a "play selection" twice to get everything to work. Has anyone else seen this?
-
When you say "cut", do you mean you're adding track splits or your removing a portion of the file?
-
-
Say I have a 4 minute song and want to remove (cut) the last 1 minute then do a short fade to the end of the remaining 3 minute song. I have done this often to make the music fit a dance that my wife has taught her students. This has always worked with no issues until the WE 2016 was loaded. Now the program puts a fade some where arbitrary, say around 1 minute or 2 minutes in the 3 minute song and picks back up the remainder of the music after the fade at full volume. In other words, I can't put a fade at the end of my music where it should be. This makes editing music extremely difficult. Who needs a fade out in the middle of a song instead of at the desired end (3 minutes in this example)?
-
-
I have a song by Adele which is about 3.5 minutes. I selected the last 1 minute and then clicked on the scissors. I then zoomed in and selected the last 10 seconds and clicked on Volume, Fade Out. It worked perfectly.
-
Where did you go?
-
-
That is exactly what I do to edit a song. I now use W10 ver 1511 on my prime PC. Maybe it is an issue with W10 or maybe something else specific within this PC. Seems strange since earlier WE versions did not have this issue..
-
-
-
-
-
I'm was using WE v14.0.0020. After I installed v14.0.0050, I get the same results as you do and I'm using Win 7.
Use the contact form at nero.com, support, contact, technical support and submit this problem. You can say that I can also reproduce it. -
-
Lamar,
I've tried this several times without difficulty on Windows 10 Pro:
How often does it happen? What is a typical fadeout duration? -
-
This problem happens every time. I have now done additional testing and found that on a totally different PC which likewise has W10 ver 1511 loaded but uses older WE ver 12.0.4000, the same issue occurs every time. So, this is a compatibility "problem" between Nero WE and W10.
Thanks for the video Omega. I have never tried the (menu) method you demonstrated. I followed your example and it worked perfectly for me. In the past I just used the time markers (mouse clicks) manually and slid them around as need be using the mouse. That is were these issues started. I will re-train myself to use your menu method and hopefully all will be well. On previous Windows versions moving the markers around with the mouse seemed to be totally satisfactory, but I guess W10 has a different reaction to that. Thanks..-
WE 14.0.0020 works fine on windows 10 ... so it seems the more modern versions of WE have a problem.
-
-
-
-
-
Very strange. It didn't do it in 14.0.002 in Win 7 but did it in 14.0.005. It does it using 14.0.002 in Vista. I'm not going to install 14.0.005 in Vista. This is using the method we were talking about. I don't have time this morning to do anything else.
-
It looks like I'll be "frozen in time" from now on ... I'm not doing any Nero updates ever again! (I'm hanging onto my current version that still allows HD audio decoding, and WE that performs "normally".
-
-
Lucky Phil- Thanks. Your post wasn't displayed when I posted.
-
-
-
-
-
Lamar,
By dragging the mouse instead of using the menu method, I duplicated your result. The problem seemed to arise when I "accidentally" went beyond the cut end (which shouldn't happen). I played around and eventually the program froze. When it restarted, I had an old problem with a "Crash Guard" dialog appearing. The "fix" for that is to delete the temporary files and peak files. Doing that enabled normal start-up and appears to have fixed the fade problem also! ( "Options | Editor Options | Directories" for the location of the files). -
-
Deleting the peak files worked in Vista with 14.0.0020. Can't figure out why that version didn't present a problem in Win 7.
-
Loading Profile...





