Nxt 5 Pro - Sound Editor

[JMcCon57 0]

I am currently using Creator 12 Pro, Windows 10. It does glitch from time to time. Just wanted to see if the version of Sound Editor that comes with NXT 5 Pro is the same as was in Creator 12, or if it is a new program. I really only use Roxio for audio work, so I'm not too concerned with the video functionality.

 

Thanks!

[Jim_Hardin 418]

I think it is the same...

 

But there are several here that know more about that one than I do and should chime in.

 

Curious about Creator 12. What OS are you running it on? Have you done a Repair to the software? Any error message with it?

[JMcCon57 0]

I originally installed it on a Windows 8 machine. When 10 came along I did the update without making any changes to C12. For the most part, it functions okay, at least for what I use it for which is audio. But, and I can't isolate why, on some occasions after recording a vinyl LP using my line in connection, I'll hit stop at the end of the recording and sound editor freezes up leaving me with nothing. Rare, but it happens. No error messages.

[Jim_Hardin 418]

You can try to do a Repair. Turn OFF any firewall/anti virus.

 

Run your Creator 2012 Setup program and choose Install when it offers it. Don't let it do updates if it asks.

 

Reboot and see what happens

[Brendon 197]

I think it is the same...

 

But there are several here that know more about that one than I do and should chime in.

 

 

Creator 2012 uses Soundedit13 version 13 by RoviCorp.

NXT Pro 5 uses Soundedit15 version 18 by Corel.

[JMcCon57 0]

I went ahead and ordered NXT 5 Pro. I have it installed, and to my eye and experience, sound editor is identical to what it's been for several generations now. No cosmetic changes whatsoever. The proof that there is something new under the hood will come when I no longer have the freeze ups that I had with 12. I've done some editing but haven't yet ripped any LP's. I'll post more when I've had a bit more time with it.

[JMcCon57 0]

Well, a little over a week with it. So far, no freezes. But........almost every LP I rip has some kind of minor hiccup. Not a problem if there is a break between songs because I just go back and rip that one again. If it's an entire album side, that could/would be a problem. Haven't tried that yet.

 

What are the kinds of things that cause the software to hiccup/glitch? I don't hear it as it's recording, only when I check the finished product. I turn Norton to "silent mode" for the duration of a session. Suggestions?

[Bach Fan 0]

I'm not ripping LP's. But the procedure is similar - edit/cut recordings, set trackmarks, export tracks to separate files.

At the moment I'm using both, the soundeditor of WinOnCD12 and Creator NXT5.

Your description of those hiccup/glitches remind me of what I'm getting when exporting to MP3 files. I hear the hiccup/glitches when I play those files from a contiguous list, but not when I play them in the original project window. If I export to WAV Format, there are no hiccups/glitches.

Would that be of any help? Trigger any idea?

[Jim_Hardin 418]

Interesting...

 

I wonder what would happen if you imported the WAV and then converted it to MP3???

[Bach Fan 0]

Every exported MP3 is mutilated a tiny little bit at the end. That only shows if the two exported tracks had been taken from a contiguous sound. Playing the two files after each other gives you the little hiccup. Bringing them back to WAV doesn't help.

[sknis 216]

Every exported MP3 is mutilated a tiny little bit at the end. That only shows if the two exported tracks had been taken from a contiguous sound. Playing the two files after each other gives you the little hiccup. Bringing them back to WAV doesn't help.

 

If you bring the files back into Sound editor and expand the timeline to max, what do you see at the beginning and the end of the wav display? If you see a little glitch, what happens if you edit it to cut off the glitch?

 

Also, make sure that you don;t have 2 or more audio player opening at the same time. That will cause glitches..

Edited December 23, 2016 by sknis

[Bach Fan 0]

Sorry, hit post before finishing the answer to Jim_Hardin ... importing the single WAVs and export them to MP3 brings that same little mutilation.

[Bach Fan 0]

 

If you bring the files back into Sound editor and expand the timeline to max, what do you see at the beginning and the end of the wav display? If you see a little glitch, what happens if you edit it to cut off the glitch?

...

 

There are no visible glitches.

If I recombine the two tracks where the sound runs through, they certainly look different if it is original WAV+WAV or MP3+MP3 (good quality) exported from those WAVs. The running time seems to be different, too.

WAV+WAV

MP3+MP3

 

 

...

 

Also, make sure that you don;t have 2 or more audio player opening at the same time. That will cause glitches..

No, only one Soundeditor open. No other player.

[Bach Fan 0]

