Last doubts before the inevitable
- This topic is empty.
-
Posts
-
Okay, I made a collection of doubts about the Reaper, I want to address some problems that are preventing me from completing the next customs that I am about to launch since last year and at that point I can not stand to suspend so many jobs and fill the queue new projects due to these impertinations.I will number again to simplify the understanding and possible answers.1. When I use FX from RBN Preview, be it on any instrument, I noticed that there is an alarming delay. Basically, when it seems that the song is in rhythm with the notes and image of the frets, it means that the notes are advanced. In this I waste time dragging everything forward, except MIDI, I finish the test and convert it to Magma, convert it to my console, edit the DTA and transfer it to my SD card until it works … the problem is not just this detail the lack of synchrony, but the vocals mode that only has the aid of a tone FX, but like the RBN Preview, it is not as accurate as it should be. My question here is, is this just for me? should i configure something in the options like calibration or sync?this is exactly where the music starts, see that the notes on both FX and graphical scrolling come later.2. regarding stage animations, such as cameras and lights. Is there a video about this topic? it seems that I’m not doing the right thing by editing this part, the result is visible at the time of gameplay. I noticed that if it’s autogenerated, the animation is 90% only for the vocalist since the custom itself has dryvox, but I don’t want to release it that way. And also, if possible, I would like an exact reference for each camera, many of them only have acronyms like D_Vox_Cam_PR or D_Bass_NP … I have no idea where the angle of this is.
Here is how it is currently done, but not yet finished3. about the keyboardist’s animation, before I had created a topic about it, but from what was indicated, nothing generated results, at least not in the right way as it should be expected. I even asked some members for help, both by direct message and on the custom page itself, no one answered me. So here I come back with the same question: how to give life to the keyboard player during the performance? before paying attention to the images below, know that i included [play] at the exact moment that Keys/PRO Keys starts, although it was only at PART KEYS (as I was suggested and was taught in that Farottone tutorial file). But the keyboardist just stands there on the stage, he doesn’t strum the keys, he looks like a statue. Now, observe how I followed the rules of animation for both the right hand and the left hand, respecting the minimum and maximum reach for both.Right Hand below
and… Left Hand below
these are just those doubts, I hope to gain some experience to generate future quality customs.1. Sound delays in DAWs are caused by your CPU. It’s very hard to get no delays.
The only thing you can try really is use the ASIO4ALL driver, just a fair warning though, this driver will completely take over your sound card when active, so if you’re using REAPER and you told it to use ASIO4ALL as audio driver, you will not be able to use the same sound card for any other software until REAPER is closed. Even with ASIO4ALL, you will get a delay, but it will be much smaller.
If that delay is causing you o have trouble to make a proper tempo map, the rule of thumb is using the audio’s waveform rather than your ears, or slowing down the song enough when there’s too much noise to see something of interest in the waveform.
2. IMO, the only way to know how much each camera cut shows at once is by speculation, or, if you have played and/or charted long enough to memorize at least several of them. The “coop” events are the easiest to discern, I’d say there’s no trouble as to how they are described. Now, the “directed” cuts require some experience.
3. Strange it doesn’t work. If you put animation events and charted animations, it should work correctly. Are both KEYS and PROKEYS charted (no blank track)? Have you checked if they’re not marked as “text event”?
1. Sound delays in DAWs are caused by your CPU. It’s very hard to get no delays.
The only thing you can try really is use the ASIO4ALL driver, just a fair warning though, this driver will completely take over your sound card when active, so if you’re using REAPER and you told it to use ASIO4ALL as audio driver, you will not be able to use the same sound card for any other software until REAPER is closed. Even with ASIO4ALL, you will get a delay, but it will be much smaller.
If that delay is causing you o have trouble to make a proper tempo map, the rule of thumb is using the audio’s waveform rather than your ears, or slowing down the song enough when there’s too much noise to see something of interest in the waveform.
I understand, I will start the tests using the audio’s waveform, I hope to get the most accurate synchrony.
3. Strange it doesn’t work. If you put animation events and charted animations, it should work correctly. Are both KEYS and PROKEYS charted (no blank track)? Have you checked if they’re not marked as “text event”?
I still haven’t finished creating the animations for this custom in question, but is it relevant to how it works? both PARTs are 100% edited and that last question opened hypotheses, in the PART KEYS_ANIM_RH and PART KEYS_ANIM_LH tracks, in that part where text events are placed, for both hands right at the beginning in 1.1.00, they are marked as Track Name as well as the instruments , should I switch to Text Events?
…in the PART KEYS_ANIM_RH and PART KEYS_ANIM_LH tracks, in that part where text events are placed, for both hands right at the beginning in 1.1.00, they are marked as Track Name as well as the instruments , should I switch to Text Events?
By “as well as the instruments” I take it you mean the Name events in other tracks. The Name at the beginning of the tracks is necessary for the song to function. All other events must be marked “text event”, unless you’re charting lyrics. It’s implicit.
It happens sometimes, though, that one forgets to change the event type, and ends up with nuisances like that.
2. IMO, the only way to know how much each camera cut shows at once is by speculation, or, if you have played and/or charted long enough to memorize at least several of them. The “coop” events are the easiest to discern, I’d say there’s no trouble as to how they are described. Now, the “directed” cuts require some experience.
I just took a look at this detail, do I need to add the coop too? take a look at the print and you will see that I just repeated the command as shown in the left corner of the screen.
- You must be logged in to reply to this topic.