![]() |
|
Microstudio Help Post Microstudio questions, tips and suggestions here. |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
DDOUGLAS
The entire CUSTOM ASSEMBLY feature with all it's multi-faceted flexibility including the ability to save more than one work in progress at a time was removed, and you didn't notice that when Beta Testing?? It has been put back in under the WRITE CD(or words to that effect) TAB due to all the flack raised about it when 3XXX came out. Last edited by George; March 16th, 2007 at 10:24 AM. |
#2
|
|||
|
|||
Quote:
Plextor was discontinuing their drives, which MTU's SURVIVAL depended upon. We licensed a new vendor's code to interface to other drives.. paying 4 times what we had been paying per year before. Then, it took us from February to October to get their bloody code working right, being forced to prove to them where their bugs were before they would even look at fixing them. Microstudio 3.0 cost us about $50,00 more than expected to deliver. We released 3.0 for the Christmas buying season. No one forced you to buy it. You did it of your own volition. Microstudio 2.6xx only would write CDG/WAV files to a disc until 2.609 when we added BIN file support. V3.0 handles KMA, BIN, CDG, MP3+G, ZIP, WMA+G, MP3, WMA, and WAV, transparently in any mix to write either a CDG or CD disc with the same project. Incredible ADDED flexibility! V3.0 also works with almost any drive on the market, not just CDG capable drives of the past. Users today don't need to buy an expensive drive, and MTU cut our price for our CDG Certified drives almost in half. Incredible ADDED flexibility! We also allow displaying, and searching the My Songs list, and automatically build a list for each opened folder so it won't take minutes or tens of minutes to build the list every time when you have tens of thousands of files in a folder. V2.6xx only showed Incredible ADDED flexibility! QED |
#3
|
|||
|
|||
Right...and no one told us what features were not present, either. How could we possibly imagine that custom assy. was missing? And that's the whole point. Had that information been included in the changes portion on the website, we wouldn't be having this conversation today.
That's all I'm saying. I'm not lathered up... not trying to be argumentative... it's only "stuff". Closed issue as far as I'm concerned. Peace. |
#4
|
|||
|
|||
Quote:
I agree, closed subject... and Thread. |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|