Maybe I should add that I don't see that as a problem but as a natural part of MP3 compression. It is a procedure with quality loss vs. WAV. If you work with contiguous sounds, like in an oratorio, you better use WAV.

[cdanteek 217]

Try the excellent and free Exact Audio Copy , http://www.exactaudiocopy.de/

 

• EAC is able to copy ranges of music data, not only tracks
• Automatic speed reduction on read errors and fallback to a higher speed afterwards (depends on the used drive)
• Volume normalization of extracted audio to a given percentage
• Usage of the Windows Audio Compression manager (ACM Codecs) for direct compression to e.g. MP3 waves
• Support for the LAME DLL that is usable like an ACM Codec for on-the-fly MP3 compression
• Support of external MP3, WMA, flac and OggVorbis encoders for automatic compression after extraction (supports multi-processor environments)
• Batch compression to WAV files and decompression of supported encoded files to WAV
• Compression offset support for exact compression/decompression
• Detection of pre-track gaps (positions where negative track times runs towards 00:00:00)
• Detection of silence in pre-track gaps
• Automatic creation of CUE sheets for Burnnn, Feurio, Nero or even EAC, which can include all gaps, indicies, track attributes, UPC and ISRC and also CD-Text for an exact copy
• CD player functionality and prelistening to selected ranges
• Automatic detection of drive features, whether a drive has an accurate stream and/or does caching
• Sample offsets for drives with noaccurate streams, including the option of filling up missing samples with silence
• Synchronizing between tracks for non-accurate stream drives
• Trackname editing with local/remote CD databases support and more features like ID3 tagging
• Browse and edit local database
• Certified Escient ® CDDBCompatible
• Local CDDB support
• Record and loop record functions for recording from LP, radio, etc.
• Automatic renaming of MP3 files accordingto their ID3 tag
• Catalog extraction function (e.g. first 20 seconds of a track)
• Multisession (CD-Extra) support
• CD-Text support
• CD-Write support for some drives (internally and using CDRDAO)
• ID3 V1.1 tag editor with drag and drop ability from track listing and CD database browser
• Glitch removal after extraction
• Small WAV editor with the following functionality: delete, trim, normalize, pad, glitch removal, pop detection, interpolation of ranges, noise reduction, fade in/out, undo (and much more)
• Program is free for personal use, so feel free to copy

[d_deweywright 116]

To understand what's going on here, we have to get a little bit technical. CDs are written in sectors. Each sector on an Audio CD contains 2352 bytes of data (music) which is 1/75 of a second. (On a data CD, there are 2048 bytes of "data" plus 304 bytes of error correction code, still a total of 2352 bytes.)

 

Each track (song) on a CD _must_ start on sector boundary. So, if the previous track doesn't completely fill the previous sector, that sector is padded with zeros (silence). If there is music playing in there, that bit of padding will be heard as a little "glitch" or "dropout."

 

If you're capturing from an LP, you need to use a program that will split your tracks on a sector-size boundary. (And if you then edit the track by trimming anything, all bets are off.) The free CD Wave program automatically positions the split on a sector boundary so that any tracks the flow from one to the next won't have those glitches. I believe GoldWave has a "prep for CD" option to help with this. All of these are dependent on capturing and editing in .WAV format. Converting to/from .MP3 can indeed change the final file size so it is no longer on a sector boundary. I don't know for certain whether or not Roxio's Sound Editor concerns itself with prepping tracks for CD burning that way.

 

Oh, and you can't calculate whether your track is properly sized just by looking at the byte count of the .WAV file, because there is header information in the .WAV file that isn't part of the actual music data. You'd have to make sure you take out the header data (usually, but not necessarily, 44 bytes).

 

I confess, I don't use Sound Editor to capture my LPs, I use CD Wave to capture and split out my tracks. I do most of my noise reduction processing on the entire side of an LP, then split that final file apart. Then I use Roxio's Music Disc Creator to burn my discs.

 

Standard disclaimer, I have no affiliation with CD Wave or GoldWave, except as a satisfied user, and receive no remuneration for mentioning their products.

[sknis 216]

 

There are no visible glitches.

If I recombine the two tracks where the sound runs through, they certainly look different if it is original WAV+WAV or MP3+MP3 (good quality) exported from those WAVs. The running time seems to be different, too.

WAV+WAV WAVWAV.png

MP3+MP3 MP3MP3.png

 

No, only one Soundeditor open. No other player.

 

You should be able to increase the size of the audio track to better see any glitches. What you posted is not very informative.

 

What is your Windows default player? It may6 try to play the file that you are opening with Sound Editor simultaneously.

