AMDMIGraphX icon indicating copy to clipboard operation
AMDMIGraphX copied to clipboard

migraphx bug [vapoursynth]

Open ryou128hr opened this issue 9 months ago • 1 comments

Image

Arch linux

CPU 5700X3d

MPV player Vapoursynth

RX 7800XT

GPU color noise i, stutter without framedrop

gpu usage 60%

stutter with num_streams=>2

Code:

onnx:

Comapct 2x ( 960x540 reize 1920x1080)


/opt/rocm/bin/migraphx-driver compile --onnx 2x_Compact_fp32_op17.onnx --gpu --optimize --binary --output Compact.mxr --input-dim @input 1 3 540 960 --fp16

VS:

import vapoursynth as vs
core = vs.core
core.std.LoadPlugin( "/usr/local/lib/libvsmigx.so")
clip= video_in
clip = video_in
clip = vs.core.resize.Bicubic(clip,format=vs.RGBS, matrix_in_s=709)
clip = core.migx.Model(clip, program_path="/home/ryou/Videos/Compact.mxr",num_streams=1,tilesize=[960,540],overlap=[0, 0])
clip = vs.core.resize.Bicubic(clip,format=vs.YUV420P8, matrix_s=709)
clip.set_output()


What is the cause?

ryou128hr avatar Apr 02 '25 19:04 ryou128hr

Hi @ryou128hr. Internal ticket has been created to assist with your issue. Thanks!

ppanchad-amd avatar Apr 02 '25 20:04 ppanchad-amd

Hi @ryou128hr To help us reproduce and debug this properly, could you please share the following?

  1. The 2x_Compact_fp32_op17.onnx model used during compilation.
  2. A short sample video clip (or any test pattern) that reproduces the stutter issue.
  3. Exact ROCm and MIGraphX versions you're using (output of rocminfo, migraphx-driver --version, and rocm-smi would be helpful). My initial speculation is- Using num_streams=2 might be invoking an async multi-queue path in MIGraphX → ROCm stack, which may have synchronization issues in the VapourSynth integration layer or driver layer.

Noise/stutter without frame drop suggests timing or scheduling inconsistencies — possibly caused by tiling overlap issues (tilesize=[960,540], overlap=[0,0]) on the 7800XT architecture.

adityas-amd avatar May 14 '25 18:05 adityas-amd

Hi @ryou128hr, just following up.

Since we haven't heard back, I'll go ahead and close this issue for now. If you're still encountering the problem or have more details to share, please feel free to reopen the issue or leave a comment — we’ll be happy to take another look.

Thanks!

adityas-amd avatar Jun 11 '25 12:06 adityas-amd