Jump to content

jim137

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

2 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. jim137

    Pianoteq 7 released

    PianoTeq Pro and others BF 20% sale
  2. jim137

    Pianoteq 7 released

    Does anyone think the Pianoteq Pro Studio will offer anything off on Black Friday?
  3. For the past few years I have been buying sheet music, scanning it into the computer with SmartScoreX2 (now SmartScore64) correcting the scan and turning into a MIDI type 1 for cakewalk to use. If necessary, I have learned how to split the file into left and right versions using the Staff view. There are some songs that simply never made it to sheet music or a MIDI file. Surfing around recently, I saw someone convert an audio file to MIDI in Fruity Loops. I followed it and realized that Melodyne can convert audio to MIDI. I am currently in Melodyne Studio 5.02.2003, loaded the audio; pulled up melodyne region effects; set the pitch and quantize to 100%; and then bounced the track to MIDI in melodyne. The result was very close; The melody is there. The Bass line is a mess. I am musically rather ignorant and have developed various tricks to get by. I have a good ear and can hear when something is off. I took an online course this spring on Music Theory which filled in many of my gaps in knowledge. https://stackskills.com/p/music-theory-for-electronic-producers-the-complete-course My question is: Can anyone give me suggestions on correcting the produced MIDI which seems to have a lot of extra notes and is quite busy(?). It is in the key of D major and I assume that should help me determine which notes are correct. Any guidance would be appreciated. If I can figure out how to do this, I'll have quite a bit of work to do on Music that did not reach sheet or MIDI level!
  4. jim137

    UVI Vintage Vault 3

    After I got the update notice from UVI for $199 from Vintage Vault 2 to Vintage Vault 3; an hour later they sent me a code that let me upgrade to Vintage Vault 3 for $29.00 which I successfully did.
  5. Thanks again to everybody for your help. Label these two problems solved! I was flying fast for the rest of the day yesterday; not having to wait and dismiss strange dialog boxes. I resisted for so long to post my problem and look at how fast it was solved and the amount of input I gained.
  6. I didn't delete; just renamed it \xASIO. Thanks everybody for all the solutions and responses. I appreciate all the quick responses and suggestions. Both problems are solved.
  7. Scook work-around appears to be working for problem No. 2. I wish the preferences dialog worked. Suspend Audio.....
  8. The Registry information was useful I think. I went through the procedure of removing the Steinberg\ASIO folder suggested by Noel. I had to close down 5 programs and reboot and am testing it now. So far that solves the first problem. Strange that it appeared only after this new build. This other problem is still there and has been for some time; but I can live with it. I also get the audio Dropout teal dialog.
  9. Cubase 10.20 is on the machine. Cubase was on the machine before the install of 2019.7 and this dialog box never came up. I have searched the computer and there is no generic ASIO driver listed.
  10. I doubt this is the answer. Both Audition and Soundforge have been in place for months or years time. The appearance of the generic dialog box just appeared with 2019.07 the first one and now 2019.07 B79 These are two different problems.
  11. I have not installed a generic ASIO Driver. This is the RME Driver. In preferences when I poke the ASIO Panel the RME ASIO Dialog comes up. The RME is listed in the drivers area .
  12. A small dialog box flashes on the screen just since the recent update (2019.07 B79 and the first 2019.07) when I push the space bar to start playback. it never appeared before. I have had trouble capturing it; it comes and goes so quickly. I have to wait until it is done; then push the space bar again. I bounce around between SoundForge 13.0 B100 and Adobe Audition 2019 constantly get this box: Even though in preferences, I have 'Suspend Audio Engine When Cakewalk is Not in Focus' checked. I have tried it both checked and unchecked and perceive no difference. I am using a RME Multideck II with lastest drivers on Windows 10 1903. Any suggestions or advice had to correct this? Anyone else experiencing this? It is really is stopping the flow of working.
  13. Same methods work in Cubase 10.5. The key is that only one preset must be shown in the preset filter list. Too bad this does not work in Cakewalk/Sonar.
  14. ok. I now have a work around. One must be sure that in Studio One, that only one preset is listed in the presets window after a search otherwise it will jump to the top preset. The correct patch will play repeatedly. I bounced to audio and then imported back into Cakewalk. Whew! At least I can make it do what I want it too now.
  15. I too have Studio One R4. But it too exhibits the same jumping patch when played as the other DAWS. I set "Double Autoharp" as patch; hit play; patch jumps to Plain "Autoharp." I set "80s Disco Funk" as patch; hit play; patch humps to "1963SemiAcoutic Short."
×
×
  • Create New...