Jack11223344

Monitoring Options

If you are using ASIO hardware then you can choose the "Monitor channel"  which will allow you to hear what you are recording through your headphones. However, a better approach to monitoring your recording is to use your hardware directly. Most external soundcards will allow you to directly monitor your input via a headphone output. This option will provide you with the best performance and zero latency."

To use Monitor channel in Mixpad, you will need to:

1 Use an ASIO device.

2 Setup the Monitor channels as shown in the image.

3 Enable the headphone button as shown in the image.

Than you will hear the same sound from the Recording device.

Hi All:

In recently released version, we have implemented core audio recorder and player. It has a much better result in regarding to the latency. Please try it.

Try the project bookmark from right click on the time line at the bottom.

Hi Medic:

If the original music is in midi format, you can use a free piano vst to play it.

HI Paul:

Are you able to attach your mixpad project file here?

I will look into this issue.

Thanks

Jack

Hi Jofra:

Todo that, you just need to add all songs into one track.

Hi, I have confirmed this bug. It will be fixed in the next release.

Thanks for reporting.

Regards

Jack

Yes, I can see the problem, will look into it.

Cheers

Jack

HI Sean:

This is related to the original source. 

You are setting the "target bitrate for Average BitRate (ABR) rate control." but the end result is always less than the target. When the source bitrate is low, you will get lower bitrate as well.

Yes, when preview, videopad is always uses 30 fps and there it no options to change it. But you can always seek to any position you want. I can see the problem and will raise this issue for any possible solution.

Hi borate:

Yes, i can confirm that videopad is not able to open this video file. It has a codec we don't fully support yet.

I will add this as a todo item.

Regards

Jack

Hi Softball:

I can see that you CPU usage is low which seems abnormal.  64G Memory is also good. I can't reproduce the issue here. 

Could it be the disk problem? 

Thanks

Jack

HI, the reason that the first clip and NLE reverse are fast is most likely because of the lossless export, no re-encoding needed. If you try to use a different resolution other that the original, you can see the difference.

Yes, the reverse algorithm can be optimized but not an urgent job. We will consider this in the future release.

Hi equalthree, which version were you using?

Please try to update to the latest version from our website and try again.

Thanks everybody for reporting, this bug will be fixed in the coming release.

Cheers

Jack

Thanks everybody, this bug will be fixed in the next release.

6 minutes ago, Jo-Fx said:

That was for a visual effect showing accelerated time you see...

Ok, I see.  We might need to improve this.  A work around can be export that part to a video firstly and replace the clip with the video. This exporting will be faster.

Thank for your help, this bug will be fixed in the next release. 

BTW, there is a clip in track 3, at 31 seconds with speed change 9000, seems strange.  That causes the exporting slow.

Thank you all for your help,  we have identify this issue and will be fixed in the next release.

Cheers

Jack

On 3/31/2020 at 6:08 PM, Wendy Thacker said:

Thanks for the instructions.

I've followed all of this and even for the downloaded mp3 and the mp4 there is no sound. For some reason the only version that works is the 7.something. Any of the 8.versions have no sound capacity.

I'll have to wait for the key

 

Hi Wendy, thanks for your help. We are planing a new release today to fix this problem. In fact, the exported video can be play with sound using VLC player. Other player can't.  But anyway, the next released version won't have this issue.

We will make some improvement about this in the next release.

Hi GodGabriel2000: 

If you can explain in more detail about the (1, 2, End) -  (2, 2, End) issue, we can take a look into it.

Also, when exporting, try fix frame rate, increase fps, such as 60, will this fix this issue?

Regards

Jack

Thanks for reporting,  with your help, I am able to identify this bug and will be fixed in the next release.

Hi minotto :

I  can't see the original project, if you can restore it, I will look into it.

Cheers

Jack

Hi pixellphoto:  We are able to identify this bug, this is caused by too many  video tracks, in the project > 60 and thus cause a memory issue.

A temporary fix is to avoid using more tracks. In you project, you can merge to fewer tracks say < 10.

We will fix this bug asap, if not the next release, the one after next release.

Thanks borate and pixellphoto for reporting.