Edited December 23, 2016 by sknis

[Bach Fan 0]

To understand what's going on here, we have to get a little bit technical. CDs are written in sectors. Each sector on an Audio CD contains 2352 bytes of data (music) which is 1/75 of a second. (On a data CD, there are 2048 bytes of "data" plus 304 bytes of error correction code, still a total of 2352 bytes.)

 

Each track (song) on a CD _must_ start on sector boundary. So, if the previous track doesn't completely fill the previous sector, that sector is padded with zeros (silence). If there is music playing in there, that bit of padding will be heard as a little "glitch" or "dropout."

 

Thank you for explaining the technical details. I thought the little mutilation was due to the numerical procedure that produces MP3 from the original!

[Bach Fan 0]

 

You should be able to increase the size of the audio track to better see any glitches. What you posted is not very informative.

 

What is your Windows default player? It may6 try to play the file that you are opening with Sound Editor simultaneously.

Skins,

No, there is no other player running simultaniously.

Sorry for the misunderstanding. I just tried to comment and answer to the problem of JMcCon57, on 21 Dec 2016 - 10:56 PM.

I don't have any problem with these hiccups. I know that I can avoid them using WAV files.

I originally thought that they are only related to the numerical MP3-procedure.

But as d_deweywright explained there is also a technical side contributing to that problem.

[JMcCon57 0]

Okay, not sure who is responding to who on here but that's what makes it fun, right? Anyway, I took awhile off from this and tried to rip an LP over the weekend. EVERY SINGLE track had at least one minor glitch. Tried again, same thing, different spots in the music. I uninstalled and reinstalled NXT 5. Since I'm on an "older" computer, I deleted my user account and created a new, fresh one. I did do that before reinstalling NXT 5. Got everything up and running, tried again, same result. I turn Norton to silent mode, I'm trying to catch whatever might be attempting to update. I'm just at a complete loss here. Some other programs were mentioned for ripping. Would they possibly work in my case? I still want to use Roxio for editing the ripped files, but dang, can't even get one track to rip cleanly.

[JMcCon57 0]

Sorry for the second post, but should probably mention that I rip to .wav, and to a second internal hard drive which is identical to the C drive. That's what I've been doing all along. Hardware is an AT-LP120 turntable (internal preamp off), running through a U-Turn Pluto phono amp, and into the PC from there. Using the built in sound on the PC as I've done since I built the machine.

Edited January 9, 2017 by JMcCon57

[d_deweywright 116]

JMcCon57, we have a couple different things going here so we need some clarification. Let's clean up a terminology issue first. The term "rip" as applied to audio, typically refers to "ripping" a digital track from an Audio CD. What you're doing is "capturing" audio from an LP. That's just a minor nit.

 

What format file are you capturing to, .WAV, .MP3, or something else? I would suggest that .WAV is the best format to capture to, while it requires the most disk space, it requires the least processing power. (Just saw your second post.)

 

Now, when you say you have a "glitch" in your captured track, are you talking about an audible problem in the middle of the track somewhere, or are we talking about the transition between two tracks? And are you listening to it from the captured file, or are you listening to it after writing to a CD?

 

Are you capturing the entire side of an LP in one file first? And then splitting out the individual tracks? Assuming you're capturing the entire side of the album first, if you listen to that file, do you hear the same "glitches?"

 

Using Music Editor, can you split out a few seconds of music that includes the "glitch" and upload that for us to listen to and give us a link to it?

Edited January 9, 2017 by d_deweywright

[JMcCon57 0]

The problem is a glitch during the track, and occurs randomly. My most recent attempts have been to try to capture no more than three short tracks, and have attempted to capture only one several times. I usually just use "Edit Audio" for the entire operation, and do not separate tracks until I'm ready to edit and export. I did try the "digitize LP"s and tapes" option once. Glitches still present. As far as uploading a sample, give me a little time on that as I'm not at that computer and may need a bit of a tutorial to get it done! Thanks!

[d_deweywright 116]

Okay, you didn't state it clearly, please correct me if I'm wrong, or confirm it if I'm right, you're listening to the tracks from the files on your PC, and not after writing them to CD?

 

That's one of the things that gets us into trouble here, clarity of statements, and assumptions. If you don't state it precisely, and we assume something, we might not be correct.

[JMcCon57 0]

Yes, correct. I always listen to the captured files immediately after capture on the PC. If all is good I then export the file which is mostly ready for import into itunes. It's pretty rare that I burn to CD's anymore. I appreciate the help, and apologize for not being clear enough in my posts. It's SUPER clear in my thoughts! : )