User 905133

https://www.roland.com/uk/blog/rd-stage-pianos-history/#:~:text=In 2001%2C the next big,the JV and XV Series. https://cdn.roland.com/assets/media/pdf/RD-500_OM.pdf https://www.roland.com/global/products/hp700_series/#:~:text=Roland's HP700 series supports your,instrument that grows with you. https://static.roland.com/assets/media/pdf/HP704_702_eng02_W.pdf

In another thread on a different issue, David Baay wrote something that explains what I wrote (see above): This makes sense!! Thanks.

Instrument files (*.ins) shouldn't affect whether or not CbB (Cakewalk by Bandlab) sees your interface. Years ago I borrowed a Mio usb to midi interface cable to test drive and it worked very well, but that was on an XP SP3 PC. Does the interface show up as a midi device in Preferences > MIDI > Devices? A screenshot might help to figure out what's going on. Also, under MIDI > Playback and Recording, does it say MME or UWP? Update: For the Roland Instrument file which contains the definition for the RD-700GX, see the links on this page . However, the manual I found for the Digital Piano RD-700 is copyrighted 2001, which is not quite 30 years old. What model do you have? If yours is really from 1994, there might not be an *.ins file for your model. The earliest Roland.ins file I have is from 1998. I sometimes have good luck searching for *.ins files on the internet, so I will look to see if there is an instrument definition for your model.

What do you mean when you say Cakewalk was designed to attract people to the bandlab platform?

Message I started: but when I came back to finish up, John Vere had written: But there seems to be a new problem (or a manifestation of the original problem that didn't get fixed): First of all, are you using the same file or did you make a "Save As" copy of it to try to repair? That might or might not be necessary; that's just what I have done. Second, are you loading the project in CbB's Safe Mode? Not sure it will help, but it might be worth trying. NOTE: There are plenty of people trying to help you with this one and I am hesitant to interfere, but since no one else mentioned these two points, here's my "two-cents worth" just in case they help.

or .

SOS article (for Cakewalk Project 5) SOS article (for Cakewalk Project 5 v. 2)

The only time I lose the metronome is when I accidentally change it to MIDI. So, last night I tried to get rid of (exclude) the grooveplayer in the Menu-based Cakewalk plug-in manager. It was excluded (or so it said), I rescanned plug-ins, and I even restarted CbB, but I couldn't make the Metronome fail to sound. I still have the metronome today. So I renamed this: to GroovePlayer.pulled & rebooted CbB. That gave me tht Missing plug-in error warning box which included this: GroovePlayer (Track: 'LRS track bus'). And that's how I got rid of the Metronome. So I shut down CbB, renamed it back to GroovePlayer.dll, rebooted CbB, and viola--I had the metronome back. Note: I have some older Grooveplayer.dll files in storage areas of an external BU HDD, but I don't think those are being picked up by CbB. They are older than the one from 4/24/2018 (9/12/2013 and 8/10/2011) and are smaller (the 9/12/2013 file is either 795 KB, or 659 KB for the x86 version; the 8/10/2011 is 682 KB). Perhaps these details can be helpful in determining if you have the correct dll and if it's in the right place. As for editing the registry, I don't mess with that.

I also had a version of some audio software Magix did that was geared towards kids. I think it was in the Win 98 SE era and might have had the word Jam in the title. I might still have the manual somewhere. Maybe it was called Music Maker; I'll have to look. I used Cakewalk and I got the Magix thing because one of my kids was interested in making music and I thought Cakewalk was a bit too advanced. Anyhow, maybe Magix had Music Maker and Movie Maker as an audio-video product line.

OOOPS. I guess no one suggested to @DNnX to add - SOLVED to the Topic.

Would you be kind enough to post the link to the specific post where this is stated? Thanks.

What are you basing this assertion on? If its from a reputable source, please post the link. If it's just someone's opinion, does the source say it's a fact or identify it as speculation? If it originates from you, what facts did you put together to come up with this conclusion?

Gearspace has a thread "Is this site a fake? - pluginboutique.SHOP" from mid March 2022!!!!

Thanks for the clarification. I have the manual for Sony's Screenblast Movie Studio (2003). I am sure I test drove the software when I first got it, but I have no files on my current computers. There might be some tests I did on an XP SP3 PC. For a few years I played around with Nero software, even tested editing some OBS captures with it.

I get these things: I just checked with Everything (Void Tools) and the zip files for the Sound Libraries I have been updating are definitely eating up my drive space. I have also been taking screenshots of My PC to keep an eye on the free space on my HDD. Not sure if the Sound Libraries will install properly (assuming I don't run out of GBs). But the last IK Product Manager update I did has the % meter.

Looks like Tonex CS has also been updated:

My recollection is that Sonic Foundry sold both Sound Forge and Vegas to Sony (both of which Magix later acquired). I didn't follow the products closely, but I believe Sony tweaked / rebranded these products (both had Sony Screenblast versions at one point and there was evidently a Sony Screenblast version of Acid, also acquired from Sonic Foundry). As I understand it Magix took the Sony versions and tweaked / rebranded them. I thought Movie Maker was a Windows Product. 1999 SOS Article on Sonic Foundry's Vegas Pro. I don't really know the complete history; so maybe somewhere in there Sony also acquired software from Windows and merged it into their version of Vegas? In 2003 Sony called a version of their video editing software, "Screenblast Movie Studio." In my admittedly limited experience, "Screenblast" referred to the non-Pro versions of various products Sony acquired.

Did you see any additional wording like, "Please download and install the latest version / update?" If not, you could make note of the outdated build and mention the build number which doesn't have that wording.

Very well done (clear, focused, positive, etc.) set of explanations / demonstrations showcasing a whole lot of features Next offers.

Welcome back, I think. In 2020 you wrote: Now you jump onto a thread from 2021 with: It seems you came back to complain about something not covered in the post from 2020. Why?

As the OP stated: Also, please note that the OP hasn't been around since almost a year ago when the initial post was made. Please note, I voluntarily removed my posts because they addressed other high-contrast possibilities (i.e., non-100% Black and White solutions): I'd suggest if others are interested in requesting and/or discussing high-contrast themes, that is a a different topic.

I didn't assume anything of the sort. If you took the time to read what the OP wrote: when you read what I wrote: you might have realized that I was simply verifying what the OP stated. That being said, I think it's fair to say that if something has worked continuously in Cakewalk/SONAR and suddenly no longer works in Cakewalk Sonar, it might be of interest for the developers to know that PSYN II didn't make the transition into Sonar. I made no assumptions about the cause; I made no assumptions about possible remedies.

Since Cakewalk Sonar correctly picks up the presence of PSYN II, but fails to properly display the PSYN II's UI, it seems like a bug to me. If Cakewalk Sonar correctly displays the other legacy instruments, it seems to me it should also display PSYN IIs UI correctly.

Since Cakewalk Sonar correctly picks up the presence of PSYN II, but fails to properly display the PSYN II's UI, it seems like a bug to me. If Cakewalk Sonar correctly displays the other legacy instruments, it seems to me it should also display PSYN IIs UI correctly. UPDATE (2024-03-27): See Canopus' suggestion:

Glad you solved the issue. By the way, when I wrote this? and these? I was not asking, "Have you looked in this and these?" I was asking if this? and these? are the docs for your gear. Sorry if that wasn't clear. I looked through the first manual (this?) and didn't see anything that would help, so I looked for more manuals and wanted to know if I was looking at the correct manuals for your gear before reading through those, too.