Jump to content

Bach Fan

Members
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Bach Fan

  • Rank
    Rookie

Profile Information

  • Gender
    Female
  1. Bach Fan

    Nxt 5 Pro - Sound Editor

    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.
  2. Bach Fan

    Nxt 5 Pro - Sound Editor

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

    Nxt 5 Pro - Sound Editor

    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.
  4. Bach Fan

    Nxt 5 Pro - Sound Editor

    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 No, only one Soundeditor open. No other player.
  5. Bach Fan

    Nxt 5 Pro - Sound Editor

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

    Nxt 5 Pro - Sound Editor

    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.
  7. So, here I am again, with my serious problem. I try to be short, but have to explain and document. Situation: I have been using WinOnCDs Soundeditors since version 2008, appreciated the improvements from 2009 to 2012. I mainly edit/cut live-recordings of choir concerts to produce remembrance CDs. I had been happy with 2012 on Windows 7 until I needed a new CD/DVD burner. With that device Soundeditor 2012 aborts burning for all projects. Since this version isn't supported any more I bought Creator NXT5. Same error. Problem: The directory is written, then the burner speeds up to write the tracks, then aborts. Yes, avoid buffer underrun is checked. I varied the buffer size from 65MB to 500MB which seems to postpone the time of abortion a little. Equipment: Creator NXT5, runs on Silent PC, AMD Athlon 64 X2 Dual Core Proc 4000+, 2.1 GHz; 2GB RAM Win7 Professional, SP1, 32 Bit NVIDIA GeForce 6150SE nForce 430, Eizo S2111W The new burner DVD-RW Samsung SH-224GB/BEBESATA (internal) Windows states that the device driver is up to date. Windows can read from and and write to that device, data and audio. Every Soundeditor project aborts burning on that burner. burn abort details All Soundeditor projects burnt properly on former drive Samsung DVD-RW SH-S203/BEBE (internal) All Soundeditor projects still burn properly on ASUS SDRW-08D2S-U (USB) LG HL-DT-ST DVD-RAM GSA-E60L (USB) Workaround 1: write to disc image with Soundeditor, then use another feature of Creator NXT5 to burn the disc image. Main menu > Data/Copy > burn disc Image That aborts, too. error message and details Workaround 2: With Soundeditor I exported all the tracks of my project to single WAV files. I can burn audio CDs from those files with that same burner with Windows Media Center without any problem. Workaround 3: I even can burn audio CDs from those WAV files with that same burner with Roxio Creator! If I chose a different feature from the Start page: Main menu > Music/Audio > burn Audio-CDs That feature is perfectly able to burn my audio CD on that burner. To me it seems to show that the different features under the roof of Creator use different device access procedures. I can use the Workarounds 3 or 2, or use the USB burners. But I'd rather use the straight and easy path from the project and use the internal burner. Can you think of anything I might be able to do to solve the problem? Thank you for your time!
  8. Bach Fan

    Nxt 5 Pro - Sound Editor

    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?
  9. Jim_Hardin, about your remark to the Red Book Standards: Didn't think about that but the Red Book Standards do limit the space available for text and of course the length of the text is eating that space up Sure. But I would expect a professional software to deal with Red Book restrictions other than in this curious way. It should reserve whatever space the Red Book allows. Main memory isn't that precious any more like it was in the 60s and again in the new world of pcs in the 80s. And if that space runs out then it should tell so. If it were only some general type of message like "You can't burn so many tracks with artist lists of 128 char each.". Then I would know where to look for the problem. Wouldn't you agree? and little addendum answering to your concern: An Audio CD-R can hold 74 or 80 minutes of music. Having 36 tracks allows about 2:03 to 2:13 minutes per song... Yet your very first song is 8+ minutes long. You can see my concern The burn spec screenshot shows: I'm using a CD-R of 80 minutes, the total length of the music is 77 min 43 sec, and the graphic shows that lots of the tracks are very short. That's what I meant when I said in the beginning: All tracks fit onto one CD. And indeed, they fit properly if I'm using the work-around described as type of detour, above. And yes, I'll probably pop in, again, soon enough - my most serious problem hasn't been solved so far. Soundeditor doesn't like my new burner. I'll run some more tests, first, then post my problem. Experience so far tells me: I'll add to this thread and won't start a new one.
  10. Thank you for your suggestions! I'm aware of the fact that a DMSE file contains only text, that's why I changed the extension to TXT to upload those files. I knew I didn't do any harm to the content. When you asked for the project specs I thought you meant these roxio project files. Sorry for the misunderstanding. Your suggestions triggered the idea that lead me to solving the problem. Every other year our choir performs Bach's Christmas oratorio, every other year I produce those CDs. Either 2 or 3 cantatas on one CD, either 23 or 36 tracks. What is different this year? I looked into the projects and came up with a solution that reminds me of my first programming steps in 1969 (no typo). It is a text length that matters! With both above problems: Soundeditor doesn't burn all the tracks of my project/ doesn't export the tracks. In clip properties which are passed on to track properties I can specify up to 128 characters for "artists" (not album artists). (More is cut off.) artists textlength=128 char burns 17 of 36 tracks creates the export folders but they remain empty artists textlength=113 char burns 19 of 36 tracks creates the export folders but they remain empty artists textlength=88 char burns 22 of 36 tracks creates the export folders but they remain empty artists textlength=78 char burns 24 of 36 tracks exports all 36 tracks properly artists textlength=70 char burns all 36 tracks properly exports all 36 tracks properly Another Problem is solved, too: The scrubber line is moving, now. I checked the grafic card driver, Windows as well as the NVIDIA check routine confirmed: the driver is up to date. But those checks must have moved a bit somewhere in the registry. Now the line is moving. Thanks for looking into my problem!
  11. WinOnCD 12 on Acer TravelMate, Intel i3, 1.33GHz; 4GB RAM Win7 Home Premium, SP1, 64bit Project Acer project.txt Since I'm not allowed to upload a DMSE file I changed the Extension to TXT. burn spec only 17 tracks Since I didn't want to spoil more CDs I burnt to disc image for the screenshot. Creator NXT5 on Silent PC, AMD Athlon 64 X2 Dual Core Proc 4000+, 2.1 GHz; 2GB RAM Win7 Professional, SP1, 32 Bit NVIDIA GeForce 6150SE nForce 430, Eizo S2111W Project Si2 project.txt Since I'm not allowed to upload a DMSE file I changed the Extension to TXT. burn spec only 17 tracks Since I didn't want to spoil more CDs I burnt to disc image for the screenshot. It is only 17 tracks with NXT5-Soundeditor, too. I'm sorry, I mixed up the "only 19 tracks" from a different project, where Soundeditor burns only 19 of the 22 tracks. (Both versions.) Thanks for looking into my Problem!
  12. Jim_Hardin: I considered the Me Too a helpful comment to the quoted items. I posted them on THAT thread. Jim_Hardin, Brendon: I agree, this thread is terribly confusing. Not only to you, but to me, too! I answered (the Me Too) to one thread. I opened two new threads for the two problems I reported. With new header, new tags. Yesterday, when I posted, everything was in proper place. Today I see that the system (?) made one thread out of my 3 different posts - why?
  13. Soundeditor (WinOnCD12 and CreatorNXT5) doesn’t want to export all the 36 tracks of my project, if I use the command “export tracks/clips”; neither with 1 clip = 36 tracks, nor with 36 clips = 36 tracks. I tried all combinations of WAV and MP3 format as start-out and export files. No effect. Soundeditor runs (very fast) through all tracks in the process window, creates the proper folders from clip/track properties, but these folders remain empty. Same effect if I only select a few tracks. It works if I export track by track, using the command “export track” from the track’s context menu. I wonder: Did anyone else encounter that problem? Does anyone have a solution? Thanks for your comments.
  14. Soundeditor only burns 17 (WinOnCD12) resp. 19 (CreatorNXT5) of the 36 tracks of my project to audio CD (to disc image file, resp.). All tracks are selected. All tracks fit onto one CD. I tried to solve the problem by exporting the tracks, making a new project from 36 clips, burning that. Alas: same effect. I tried all combinations of WAV and MP3 format as start-out and export files. No effect. My solution is type of a detour: Burn an audio CD from those 36 clips with another tool from the WinOnCD or CreatorNXT5 suites: “Burn Audio-CD” (in the German version: “Audio-CD Brennen”). Usability of that tool is poor. (It is only meant to be used for a single CD.) This solution only works with WAV files. MP3 files create little cracks/fails between the tracks if there is no pause between tracks, if the music goes on, like in Bach’s Christmas oratorio. That is complicated, needs by far too many unnecessary steps - but it works. I wonder: Did anyone else encounter that problem? Does anyone have a solution? Thanks for your comments.
  15. Good to know! To my eye they look similar, too. Except for the fact that the position mark (blue line) doesn't advance any more, when playing the sound. :-( (Reported to support. I hope they'll come up with a solution.) I have been using WinOnCDs Soundeditors since version 2008. Had been happy with 2012 on Windows 7 until I needed a new CD/DVD burner. Soundeditor 2012 aborts burning. Since this version isn't supported any more I bought NXT5. Same error. :-( (Reported to support. I hope they'll come up with a solution.
×